Chat now with support
지원 담당자와 채팅

NetVault Backup Plug-in for SharePoint 12.1 - 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

Performing a disaster recovery of a Single Server deployment to the same server

Disaster recovery in a Single Server deployment includes the restore and recovery of the entire SharePoint deployment after a farm-level failure; that is, 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 the same server where the Single Server deployment resided. You might use this procedure if a complete media failure occurred and either the damaged host was rebuilt using the same configuration or a new server was configured imitating the original host's configuration including host name.

Verify that the following requirements are met:

SharePoint Server installed: Install the same version and edition of the SharePoint software on the system as existed on the damaged server. This step includes installing and configuring Internet Information Services (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.
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:
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.
Create web applications: Re-create all web applications for your farm before you perform the restore. This step ensures that the timer jobs associated with each web application are created. For more information, see Re-creating the web applications.
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.

For more information about disaster recovery, see http://go.microsoft.com/fwlink/?LinkId=102839&clcid=0x409.

Restore Full Backup: At a minimum, recovery 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 SP CMDLET FULL or STSADM FULL.
In the SQL Server User Name field, use the DOMAIN\username format to specify the user name that has the sysadmin server role.
In the Password field, enter the password associated with the user specified in the preceding field.
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 SP CMDLET DIFFERENTIAL or STSADM DIFFERENTIAL.
In the SQL Server User Name field, use the DOMAIN\username format to specify the user name that has the sysadmin server role.
In the Password field, enter the password associated with the user specified in the preceding field.
4
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.
5
Complete the Target Client, Schedule, Source Options, and Advanced Options lists, and click Save & Submit.
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 the same farm

Disaster recovery in a Small Farm or Scaled-Out Farm deployment includes the restore and recovery of the entire SharePoint deployment after a farm-level failure, that is, 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 the farm where the damaged SharePoint deployment resided. You can use this procedure when a complete media failure occurs and the damaged hosts are rebuilt with the same configuration or new servers are configured that imitate the original host's configuration, including host names.

Verify that the following requirements are met:

SharePoint Server installed: Install the same version and edition of the SharePoint software on the systems that make up the small farm as 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 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.
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 about disaster recovery in small-to-medium-sized deployments, see http://go.microsoft.com/fwlink/?LinkId=102839&clcid=0x409.

Restore Full Backup: At a minimum, recovery 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 SP CMDLET FULL or STSADM FULL.
In the SQL Server User Name field, use the DOMAIN\username format to specify the user name that has the sysadmin server role.
In the Password field, enter the password associated with the user specified in the preceding field.
4
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.
5
Complete the Target Client, Schedule, Source Options, and Advanced Options lists, and click Save & Submit.
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 SP CMDLET DIFFERENTIAL or STSADM DIFFERENTIAL.
In the SQL Server User Name field, use the DOMAIN\username format to specify the user name that has the sysadmin server role.
In the Password field, enter the password associated with the user specified in the preceding field.
4
To save the settings, click Ok, click Next, and specify a Job Name if you do not want to use the default.
5
Complete the Target Client, Schedule, Source Options, and Advanced Options lists, and click Save & Submit.
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.
Reconfigure Index Schedule: Reconfigure the Index Schedule back to the applicable interval. For more information, see Reconfiguring the Index Schedule.
Restart IIS: To ensure that IIS has the most current configuration, restart IIS. For more information, see Restarting IIS.

Restoring to an alternate server or farm

This topic describes the following procedures:

SharePoint PowerShell Cmdlets and STSADM let you restore to an alternate server or farm with its ability to restore to a new configuration. However, restoring to a new configuration introduces more complexity and requires more manual intervention from the user.

Restoring to an alternate server or farm includes the following steps:

The following topics provide procedures for multiple restore scenarios, including restoring individual site collections, web applications, SSPs, SharePoint Search, and disaster recovery to an alternate server. To ensure that restores to alternate servers or farms are successful, Quest recommends that you adhere to these procedures.

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.
관련 문서