Synchronizing databases in Project Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
When recovering from a failure or disaster, it is necessary to recover related databases to a point of consistency with each other to maintain data integrity and avoid orphaned records and possible system problems. Specifically, the following databases must be synchronized with each other:
Microsoft Office Project Server 2007 Draft database
Office Project Server 2007 Published database
Office Project Server 2007 Reporting database
SharePoint Products and Technologies Content database associated with a given Office Project Server 2007 instance
When restoring the SharePoint Products and Technologies configuration databases, it is important to synchronize them with existing content databases and the Office Project Server 2007 Published and Reporting databases. This can be done by restoring the failed database to the point of failure, or by restoring all related databases to a marked transaction.
The Office Project Server 2007 Archive database is only accessed when archiving data using the PWA Administrative Backup functionality. Because of this, the Archive database does not require synchronization with other Office Project Server 2007 databases and can be recovered to any point in time.
Note
As a best practice, do not recover the Archive database to a point in time when an Administrative Backup was in process.
Normally if the active transaction log is available on each of the databases that you are restoring, you can recover to the point of failure and the databases will be consistent. If the active transaction log is not available for one or more databases that you are recovering, then you must recover to an earlier point in time. In this case, you should recover to a named mark in the transaction log to help assure data integrity.
The following table provides recovery guidance for the different types of databases associated with Office Project Server 2007 deployments.
| Database | Recovery procedure |
|---|---|
Project Server Archive database |
Recover to the point of failure, if possible. If you are recovering to an earlier point in time, recover to a point in time when no administrative backup operation was in progress. |
Project Server Draft database |
Recover to the point of failure, if possible. If you are recovering to an earlier point in time, synchronize with the Office Project Server 2007 Published and Reporting databases and the SharePoint Products and Technologies Content database associated with the PWA instance. |
Project Server Published database |
Recover to the point of failure, if possible. If you are recovering to an earlier point in time, synchronize with the Office Project Server 2007 Draft and Reporting databases and the SharePoint Products and Technologies Content database associated with the PWA instance. |
Project Server Reporting database |
Recover to the point of failure, if possible. If you are recovering to an earlier point in time, synchronize with the Office Project Server 2007 Published and Draft databases and the SharePoint Products and Technologies Content database associated with the PWA instance. |
SharePoint configuration databases |
Recover to the point of failure, if possible. Avoid recovering to a point in time where configuration changes are in progress. If you are recovering to an earlier point in time, synchronize with SharePoint Products and Technologies content databases. |
SharePoint content databases |
Recover to the point of failure, if possible. Synchronize with Project Server databases if associated with Project Server. |
SharePoint search database |
Restore using SharePoint Products and Technologies tools to avoid requiring a full crawl. If you are using SQL Server tools, restore to the latest differential backup. |
SSP databases |
Restore to the latest differential backup. |
SSO database |
Restore to the point of failure, if possible; otherwise restore to the latest available point in time (last available transaction log). If you are using Simple recovery, restore to the latest differential backup. |
SSP content databases |
Restore to the point of failure, if possible; otherwise restore to the latest available point in time (last available transaction log). |
When recovering your databases, keep in mind the following best practices:
If a SharePoint Products and Technologies database failed during a major business transaction (such as creating a site or a Web application), recover that database to a point in time before the business transaction began.
If one or more Office Project Server 2007 databases failed, recover them to the point of failure, if possible. If point-of-failure recovery is not possible, then recover the Published and Reporting databases and the SharePoint Products and Technologies Content database associated with your Office Project Server 2007 deployment to a marked transaction.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for Project Server 2007.
See Also
Concepts
Enterprise disaster recovery for Project Server 2007
Other Resources
Working with Transaction Log Backups (https://go.microsoft.com/fwlink/?LinkID=129350&clcid=0x409)
Using Marked Transactions (Full Recovery Model) (https://go.microsoft.com/fwlink/?LinkID=129352&clcid=0x409)