

* The effect of losing client data is relatively small. It is neither practical nor beneficial to backup and restore the clients assigned to a site. Stopping and starting the client services can potentially corrupt the data on the client�s disk or in the backup snapshot. However, there is no reliable way to stop and start the client services. * To properly back up a Configuration Manager client, the client services must be stopped. 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: 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. 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. 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. 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.

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.
