none
Backing up fixed size .vhd's RRS feed

  • Question

  • When you back up a child partition via a hyper-v host and the VM has fixed disk's. The replica volume is automatically set to volume size * 1.5

     

    In other words a fixed size vhd of 100GB will have a 150GB replica volume created.  

    If i was backing up the computer from a agent inside the VM i could understand why the replica volume is automatically set to 1.5 the size, since the data amount is sure to expand. But when youre backing up a VHD that has a fixed size, that replica is NOT going to change.

    Is there a way to get around this? If you try to shrink the replica youll get an error saying X GB doe not meet the minimum allocation value.

    When you have alot of production servers (100+) Then this is getting abit exessive in terms of wasted space.

    Like 33% , 100 servers with 100GB disks is 5 TB of not useable backup space. 

     

    Im not talking about the recoverypoint volume here, of course that one is going to expand.

    One should think think that the DPM and agents should be hyperv / vhd aware, and be able to set a fixed vhd  to a fixed size replica volume?

     

    • Moved by Larry Yin Wednesday, March 28, 2012 11:20 PM (From:DPM 2012 Beta - Locked)
    Monday, October 31, 2011 6:40 PM

Answers

  • [Satish_MSFT]
    Yes, It is a  valid concern. Currently in  DPM ,Fixed VHD is treated in par with other application data.
    But at the  same time the extra space allocated can act as buffer for  VM snapshots(AVHDs) or additional VHDs that gets added afterwards.
    The workaround currently available is only to allocate storage  approriately while PG is created.
    ** As is provided without warranties and confers no rights **
    • Marked as answer by Fredrik Weme Thursday, November 3, 2011 2:25 PM
    Thursday, November 3, 2011 1:43 PM

All replies

  • [Satish_MSFT]
    Yes, It is a  valid concern. Currently in  DPM ,Fixed VHD is treated in par with other application data.
    But at the  same time the extra space allocated can act as buffer for  VM snapshots(AVHDs) or additional VHDs that gets added afterwards.
    The workaround currently available is only to allocate storage  approriately while PG is created.
    ** As is provided without warranties and confers no rights **
    • Marked as answer by Fredrik Weme Thursday, November 3, 2011 2:25 PM
    Thursday, November 3, 2011 1:43 PM
  • Thank you for your response

    Thursday, November 3, 2011 2:25 PM