An administrator has been tasked with mitigating datastore capacity issues without datastore expansion.
Which vSphere Storage vMotion migration option would achieve this mitigation?
An administrator has been tasked with mitigating datastore capacity issues without datastore expansion.
Which vSphere Storage vMotion migration option would achieve this mitigation?
To mitigate datastore capacity issues without expanding the datastore, the administrator should use the thin-provisioned vSphere Storage vMotion migration option. Thin provisioning allows the virtual machine's disk to only consume the actual used space, rather than the fully provisioned size. This helps in conserving storage space, making it suitable for scenarios where the actual data usage is much smaller than the total provisioned capacity.
B. Thin-provisioned To mitigate datastore capacity issues without expanding the datastore, the administrator should use the vSphere Storage vMotion migration option called "Thin-provisioned." Explanation: Thin-provisioned: When using thin-provisioned storage vMotion, the virtual machine's disk is migrated to the destination datastore, but it only consumes the actual used space on the source datastore. It does not reserve the entire provisioned size of the virtual disk on the destination datastore. This migration option helps to conserve storage space on the destination datastore and is suitable for scenarios where the actual data usage is significantly smaller than the provisioned disk size.
BBB - Easy one