Jan 06, 2017 Data Protection Manager error codes. Install the protection agent manually. And then click Data Protection Manager 2010. You can install protection agents manually. To manually install a protection agent. Applies To: Data Protection Manager.

You have installed and configured Data Protection Manager (DPM) 2010 for backup and restore. Now you need to protect the Hyper-V host in your environment. This article explains the process of configuring a Hyper-V host for protection, performing a backup and then restoring part of the configuration. This is the third in a series of articles that explains how to install, configure, and utilize DPM 2010 to backup and restore virtual machines and Hyper-V servers. Introduction This is the third article in a series on DPM 2010 and focuses on configuring a Hyper-V host in DPM 2010 for backup and restoration. This article assumes that you have completed the installation of DPM 2010 as detailed in the first article in the series, completed the configuration steps in the second article in the series and now you need to configure a Hyper-V host in the protection section of DPM in order to perform a backup.

Once the backup is performed, you will restore the Hyper-V configuration to an alternative location. DPM Configuration Before you can configure protection of a Hyper-V host, you must have DPM 2010 installed and storage pool disks added with un-allocated capacity. At the end of the second article in this series, the DPM server had a 127GB storage pool drive added to the system. No protection for any Hyper-V hosts had been configured yet.

You should see unallocated storage available from storage pool disks under the Disks tab in the Management section. Figure 1 Deploying DPM 2010 Agent to Hyper-V Host Before you can protect a Hyper-V host, you must deploy a DPM agent to the machine. There are three possible ways to install the DPM 2010 Agent. • Use the DPM 2010 console • Use a software deployment solution like System Center Configuration Manager 2007 • Manually install the DPM agent Each method has its advantages and disadvantages. Using the DPM 2010 console is the easiest approach. It is a simple wizard solution and all you really need to know is the machine name and the credentials that have local administrative rights on it. The disadvantage is that the firewall must be disabled prior to installing the client.

Once installed you can re-enable the firewall and enable the DPM agent as an exclusion in the firewall options. Cdj 2000 Skin Virtual Dj. If you have System Center Configuration Manager 2007 deployed in your environment already, then it is possible to use SCCM to deploy the DPM agent.

The target machine must have an operating SCCM agent and the DPM agent must be created as a software distribution package. Once the package is created, you can create a collection and target that collection with the advertisement for the DPM software package. You will want the package to be a mandatory package that does not require a user to be logged on. The advantage of this approach is the Windows Firewall is not an issue. The disadvantage is the amount of work required to get the agent deployed. If you do not have SCCM and it is a security issue to disable the firewall on the target machine, then the last option is to manually install the DPM agent on the target machine and then attach the agent in the DPM console so there is a mapping defined for that machine.