You can Microsoft SQL Server 2005 tools to back up the following databases used by Microsoft Office Project Server 2007:
Draft database
Published database
Archive database
Reporting database
Content databases
Databases for Shared Services Providers (SSPs)
Search databases for the SSPs
Search databases
.gif) Note |
|---|
The search index is not stored in SQL Server. If you use SQL Server 2005 tools to back up search, you must perform a full crawl upon recovering 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 migrate 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 migrate the configuration database. |
The procedures in this article assume that you are moving data to a server that is different from the one that produced the backup. The procedures also assume that Office Project Server 2007 has already been installed on the destination server farm.
| Important |
|---|
Membership in the dbcreator fixed server role is the minimum required to complete these procedures. |
Using SQL Server tools to migrate a database
In the event of a failure, you must use your backups to migrate or re-create the database. You should migrate 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.
Migrate the last full database backup.
Migrate the most recent differential database backup since the last full database backup.
Migrate all transaction log backups since the last full or differential database backup.
Migrate 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 migrated all the databases that you need to migrate.
Open Microsoft SQL Server Management Studio and connect to the database server.
In Object Explorer, right-click Databases, and then click Restore Database.
In the Restore Database dialog box, type the name of the database you want to create and restore to in the To database text box. The name must have the exact same name as the source database.
In the Source for restore section, select the From device option.
Click the ellipsis […] button.
In the Specify Backup dialog box, select the Backup media type. The backup file might be either on a tape device or the file system.
Click Add and browse to the backup file.
Select the backup file and click OK.
If you want to review the contents of the backup file to make sure it is the correct one, click Contents.
In the Specify Backup dialog box, click OK.
In the Restore Database dialog box, specify the destination and the source, and then select the backup set from the Select the backup set to restore list.
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 Overwrite the existing database.
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 migration process.
Repeat the procedure for each the database you are migrating.
Start the Windows SharePoint Services Timer service.
See Also