Chat now with support
Chat with 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

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
Open SharePoint Central Administration, and select the Operations tab.
2
In the Topologies and Services section, click Services on server.
3
In the Server field, select the server where the Search Indexing service is installed.
4
In the Action column, click the Start option.
5
Complete the configuration for the SharePoint Search service.
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.
Farm\
[SharePoint_Config_20df73ac-d2b0-4c99-a919-b853626bae80]\
Windows SharePoint Services Web Application\
SharePoint - 2073\
WSS_Content_PM\
SharePoint - 80\
WSS_Content\
[WSS_Administration]\
[Web Application]\
SharePoint_AdminContent_feb7e07b-aeb4-4403-a5d4-a78fe0f90b0e
SharedServeices1\
[SharePoint - 36448]\
SharedServicesContent_96a5c320-6b44-4daa-a7ar-1a43e1e3a3a2\
[SharedServices1_DB_c99ef411-87c1-4d91-bea6-dde5b1acbb16]\
[UserProfileApplication]\
[SessionStateSharedApplication]\
[Shared Search Index]\
[SharedServices1_Search_DB_9461bb96-b54b-4368-bd42-826f2b03d837]\
Global Search Settings\
Windows SharePoint Services Search\
[Search instance]\
[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:
stsadm ‑o deletessp ‑title SharedServices1 ‑deletedatabases
 
* 
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

Re-create all web applications for your farm before you perform a restore. This step ensures that the timer jobs associated with each web application are created.

1
Open SharePoint Central Administration, and select the Application Management tab.
2
In the SharePoint Web Application Management section, click Create or extend Web application.
3
In the Adding a SharePoint Web Application section, click Create a new Web application.
4
Enter the settings for the new web application.
Ensure that the IIS web site and the Database Name match the web application as it existed on the source SharePoint deployment.
The web applications and associated database names are detailed in the NetVault Backup log for the backup job that is used in a disaster recovery. For example, if the NetVault Backup log for the backup job included the following tree for SharePoint 2007, the following web applications must be created:
•
Web Application Name: SharePoint - 2073
•
Database Name: WSS_Content_PM
•
Web Application Name: SharePoint - 80
•
Database Name: WSS_Content
Farm\
[SharePoint_Config_20df73ac-d2b0-4c99-a919-b853626bae80]\
Windows SharePoint Services Web Application\
 SharePoint - 2073\
WSS_Content_PM\
SharePoint - 80\
WSS_Content\
[WSS_Administration]\
[Web Application]\
SharePoint_AdminContent_feb7e07b-aeb4-4403-a5d4-
a78fe0f90b0e
SharedServeices1\
[SharePoint - 36448]\
SharedServicesContent_96a5c320-6b44-4daa-a7ar-1a43e1e3a3a2\
[SharedServices1_DB_c99ef411-87c1-4d91-bea6-dde5b1acbb16]\
[UserProfileApplication]\
[SessionStateSharedApplication]\
[Shared Search Index]\
[SharedServices1_Search_DB_9461bb96-b54b-4368-bd42-
826f2b03d837]\
Global Search Settings\
Windows SharePoint Services Search\
[Search instance]\
[WSS_Search_BKB_APM_PM]\
For more information, see http://go.microsoft.com/fwlink/?LinkId=102634&clcid=0x409.

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
On the Delete Object dialog box, select Close existing connections, and click OK.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating