none
Secondary protection of Hyper-V resource - scheduled synchronization fails with 30228, but consistency check always succeeds RRS feed

  • Question

  • Scheduled recovery points of Hyper-V VMs on the primary DPM 2012 server succeed, but one particular server's scheduled "recovery points" (although all it runs are Synchronization jobs) fails with message like the following after only a few seconds:

    This replica of Microsoft Hyper-V\Backup Using Child Partition Snapshot\server(vsvr1.domain.com) on primarydpm.domain.com is not consistent with the protected data source.

    DPM has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. (ID 30228).

    BUT, manually running a consistency check ALWAYS works and follow-up with a manual recovery point does a successful synchronization and the recovery point is available.

    At one point, the disk partition within the Hyper-V VM was extended, but that was months ago and the primary DPM server doesn't have any issue with protecting the resource.

    So, I'm looking for some option to get the secondary DPM server to think that has consistent protection for more than a few hours (manual consistency checks work, but scheduled recovery points fail).

    Wednesday, July 25, 2012 1:42 AM

Answers

  • Hi,

    Please try removing that problematic server from the protection group and then reprotect it to see if that clears it up.  That should cause a full re-enumeration of that VM's location and details and build new job schedules using the new details.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, July 25, 2012 9:24 PM
    Moderator

All replies

  • Hi,

    Please try removing that problematic server from the protection group and then reprotect it to see if that clears it up.  That should cause a full re-enumeration of that VM's location and details and build new job schedules using the new details.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, July 25, 2012 9:24 PM
    Moderator
  • Since Im having the same issue, Im asking here. If it isnt suitable ill repost in a new thread.

    We upgraded our dpmservers (hosts from 2008r2 > 2012 and dpm 2012 > 2012 sp1 ru3 ).

    And upon re-establishment of agents, we get this 30228 on all secondary protection. Our secondary dpm can only backup dpmdb from the primary servers, but cant backup secondarly.

    I've taken PS out of PG, and also threw the disk replica on the secondary server away without change.

    Consisteny checks is ok, but recoverypoints fails.

    Its a general failure, no specific PG or WL, and we've got Three primaries against one secondary which all fails in the same way


    Ivarson


    • Edited by Ivarson Sunday, October 6, 2013 9:36 PM
    Sunday, October 6, 2013 9:34 PM
  • HI,

    Would need failed job details and logs to see the cause of the failures, please open a support case to help troubleshoot and resolve your issue. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, October 7, 2013 2:37 PM
    Moderator