1. Agent Status on the Primary System Center Data Protection Manager 2010 (DPM) server shows as OK for all Agents.
2. The Consistency Check on the Primary DPM server is failing with the following error:
An unexpected error occurred while the job was running. (ID 104 Details: Access is denied (0x80070005))
3. Recovery Point creation fails with the following error:
DPM failed to communicate with the protection agent on <Server Name>because access is denied. (ID 42 Details: The target principal name is incorrect (0x80090322))
4. On the Secondary DPM Server, Agent Status for the Primary shows as Unavailable.
Detailed error code: A security package specific error occurred (0x80070721
The protection agent operation failed because DPM could not communicate with the Protection Agent service on <Primary DPM Server Name>.
Detailed error code: A security package specific error occurred (0x80070721)
In a DPM 2010 primary – secondary configuration, the DPMRA service account on the primary DPM server is changed from local system to a domain user account who is also part of Local Admin group.
To resolve this issue, DPM services should be configured to run using the Local System account on the Primary DPM server.
For the latest version of this article see the link below:
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis