Restoring a Shared Services Provider to an alternate server or farm
Verify that the following requirements are met:
|
• |
SSP must not exist: If an SSP with the same title as the SSP being restored to the alternate server or farm exists, the restore job fails. Rename or delete the existing SSP in the alternate server or farm before submitting the restore job. |
|
• |
SSP Administration Site Host Web Application created: Re-create the SSP Administration site host web application in the alternate server or farm before you complete a restore, so that the timer jobs associated with the web application are created. (On the alternate farm, perform the steps outlined in Re-creating the web applications.) For example, if the NetVault Backup log for the backup job included the following tree for SharePoint 2007, the following SSP web applications must be created: Web Application Name: SharePoint - 47807; Database Name: SharedServicesContent |
|
• |
Shared Services Provider Administration Site Host Content Database deleted: To ensure that the name of the SSP Administration Site Host content databases for the new server or farm matches the name of the content databases for the source server or farm, ensure that the content database created is deleted with the SQL Server Management Studio. |
|
1 |
On the server where the SQL Server Instance resides, open SQL Server Management Studio. |
|
2 |
In the Object Explorer, navigate to the Databases node, right-click the database for the SSP Administration Site Host web application, and select Delete. |
|
3 |
|
• |
Restore Full Backup: At a minimum, restoring the SSP requires the restore of a Full Backup. |
|
1 |
|
2 |
Select the Farm node. |
|
3 |
|
• |
|
• |
Select Restore Files from Backup Only. |
|
4 |
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default. |
|
5 |
In the Target Client list, select the server where the plug-in is installed in the alternate server or farm. |
|
6 |
|
• |
Restore Full Backup to alternate server or farm: On the server where the plug-in is installed in the alternate server or farm, run the following STSADM command to restore the Full Backup to a new configuration. |
|
• |
<directoryForTemporaryFiles>: Enter the UNC share path that is specified in the Configure dialog box. |
|
• |
<SQLserverUserName>: Specify a SQL Server user with the sysadmin server role in the DOMAIN\username format. |
|
• |
<password>: Enter the password associated with the user specified in the preceding field. |
|
• |
<SharedServiceProviderName>: Enter the name of the SSP as it existed on the source server or farm. |
|
• |
Restore Differential Backup (optional): If your backup strategy includes Differential Backups, restore the last available Differential Backup. |
|
1 |
|
2 |
Select the Farm node. |
|
3 |
|
• |
|
• |
Select Restore Files from Backup Only. |
|
4 |
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default. |
|
5 |
In the Target Client list, select the server where the plug-in is installed in the alternate farm. |
|
6 |
|
• |
Restore Differential Backup to alternate server or farm: On the server where the plug-in is installed in the alternate server or farm, run the following STSADM command to restore the Full Backup to a new configuration. |
|
• |
<directoryForTemporaryFiles>: Enter the UNC share path that is specified in the Configure dialog box. |
|
• |
<SQLserverUserName>: Specify a SQL Server user with the sysadmin server role in the DOMAIN\username format. |
|
• |
<password>: Enter the password associated with the user specified in the preceding field. |
|
• |
<SharedServiceProviderName>: Enter the name of the SSP as it existed on the source server or farm. |
|
Enter the new URL with the new web server host name and the original port. | ||
|
To accept the <default>, press Enter. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for a nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the source server or farm. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the source server or farm. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the source server or farm. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the source server or farm. |
Also, several Shared Services Provider settings reference host names that are not updated during the restore and must be modified to reference the alternate server or farm.
|
• |
Add Shared Services Provider service credentials: Ensure that the SSP service credentials are added to the alternate server or farm after the restore. For more information, see Adding SSP Credentials to the Alternate Server or Farm. |
|
• |
Validate Personalized Service permissions: Ensure that the Shared Services Rights reference the local administrator on the alternate server or the domain administrator on the alternate farm. For more information, see Verifying that the Shared Services rights reference the correct administrator. |
|
• |
Validate Business Data Catalog permissions: Ensure that the Business Catalog Permissions reference the local administrator on the alternate server or the domain administrator on the alternate farm. For more information, see Verifying that the Business Catalog Permissions reference the correct administrator. |
|
• |
Validate Search Authoritative web page settings: Ensure that the Authoritative Pages in the Search Setting references the alternate server or farm. For more information, see Validating the Authoritative Pages for Search Settings. |
|
• |
Validate Trusted File location: Ensure that the Trusted File location in the Excel Services Trusted File Locations references the alternate server. For more information, see Validating the Trusted File location. |
Performing a disaster recovery of a Single Server deployment to an alternate server
Verify that the following requirements are met:
|
• |
SharePoint Server installed: Install the same version and edition of the SharePoint software on the system as it existed on the damaged server. This step includes installing and configuring IIS so that your computer acts as a web server, installing the Microsoft.NET Framework version 3.0, and enabling ASP.NET 2.0. |
|
• |
Service Packs installed: Install the same Service Packs for Windows Server and SharePoint that were previously installed on the damaged server. A minimum of SP1 is required for WSS. |
|
• |
Delete Shared Services in the new deployment: Delete the default SSP, SharedServices1, in the newly installed deployment. For more information, see Deleting Shared Services in a new deployment. |
|
• |
Web applications created: Re-create all web applications for your farm before you complete a restore, so that the timer jobs associated with each web application are created. For more information, see Re-creating the web applications. |
|
• |
Content databases deleted: To ensure that the names of content databases for the new farm match the names of the content databases for the damaged farm, ensure that all content databases except for the Configuration Database and Central Administration website are deleted; for more information, see Deleting content databases. Repeat the steps outlined in Deleting content databases for each database except Configuration Database and Central Administration. |
|
IMPORTANT: The Configuration Database and Central Administration databases are not recovered. Deleting these databases causes you to start the entire Disaster Recovery process over because they must be created in place by the SharePoint Products and Technologies Configuration Wizard. |
|
• |
Ensure that the SQL Server Express Data directory exists: If a directory other than the default directory for the SQL Server Express Data directory was used on the damaged server, ensure that this directory structure exists on the newly installed deployment. |
|
IMPORTANT: If the SQL Server Express Data directory does not exist on the newly installed deployment, the restore job fails with errors referencing: Directory lookup for the file “<Directory\FileName>” failed with the operating system error 3. (The system cannot find the path specified).
Re-create the directory structure referenced in the error message and submit the restore job again. |
|
• |
NetVault Backup software and the Plug‑in for SharePoint installed: The same version of NetVault Backup and the plug-in must be installed and configured as they originally existed on the damaged server. |
|
• |
Full and optional Differential Backups available: Ensure that you have the latest Full Backup and Differential Backup, if applicable, available. |
|
• |
Plug-in for FileSystem backups of additional items available: Verify that you have backups of the following items available as detailed in Extra items to protect using NetVault Backup and the Plug-in for FileSystem: |
For more information, see: http://technet.microsoft.com/en-us/library/cc262370.aspx
|
• |
Restore Full Backup: At a minimum, recovery requires the restore of a Full Backup. |
|
1 |
|
2 |
Select the Farm node. |
|
3 |
|
• |
|
• |
Select Restore Files from Backup Only. |
|
4 |
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default. |
|
5 |
In the Target Client list, select the server where the plug-in is installed in the alternate farm. |
|
6 |
|
• |
Restore Differential Backup (optional): If your backup strategy includes Differential Backups, restore the last available Differential Backup. |
|
1 |
|
2 |
Select the Farm node. |
|
3 |
|
• |
|
• |
Select Restore Files from Backup Only. |
|
4 |
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default. |
|
5 |
In the Target Client list, select the server where the plug-in is installed in the alternate farm. |
|
6 |
|
• |
Restore Full and Differential Backups to the alternate farm: On the server where the plug-in is installed in the alternate farm, run the following STSADM command to restore the Full Backup to a new configuration. |
|
• |
<directoryForTemporaryFiles>: Enter the UNC share path that is specified in the Configure dialog box. |
|
• |
<SQLserverUserName>: Specify a SQL Server user with the sysadmin server role in the DOMAIN\username format. |
|
• |
<password>: Enter the password associated with the user specified in the preceding field. |
|
Enter the new URL with the new web server host name and the original port. | ||
|
To accept the <default>, press Enter. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for a nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the damaged farm. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the damaged farm. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the damaged farm. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the damaged farm. |
Also, several Shared Services Provider settings reference host names that are not updated during the restore and must be modified to reference the alternate server.
|
• |
Add Shared Services Provider service credentials: Ensure that the SSP service credentials are added to the alternate server or farm after the restore. For more information, see Adding SSP Credentials to the Alternate Server or Farm. |
|
• |
Validate Personalized Service permissions: Ensure that the Shared Services Rights reference the local administrator on the alternate server or the domain administrator on the alternate farm. For more information, see Verifying that the Shared Services rights reference the correct administrator. |
|
• |
Validate Business Data Catalog permissions: Ensure that the Business Catalog Permissions reference the local administrator on the alternate server or the domain administrator on the alternate farm. For more information, see Verifying that the Business Catalog Permissions reference the correct administrator. |
|
• |
Validate Search Authoritative web page settings: Ensure that the Authoritative Pages in the Search Setting references the alternate server or farm. For more information, see Validating the Authoritative Pages for Search Settings. |
|
• |
Validate Trusted File location: Ensure that the Trusted File location in the Excel Services Trusted File Locations references the alternate server. For more information, see Validating the Trusted File location. |
|
• |
Redeploy solutions: If you have a solution package that you want to redeploy, use the STSADM deploysolution option. For more information, see Redeploying solutions. |
|
• |
Restore unpackaged customizations and alternate access mappings: Use the Plug-in for FileSystem to restore unpackaged customizations and mappings as detailed in Alternate access mapping and Customizations. |
|
• |
Re-create alternate access mappings (optional): Use the Alternate Access Mapping text file to re-create mappings. For more information, see Re-creating Alternate Access Mappings (optional). |
|
• |
Restart timer jobs: Some timer jobs are not started when you restore the web-application backup. For more information, see Restarting timer jobs. |
|
• |
Reactivate features: If your solution contains features that must be enabled, enable the features at the appropriate level — web application, site collection, or website. For more information, see Reactivating features. |
|
• |
Restart IIS: To ensure that IIS has the most current configuration, restart IIS. For more information, see Restarting IIS. |
Performing a disaster recovery of a Small Farm or Scaled-Out Farm to an alternate farm
Verify that the following requirements are met:
|
• |
SharePoint Server is Installed: Install the same version of the SharePoint software on the systems that make up the alternate farm as it existed on the damaged farm. This step includes installing and configuring the following software on each of the servers in the farm. |
|
• |
|
• |
Service Packs installed: Install the same Service Packs for Windows Server and SharePoint that were previously installed on the damaged server. A minimum of SP1 is required for WSS. |
|
• |
SharePoint Central Administration Web Site created: The SharePoint Central Administration Web Site is installed by default on the first server on which you install SharePoint, such as the application server. For more information, see Creating the SharePoint Central Administration Web Site. |
|
• |
SharePoint Search configured: On the application server, start the SharePoint Search service. For more information, see Configuring the SharePoint Search service and Configuring the SharePoint Search service. For more information about the service names, see SharePoint 2007, 2010, 2013, and 2016 terminology. |
|
• |
Web applications created: Re-create all web applications for your farm before you complete a restore, so that the timer jobs associated with each web application are created. For more information, see Re-creating the web applications. |
|
• |
Content databases deleted: To ensure that the names of content databases for the new farm match the names of the content databases for the damaged farm, ensure that all content databases except for the Configuration Database and Central Administration website are deleted; for more information, see Deleting content databases. Repeat the steps outlined in Deleting content databases for each database except Configuration Database and Central Administration. |
|
IMPORTANT: The Configuration Database and Central Administration databases are not recovered. Deleting these databases causes you to start the entire Disaster Recovery process over because they must be created in place by the SharePoint Products and Technologies Configuration Wizard. |
|
• |
NetVault Backup software and the Plug‑in for SharePoint installed: The same version of NetVault Backup and the plug-in must be installed and configured as they originally existed on the damaged server. |
|
• |
Full and optional Differential Backups available: Ensure that you have the latest Full Backup and Differential Backup, if applicable, available. |
|
• |
Plug-in for FileSystem backups of additional items available: Ensure that you have backups of the following items available as detailed in Extra items to protect using NetVault Backup and the Plug-in for FileSystem: |
For more information, see http://technet.microsoft.com/en-us/library/cc262370.aspx.
|
• |
Restore Full Backup: At a minimum, recovery requires the restore of a Full Backup. |
|
1 |
|
2 |
Select the Farm node. |
|
3 |
|
• |
|
• |
Select Restore Files from Backup Only. |
|
4 |
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default. |
|
5 |
In the Target Client list, select the server where the plug-in is installed in the alternate farm. |
|
6 |
|
• |
Restore Differential Backup (optional): If your backup strategy includes Differential Backups, restore the last available Differential Backup. |
|
1 |
|
2 |
Select the Farm node. |
|
3 |
|
• |
|
• |
Select Restore Files from Backup Only. |
|
4 |
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default. |
|
5 |
In the Target Client list, select the server where the plug-in is installed in the alternate farm. |
|
6 |
|
• |
Restore Full and Differential Backups to the alternate farm: On the server where the plug-in is installed in the alternate farm, run the following STSADM command to restore the Full Backup to a new configuration. |
|
• |
<directoryForTemporaryFiles>: Enter the UNC share path that is specified in the Configure dialog box. |
|
• |
<SQLserverUserName>: Specify a SQL Server user with the sysadmin server role in the DOMAIN\username format. |
|
• |
<password>: Enter the password associated with the user specified in the preceding field. |
|
Enter the new URL with the new web server host name and the original port. | ||
|
To accept the <default>, press Enter. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for a nondefault SQL Server Instance name. | ||
|
To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To accept the <default>, press Enter, and ensure that the resulting database name matches the name for the content database of the damaged farm. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name | ||
|
To accept the default SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To ensure that the resulting database name matches the name for the content database of the damaged farm, press Enter to accept the <default>. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name | ||
|
To accept the default SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To ensure that the resulting database name matches the name for the content database of the damaged farm, press Enter to accept the <default>. | ||
|
Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name | ||
|
To accept the default SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name. | ||
|
To ensure that the resulting database name matches the name for the content database of the damaged farm, press Enter to accept the <default>. |
|
• |
Add Shared Services Provider service credentials: Ensure that the SSP service credentials are added to the alternate server or farm after the restore. For more information, see Adding SSP Credentials to the Alternate Server or Farm. |
|
• |
Validate Personalized Service permissions: Ensure that the Shared Services Rights reference the local administrator on the alternate server or the domain administrator on the alternate farm. For more information, see Verifying that the Shared Services rights reference the correct administrator. |
|
• |
Validate Business Data Catalog permissions: Ensure that the Business Catalog Permissions reference the local administrator on the alternate server or the domain administrator on the alternate farm. For more information, see Verifying that the Business Catalog Permissions reference the correct administrator. |
|
• |
Validate Search Authoritative web page settings: Ensure that the Authoritative Pages in the Search Setting references the alternate server or farm. For more information, see Validating the Authoritative Pages for Search Settings. |
|
• |
Validate Trusted File location: Ensure that the Trusted File location in the Excel Services Trusted File Locations references the alternate server. For more information, see Validating the Trusted File location. |
|
• |
Redeploy solutions: If you have a solution package that you want to redeploy, use the STSADM deploysolution option. For more information, see Redeploying solutions. |
|
• |
Restore unpackaged customizations and alternate access mappings: Use the Plug-in for FileSystem to restore unpackaged customizations and mappings as detailed in Alternate access mapping and Customizations. |
|
• |
Re-create alternate access mappings (optional): Use the Alternate Access Mapping text file to re-create mappings. For more information, see Re-creating Alternate Access Mappings (optional). |
|
• |
Restart timer jobs: Some timer jobs are not started when you restore the web-application backup. For more information, see Restarting timer jobs. |
|
• |
Reactivate features: If your solution contains features that must be enabled, enable the features at the appropriate level — web application, site collection, or website. For more information, see Reactivating features. |
|
• |
Restart IIS: To ensure that IIS has the most current configuration, restart IIS. For more information, see Restarting IIS. |
Extra items to protect using NetVault Backup and the Plug-in for FileSystem
|
• |