NetVault Plug-in for SharePoint 1.3

Stopping the SharePoint Search service Deleting the Search Instance Database Restarting the SharePoint Search service Deleting Shared Services in a new deployment Re-creating the web applications Deleting content databases Redeploying solutions Re-creating Alternate Access Mappings (optional) Restarting timer jobs Reactivating features Restarting IIS Creating the SharePoint Central Administration Web Site Configuring the SharePoint Search service Configuring the SharePoint Search service Reconfiguring the Index Schedule Verifying that the Site Collection Administrator matches on the source and alternate Adding SSP Credentials to the Alternate Server or Farm Verifying that the Shared Services rights reference the correct administrator Verifying that the Business Catalog Permissions reference the correct administrator Validating the Authoritative Pages for Search Settings Validating the Trusted File location

Restoring to the same server or farm

Restoring SharePoint Search to the same server or farm Performing a disaster recovery of a Single Server deployment to the same server Performing a disaster recovery of a Small Farm or Scaled-Out Farm to the same farm

Restoring to an alternate server or farm

Validating prerequisites Restoring an Individual Site Collection to an alternate farm Restoring a Web Application to an alternate server or farm Restoring a SharePoint Search to an alternate server or farm Restoring a Shared Services Provider to an alternate server or farm Performing a disaster recovery of a Single Server deployment to an alternate server Performing a disaster recovery of a Small Farm or Scaled-Out Farm to an alternate farm

Extra items to protect using NetVault Backup and the Plug-in for FileSystem

Overview Customizations IIS configuration Alternate access mapping Document SharePoint farm configuration

Troubleshooting

Enabling NetVault Backup Tracing Disabling NetVault Backup Tracing Additional information

Performing a disaster recovery of a Single Server deployment to an alternate server

Disaster recovery in a Single Server deployment includes the restore and recovery of the entire SharePoint deployment after a farm-level failure — the loss of the entire server that houses the SharePoint SQL Server Instance, application server, and web server. To perform disaster recovery, the minimum set of backups, which includes at least a Full Backup, is required.

The following procedure describes how to perform disaster recovery to a server other than where the damaged SharePoint deployment resided. You might use this procedure if a complete media failure occurred and the backups from the damaged server were restored to a replacement server that has a different host name.


	IMPORTANT: When performing disaster recovery, Quest recommends that you perform recovery to the damaged server that was rebuilt using the same configuration or a new server that was configured to imitate the original host’s configuration including host name; otherwise, several more steps are required during the post-recovery process to rename the host name in several configuration settings that are not updated automatically with STSADM.

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.


	IMPORTANT: In a Single Server deployment, a Basic Installation of the SharePoint software, free or enhanced version, is assumed for these procedures.

•

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:

•

Customizations

•

Alternate Access Mapping

•

Document SharePoint Farm Configuration

Beginning the restore

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.

On the Create Selection Set page, select the saveset of the last Full Backup.

Select the Farm node.

On the Create Selection Set page, click Edit Plugin Options, and complete the following steps:

•

Verify that the Backup Type is labeled STSADM FULL.

•

Select Restore Files from Backup Only.

To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.

In the Target Client list, select the server where the plug-in is installed in the alternate farm.

Complete the Schedule, Source Options, and Advanced Options lists, and click Save & Submit.

The plug-in performs a full restore of the SharePoint Farm to the newly installed deployment.

•

Restore Differential Backup (optional): If your backup strategy includes Differential Backups, restore the last available Differential Backup.

On the Create Selection Set page, select the saveset of the last Differential Backup.

Select the Farm node.

On the Create Selection Set page, click Edit Plugin Options, and complete the following steps:

•

Verify that the Backup Type is labeled STSADM DIFFERENTIAL.

•

Select Restore Files from Backup Only.

To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.

In the Target Client list, select the server where the plug-in is installed in the alternate farm.

Complete the Schedule, Source Options, and Advanced Options lists, and click Save & Submit.

The plug-in restores the backup package to the alternate server or farm.

•

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.

stsadm ‑o restore ‑directory <directoryForTemporaryFiles>\nvsprestore

‑restoremethod new ‑username <SQLserverUserName> ‑password <password>

Replace the variables with the following information:

•

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

STSADM begins an interactive session and prompts for the following information:


Item	Parameter	New value
Web Application	New web application URL	Enter the new URL with the new web server host name and the original port.
Web Application	New web application name	To accept the <default>, press Enter.
Content Database	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for a nondefault SQL Server Instance name.
	New directory name	To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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.
Shared Services Database	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name.
	New directory name	To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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.
User Profile Application	New server name	Enter the host name of the new application server.
Shared Search Index Database	New server name	Enter the host name of the new application server.
Shared Search Index Database	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name.
	New directory name	To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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.
Search Instance Database	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name.
	New directory name	To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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.

Completing the restore

In Single Server deployments, a local administrator is typically used as the SharePoint administrator. This setting complicates the restoring of an SSP to an alternate Single Server deployment because each deployment is using a different local administrator. Therefore, you must perform the following post-restore procedures to ensure that the restored Shared Services on the alternate server reference the local administrator of the alternate server.

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

Disaster recovery of a Small or Scaled-Out Farm deployment includes the restore and recovery of the entire SharePoint deployment after a farm-level failure — the loss of servers that house the SharePoint SQL Server Instance, application server, and web server. To perform disaster recovery, the minimum set of backups, which includes at least a Full Backup, is required.

The following procedure describes how to perform disaster recovery to a farm other than the one where the damaged SharePoint deployment resided. You might use this procedure if a complete media failure occurred and the backups from the damaged farm were restored into a replacement farm that was made of different servers using different host names.

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.

•

Database Server

•

SQL Server software and updates

•

Application Server

•

Net Framework 3.0

•

Front-End Web Server

•

Internet Information Services (IIS)

•

Net Framework 3.0

•

APS.NET


	IMPORTANT: In Small and Scaled-Out Farm deployments, an Advance Installation of the SharePoint software, free or enhanced, is assumed for these procedures.

•

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, and 2013 terminology.

•


	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.

•

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:

•

Customizations

•

Alternate Access Mapping

•

Document SharePoint Farm Configuration

Beginning the restore

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.

On the Create Selection Set page, select the saveset of the last Full Backup.

Select the Farm node.

On the Create Selection Set page, click Edit Plugin Options, and complete the following steps:

•

Verify that the Backup Type is labeled STSADM FULL.

•

Select Restore Files from Backup Only.

To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.

In the Target Client list, select the server where the plug-in is installed in the alternate farm.

Complete the Schedule, Source Options, and Advanced Options lists, and click Save & Submit.

The plug-in restores the backup package to the alternate server or farm.

•

Restore Differential Backup (optional): If your backup strategy includes Differential Backups, restore the last available Differential Backup.

On the Create Selection Set page, select the saveset of the last Differential Backup.

Select the Farm node.

On the Create Selection Set page, click Edit Plugin Options, and complete the following steps:

•

Verify that the Backup Type is labeled STSADM DIFFERENTIAL.

•

Select Restore Files from Backup Only.

To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.

In the Target Client list, select the server where the plug-in is installed in the alternate farm.

Complete the Schedule, Source Options, and Advanced Options lists, and click Save & Submit.

The plug-in restores the backup package to the alternate server or farm.

•

stsadm ‑o restore ‑directory <directoryForTemporaryFiles>\nvsprestore

-restoremethod new ‑username <SQLServerUserName> ‑password <password>

Replace the variables with the following information:

•

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

STSADM begins an interactive session and prompts for the following information:


Item	Parameter	New value
Web Application	New web application URL	Enter the new URL with the new web server host name and the original port.
Web Application	New web application name	To accept the <default>, press Enter.
Content Database	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for a nondefault SQL Server Instance name.
	New directory name	To accept the <default> SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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.
Shared Services Database	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name
	New directory name	To accept the default SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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>.
User Profile Application	New server name	Enter the host name of the new application server.
Shared Search Index	New server name	Enter the host name of the new application server.
	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name
	New directory name	To accept the default SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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>.
Search Instance Database	New database server name	Enter the name of the new SQL Server Database server. Use the Server\Instance Name format for nondefault SQL Server Instance name
	New directory name	To accept the default SQL Server Data directory, press Enter; or enter the Data directory for the new SQL Server Instance name.
	New database 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>.

Completing the restore

•

Redeploy solutions: If you have a solution package that you want to redeploy, use the STSADM deploysolution option. For more information, see Redeploying solutions.

•