You have a Hyper-V host named Server1 that runs Windows Server 2012.
Server1 hosts a virtual machine named VM1 that runsWindows Server 2012.
VM1 has several snapshots.
You need to modify the snapshot file location of VM1.
What should you do?
A.
Right-click VM1, and then click Export…
B.
Shut down VM1, and then modify the settings of VM1.
C.
Delete the existing snapshots, and then modify the settings of VM1.
D.
Pause VM1, and then modify the settings of VM1.
Explanation:
There is no need to shut down, delete,or pause.
Note:
* By default, the snapshots are stored in subfolderof the virtual machine’s folder called Snapshots. You can
change this setting and you can move snapshots using Live Storage Migration.
* Storage Live Migration provides the ability to move your virtual machine storage while your VM is running. In
comparison, Storage Live Migration is similar in offering to the VMware storage offering called vMotion. The
virtual hard disks used by a virtual machine can bemoved to different physical storage while the virtual machine
remains running making it unnecessary to take a virtual machine offline to move the VMs files to different
physical storage.
Wrong. You must delete current snapshot then you can change the location.
Agreed with seenagape!
How can I change the snapshot location from default
Answer:
The easiest way for you to do this (at this point) is to export the VM to D:\vms
Then import the VM from that location.
This will fix all of the snapshots, retain the snapshot history, and change the default snapshot location from this point moving forward.
After you complete the export and import and power on the new VM (to verify it is working). Then delete the vm from Hyper-v (wait for the background merge to complete) then delete the VHD that will be left over.
As you have discovered, the snapshot location for hte VM cannot be changed in mid-stream (after some have been created).
on a side note – you may run into problems in deleting the origional VMs due to the combination of low disk space and the default merge process.
The way to get around this is difficult to explain.
Let us know if you need a work around.
Brian Ehlert (hopefully you have found this useful)
Proposed as answer by Vincent HuModerator Tuesday, May 12, 2009 8:57 AM
Marked as answer by Vincent HuModerator Wednesday, May 13, 2009 8:49 AM
Tuesday, May 12, 2009 1:50 AM
Reply
Avatar of BrianEh
BrianEh
Avatar of BrianEh
Citrix Labs
(MCC, Partner, MVP)
Agree with both
An explanation I found:
“In order for snapshot file location to be changed, all previous snapshots need to be deleted”
I can confirm the answer is ‘C’ as I have just done this test on a Hyper-V server. Plus (just to pick) snapshots are called ‘Checkpoints’ in Hyper-V 2012.
Though the answer above is technically correct, there is a way to keep your snapshots/checkpoints if you want to move them. Export the VM. Then import the VM, and specify a new location. This will move the snapshots/checkpoints as well and retain them. Then, delete the old VM/VHDX from HyperV.
As a side note, this does also move the VM as well, which is why this may not be an available answer to this question.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/4fcf81f0-a635-4974-8e5e-cea4bd1103a4/how-can-i-change-the-snapshot-location-from-default?forum=winserverhyperv
Both A and C are correct, however A seems to me to be a fairly extreme method and the question doesn’t specify that we need to keep all the existing snapshots. So I’d still go with C.
Exactly – using A is terrible
only “C” I think
no way with A – export takes snaps also !!
ANSWER C (definitelly !)