Reboot of HyperV host causes subsequent recovery point jobs to fail for some protected VMs. Is this normal? RRS feed

  • Question

  • We have a DPM Server which protects several HyperV vm's in 2-node failover cluster.

    There is a total of 8 protected vm's on the cluster. These vm's do not have the DPM agent installed - it is the whole vm that is protected for each of them. There are additional vm's on the cluster that are protected via an installed agent.

    Two of the vm's had a recovery point scheduled a few hours after the host reboot. These two recovery point jobs both failed after 2½ minutes. And this caused a consistency check for both vm's.

    The errors were these:

    Change Tracking has been marked inconsistent due to one of the following reasons
    1. Unexpected shutdown of the protected server
    2. Unforeseen issue in DPM Bitmap failover during cluster failover of one or more datasources sharing the tracked volume. (ID 30501 Details: The parameter is incorrect (0x80070057))

    Is this normal?

    The other 6 vm's have not had recovery point jobs scheduled since the host reboot.

    DPM is 2012 R2 v. 4.2.1553

    All OS's are Windows Server 2012 R2.

    Thursday, September 15, 2016 4:59 PM

All replies

  • Trying to figure this out for myself. Well, our secondary server at the remote site had a power outage and now regularly scheduled jobs keep producing this error. Bit different situation but there's not much to found out about this it seems.. 
    Wednesday, December 7, 2016 4:53 PM
  • No, this is not normal.
    Thursday, December 8, 2016 2:45 PM
  • Thanks! I didn't think so.

    Any thoughts on how to fix it?

    Thursday, December 8, 2016 2:47 PM
  • A shot in the dark: Consistency check the datasource. Maybe it fixes itself.
    Thursday, December 8, 2016 5:02 PM
  • A consistency check is actually what DPM initiates on its own every time this happens
    Thursday, December 8, 2016 5:13 PM