A database administrator has requested that a virtual disk attached to a virtual machine running an
I/O intensive database application be fully provisioned. The virtual disk was initially thin
provisioned.
Which two methods would accomplish this task? (Choose two.)
A.
Use Storage vMotion and change the disk type to Flat.
B.
Use the Inflate option in the Datastore Properties.
C.
Use Storage vMotion and change the disk type to Thick Provisioned Lazy Zeroed.
D.
Use Storage vMotion and change the disk type to Thick Provisioned Eager Zeroed.
I believe the answers should be B & D.
B: “The inflated virtual disk occupies the entire datastore space originally provisioned to it”
http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-A7806753-F37C-4C0D-BABF-0A1AE2B0811C.html
C: Providing a Thick Provisioned Lazy Zeroed disk for I/O intensive DB doesn’t make any sense.
D: Think Provisioned Eager Zeroed is a no-brainer.
0
0
Agreed B & D
http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf
-page 186
“Inflate Thin Virtual Disks
If you created a virtual disk in the thin provision format, you can inflate it to its full size.
This procedure converts a thin disk to a virtual disk in thick provision format.”
-Unless this is a trick question and VMware meant to say “datastore properties”, in which case I don’t think you can inflate from there. You need to click into the datastore and right click the virtual file and hit inflate… this may make C the next best answer. I don’t think this is the case, but with VMware, who knows.
0
0
Why not B,C,D, since based on fact that these three ways all can convert vDisk from thin to thick.
0
0
Explanation:
Option B is correct:
Page 130 from vsphere-esxi-vcenter-server-50-storage-guide.pdf
Option D is correct:
Page 226 from vsphere-esxi-vcenter-server-50-storage-guide.pdf
0
0
Dummies – you don’t have an “Inflate option” in the datastore properties. It is possible via command line though.
0
0