You can use Microsoft SQL Server 2005 tools to back up and recover databases that are used by Microsoft Office Project Server 2007.
.gif) Important |
|---|
You cannot use the Office Project Server 2007 restore feature to restore the configuration database or the Central Administration content database. You cannot use the SQL Server 2005 backup and restore tools to restore your configuration database to a different farm or topology configuration. |
You can restore the following databases:
Draft database
Published database
Archive database
Reporting database
Content databases
Databases for Shared Services Providers (SSPs)
Search databases for the SSPs
Search databases
| Note |
|---|
The search index is not stored in SQL Server. If you use SQL Server 2005 tools to back up and restore search, you must perform a full crawl upon restoring the database. For more information, see Protecting search in Choose what to protect (Project Server). |
Central Administration content database
Configuration database
| Note |
|---|
The configuration database and the Central Administration content database contain computer-specific information. Therefore, you can restore them only to an environment that you configure to be precisely the same, including all software updates, server names, and numbers of servers. That is, you cannot back up the configuration database, change your topology or server roles, and then restore the configuration database. |
For more information about using SQL Server to restore databases, see Backing Up and Restoring Databases in SQL Server (http://go.microsoft.com/fwlink/?LinkID=102629&clcid=0x409).
Using SQL Server tools to recover a database
In the event of a failure, you must use your backups to restore the database. You should recover your database in the following order:
If possible, back up the live transaction log of the current database to protect any changes that have been made since the last full back up.
Restore the last full database backup.
Restore the most recent differential database backup since the last full database backup.
Restore all transaction log backups since the last full or differential database backup.
| Important |
|---|
Membership in the dbcreator fixed server role is the minimum required to perform this procedure. |
Restore an existing database
If the Windows SharePoint Services Timer service is running, stop the service and wait for a few minutes for any currently running stored procedures to complete. Do not restart the service until you have restored all the databases that you need to restore.
Open Microsoft SQL Server Management Studio and connect to the database server.
In Object Explorer, expand Databases.
Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.
The database is automatically taken offline during the restore operation and cannot be accessed by other processes.
In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore.
The default values for destination and source typically suit most recovery scenarios.
In the Select a page pane, click Options.
In the Restore options section, select only Overwrite the existing database. Unless your environment or policies require otherwise, do not select the other options in this section.
In the Recovery state section:
If you have included all the transaction logs that you must restore, select RESTORE WITH RECOVERY.
If you must restore additional transaction logs, select RESTORE WITH NO RECOVERY.
The third option, RESTORE WITH STANDBY is not used in this scenario.
Click OK to complete the restore operation.
Repeat this process for each database that you are restoring.
Start the Windows SharePoint Services Timer service.
See Also