Recovering databases in Project Server 2007

  • Article

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: 2017-01-24

When recovering one or more databases in your Microsoft Office Project Server 2007 deployment, there are two primary options:

  • Recover to the point of failure   If the active transaction log is undamaged, you can recover to the point of failure and minimize data loss.

  • Recover to an earlier point in time   If the active transaction log is not available or if the failure occurred during a logical transaction, you can recover to an earlier point in time.

When recovering one or more databases that are part of a set of related databases, be sure to recover all the related databases to the same point in time. When recovering to a point in time earlier than the point of failure, for best results recover each related database to a common marked transaction.

Recovering to the point of failure

To recover your database to the point of failure, you must be able to back up the currently active transaction log. If you cannot back up the currently active transaction log due to media failure or other problems, you must recover the database to an earlier point in time.

If a logical transaction was taking place at the time of failure, you may want to recover to an earlier point in time to help assure database consistency. For more information, see Database synchronization in Project Server 2007.

Recover to the point of failure

  1. Back up the currently active transaction log.

  2. Restore your backups of the Master and Msdb databases.

  3. Restore the most recent full database backup.

  4. Restore any differential database backups that were created since the most recent full backup.

  5. Restore transaction-log backups up to and including the log you backed up in step 1.

  6. Recover the database.

If you are able to recover any failed databases to the point of failure, your Office Project Server 2007 deployment should function normally and data loss should be minimal, if any.

Recovering to an earlier point in time

If you are unable to back up the currently active transaction log after a system failure or disaster, recover the database to an earlier point in time.

When choosing a time to recover to, consider the following best practices:

  • If you are recovering related databases (databases that need to be synchronized), recover each of the related databases to a common marked transaction.

  • Choose a point in time when there were no logical transactions running.

Recover to a specific point in time

  1. Restore your backups of the Master and Msdb databases.

  2. Restore the most recent full database backup without recovering the database.

  3. Restore any differential database backups that were created since the most recent full backup without recovering the database.

  4. Apply each transaction-log backup in the same sequence in which it was created.

  5. Recover the database at the specified point in time within a transaction log backup.

See Also

Concepts

Enterprise disaster recovery for Project Server 2007

Other Resources

Backing Up and Restoring Databases in SQL Server (https://go.microsoft.com/fwlink/?LinkID=129349&clcid=0x409)
Overview of Restore and Recovery in SQL Server (https://go.microsoft.com/fwlink/?LinkID=132753&clcid=0x409)