Back up and restore SSPs (Office SharePoint Server 2007)

SharePoint 2007

Updated: July 24, 2008

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.


Topic Last Modified: 2008-08-25

Backing up or restoring a Shared Services Provider (SSP) consists of backing up or restoring the following components:

  • SSP Web application

  • SSP database

  • One or more SSP content databases

  • User profile data

  • Session state data

  • Search data, including the search database and index

You can back up or restore the entire SSP. Alternatively, if an SSP has more than one content database, you can back up or restore the content databases separately.

You should back up the SSP on a regular schedule to ensure that you can restore the content and settings in case of a server failure. Typically, you would perform a full backup once a week, with differential backups every day. You might also perform a full backup immediately before performing any substantial changes to the SSP, and then another backup after the changes are made. When you back up an SSP for the first time, you must perform a full backup.

You can perform the procedures for this task by using the SharePoint Central Administration Web site or by using the Stsadm command-line tool.

Backup and restore operations are performed as Timer jobs and are performed in the background. These operations will wait until any other operations that are currently being performed on the databases are finished before they begin. Therefore, if a full crawl on one of the content databases is currently running, the start of the backup or restore operation might be delayed.

If the farm has more than one SSP, each SSP must be backed up individually.

When you back up the SSP, all the databases are also backed up, but SSP content databases can be backed up and restored separately from the SSP. If the SSP has more than one content database and database changes are not evenly distributed, backing up the more active databases separately can save time and consume fewer resources than backing up the entire SSP. When backing up SSP content databases, each SSP content database must be backed up separately. For more information about backing up and restoring databases, see Back up databases (Office SharePoint Server).

For more information about SSPs, see Plan Shared Services Providers.

The following are required to perform the procedures for this task:

  • Membership in the Farm Administrators SharePoint group is the minimum required to complete these procedures using the SharePoint Central Administration Web site.

  • To run the Stsadm command-line tool, you must be a member of the Administrators group on the local computer.

  • You must be logged on to the server that runs the SharePoint Central Administration Web site.

  • You must have a shared folder that you will use to store the backup files. For more information about preparing for backup, see Prepare to back up and restore a farm (Office SharePoint Server 2007).

  • If the IT environment requires that the database administrator (DBA) must back up or restore the databases associated with the SSP, you must coordinate the backup and restore operations with the DBA. The account used to back up the databases must be a member of the SQL Server db_backupoperator fixed database role. The account used to restore the databases must be a member of the SQL Server dbcreator fixed server role.

  • You do not need to restart the computer to complete these tasks.

You can perform the following procedures to back up and restore an SSP: