Supported scenario to restore a backup of data from the original release version of SharePoint Portal Server 2003 to SharePoint Portal Server 2003 Service Pack 1 (891983)

MORE INFORMATION

The SharePoint Portal Server Backup and Restore tool is designed to back up and restore portal site data on computers that are running the same service pack level of SharePoint Portal Server 2003. For example, you use the SharePoint Portal Server Backup and Restore tool or the SQL Server backup tools in SQL Server Enterprise Manager to back up data on a computer that is running the original release version of SharePoint Portal Server 2003. You cannot use the SharePoint Portal Server Backup and Restore tool to restore the backup to a computer that is running SharePoint Portal Server 2003 SP1. You can only restore the backup to a computer that is running the original release version of SharePoint Portal Server 2003.

The XML manifest file that is created during the backup operation is stamped with the version number of SharePoint Portal Server 2003. The version number prevents the restore operation if you try to use the SharePoint Portal Server Backup and Restore tool on a computer that is running SharePoint Portal Server 2003 SP1 to restore a backup of portal site data from a computer that is running the original release version of SharePoint Portal Server 2003.

In a disaster recovery situation, the following scenario is supported. If you use the SharePoint Portal Server 2003 Backup and Restore tool or the SQL Server backup tools in SQL Server Enterprise Manager to back up data on a computer that is running the original release version of SharePoint Portal Server 2003, you can use the SQL Server backup tools in SQL Server Enterprise Manager to restore the backup files to a computer that is running SharePoint Portal Server 2003 SP1. The following is an example of a scenario that has been tested and that is supported:

1. You use the SharePoint Portal Server 2003 Backup and Restore tool or the SQL Server backup tools in SQL Server Enterprise Manager to back up the following databases on a computer that is running the original release version of SharePoint Portal Server 2003:
   • The SiteName_SITE database
   • The SiteName_SERV database
   • The SiteName_PROF database
   • The database that is used for the Single Sign-On feature, if the Single Sign-On feature is configured.
2. You upgrade the installation of SharePoint Portal Server 2003 to SharePoint Portal Server 2003 SP1. To do this, you install Microsoft Windows SharePoint Services Service Pack 1 (SP1) and SharePoint Portal Server 2003 SP1.
3. You delete the portal sites, and you delete the databases that are used by SharePoint Portal Server 2003, except for the configuration database.
   
   Note The databases that are used by SharePoint Portal Server 2003 include the following:
   • The content database, SiteName_SITE database.
   • The services database, SiteName_SERV database.
   • The user profile database, SiteName_PROF database.
   • The configuration database. By default, the configuration database is named SPS_Config_db.
4. You use the SQL Server backup tools in SQL Server Enterprise Manager to restore all the databases except for the configuration database. The restored databases use the same names as the original databases.
5. You restore the portal site to the same server by using the Create Portal Site for ServerName page.

Note After you perform this procedure, the stored procedures are not updated to the SP1 version of these procedures. If you plan to use this environment for work instead of using it to just retrieve data we recommend that you use the stsadm command to perform a forceupgrade operation to make sure that all the stored procedures are up tp date. To perform a forceupgrade operation:

1. Log on to SPS using an account that has permissions to the backend databases. We recommend that you use the SharePoint service account.
2. Go to the following location on every server that is running SharePointPortal Services to find the stsadm command:

   C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN

3. Run the following command:

   stsadm -o upgrade -forceupgrade

4. Wait while Setup upgrades the SharePoint sites. This may take a few minutes to a few hours, depending on the size of your sites.

You will see the following message when the forceupgrade operation is complete:Operation completed successfully.

Additionally, the SQL Server backup tools in SQL Server Enterprise Manager can only back up and restore SQL Server databases. Therefore, some components are not restored. Components that are not restored include the following:

• Index and catalog files
• Content sources
• Web Storage System-based backward-compatible document libraries

To restore content source data to the portal site, you must first re-create the content source data, and then perform a full update of the content index. To restore Web Storage System-based backward-compatible document libraries, restore a backup from the original release version of SharePoint Portal Server 2003, and then manually migrate the document library to the SharePoint Portal Server 2003 SP1 server farm. Alternatively, you can perform a backup immediately after you upgrade to SharePoint Portal Server 2003 SP1.

When you plan an upgrade to SharePoint Portal Server 2003 SP1, you may want to use the following method. The following method uses the SharePoint Portal Server Backup and Restore tool to back up data after you upgrade to SharePoint Portal Server 2003 SP1. You can then use the backup to restore databases and other data that cannot be restored by using the SQL Server backup tools in SQL Server Enterprise Manager.

1. Back up portal site data on the computer that is running the original release version of SharePoint Portal Server 2003.
2. Upgrade the original release version of SharePoint Portal Server 2003 to SharePoint Portal Server 2003 SP1.
3. Use the SharePoint Portal Server Backup and Restore tool to back up portal site data on the computer that is running SharePoint Portal Server 2003 SP1.
4. Use the backup that you performed in step 3 for restore operations.