none
DPM 2010 - HyperV R2 VM Backup RRS feed

  • Question

  • Hi,

    I want to backup a Virtual Machine in HyperV on 2008 R2.  This virtual machine is a file server that has 9TB of storage attached to it.  The OS is on one volume and the storage is on 5 other separate volumes for a total of 6 disks within that VM.  What would be the best way to backup this Virtual Machine and data using DPM?

    Thanks!

    Sunday, July 4, 2010 1:06 AM

Answers

  • Hi,

    With that much data, it would be best to protect the data directly by installing the DPM agent inside the guest and protect it like a physical server.  The reason I say that is because the DPM Volume filter can keep track of file changes inside the guest and only transfer the data it knows changed. It can do this more effeciently than protecting the guest as a VM.   When DPM protects VM's, it does so by performing a targeted Consistency check between the .VHD on the host and that on the DPM replica, and that CC is not as effecient or as fast as protecting file data directly using an agent in guest.  To protect the O.S., protect the systemstate or BMR if Windows 2008.

     

     

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Sunday, July 4, 2010 4:37 PM
    Moderator
  • Hi,

    You can accomplish this by making the 5 data disks pass thru disks, meaning you create 5 LUNS on back end SAN storage (or local raid disks) and expose them to the host, so now the host sees the 5 physical disks. Re-configure the guests to use the 5 physical disks instead of using .VHD files. Inside the guest, create the volume(s) in the new disks and copy your data to the new volume(s). Now you can protect the guest as a VM because DPM will not backup data located on pass thru disks.  So now you are protecting the Operating System disk as a VM, but protecting the data on the pass thru disks as file data through the DPM agent installed in the Guest.

    System state consists of only the following components:

    Component

    When this component is included in System State?

    Registry

    Always

    COM+ Class Registration database

    Always

    Boot files, including the system files

    Always

    Certificate Services database

    If it is a Certificate Services server

    Active Directory directory service

    If it is a domain

    SYSVOL directory

    Only if it is a domain controller

    Cluster service information

    If it is within a cluster

    IIS Metadirectory

    If it is installed

    System files that are under Windows File Protection

    Always

    BMR consists of System State plus all critical volumes (C: volume plus any volumes hosting a systemstate component.)

    Both systemstate and BMR use the Windows backup feature to do the backup, then DPM protects the backup.  BMR does not require any local storage on the protected machine, window backup writes directly to the DPM replica volume via UNC share created when BMR is protected.  System State backup (without BMR) requires ~10GB local storage on the protected server and will be located on the volume with the most free space at the time of protection.  You can move that location if you wish anytime you like. 

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Caleb44 Tuesday, July 6, 2010 2:31 PM
    Monday, July 5, 2010 12:58 AM
    Moderator

All replies

  • Hi,

    With that much data, it would be best to protect the data directly by installing the DPM agent inside the guest and protect it like a physical server.  The reason I say that is because the DPM Volume filter can keep track of file changes inside the guest and only transfer the data it knows changed. It can do this more effeciently than protecting the guest as a VM.   When DPM protects VM's, it does so by performing a targeted Consistency check between the .VHD on the host and that on the DPM replica, and that CC is not as effecient or as fast as protecting file data directly using an agent in guest.  To protect the O.S., protect the systemstate or BMR if Windows 2008.

     

     

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    Sunday, July 4, 2010 4:37 PM
    Moderator
  • Good suggestions.  Thank you Mike.  I have several follow up questions.

     

    1. Can I backup just the OS VHD as a VM backup?  (This would be ideal for a quick restore of the OS.  Then the data could be restored independently.)

     

    2. Can you tell me what the difference between BMR and system state is?

    Sunday, July 4, 2010 6:50 PM
  • Hi,

    You can accomplish this by making the 5 data disks pass thru disks, meaning you create 5 LUNS on back end SAN storage (or local raid disks) and expose them to the host, so now the host sees the 5 physical disks. Re-configure the guests to use the 5 physical disks instead of using .VHD files. Inside the guest, create the volume(s) in the new disks and copy your data to the new volume(s). Now you can protect the guest as a VM because DPM will not backup data located on pass thru disks.  So now you are protecting the Operating System disk as a VM, but protecting the data on the pass thru disks as file data through the DPM agent installed in the Guest.

    System state consists of only the following components:

    Component

    When this component is included in System State?

    Registry

    Always

    COM+ Class Registration database

    Always

    Boot files, including the system files

    Always

    Certificate Services database

    If it is a Certificate Services server

    Active Directory directory service

    If it is a domain

    SYSVOL directory

    Only if it is a domain controller

    Cluster service information

    If it is within a cluster

    IIS Metadirectory

    If it is installed

    System files that are under Windows File Protection

    Always

    BMR consists of System State plus all critical volumes (C: volume plus any volumes hosting a systemstate component.)

    Both systemstate and BMR use the Windows backup feature to do the backup, then DPM protects the backup.  BMR does not require any local storage on the protected machine, window backup writes directly to the DPM replica volume via UNC share created when BMR is protected.  System State backup (without BMR) requires ~10GB local storage on the protected server and will be located on the volume with the most free space at the time of protection.  You can move that location if you wish anytime you like. 

     


    Regards, Mike J [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Caleb44 Tuesday, July 6, 2010 2:31 PM
    Monday, July 5, 2010 12:58 AM
    Moderator
  • Thanks for all your help Mike.  You have been most helpful.
    Tuesday, July 6, 2010 2:32 PM