To
restore an individual Site from a Database backup set:
Right-click a SharePoint database backup set and select Browse Backup
Data. See
Browse and Restore for
step-by-step instructions.
Click OK.
From the Browse Data window, select Site or select Site
under Site Collections if the Site Collection was backed up.
Click Recover All Selected...
In Report Options dialog box, click the Site tab.
Select the site to restore from the list and click Overwrite URL.
The existing site will be deleted and restored only when Overwrite URL
is selected. If the site cannot be deleted, the content will be merged into
an existing site.
For out-of-place restores, the top-level sites will be restored as
top-level sites and subsites will be restored as subsites.
Set the
bSiteImportRetainObjectIdentity to
1 to override the object identity if the
Site URL path is similar to the original one for out-of-place restore
operations.
Click OK.
Restore a WSS Web
Application Content Database
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the Web Application Content Database was removed from the Virtual Server but the
database was not deleted from the SQL Instance, delete it before beginning
the restore (for Stand-alone or Single server with SQL Server Deployments).
If the Web Application was deleted, or if SharePoint was removed from the IIS web site with the option "Delete IIS Web sites",
or if an IIS web site does not exist, then the IIS web site should be manually created in IIS.
If SharePoint was removed from an IIS web site, delete the WSS Web Application prior to
restoring the WSS Web Application Content Database.
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If SharePoint was removed from an IIS web site, delete the WSS Web
Application prior to restoring the WSS Web Application Content Database.
If the Web Application was deleted or SharePoint was removed from the
IIS web site with the option "Delete IIS Web sites",
then the IIS web site should be manually created in IIS.
To preserve the original Web Application name, set the
sOwnerLogin
and
sOwnerEmail registry keys, and then restore the WSS Web Application
Content Database with the Extend URL option selected.
Restore the WSS Web Application Database using the SQL
iDataAgent. Refer to
Recovering Database for step-by-step instructions. [Do not restore the SharePoint Configuration Database].
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, expand the WSS Web Application node
and select Web Application Database.
For SharePoint 2010: After you restore a Web Application with the
Extend URL option, you must do the following:
Open IIS Manager.
Under Web Site, select the restored Web Application, and
then check the Application Pool name assigned to it.
If the Application Pool credentials
are set to NetworkService, then stop the Web Site.
Select a different
Application Pool with Managed Account credentials.
Start the Web Site.
Restore a WSS Search
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the WSS Search database was not deleted from the SQL Instance, delete
it before beginning the restore (for Stand-alone or Single server with SQL
Server Deployments).
In Windows Services, stop the Windows
SharePoint Services Search service
and delete WSS Search Index that is
typically located under ..\Microsoft Office
Servers\12.0\Data Application.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select the SP Search node.
Click
Recover all Selected.
From the Restore Options dialog box, enter the required
information in the Restore Options
WSS Search DB
tab.
Continue with the restore procedure.
Server Farm (Small, Medium, Large)
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
In Windows Services, stop the Windows
SharePoint Services Search service
and delete WSS Search Index that is
typically located under ..\Microsoft Office
Servers\12.0\Data Application.
Restore the WSS Search Database using the SQL
iDataAgent. Refer to
Recovering a Database for step-by-step instructions. Do not restore the SharePoint Configuration Database.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select
SP Search. Click
Recover all Selected.
From the Restore Options dialog box, enter the required
information in the Restore Options
WSS Search DB
tab.
Continue with the restore procedure.
Restore a Service Application
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any restore operation.
This procedure applies only to database backup sets.
For a successful restore, ensure that the SQL Server instance service
account and SharePoint 2010 Timer service account are switched to
Local System. Once the restore is finished,
you can switch back to using the previous accounts (e.g.,
Network Service).
To restore Microsoft Office Project Server 2010 Project Web Access (PWA)
Sites,
follow the procedure below. These sites cannot be restored using the
Restore a SharePoint Server Site Collection procedure or the
Restore a
2007 Project Web Access (PWA) Site procedure.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select Service Application.
From the Restore Options dialog box, enter the required information
in the
Service Application tab.
Continue with the restore procedure.
Restore a Service Application Proxy
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any restore operation.
This procedure applies only to database backup sets.
For a successful restore, ensure that the SQL Server instance service
account and SharePoint 2010 Timer service account are switched to
Local System. Once the restore is finished,
you can switch back to using the previous accounts (e.g.,
Network Service).
To restore Microsoft Office Project Server 2010 Project Web Access (PWA)
Sites,
follow the procedure below. These sites cannot be restored using the
Restore a SharePoint Server Site Collection procedure or the
Restore a
2007 Project Web Access (PWA) Site procedure.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select Site Collection.
From the Restore Options dialog box, enter the required information
in the
Site Collection tab.
Continue with the restore procedure.
Restore a WSS Web
Application Content Database
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the Web Application Content Database was removed from the Virtual Server but the
database was not deleted from the SQL Instance, delete it before beginning
the restore (for Stand-alone or Single server with SQL Server Deployments).
If the Web Application was deleted, or if SharePoint was removed from the IIS web site with the option "Delete IIS Web sites",
or if an IIS web site does not exist, then the IIS web site should be manually created in IIS.
If SharePoint was removed from an IIS web site, delete the WSS Web Application prior to
restoring the WSS Web Application Content Database.
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If SharePoint was removed from an IIS web site, delete the WSS Web
Application prior to restoring the WSS Web Application Content Database.
If the Web Application was deleted or SharePoint was removed from the
IIS web site with the option "Delete IIS Web sites",
then the IIS web site should be manually created in IIS.
To preserve the original Web Application name, set the
sOwnerLogin
and
sOwnerEmail registry keys, and then restore the WSS Web Application
Content Database with the Extend URL option selected.
Restore the WSS Web Application Database using the SQL
iDataAgent. Refer to
Recovering Database for step-by-step instructions. [Do not restore the SharePoint Configuration Database].
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, expand the WSS Web Application node
and select Web Application Database.
For SharePoint 2010: After you restore a Web Application with the
Extend URL option, you must do the following:
Open IIS Manager.
Under Web Site, select the restored Web Application, and
then check the Application Pool name assigned to it.
If the Application Pool credentials
are set to NetworkService, then stop the Web Site.
Select a different
Application Pool with Managed Account credentials.
Start the Web Site.
Restore a WSS Search
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the WSS Search database was not deleted from the SQL Instance, delete
it before beginning the restore (for Stand-alone or Single server with SQL
Server Deployments).
In Windows Services, stop the Windows
SharePoint Services Search service
and delete WSS Search Index that is
typically located under ..\Microsoft Office
Servers\12.0\Data Application.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select the SP Search node.
Click
Recover all Selected.
From the Restore Options dialog box, enter the required
information in the Restore Options
WSS Search DB
tab.
Continue with the restore procedure.
Server Farm (Small, Medium, Large)
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
In Windows Services, stop the Windows
SharePoint Services Search service
and delete WSS Search Index that is
typically located under ..\Microsoft Office
Servers\12.0\Data Application.
Restore the WSS Search Database using the SQL
iDataAgent. Refer to
Recovering a Database for step-by-step instructions. Do not restore the SharePoint Configuration Database.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select
SP Search. Click
Recover all Selected.
From the Restore Options dialog box, enter the required
information in the Restore Options
WSS Search DB
tab.
Continue with the restore procedure.
Restore a Shared Service Provider
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
Delete the Shared Services Provider if it is not default. If it is the
default and others do not exist, create new Shared Services Provider for
temporal usage and set it as default.
Delete old Shared Services Provider.
Delete the WSS Web Application that hosted the Shared Services Provider.
Using stsadm.exe command, delete
site
../ssp/admin from restored Web Application.
For example, stsadm -o deletesite -url http://<URL
of WebApp Hosting SSP>/ssp/admin.
From the Browse Data window, expand the Shared Services Provider, select
Shared Services.Click
Recover all Selected.
Set restored Shared Services Provider as default if necessary and re-associate
regional Web
Application back to it. Delete Shared Services Provider for
temporal usage if it was created.
Server Farm (Small, Medium, Large)
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
Using stsadm.exe command, delete
site
../ssp/admin from restored Web Application.
For example, stsadm -o deletesite -url http://<URL
of WebApp Hosting SSP>/ssp/admin.
Restore the Shared Services Provider Databases using the SQL
iDataAgent. Refer to
Recovering Database for step-by-step instructions. Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, expand the Shared Services Provider, select
Shared Services.Click
Recover all Selected.
Set restored Shared Services Provider as default if necessary and re-associate
regional Web
Application back to it. Delete Shared Services Provider for
temporal usage if it was created.
Restore a Single Sign-on Database
Stand-alone or Single server with SQL Server Deployments
Before You Begin:
Review the general and agent-specific restore requirements accessed from Restore
Backup Data
prior to performing any restore operation.
These Project Server databases can typically be restored:
Project server_Archive,
Project server_Draft,
Project server_Published, and
Project server_Reporting. These cannot be
distributed over multiple subclient. They need to be backed up and restored
together as they belong to the same PWA (Project Web Access) Site.
Restore the Project Server Database using the SQL
iDataAgent. Refer to
Recovering Database for step-by-step instructions. Do not restore the SharePoint Configuration Database.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select
Project Server Application. Click
Recover all Selected.
From the Restore Options dialog box, enter the required
information in the Restore Options
Project Server Application
tab.
Continue with the restore procedure.
Restore a Search Server Shared
Service Provider
Stand-alone Deployment
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
At the Databases backup set level, begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, expand the Shared Services Provider, select
SharedServices.Click
Recover all Selected.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select Site Collection.
From the Restore Options dialog box, enter the required information
in the
Site Collection tab.
Continue with the restore procedure.
Restore a Teamsite Database
Stand-alone or Single server with SQL Server Deployments
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the Teamsite database was not deleted from the SQL Instance, delete it
before beginning the restore (for Stand-alone or Single server with SQL
Server Deployments).
Restore the Teamsite Databases using the SQL
iDataAgent. Refer to
Recovering Database for step-by-step instructions. Do not restore the SharePoint Configuration Database.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select the Teamsite Database.
From the Restore Options dialog box, enter the required
information in the Restore Options
Teamsite
Databases tab.
Continue with the restore procedure.
Restore the directory for the IIS Virtual Server using the File System
iDataAgent.
Restart IIS.
Microsoft Office SharePoint Portal Server 2003 Procedures
Restore a Site Collection
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any restore operation.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select Site Collection.
From the Restore Options dialog box, enter the required information
in the
Site Collection tab.
Continue with the restore procedure.
Restore a Teamsite Database
Stand-alone or Single server with SQL Server Deployments
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the Teamsite database was not deleted from the SQL Instance, delete it
before beginning the restore (for Stand-alone or Single server with SQL
Server Deployments).
Restore the Teamsite Databases using the SQL
iDataAgent. Refer to
Recovering Database for step-by-step instructions. Do not restore the SharePoint Configuration Database.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select the Teamsite Database.
From the Restore Options dialog box, enter the required
information in the Restore Options
Teamsite
Databases tab.
Continue with the restore procedure.
Restore the directory for the IIS Virtual Server using the File System
iDataAgent.
Restart IIS.
Restore a Portal Site
Stand-alone or Single server with SQL Server Deployments
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the portal site databases were not deleted from the SQL Instance,
delete them before beginning the restore (for Stand-alone or Single server
with SQL Server Deployments).
Disconnect any Virtual Servers that are mapped to the portal site.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, expand the Portal Site node, select
Portal Site, and deselect the Index and any Site ContentDatabases;
these should be restored after the Portal Site restore is complete. Click
Recover all Selected.
From the Restore Options dialog box, enter the required
information in the Restore Options
Site Databases
tab.
Restore the Portal Site Databases using the SQL
iDataAgent to
Recovering a Database. Do not restore the SharePoint Configuration Database.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, expand the Portal Site node, select
Portal Site, and deselect the Index and any Site ContentDatabases;
these should be restored after the Portal Site restore is complete. Click
Recover all Selected.
From the Restore Options dialog box, enter the required
information in the Restore Options
Site Databases
tab.
When the Site Content database restore completes, perform the
Site Index restore.
Restore the directory for the IIS Virtual Server using the File System
iDataAgent.
Restart IIS.
Restore a Site Content Database
Stand-alone or Single server with SQL Server Deployments
Before You Begin:
Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore operation.
If the Site Content Database restore is part of Portal Site Restore do
not restore the Site Content database before the
Portal Site Restore.
If the Site Content Database was removed from the Virtual Server but the
database was not deleted from the SQL Instance, delete it before beginning
the restore (for Stand-alone or Single server with SQL Server Deployments).
Restore the Site Content Databases using the SQL
iDataAgent. Refer to
Recovering a Database for step-by-step instructions. Do not restore the SharePoint Configuration Database.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, expand the Portal Site node and
select Site Content Database.
From the Restore Options dialog box, enter the required
information in the Restore Options
Site Content
Databases tab.
Continue with the restore procedure.
Restore a Site Index
Before You Begin:
Review the general and agent-specific restore requirements accessed from Restore
Backup Data
prior to performing any restore operation.
Restore the Portal Site before restoring the Index.
Begin a restore procedure using the SharePoint Server
iDataAgent. See
Browse and Restore for
step-by-step instructions.
From the Browse Data window, select Webstorage System Database.
Continue with the restore procedure.
After successfully completing a restore, any restored document libraries that were
disconnected or deleted will come back with a Portal Association value of
"None". To associate the library with a Portal Site, disconnect and then
reconnect the library manually.
To restore unstructured data in RBS, which was either backed up by
SnapProtect or the SQL ServeriDataAgent, in a server farm
configuration follow the steps given below:
Ensure that the RBS is enabled on the destination instance.
From the CommCell Browser, navigate to the SQL agent | Backup set
and click All Tasks and then click Browse.
After completing your selections, you can either start an immediate restore or schedule the restore.
If you want to schedule the job, click the
Job Initiation tab from the Restore Options dialog box, click Schedule, schedule the job, and then click OK.
If you want to run the job now, accept or click Run Immediately in the same tab and then click OK.
From the CommCell Browser, navigate to the SharePoint agent | Database
and click All Tasks and then click Browse.
After completing your selections, you can either start an immediate restore or schedule the restore.
If you want to schedule the job, click the
Job Initiation tab from the Restore Options dialog box, click Schedule, schedule the job, and then click OK.
If you want to run the job now, accept or click Run Immediately in the same tab and then click OK.
For Out-of-Place, ensure that the RBS is installed on the destination
client.
From SharePoint Management Shell type the following commands to
re-attach the restored content database with web application: