Planning for Backup and Recovery
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
Consider the information in this section when planning for Configuration Manager 2007 backup and recovery operations.
Planning for Backup
Volume Shadow Copy Service
The Configuration Manager 2007 backup task utilizes the Volume Shadow copy Service (VSS) to create the backup snapshot. VSS is essentially a framework which facilitates communication between applications, storage subsystems, and storage management applications (including backup applications) in order to define point-in-time copies of storage data. These point-in-time copies, or shadow copies, of site server and site database information are used to backup and restore Configuration Manager sites. By using VSS shadow copies, the Backup ConfigMgr Site Server maintenance task is able to minimize off-line times for site servers.
What Gets Backed Up
In order to completely back up a Configuration Manager 2007 site server, the following data needs to be included in the backup:
The Configuration Manager site database (SQL Server database)
Configuration Manager installation directory on the site server
Master site control file (.\Inboxes\Sitectrl.box\Sitectrl.ct0)
SMS and NAL registry keys on the site server
What Does Not Get Backed Up
Some Configuration Manager 2007 site systems contain site data that is easily recreated if the site fails and are not backed up during the site backup process. For example, there is no need to backup data from site systems such as standard and branch distribution points, management points, reporting points, and server locator points. These site systems can easily be reinstalled by the site server if they fail.
The Backup ConfigMgr Site Server maintenance task backs up logs located in the Configuration Manager logs directory, but some Configuration Manager 2007 site systems write logs in other locations and are not backed up by the Backup ConfigMgr Site Server maintenance task. You should plan an alternative method to back up these logs if required.
It is not necessary to back up the SQL Server master database when backing up the Configuration Manager site database. The Backup ConfigMgr Site Server maintenance task backs up all of the required information for restoring the site from the SQL Server hosting the site database as part of the backup process. The original SQL Server master database is not required for restoring the site database on a new SQL database server.
Backing up Configuration Manager 2007 clients are not backed up as part of the site backup process for the following reasons:
To properly back up a Configuration Manager client, the client services must be stopped. However, there is no reliable way to stop and start the client services. Stopping and starting the client services can potentially corrupt the data on the client’s disk or in the backup snapshot.
Clients are too numerous. It is neither practical nor beneficial to backup and restore the clients assigned to a site.
The effect of losing client data is relatively small.
Maintenance Mode Support
When the Backup ConfigMgr Site Server maintenance task performs a site backup, critical site services must be stopped including:
SMS Executive service (SMS_Executive)
SMS Site Component Manager service (SMS_Site_Component_Manager)
If the site server or site database server is being monitored by the Microsoft Operations Manager 2005 or System Center Operations Manager 2007 client monitoring agent, the backup process may generate false stop service alerts when critical Configuration Manager 2007 services are stopped for backup. To avoid this problem, the entire backup process is monitored as a single transaction and managed utilizing Microsoft Operations Manager maintenance mode state management.
For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.