Managing Protected Client Computers
Updated: April 21, 2010
Applies To: System Center Data Protection Manager 2010
Microsoft System Center Data Protection Manager (DPM) 2010 allows you to protect your data on client computers. Client computers include desktop computers that are connected to the network, and laptop and notebook computers that are intermittently connected to your corporate environment. Backup administrators can centrally configure data protection for the client computers in their environment using the Data Protection Manager Client. Additionally, administrators can give their end users the ability to define and manage their own backups. DPM 2010 enables end users to perform their own recoveries by leveraging the Previous Versions feature in Windows. For more information about using the Data Protection Manager Client, see Data Protection Manager Client Help (http://go.microsoft.com/fwlink/?LinkId=197113).
Laptop and notebook computers will not be connected to the network at all times and the number of protected client computers can be much larger than the number of protected file servers. These scenarios have resulted in the following changes about how DPM manages client computer protection.
The administrator can configure protection for the client computer that they want to protect without being online. We recommend that administrators use software distribution mechanisms such as Microsoft System Center Configuration Manager to install and configure the DPM protection agent.
The client computer polls the DPM server at 15 minute intervals and obtains the backup schedule that the administrator specifies for the protection group. The client computer starts the backup according to the schedule, or by user demand. Alternatively, once the administrator configures a protection group that allows the end user to specify their protected data items, the end user can start a backup at any time from the Data Protection Manager Client.
DPM will not show alerts for client computers that usually appear for protected servers. These alerts pertain to failures of individual jobs. For example, a synchronization failure alert will not appear for the DPM administrator to act upon for any of the failed synchronizations. This is because client computers are designed to retry the synchronization in the event of a failure. However, DPM allows you to configure DPM to alert the end user if a client computer has not been backed up for a predefined number of days that the administrator defined when they created the protection group.