A VM has the following configuration:
2 vCPU4 GB RAM
HDD1 10 GB
HDD2 20 GB
A vSphere Administrator creates a snapshot of a powered off VM.
What is the maximum size of all of the snapshots that can be consumed on the datastore?
A.
30 GB
B.
100% of the datastore minus 512 bytes
C.
34 GB
D.
50% of the datastore
I Think C.
https://kb.vmware.com/s/article/1003755
Virtual machine without snapshots
Use this general formula to calculate the disk space required:
(Size of virtual machine’s hard disk(s)) + (size of RAM for virtual machine) + ( 100 MB for log files per virtual machine) is the minimum space needed for each virtual machine.
When you take a snapshot of a powered off machine the option “Snapshot the virtual machine’s memory” is greyed out, so i think option A.
Definitely A
extract from vsphere 5.1 documentation:
A .vmsn file that includes the active state of the virtual machine. Capturing the memory state of the virtual machine lets you revert to a turned on virtual machine state. With nonmemory snapshots, you can only revert to a turned off virtual machine state. Memory snapshots take longer to create than nonmemory snapshots. The time the ESX host takes to write the memory onto the disk is relative to the amount of memory the virtual machine is configured to use.
https://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.vsphere.vm_admin.doc/GUID-38F4D574-ADE7-4B80-AEAB-7EC502A379F4.html
Extract from link below:
If you choose to store the memory state, this file will be slightly larger than the amount of RAM that has been assigned to the VM, as the entire memory contents, including empty memory, is copied to this file. If you do not choose to store the memory state of the snapshot then this file will be fairly small — under 32 KB.
http://searchvmware.techtarget.com/tip/Understanding-the-files-that-make-up-a-VMware-virtual-machine
Tricky question…
According to https://kb.vmware.com/s/article/1015180
Child disks and disk usage
It is important to note these points regarding the space utilization of child disks:
…
Child disks are known to grow large enough to fill an entire datastore, but this is because the LUN containing the datastore was insufficiently large to contain the base disk, the number of snapshots created, and the overhead and .vmsn files created.
…
And look at the picture
https://kb.vmware.com/servlet/rtaImage?eid=ka134000000RlQK&feoid=00N34000005kd1R&refid=0EM34000000IeRx
all child snaps refer to the parent’s snapshots and it means that every snapshot can be as large as base vmdk.
I think the answer is C