Introducing NetVault Backup Plug-in for SharePoint
NetVault Backup Plug-in for SharePoint: at a glance
Key benefits
Feature summary
Target audience
Recommended additional reading
Deploying, installing, and removing the plug-in
Deploying the plug-in
Configuring the plug-in
Backing up data
Single Server deployment
Small Farm deployment
Scaled-Out Farm deployment
Assigning the SP_DATA_ACCESS role for SharePoint 2013 and later
Installing or upgrading the plug-in
Removing the plug-in
Defining a backup-and-recovery strategy
Performing backups
Restoring data
Understanding the SharePoint restore process
Restoring backups in SharePoint
Extra items to protect using NetVault Backup and the Plug-in for FileSystem
Validating prerequisites
Selecting data for a restore
Setting restore options
Finalizing and submitting the job
Restarting services
Restoring a single Full Backup,a Full + Differential sequence, or an Individual Site Collection Backup
Restoring a single Full farm Backup
Restoring a Full + Differential farm backup sequence
Restoring an Individual Site Collection Backup
Using other restore procedures
Common tasks
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
Overview
Customizations
IIS configuration
Alternate access mapping
Document SharePoint Farm configuration
Troubleshooting
Restarting the SharePoint Search service
Restart the SharePoint Search service. For more information about the service names, see SharePoint 2007, 2010, 2013, and 2016 terminology.
|
1 |
|
2 |
|
3 |
|
4 |
Ensure that the Database Server and Database Name match the Database Server and Database Name on the damaged SharePoint Search Database. In addition, ensure that the Every X Minutes option for the Index Schedule is not selected to ensure that there are no update conflicts during the restore.
The SharePoint Search Database is detailed in the NetVault Backup log for the backup job that is used in the SharePoint Search Database Restore procedure. For example, if the NetVault Backup log for the backup job included the following tree for SharePoint 2007, the Database Name would be: WSS_Search_BKB_APM_PM.
Deleting Shared Services in a new deployment
Delete the default SSP, SharedServices1, in the newly installed deployment.
|
1 |
Open SharePoint Central Administration, and select Shared Services Administration from the menu on the navigation pane. |
|
2 |
Note the web applications that are listed under SharedServices1. |
|
3 |
On the Application Management page, in the SharePoint Web Application Management section, click Delete Web application. |
|
4 |
Delete both web applications associated with the SharedServices1 SSP as noted in Step 2 with Delete content databases and IIS Web site set to Yes. |
|
5 |
At the command prompt, use STSADM to delete the SharedServices1 SSP by entering the following command: |
|
IMPORTANT: If the default Shared Services entry in the newly installed deployment is not deleted, the restore job stops responding when trying to restore the Shared Search Index at the following step: Progress: [Shared Search Index] 90 percent complete. |
Re-creating the web applications
|
1 |
|
2 |
|
3 |
Ensure that the IIS web site and the Database Name match the web application as it existed on the source SharePoint deployment.
Deleting content databases
To ensure that the names of content databases for the new farm or server equal the names of the content databases for the source farm or server, ensure that all content databases for the web application being restored are 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 that you want to delete, and select Delete. |
|
3 |