none
DPM Jobs failing for only one Hyper-V VM RRS feed

  • Question

  • We have a DPM 2016 Server that is configured for the VM Cluster Level Protection by installing the DPM Agents in all of the Nodes( Hyper-V Hosts) of the Cluster. And till now the DPM Backup jobs for all of the VM's are fine except only one Windows VM.

    For that single VM it is showing the error as "Replica Inconsistent" I have tried running the Consistency Checks but again it is going back to the same error.

    Below is the Details of the error

    The replica of Microsoft Hyper-V RCT\VMNAME1 on SCVMM VMNAME1 Resources.cluster.domain.top is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent. 

    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106) 

    An unexpected error occurred while the job was running. (ID 104 Details: Incorrect function (0x80070001))

     I have tried by disabling and enabling the  “Backup (Volume shadow copy)”  in the Hyper-V Integration Services of the VM by following the below steps. But No Luck.

    Step1:- The trick is to first uncheck the Integration Service “Backup (Volume shadow copy)”

    Step2:- Run a backup / consistency check

    Step3:- And the recheck the backup service.

    Please help me in this regard.!!!

    Tuesday, October 15, 2019 2:26 PM

Answers

  • Hello,

    Thanks for your reply!

    The issue seems to be resolved after removing and re-adding the VM to the protection group twice.

    and removal and re-adding from protection group was performed after following the below steps.

    Tried by disabling and enabling the  “Backup (Volume shadow copy)”  in the Hyper-V Integration Services of the VM by following the below steps.

    Step1:- The trick is to first uncheck the Integration Service “Backup (Volume shadow copy)”

    Step2:- Run a backup / consistency check

    Step3:- And then recheck the backup service

    Now the VM Status seems to be OK.



    • Marked as answer by SANDEEP7760 Thursday, October 17, 2019 2:13 AM
    • Edited by SANDEEP7760 Thursday, October 17, 2019 2:21 AM
    Thursday, October 17, 2019 2:13 AM

All replies

  • Hello,

    Could you please provide some more information about your DPM and Hyper-V environments?

    • What build of DPM are you using?
    • What is the Hyper-V hosts operating system version?
    • What is the Hyper-V configuration version of the problematic guest virtual machine?
    • Was the problematic Hyper-V guest virtual machine upgraded or migrated from an older Hyper-V?

    I would also suggest you to check the DPM logs on both the DPM server and the Hyper-V hosts.

    DPM server

    • %ProgramFiles%\Microsoft System Center 2016\DPM\DPM\Temp\MSDMPCurr.errlog

    Hyper-V hosts

    • %ProgramFiles%\Microsoft Data Protection Manager\DPM\Temp\DPMRACurr.errlog

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, October 15, 2019 2:34 PM
  • Hello,

    Thanks for your reply!

    The issue seems to be resolved after removing and re-adding the VM to the protection group twice.

    and removal and re-adding from protection group was performed after following the below steps.

    Tried by disabling and enabling the  “Backup (Volume shadow copy)”  in the Hyper-V Integration Services of the VM by following the below steps.

    Step1:- The trick is to first uncheck the Integration Service “Backup (Volume shadow copy)”

    Step2:- Run a backup / consistency check

    Step3:- And then recheck the backup service

    Now the VM Status seems to be OK.



    • Marked as answer by SANDEEP7760 Thursday, October 17, 2019 2:13 AM
    • Edited by SANDEEP7760 Thursday, October 17, 2019 2:21 AM
    Thursday, October 17, 2019 2:13 AM