DPM errors

Sometimes DPM is difficult to troubleshoot. Here I collected the information describes DPM errors which I had to fix and didn’t find them on Technet and other public resources. Hope it will help you and community in your work.

 

DPM Error ID 7

Error description: Unable to connect to the Active Directory Domain Services database. Make sure that the DPM server is a member of a domain and that a domain controller is running. Also verify that there is network connectivity between the DPM server and the domain controller.
Solution: Install manually DPM agent. Then use this Powershell script (from bin folder): .\Attach-ProductionServer.ps1 (dpm server) (target server) username password domain

 

DPM Error ID 36

Error description: DPM cannot access the (vmname) because part of the path has been deleted or renamed. Check the path and enter it again.

Solution: reinstall DPM agents on all cluster’s nodes

This article describing this issue – http://dmitryivakin.info/microsoft-system-center/dpm/dpm-2012-r2-ur13-can-not-add-clustered-vms-to-protection-group-id-36/

 

DPM Error ID 60

Error description: the protection agent on (host name) was temporarily unable to respond because it was in an unexpected state. (ID 60 Details: Internal error code: 0x809909B0).

Solution: restart all COM+, VMM agent, Hyper-V management service on host

This article describing this issue – https://support.microsoft.com/en-us/kb/971411

 

DPM Error ID 104

Error description: you can’t backup VM, it’s always failing with error: an unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041010) (0x80041010)).

Solution: check DPM and Host OS version. Probably you’re trying to backup Hyper-V Win 2012 R2 with DPM 2012 SP1. It won’t work. Use DPM 2012 R2.

 

One more explanation for DPM Error ID 104

Error description:  You may have the following errors:

An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041001) (0x80041001))

or

An unexpected error occurred while the job was running. (ID 104 Details: The paging file is too small for this operation to complete (0x800705AF))

or

An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041001) (0x80041001))

Solution:

You have to restart WMI service on protected data source, then re-run backup jobs again

 

DPM Error ID 2033 - 0x80070522

Error description: DPM encountered an error while performing an operation for (file server name) on (host server name) (ID 2033 Details: A required privilege is not held by the client (0x80070522))
Solution: Usually it could happen with VMs in cluster on SMB share. The agent needs to be installed on the Hyper-V server, or on each server in the Hyper-V cluster. On the remote SMB file server, if SMB is deployed in a cluster, install the DPM protection agent on all SMB file server cluster nodes.
Enable the File Server VSS Agent service on each SMB server—Add it in Add roles and features > Select server roles > File and Storage Services > File Services > File Service > File Server VSS Agent Service. Hyper-V nodes and DPM server machine$ account should have full permissions on the specific Remote SMB File share. Restart agents on all nodes.

 

DPM Error ID 2033 - 0x80070017

Error description: VM backup failed with error: DPM encountered an error while performing an operation for (VHD drive location) on (Hyper-V node) (ID 2033 Details: Data error (cyclic redundancy check) (0x80070017)). VM storage migration also failed with the same error.
Solution: The VHD or host drive has file system inconsistency. In our case it was server crash. Make sure no bad sectors on physical drives and no VMs running on it.

Run chkdsk /f on the VHD / host disk to fix the NTFS errors.

 

DPM Error ID 30111

Error description: some VMs located on Hyper-V cluster won’t backup and generated this kind of error: The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError: The writer experienced a non-transient error.  If the backup process is retried, the error is likely to reoccur.  (0x800423F4)). All other VMs located on the same Hyper-V host can backup. Vssadmin command shows Hyper-V VSS provide is in failed state. Restarting vmms.exe won’t solve this issue, after running backup task VSS provide failing again.
Solution: In VMM, VM properties, Integration Services just disable and enable Backup (volume snapshot). After this run consistency check on DPM. Sometimes helping to migrate VM to other host.

 

DPM Error ID 30112

Error description: DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried,the error may not reoccur (0x800423F3)). Job failed, output from “vssadmin list writers” shows Exchange writer is failed
Solution: you have to restart Exchange writer.

For clustered environment:

  1. Check if current server is passive node (Failover Cluster Manager, Services and Applications,  current owner is the active node)
  2. Go to the services, restart MS Exchange Replication service
  3. Re-run backup tasks
  4. Optionally you can check status / memory usage of DPM agent (DPMRA service).

 

DPM Error ID 30134

Error description: You have the following error against of DPM replica. Replica is in inconsistent state and can’t be synced.
DPM failed to clean up data of old incremental backups on the replica for Exchange Mailbox Database (Database name) on (Server name). Synchronization will fail until the replica cleanup succeeds. (ID 30134 Details: The file or directory is corrupted and unreadable (0x80070570))

Solution: the volume where is replica is located is corrupted and need to be checked.

With SQL Studio

Run this query on SQL server and define mapping between replica and volume guid. You will need it to run chkdsk utility.

use DPMDB
select ag.NetbiosName, ds.DataSourceName, vol.MountPointPath, ds.DataSourceId, vol.GuidName
from tbl_IM_DataSource as ds
join tbl_PRM_LogicalReplica as lr
on ds.DataSourceId=lr.DataSourceId
join tbl_AM_Server as ag
on ds.ServerId=ag.ServerId
join tbl_SPM_Volume as vol
on lr.PhysicalReplicaId=vol.VolumeSetID
and vol.Usage=1
order by NetbiosName

You will get result something like this:
NetbiosName DataSourceName MountPointPath DataSourceId GuidName
EX10MBOX1J MBOX1DB9 Microsoft Exchange Replica Writer\vol_2058e37d-a79f-4c7d-b761-3add54a005b6 65610ECA-6541-44D5-B49E-803707D032E1 \\?\Volume{f430a058-b68a-11e4-93fb-a0369f141476}\

The name of volume is in GuidName column.

 Open cmd under admin, run the command chkdsk /f \\?\Volume{f430a058-b68a-11e4-93fb-a0369f141476}

Wait till it fix an errors and run again consistency check.

If it doesn’t help, you have to re-create the replica.

Without SQL Studio
Also there is an easy way to find desired volume for checking.
Go to Protection Group, select replica, click on “Click to view details”. Copy/paste replica’s path to notepad.
Open CMD, run mountvol. Then you will find the path from Notepad in mountvol output.
Then run chkdsk as it described above.

 

You may also like

5 Comments

  1. Hi Dmitry,
    I am getting different version of DPM Error ID 104.
    Details of my Error:
    An unexpected error occurred while the job was running. (ID 104 Details: Access Denied (0x80070005). Have you come across any solution. Thanks

    1. Hi BMV!
      Do you have any errors when you refresh agent on DPM server? What version of DPM and datasource are you using?

      Best regards,
      Dmitry

  2. Hi,

    File server drive running smoothly for many weeks now fails with ID 30134. I tried the recommended action here but no volume is returned thus I cannot chkdsk problematic volume.

    Is there another way to view this?

    1. My apologies. I didn’t see the second part about without SQL. However the volume is still not listed. It is ReFS. The volume appears to be inaccessible. It does not appear in C:\Program Files\Microsoft System Center 2016\DPM\DPM\Volumes\Replica unless running consistency check in which case it appears briefly then disappears when job fails.

      Why does this happen? Will be the second time having to create the replica? And I suspect again in the future as well.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.