Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault Plug-in for SharePoint 11.3 - User Guide

Introducing NetVault Backup Plug-in for SharePoint Deploying, installing, and removing the plug-in Configuring the plug-in Backing up data Restoring data
Understanding the SharePoint restore process Restoring backups in SharePoint Restoring a single Full Backup,a Full + Differential sequence, or an Individual Site Collection Backup Using other restore procedures
Common tasks Restoring to the same server or farm Restoring to an alternate server or farm
Extra items to protect using NetVault Backup and the Plug-in for FileSystem Troubleshooting

Validating prerequisites

When performing a complete farm or granular restore to an alternate SharePoint Server or Farm, ensure that the following prerequisites are met before initiating the restore procedures detailed in the following topics:

•
Same version and edition of SharePoint: Ensure that the alternate SharePoint Server or Farm has the same version and edition of SharePoint as the source SharePoint Server or Farm. This requirement includes the same Service Pack and patch level.
•
Same farm deployment: Ensure that the alternate SharePoint Server’s or Farm’s deployment matches the deployment of the source server or farm. For example, if restoring a backup from a Single Server deployment, you can only restore to a different Single Server deployment; if restoring a Small Farm deployment, you can only restore to a different Small Farm deployment. Mismatching deployments between the source and the alternate server or farm is not currently supported.
•
Same domain: When restoring from a Small or Scaled-Out Farm to an alternate Small or Scaled-Out Farm, Quest recommends that both farms reside in the same network domain. It simplifies the restore process if both farms use the same domain administrator as the SharePoint administrator.

Restoring an Individual Site Collection to an alternate farm

Verify that the following requirements are met:

•
Web application created: When restoring individual site collections, ensure that the web application that the individual site collection belongs to exists. If the web application does not exist, re-create the web applications before you perform the restore. This step ensures that the timer jobs associated with each web application are created. If a different Database Name is provided for the web application, it results in two content databases being attached to the web application after completion of the restore job. For more information, see Re-creating the web applications.
•
New content database created: To rename or relocate an individual site collection during the restore, a new content database is required.
1
Open SharePoint Central Administration, and select the Application Management tab.
2
In the SharePoint Web Application Management section, click Content Databases.
3
Select the target web application, and click Add a Content Database.
4
Navigate the selection tree for the backup saveset, and select the objects to restore, that is, the individual site collections as detailed in Selecting data for a restore.
Renaming and relocating the collection during the restore
1
On the Create Selection Set page, access the server where the plug-in is installed, and locate the applicable Individual Collection Site Backup.
2
Navigate the selection tree for the backup saveset, and select the objects to restore, that is, the Individual Site Collections as detailed in Selecting data for a restore.
3
On the Create Selection Set page, click Edit Plugin Options, and verify that the Backup Type is labeled STSADM INDIVIDUAL SITE.
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 where the Individual Site Collection backup is to be restored.
6
Complete the Schedule, Source Options, and Advanced Options lists, and click Save & Submit.
For more information, see Finalizing and submitting the job.
The plug-in restores a backup file for each alternate server or farm. Each individual site collection included in the restore is restored to a separate backup file stored in the <directoryForTemporaryFiles>\nvsprestore directory as indicated in the NetVault Backup restore job log.
7
On the server where the plug-in is installed in the alternate server or farm, run the applicable STSADM command for each site collection being restored.
•
To relocate an individual site collection to an alternate web application:
stsadm ‑o restore ‑url <newURL> ‑filename <fileName>
Replace the variables with the following information:
•
<newURL>: Enter the new URL for the site collection in the format: http:\\<newWebApplication>\<originalURL>
•
<fileName>: Enter the name of the Individual Site Collection backup file stored in the <directoryForTemporaryFiles>\nvsprestore directory as specified in the NetVault Backup restore job log.
•
To rename and relocate an individual site collection to an alternate web application:
stsadm ‑o restore ‑url <newURL> ‑filename <fileName>
Replace the variables with the following information:
•
<newURL>: Enter the new URL for the site collection in the format: http:\\<newWebApplication>\<newURL>
•
<fileName>: Enter the name of the Individual Site Collection backup file stored in the <directoryForTemporaryFiles>\nvsprestore directory as specified in the NetVault Backup restore job log.

Restoring a Web Application to an alternate server or farm

Verify that the following requirements are met:

•
Web applications created: Before performing the restore, create the web applications in the alternate farm. This step ensures that the timer jobs associated with each web application are created. When creating the web application, ensure that the Load Balanced URL provided for the new web application matches the URL of the web application being restored. On the alternate farm, perform the steps outlined in Re-creating the web applications.
The web applications and associated database names are detailed in the NetVault Backup log for the backup job that is restored. For example, if the NetVault Backup log for the backup job included the following tree for SharePoint 2007 and you wanted to restore the SharePoint - 2475 web application, you would create a web application with the following settings:
•
Web Application Name: SharePoint - 2475
•
Database Name: WSS_Content_2475
•
Load Balanced URL: http:\\<newWebServerHost>:<originalPortNumber>\
Farm\
[SharePoint_Config]\
Windows SharePoint Services Web Application\
SharePoint - 2475\
WSS_Content_2475\
SharePoint - 80\
WSS_Content\
[WSS_Administration]\
[Web Application]\
SharePoint_AdminContent_e2062b53-61cf-4ca3-aef4-
076f37aec653\
SharedServeices1\
[SharePoint - 47807]\
SharedServiceContent\
[SharedServices1_DB]\
[UserProfileApplication]\
[SessionStateSharedApplication]\
[Shared Search Index]\
[SharedServices1_Search_DB]\
Global Search Settings\
Windows SharePoint Services Help Search\
[Search instance]\
[WSS_Search_SPVMA-64]\
 
* 
IMPORTANT: Some SharePoint timer job definitions are not restored successfully when you back up a Windows SharePoint Services 3.0 Web application or a SharePoint Web application, and then you restore this application to a new farm. For a fix that eliminates the need to create web applications before you perform the restore to ensure that the timer jobs are created, see http://support.microsoft.com/kb/942989.
•
Content databases deleted: To ensure that the names of content databases for the new farm match the names of the content databases for the source farm, delete all content databases for the web application that you are restoring. For more information, see Deleting content databases.
•
SharePoint Timer stopped: On the server where the plug-in is installed in the alternate farm, use the Services window in the Windows Control Panel to ensure that the status of the SharePoint Timer service is Stopped. This step avoids update conflicts during the restore job. For more information about the service names, see SharePoint 2007, 2010, 2013, and 2016 terminology.
Beginning the restore
•
Restore Full Backup: At a minimum, restoring a web application to an alternate farm requires the restore of a Full Backup.
1
On the Create Selection Set page, select the saveset of the last Full Backup.
2
Select the Farm node.
3
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.
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
Complete the Schedule, Source Options, and Advanced Options lists, and click Save & Submit.
The plug-in performs a full restore of the web application.
•
Restore Differential Backup (optional): If your backup strategy includes Differential Backups, restore the last available Differential Backup.
1
On the Create Selection Set page, select the saveset of the last Differential Backup.
2
Select the Farm node.
3
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.
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
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.
7
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>
‑item “FARM\Windows SharePoint Services Web Application\
<WebApplicationName>”
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.
•
<WebApplicationName>: Enter the name of the web application that you are restoring.
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.

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.

Completing the restore

During the restore to an alternate server or farm, STSADM maintains the Site Collection Administrator of the source server or farm. If the source server farm Site Collection Administrator differs from the alternate server or farm Site Collection Administrator, update the Site Collection Administrator for every site collection restored in the alternate server or farm. For more information, see Verifying that the Site Collection Administrator matches on the source and alternate.

Restoring a SharePoint Search to an alternate server or farm

The following procedure describes how to restore the SharePoint Search service to an alternate farm. For more information about the service names, see SharePoint 2007, 2010, 2013, and 2016 terminology.

Verify that the following requirements are met:

•
SharePoint Search service stopped: Stop the SharePoint Search service. For more information, see Stopping the SharePoint Search service.
•
Search Instance Database deleted: Delete the Search Instance Database. For more information, see Deleting the Search Instance Database.
•
SharePoint Search service restarted: Restart the SharePoint Search service. For more information, see Restarting the SharePoint Search service.
•
Search Instance Database deleted again: To ensure that the name of Search Instance Database for the new farm is the same as the name provided when starting the SharePoint Search service, verify that the content database specified during the SharePoint Search service creation process is deleted again. For more information, see Deleting the Search Instance Database.
Beginning the restore
•
Restore Full Backup: At a minimum, restoring the SharePoint Search Database requires the restore of a Full Backup.
1
On the Create Selection Set page, select the saveset of the last Full Backup.
2
Select the Farm node.
3
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.
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
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 Backup to 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>
‑item "FARM\Windows SharePoint Services Help Search"
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

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

•
Restore Differential Backup (optional): If your backup strategy includes Differential Backups, restore the last available Differential Backup.
1
On the Create Selection Set page, select the saveset of the last Differential Backup.
2
Select the Farm node.
3
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.
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
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 to 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>
‑item "FARM\Windows SharePoint Services Help Search"
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

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

•
Reconfigure Index Schedule: Reconfigure the Index Schedule back to the applicable interval. For more information, see Reconfiguring the Index Schedule.
•
Verify Site Collection Administrator: During the restore to an alternate server or farm, STSADM maintains the Site Collection Administrator of the source server or farm. If the source server farm Site Collection Administrator differs from the alternate server or farm Site Collection Administrator, update the Site Collection Administrator for every site collection restored in the alternate server or farm. For more information, see Verifying that the Site Collection Administrator matches on the source and alternate.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation