none
VM Selection in protection group RRS feed

  • Question

  • We have recently updated to DPM 2012SP1. While going through and verifying VM's in a protection group, it gives me the ability to select them while already protected.

    The protection group lists the VM already protected, and in a OK state.

    Modifying the protection group, give me the option to add the VM.

    I didn't think it was possible to protect a VM more than once. Is this a known issue?

    There is a posting on VM's being added to more then one PG http://social.technet.microsoft.com/Forums/en-US/dpmhypervbackup/thread/b02f2eb9-256c-4243-8675-1de949cc323d is this how it happened?

     Thanks. 
    Wednesday, February 6, 2013 2:24 PM

All replies

  • Hi,

    This should not happen, can you please provide details of how the Hyper-V servers are configured and the steps you took to protect them at the start ? 

    IE: is this a cluster ?  Did you protect them when node1 owned them, now note2 owns them ?  Did you use VMM to migrate or move the VM's around. 

    Any details that would help us repro the condition. 


    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.

    Thursday, February 7, 2013 5:23 PM
    Moderator
  • It is a cluster. We have migrated to VMM 2012 SP1 and DPM 2012 SP1 from the 2012 version. The Hyper-V hosts are 2008 R2. All was good until the DPM upgrade. We do use VMM to migrate the VM's but in the past this problem didn't arise.

    Does that give you more info? What else would you like to know?

    Thursday, February 7, 2013 5:26 PM
  • Hi,

    Do you have VMM tracking enabled on the DPM Server ?

    http://technet.microsoft.com/en-us/library/hh757866.aspx#bkmk_protectvmwithlivemigration

    see Protecting Hyper-V machines using Live Migration section.

    VMM Tracking
    The other new functionality for DPM 2012 SP1 in relation to Hyper-V protection is in relation to following movement of VMs.  Windows 2012 allows users to move a VM from a stand alone Hyper-V server to another or into a cluster.  DPM can now integrate with VMM to follow this movement and continue protection of a protected VM.
    To allow DPM to track VMs across multiple Hyper-V servers, the following steps must be taken.

      Warning:  The DPM server, VMM server and Hyper-V hosts should be in the same domain.


    Users should create separate protection groups for protecting virtual machines hosted on Windows Server 2012.

    1. Install the DPM protection agent on all the computers that will host the virtual machine.
    2. Install the VMM console on the DPM server to allow DPM server to talk to VMM server.

      Note:
    This will not be the VMM server managing Hyper-V, but the VMM bits need to be installed for DPM to leverage.


    3. VMM Console should be installed on the DPM server in the default location, that is, [C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager]. If VMM Console is installed in any other location then the Live Migration scenario will not work.
    4. Copy VmmPowershellWrapper.exe from DPM\bin to C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin folder.
    5. Add DPMMachineName$ account as an Administrator in the VMM server Administrator Role.
    6. Set Global Property in DPM server for the KnownVMMServerName.  Use a DPM Management Shell to run:

    Set-DPMGlobalProperty -dpmservername <dpmservername> -knownvmmservers <vmmservername>.


    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.


    Thursday, February 7, 2013 5:44 PM
    Moderator
  • Yes, that is enabled. But doesn't that only work if the hosts are 2012?
    Thursday, February 7, 2013 5:45 PM
  • Yes, that is correct, but another variable that needs to be taken into consideration for the repro.  Anything else you can tell me about your configuration ?

    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.

    Thursday, February 7, 2013 5:49 PM
    Moderator
  • We are doing D2D2T, using Equallogic Hardware VSS snapshots, to some Dell MD1000's.

    I don't know what else you would need to know. Feel free to ask if you need any other details.

    Thursday, February 7, 2013 5:53 PM
  • Hi,

    OK, Good news - we were able to reproduce your behavior in a lab and are investigating.  At this time, it just seems to be a GUI bug, where it's not filtering the protected VM's properly, but should not let you actually protect it more than once.

    Please let me know if that is NOT the case for you.


    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.

    Friday, February 8, 2013 3:44 PM
    Moderator
  • I have not tried to protect an already protected VM. I have read other postings on how some got protected twice, and then they ran into other problems. I'll wait until there is a fix.
    Friday, February 8, 2013 4:56 PM
  • Has there been any progress on this issue?
    Thursday, April 25, 2013 5:32 PM
  • Hi,

    There were two different scenarios in this post.

    1) Protect a VM from a DPM server. Open Modify PG wizard and then run an Inquiry. The user is allowed to select the same VM again.

     Impact - This is purely a GUI issue. The customer might feel confused with this behavior, However if he continues and selects that VM and protects it, there is no Impact.

    Status - It is an open item to be fixed in Vnext.

    User action - none.

    2) Protect a HA virtual machine VM1.CL1 from a DPM server. Do NOT configure Live Migration tracking on the DPM server.
        Perform Migration from CL-1 to CL-2. [The host OS can be Win2K8 R2 or Win 2012]
        Create a new PG in the same DPM server and try protecting the VM1.CL-2
        The user is allowed to select the same VM again and create PG. Now when he tries to delete the older VM from PG, it fails with error 157.

     Impact - The customer is unable to Stop-Protect a VM which does not exist in the Hyper-V host.

    Status - This is by design if you do not enable Live migration tracking.

    User action - enable Live migration tracking - see http://technet.microsoft.com/en-us/library/hh757866.aspx#bkmk_protectvmwithlivemigration


    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.

    Thursday, April 25, 2013 7:34 PM
    Moderator