21.2 Windows Migration with an MS SQL Database

21.2.1 Preparing the Target Windows Server

On the target server:

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

    IMPORTANT:Select the same encryption algorithm for the Vibe database. If the database encryption algorithms do not match between the source and target systems, you cannot log in to the new Vibe 3 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. This is because 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\apache-tomcat\webapps\
                                    ssf\WEB-INF\classes\config

  6. (Conditional) If you are migrating a Teaming 2.1 system to a Vibe 3 system, you need to manually change the encryption algorithm in the ssf-ext.properties file:

    1. On the Vibe server that you are migrating from, change to the directory where the ssf-ext.properties file is located.

      The default location of this file varies by platform:

      Linux:

      		 
      /opt/novell/teaming/apache-tomcat/webapps/
                                    ssf/WEB-INF/classes/config

      Windows:

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

    2. Open the ssf-ext.properties file in a text editor, then locate and copy the appropriate property setting for your encryption algorithm. The encryption algorithm for your Vibe server is represented by one of the following lines:

      user.password.encryption.algorithm=SHA

      user.password.encryption.algorithm=SHA-256

      user.password.encryption.algorithm=MD5

    3. On the Vibe server that you are migrating to, change to the directory where the ssf-ext.properties file is located.

      The default location of this file varies by platform:

      Linux:

      		 
      /opt/novell/teaming/apache-tomcat/webapps/
                                    ssf/WEB-INF/classes/config

      Windows:

      		 
      c:\novell\teaming

    4. Open the ssf-ext.properties file in a text editor, then paste the line that you copied in Step 6.b.

    5. Save and close the ssf-ext.properties file.

  7. Continue with Section 21.2.2, Preparing the Source Windows Server.

21.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 21.2.3, Transferring Data from the Source Server to the Target Server.

21.2.3 Transferring Data from the Source Server to the Target Server

On the source server:

  1. Map a drive from the destination 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

    In 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. Continue with Section 21.2.4, Importing the Database to the Target Server.

21.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 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 system.

  6. Continue with Section 21.2.5, Updating the Vibe Database on the Target Server.

21.2.5 Updating the Vibe Database on the Target Server

This section applies only when migrating a Teaming 2.1 server to a Vibe 3 server.

On the target server:

  1. Unzip the teaming-3.0.n-sql.zip file, change to the resulting update-2.1.0-3.0.n directory, then run the update script to update the database from Teaming 2.1 to Vibe 3:

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

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

  2. Continue with Section 21.2.6, Finalizing Your New Vibe 3 Site.

21.2.6 Finalizing Your New Vibe 3 Site

  1. Start Vibe 3, as described in Section 4.1.6, Starting Vibe on Linux.

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

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