25.2 Windows Migration with an MS SQL Database

On the target server:

1. Install the Vibe 3.4 software, as described in Section II, Basic Installation.

   IMPORTANT:Select the same encryption algorithm for the Vibe 3.4 database that you selected for the source Vibe server. If the database encryption algorithms do not match between the source and target systems, you cannot log in to the new Vibe 3.4 site.

2. Start Vibe on the target server.

3. Verify that the new Vibe site is working as expected.

4. Stop Vibe on the target server.

5. Rename the teaming directory to teaming_backup. In a future step you will copy the teaming directory from the source server to the target server.

   The location of the teaming directory varies by platform:

   Linux:	/var/opt/novell/teaming
   Windows:	c:\Program Files\Novell\Teaming

6. Continue with Section 25.2.2, Preparing the Source Windows Server.

On the source server:

1. Stop Vibe.

2. Back up your existing database:

   1. In Microsoft SQL Server Management Studio, browse to and right-click the existing database (named sitescape), then click Tasks > Back Up.

   2. For Backup type, select Full.

   3. Set other backup options as desired, then click OK.

      This creates a file named sitescape.bak in the following directory:

      c:\Program Files\Microsoft SQL Server\MSSQL\Backup
      

3. Make sure that you have a recent backup of your entire system.

4. Continue with Section 25.2.3, Transferring Data from the Source Server to the Target Server.

On the source server:

1. Map a drive from the target server to the source server so that data can be copied from one server to the other.

2. Copy your existing software extensions to the target server:

   From:	c:\home\icecoredata\extensions
   To:	c:\novell\teaming\extensions

   Beginning with Vibe 3, the extensions directory now contains kablink and liferay.com directories.

3. Delete the empty kablink directory.

4. Delete or rename the following directories to make room for the corresponding directories that you are copying from the source server:

   c:\novell\teaming
   c:\novell\teaming\lucene
   c:\novell\teaming\extensions
   

5. Copy the entire data area from c:\novell\teaming on the source server to the same location on the target server.

6. (Conditional) If you are using secure LDAP (LDAPS), you need to copy the cacerts file to the same location on the target server.

7. Continue with Section 25.2.4, Importing the Database to the Target Server.

On the target server:

1. In Microsoft SQL Server Management Studio, browse to and right-click the existing Vibe database (named sitescape) that was created when you installed the Vibe 3.4 software, then click Delete.

2. To import the data from your source database, browse to and right-click Databases, then click Tasks > Restore.

3. In the To database field, specify sitescape.

4. In the From device field, browse to and select the sitescape.bak file that you transferred to the target server.

5. Set other restore options as desired, then click OK.

   This creates the sitescape database in the following directory on the target server:

   c:\Program Files\Microsoft SQL Server\MSSQL
   

   Backed-up data from the source database is imported into the database for your new Vibe 3.4 system.

1. Unzip the teaming-3.3.n-sql.zip file, change to the resulting update-3.2.0-3.3.n directory, then run the update script to update the database from Vibe 3.2 to Vibe 3.3:

   osql -Uusername -Ppassword -i update-sqlserver.sql
   

   If you are updating from a version prior to 3.2, you need to run the appropriate update scripts in addition to the update script found in the update-3.2.0-3.3.n directory.

   For more complete database update instructions, refer to Section 21.3.2, Manual Vibe Database Update.

2. Continue with Section 25.2.7, Finalizing Your New Vibe 3.4 Site.

1. On the source server, navigate to the zone-ext.cfg.xml file and view the default zone name.

   The zone-ext.cfg.xml file is located in the following directory:

   C:\Program Files\Novell\Teaming\apache-tomcat\webapps\ssf\WEB-INF\classes\config

2. On the target server, navigate to the zone-ext.cfg.xml file, and view the default zone name.

3. (Conditional) If the name on the target server is different than the name on the source server, change the name on the target server so that it matches the name of the source server.

   A Vibe site that originated as Teaming 1.0 has the default zone name of liferay.com. In this case, you need to change the default zone name on the target server to liferay.com.

4. Save and close the zone-ext.cfg.xml file on the target server.

1. Start Vibe 3.4, as described in Section 4.1.7, Starting Vibe on Linux.

2. Reindex the Vibe site, as described in Rebuilding the Lucene Index in Site Maintenance in the Novell Vibe 3.4 Administration Guide.

   Your Vibe site should now function just as it did on the original source server.