Operation Manual

307 Copyright © Acronis International GmbH, 2002-2015
To recover a content database to the original SQL server
1. If the Windows SharePoint Services Timer service is running, stop the service and wait for a few
minutes for any running stored procedures to complete. Do not restart the service until you have
recovered all the databases that you need to recover.
2. If you are recovering the database to the original location on the disk, do the following:
a. Bring the destination database offline.
b. Recover the database files as described in "Recovering SQL Server databases from a disk
backup" (p. 297), except for the database attachment step (the database is already attached).
c. Bring the recovered database online.
If you are recovering the database to another location on the disk, recover the database files as
described in "Recovering SQL Server databases from a disk backup" (p. 297), including the
database attachment step.
3. Start the Windows SharePoint Services Timer service.
To recover a content database to another SQL server of the original farm
1. Remove from the SharePoint farm the database that you will later recover. To do this, run the
following command on a front-end Web server:
In SharePoint 2010 or later:
Dismount-SPContentDatabase <database>
If you have multiple content databases that have the same name, you must use the content database GUID
in this command instead of using the content database name. To retrieve the GUID of the content database,
run the Get-SPContentDatabase cmdlet with no arguments.
In SharePoint 2007:
stsadm -url <web application url> –o deletecontentdb –databasename <database>
2. Recover the database files as described in "Recovering SQL Server databases from a disk backup"
(p. 297), including the database attachment step.
3. Attach the recovered database to the SharePoint farm. To do this, run the following command on
a front-end Web server:
In SharePoint 2010 or later:
Mount-SPContentDatabase <database> -DatabaseServer <database server>
-WebApplication <site url>
In SharePoint 2007:
stsadm.exe -o addcontentdb -url <site url> -databasename <database> -databaseserver
<database server>
11.5.2 Recovering configuration and service databases
Configuration and service databases must be synchronized with other databases. Hence, it is
recommended to recover configuration and service databases either along with content databases or
to the latest point in time (if content databases do not need recovery).
The configuration database contains hostnames of the farm's servers. Therefore, you can recover the
configuration database only to the original SharePoint farm. Service databases can be recovered to a
non-original farm.
To recover the configuration database
1. On the server that is running the Central Administration site, in the Services snap-in, stop the
services listed in the table below.