An administrator needs to recover disk space on a previously-used thin provisioned virtual disk. The volumes where the administrator needs to recover the disk
blocks are on VAAI-compliant storage arrays.
Which two actions should the administrator take accomplish this task? (Choose two.)
A.
Perform a Storage vMotion to another volume in order to force free space recovery to occur.
This recreates the volume in a new location and recovers all unused space.
B.
Use VMware Converter to migrate the virtual machine to a new datastore. This will recreate the volumes and recover all unused space.
C.
Issue the vmkfstools -vmfs unmap command within the VMFS volume directory on the ESXi host console.
D.
Execute the esxcli storage vmfs unmap command.
Explanation:
Explanation/Reference:
B and D are correct.
B
http://www.vmware.com/pdf/convsa_55_guide.pdf
D
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513
A and D.
Because virtual disk is already thin, VMware Converter is not needed (it usabe only if virtual disk is thick and need to be converted to thin).
For reclaim volume space, you need to SvMotion virtual disk to another volume (A)
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004155
Unless you’re moving to a datastore with different block size, vMotion does NOT reclaim null blocks.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513
… However, UNMAP operations are still manual. This means Storage vMotion or Snapshot Consolidation tasks on VMFS do not automatically reclaim space on the array LUN.
B&C
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513
With the introduction of 62 TB VMDKs, UNMAP can now handle much larger dead space areas. However, UNMAP operations are still manual. This means Storage vMotion or Snapshot Consolidation tasks on VMFS do not automatically reclaim space on the array LUN.
Sorry B & D
The key point in this question is “VAAI-Compliance”. check this Knowledge base from VMware https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004155
“When the blocksizes of source and destination are equal, the new datamover (FS3DM) is used. FS3DM uses VAAI or just the software component. In either case, null blocks are not reclaimed.”
That means vMotion dosenot accomplish the required from the question. which make option A wrong
also, vmkfstools -vmfs unmap command doesn’t exist. option C is wrong
which leaves us with options A & D correct
You mean B and D
Thanks Khozi for the note.
yes B & D are
A,D because C is not a valid command and is this question saying I have to globally deploy and certify Converter product for such a simple requirement (RUBBISH) after I invest millions in VAAi storage.. and the most expensive SKU VMware have..
AD
When a virtual machine is migrated from a datastore or deleted, UNMAP is immediately called and space is reclaimed on the array.
In ESXi 5.5, vmkfstools -y is deprecated and is replaced by the esxcli storage vmfs unmap command. However, issuing UNMAP is still disabled by default and space reclamation can be done manually by running the esxcli storage vmfs unmap command.
BD;
While choosing between C and D is simple (there is no “vmkfstools -vmfs unmap” command), between A and B is tricky. I believe the reasoning is that Storage vMotion will not release all space that could be released (see https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004155), and this means that picking A and D will leave you with unused blocks on the destination datastore. Using VMware Converter will not copy unused blocks, and thus picking B and D will allow you to recover all space.