Backing up 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: 2016-11-14

Microsoft Office Project Server 2007 data and SharePoint Products and Technologies data is stored in Microsoft SQL Server databases. To protect your data against loss, you must create database backups by using the tools provided with SQL Server. Database backups contain a complete record of all the data in your database at the time the backup finishes. Database backups can be used in combination with transaction-log backups to restore your Office Project Server 2007 and Windows SharePoint Services data to the point of failure or to an earlier point in time.

Because Office Project Server 2007 data is stored in multiple related databases, we recommend that you use marked transactions in the transaction logs of each database to facilitate recovery. For more information about database synchronization, see Database synchronization in Project Server 2007.

Setting the recovery model

Set the recovery model for each of the databases in your deployment as follows:

  • Project Server databases: Full Recovery Both point-of-failure recovery and recovery to earlier points in time require full backups and transaction-log backups of your Project Server databases.

    Note

    We recommend that you move your Project Server databases to fault-tolerant storage.

  • Project Server SSP database: Simple Recovery This database stores configuration settings for the Shared Services Provider. Back up this database whenever you make changes to the Shared Services Provider, such as adding or removing a PWA site.

  • Project Server content database(s): Full Recovery These database(s) contain the project workspaces for your Office Project Server 2007 deployment. Both point-of-failure recovery and recovery to earlier points in time require full backups and transaction log backups of the SharePoint Products and Technologies content databases associated with your Office Project Server 2007 deployment.

    Note

    We recommend that you move your Windows SharePoint Services databases to fault-tolerant storage.

  • SharePoint Configuration databases: Full Recovery   This database contains configuration and site mapping information for your server computer, the Web applications on your server computer, and servers in a server farm. Both point-of-failure recovery and recovery to earlier points in time require full backups and transaction log backups of the SharePoint Products and Technologies configuration databases.

  • Additional SharePoint databases:   For SharePoint Products and Technologies databases that are not associated with your Office Project Server 2007 deployment, choose a recovery model based on your data loss tolerance, service-level agreements, and other business requirements.

  • SSO database:   If you are using the optional Microsoft Office SharePoint Server 2007 single sign-on functionality, choose a recovery model based on your data loss tolerance, service-level agreements, and other business requirements. If your single sign-on settings rarely change, Simple recovery may be the best option.

  • Msdb: Simple Recovery   This database contains the backup and recovery history as well as the log marking history for all of your databases. You will need this information when recovering your Project Server deployment. We recommend a daily backup of the Msdb database.

    Note

    We recommend that you move the Msdb database to fault-tolerant storage.

  • Master: Simple Recovery   This database contains SQL Server security and configuration information. We recommend a daily backup of the Master database.

If you are backing up a non-critical Office Project Server 2007 deployment, you can set all databases to Simple recovery if you are able to tolerate the loss of all data between backups.

Important

If you use Simple recovery, you should back up your deployment when the system is not in use (that is, when no database transactions are occurring). This will assure database consistency after recovery.

For more information about SQL Server recovery models, see Backing Up and Restoring Databases in SQL Server (https://go.microsoft.com/fwlink/?LinkID=129349&clcid=0x409) in SQL Server Books Online.

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

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)