Your network contains an Active Directory domain named contoso.com. The domain contains a server
namedServer1. Server1 runs Windows Server 2012 and has the Hyper-V server role installed. On Server1, you
createand start a virtual machine named VM1.
VM1 is configured as shown in the following table. You plan to create a snapshot of VM1. You need
torecommend a solution to minimize the amount of disk space used for the snapshot of VM1. What should
youdo before you create the snapshot?
A.
Shut down VM1.
B.
Decrease the Minimum RAM.
C.
Decrease the Maximum RAM.
D.
Configure VM1 to have a smaller virtual disk.
E.
Convert disk1.vhd to a dynamically expanding disk.
F.
Run the Stop-VM cmdlet.
G.
Run the Resize-VHD cmdlet.
H.
Run the Convert-VHD cmdlet.
Explanation:
Virtual machine snapshots are file-based snapshots of the state, disk data, and configuration of a
virtualmachine at a specific point in time.
You can take multiple snapshots of a virtual machine, even while it is running.
You can then revert the virtual machine to any of the previous states by App1ying a snapshot to the
virtualmachine.
Taking a snapshot of a VM is to in essence freeze the current state and make it a parent disk based on
currentstate, and at the same time create a child disk to capture all subsequent changes. – See more at:
Snapshots require adequate storage space. Snapshotsare stored as .avhd files in the same location at
thevirtual hard disk. Taking multiple snapshots canquickly consume a large amount of storage space.
When you use Hyper-V Manager to delete a snapshot, the snapshot is removed from the snapshot treebut the .
avhd file is not deleted until you turn off the virtual machine.
Each snapshot introduces a parent-child dependency of the runtime environment when the snapshot wastaken,
and over time a series of backups will results in amulti-level hierarchy of snapshots with nested
parentchilddependencies.
When you have systems that are required to be up and running 24/7 it basically throws away any use
thatsnapshots have. It seems somewhat ridiculous that you have to bring a system down to delete the
snapshotwhen one of the reasons you created the snapshot was to help reduce downtime in case something
goeswrong. It is even more ridiculous that if you don’t power down your system and wait for the vhd tomerge,
the snapshot will continue to grow until the systemcomes crashing down due to a lack of disk space!
(Microsoft does not recommend snapshots for production environments)
http://www.laneolson.ca/2009/10/09/hyper-v-snapshots-and-disk-space/ http://blogs.technet.com/b/yungchou/
archive/2013/01/23/hyper-v-virtual-hard-disk-vhd- operations-explained.aspx
http://zoom.it/12u8
http://www.server-talk.eu/wp-content/uploads/article_2010-05-28_02.png http://blogs.msdn.com/b/
virtual_pc_guy/archive/2009/04/15/what-happens-when-i-delete-a- snapshot-hyper-v.aspx
Answer shut down the VM before snapshot..
Was the VM running when you took the snapshot?
Here is a big one. If the VM was running the VM can be restored to that previously running state. Thus all that occupied memory space must be saved as well. Now, not only is the disk (potentially) using more storage, but the SQL instance in the VM was set to use 2Gb of RAM, and all of that memory space must be saved as well.
Hi there,
I´m pretty sure the correct answer would be E. convert the vmd to a dynamically expanding disk. Therefore the snapshot is only as big as the acctually used space. But this question is quite strange anyway, because it doesn´t state ,if there should be one or more answers be chosen and as well there are the same answers with different wordings (like shut down the vm oder run the stop-VM cmdlet, as well as convert the vmd file and run the convert-VHD cmdlet).
Stupid question, still I´d go for E.
Cheers, Michael
E is wrong. The size of the disk does not affect the size of the snapshot, because the snapshot (avhd(x)) is only the delta of the vhd(x).
I tend to A – shut down the VM due to the reason explained by Goose.
Thank you, I liked your explanation.
Answer should be A. Shut down VM1
A – Shutdown the VM:
http://technet.microsoft.com/en-us/library/dd560637%28v=ws.10%29.aspx
.
A
Hello very nice website!! Guy .. Excellent .. Amazing .. I will bookmark your site and take the feeds additionally?KI am glad to find so many helpful info here within the put up, we’d like develop more strategies in this regard, thank you for sharing. . . . . .