Backing up your deployment in Project Server 2007
Updated: March 5, 2009
Topic Last Modified: 2009-03-04
Because Microsoft Office Project Server 2007 and Windows SharePoint Services 3.0 data is stored in SQL Server databases, it is not necessary to back up the computers on which Office Project Server 2007 and Windows SharePoint Services are installed. In the event of a media failure or disaster involving those computers, reinstalling Office Project Server 2007 provides a cleaner and more reliable alternative to restoring from a backup.
For information about recovering specific computers in your deployment, see Recovering computers in your deployment in Project Server 2007.
As part of any backup plan, you should back up any SSL certificates associated with your Office Project Server 2007 deployment. In the event that you need to reinstall Office Project Server 2007 or a front-end Web computer, you may need to restore your SSL certificates. For more information, see your Internet Information Services documentation.
Office SharePoint Server 2007 search uses a SQL Server database as well as index files on the local disk of the computer running Office SharePoint Server 2007. When backing up search, it is necessary to maintain synchronization between the file system files and the database in order to avoid a full crawl after recovery.
SharePoint Central Administration backup and the Stsadm command-line tool are the only backup options that are able to maintain proper synchronization between the database and the index files on the local disk. If you want to avoid a full crawl after recovery of your search database, use SharePoint Central Administration backup or the Stsadm command line tool to back up the farm.
If your recovery-point objectives and recovery-time objectives are better served by point-of-failure or point-in-time recovery using SQL Server tools, you can use SQL Server tools to back up the Office SharePoint Server search database, but a full crawl will be necessary after recovery.
When you back up and restore a database, you must back up the data onto media (for example, tapes and disks). Your backup plan should include provisions for managing media, such as:
A tracking and management plan for storing and recycling backup sets.
A schedule for overwriting backup media.
In a multi-server environment, a decision to use either centralized or distributed backups.
A means of tracking the useful life of media.
A procedure to minimize the effects of the loss of a backup set or backup media (for example, a tape).
A decision to store backup sets onsite or offsite, and an analysis of how this will affect recovery time.
To safeguard against a catastrophic event (such as a fire or earthquake), keep duplicates of your server backups in a different location from the location of the servers. This will protect you against the loss of critical data. As a best practice, keep three copies of the backup media, and keep at least one copy offsite in a properly controlled environment:
One copy on the computer running SQL Server (if backing up locally) on alternate disk storage.
One copy on an alternate server.
One copy off site (depending upon your data recovery Service Level agreements this might be weekly or daily).
For more information about managing media, see Working with Backup Media in SQL Server (http://go.microsoft.com/fwlink/?LinkId=132746&clcid=0x409) in SQL Server Books Online.