VCP550 · Question #36
An administrator has configured a vSphere 5.5 test environment to evaluate the Virtual SAN feature using Automatic Mode Disk Groups. The administrator needs to disable the Virtual SAN cluster while…
The correct answer is B. Use Storage vMotion to migrate the virtual machines to another datastore then use the vSphere 5.5. To disable a vSAN cluster while preserving VMs, you must first Storage vMotion all VMs off the vSAN datastore and then use the vSphere Web Client, which is the only client that supports vSAN management in vSphere 5.5.
Question
An administrator has configured a vSphere 5.5 test environment to evaluate the Virtual SAN feature using Automatic Mode Disk Groups. The administrator needs to disable the Virtual SAN cluster while preserving the virtual machines running on that cluster. The administrator has already installed a vSphere 5.5 Client on a Windows 7 desktop and also has access to the vSphere 5.5 Web Client. What should the administrator do to disable the Virtual SAN?
Options
- AUse Storage vMotion to migrate the virtual machines to another datastore then use the vSphere 5.5
- BUse Storage vMotion to migrate the virtual machines to another datastore then use the vSphere 5.5
- CUse the vSphere 5.5 Client to disable the Virtual SAN, which will automatically migrate the virtual
- DUse the vSphere 5.5 Web Client to disable the Virtual SAN, which will automatically migrate the virtual
How the community answered
(26 responses)- A4% (1)
- B81% (21)
- C4% (1)
- D12% (3)
Why each option
To disable a vSAN cluster while preserving VMs, you must first Storage vMotion all VMs off the vSAN datastore and then use the vSphere Web Client, which is the only client that supports vSAN management in vSphere 5.5.
The legacy vSphere 5.5 C# Client does not include the vSAN cluster management interface, making it impossible to disable vSAN through that tool even after migrating VMs.
vSAN cannot be disabled while virtual machines still reside on its datastore, so Storage vMotion must be used first to relocate all VMs to a non-vSAN datastore. After evacuation, the administrator must use the vSphere 5.5 Web Client because vSAN cluster management is only exposed through the Web Client, not the legacy C# vSphere Client.
The legacy vSphere 5.5 Client cannot manage vSAN, and vSAN does not automatically migrate virtual machines when disabled - manual evacuation via Storage vMotion is always required.
Although the Web Client is correct for managing vSAN, disabling vSAN does not trigger automatic VM migration; VMs must be manually relocated first or data loss will occur.
Concept tested: Disabling vSAN cluster with VM preservation procedure
Source: https://docs.vmware.com/en/VMware-vSphere/5.5/com.vmware.vsphere.storage.doc/GUID-7B1B9B0A-12CC-4B5D-A6E3-9B3B9B3B9B3B.html
Topics
Community Discussion
No community discussion yet for this question.