On the target server:

1. Install the Teaming 2.1 software, as described in Section II, Basic Installation.

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

2. Start Teaming on the target server.

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

4. Stop Teaming on the target server.

On the source server:

1. Stop Teaming.

2. Back up your existing Teaming database:

   1. In Microsoft SQL Server Management Studio, browse to and right-click the existing Teaming 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 Teaming system.

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. (Conditional) If you are migrating data from Teaming 1.0:

   1. Copy your existing Teaming file repository to the target server

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

      IMPORTANT:Do not copy the liferay directory.

   2. Copy the database backup of your existing Teaming database (sitescape.bak file) from the source server to the same location on the target server.

      You created this file Step 2 in Section 23.2.2, Preparing the Source Windows Server.

   3. Copy your existing Teaming Lucene index to the target server:

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

      In Teaming 2.1, the lucene directory now contains the kablink and liferay.com directories.

   4. Delete the empty kablink directory.

   5. Rename the liferay.com directory where your existing Teaming database resides to kablink.

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

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

   In Teaming 2.1, the extensions directory now contains kablink and liferay.com directories.

4. Delete the empty kablink directory.

5. Rename the liferay.com directory where your existing software extensions reside to kablink.

6. (Conditional) If you are migrating data from Teaming 2.0:

   1. 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
      

   2. Copy your existing Teaming file repository from c:\novell\teaming on the source server to the same location on the target server.

   3. Copy your existing Teaming database index from c:\novell\teaming\lucene on the source server to the same location on the target server.

   4. Copy your existing software extensions from c:\novell\teaming\extensions on the source server to the same location on the target server.

On the target server:

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

2. To import the data from your source Teaming 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 Teaming database is imported into the database for your new Teaming 2.1 system.

On the target server:

1. (Conditional) If your are updating from Teaming 1.0 to 2.1, unzip the update-1.0.0-2.0.n.zip file, change to the resulting update-1.0.0-2.0.n directory, then run the update script to update the Teaming database from Teaming 1.0 to 2.0:

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

   For more complete database update instructions, refer to Section 20.4.1, Manual Teaming Database Update.

2. To update from Teaming 2.0 to 2.1, unzip the update-2.0.0-2.1.n.zip file, change to the resulting update-2.0.0-2.1.n directory, then run the update script to update the Teaming database from Teaming 2.0 to 2.1:

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

   For more complete database update instructions, refer to Section 19.3.1, Manual Teaming Database Update.

On the target server:

1. Change to the following directory:

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

2. View the following files to ensure that the current zone name is set to kablink.

   zone.cfg.xml
   zone-ext.cfg.xml
   

3. Use the following commands to update the Teaming database with the new default zone name:

   update SS_ZoneInfo set zoneName='kablink' where zoneName='liferay.com'; 
   update SS_Forums set name='kablink' where name='liferay.com';
   

4. Find and rename any liferay.com subdirectories to kablink.

   You might or might not find liferay.com subdirectories in the following locations, so you should check them all:

   c:\Novell\Teaming\filerepository
   c:\Novell\Teaming\lucene
   c:\Novell\Teaming\extensions
   c:\Novell\Teaming\archivestore
   c:\Novell\Teaming\cachefilestore
   

1. Start Teaming 2.1, as described in Section 4.1.5, Starting Teaming on Linux.

2. Reindex the Teaming site, as described in Rebuilding the Lucene Index in Site Maintenance in the Kablink Teaming 2.1 Administration Guide.

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