A vSphere administrator needs to enable Fault Tolerance on a virtual machine.
When performing a Storage vMotion migration, which setting should the vSphere administrator
change in the virtual machine’s disk format to ensure it meets Fault Tolerance requirements?
A.
Thick Provision Eager Zeroed
B.
Thick Provision Lazy Zeroed
C.
Thin Provisioned
D.
Thin Provision Eager Zeroed
Explanation:
A is correct
Thick Provision Eager Zeroed disk that supports clustering features such as Fault Tolerance.
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-4C0F4D73-82F2-4B81-8AA7-1DD752A8A5AC.html
0
0
Storage vMotion is not supported with FT VMs. so what’s storage vmotion doing here?
0
0
I agree. The question is poorly designed. “Snapshots, storage vMotion, linked clones, VCB backups” not supported with FT.
However, if the goal of this question was to ask the disk type needed for FT, then it would be A.
0
0
i think he is only asking about FT requirements , you can perform the storage vMotion action if you temporarily turn off the FT, and when it gets complete, you can turn FT back on.
0
0
I read the question this way:
The admin needs a VM to be FT.
The existing machine’s disk format is apparently not compatible with FT so migrating to another data store and changing the format to Thick-eager will make the format compatible. The admin can then enable FT (if all other requirements are met). This question is only concerned with disk compatibility so our answer is A.
They should have just asked what disk type is compatible with FT and skipped the extraneous info.
0
0
yes Bob that is the correct point of view
0
0
You need to Storage vMotion a VM to convert it’s disk format.
The VM needs a Thick Eager-Zero format before FT can be enabled
Therefore, A is answer
0
0
You can certainly see your skills in the work you write. The arena hopes for more passionate writers such as you who aren’t afraid to say how they believe. All the time follow your heart.
http://www.bastcilkdoptb.com/
0
0