CV0-003 · Question #453
An administrator is performing a migration of a physical cluster that uses boot from SAN into private cloud. The systems administrator needs to minimize the downtime required. Which of the following…
The correct answer is C. P2V with copy of the LUNs into data stores for hypervisor access. For a boot-from-SAN physical cluster migration to a private cloud, copying the SAN LUNs into hypervisor datastores minimizes downtime by converting storage into a hypervisor-native format while the source remains available.
Question
An administrator is performing a migration of a physical cluster that uses boot from SAN into private cloud. The systems administrator needs to minimize the downtime required. Which of the following migrations is the BEST option for the systems administrator to use?
Options
- AP2V with cold system cloning on the storage infrastructure.
- BP2V with storage migration on the hypervisor.
- CP2V with copy of the LUNs into data stores for hypervisor access.
- DP2V with raw device mapping/pass-through LUNs on the storage system.
How the community answered
(49 responses)- A14% (7)
- B29% (14)
- C49% (24)
- D8% (4)
Why each option
For a boot-from-SAN physical cluster migration to a private cloud, copying the SAN LUNs into hypervisor datastores minimizes downtime by converting storage into a hypervisor-native format while the source remains available.
Cold system cloning requires the physical server to be fully powered off for the entire cloning duration, producing the maximum possible downtime rather than minimizing it.
Storage migration on the hypervisor requires the P2V conversion to complete first before storage can be relocated, adding sequential steps that extend the total downtime window.
Copying the SAN LUNs into hypervisor datastores converts the existing boot volumes into a format the hypervisor can manage natively, allowing VMs to be created from the migrated data without dependency on the original SAN infrastructure. This method permits the LUN copy operation to occur while the physical system remains partially operational, reducing the offline window to the final cutover switchover only. Once the LUNs are in the datastore, the hypervisor manages I/O directly, eliminating the SAN boot dependency and completing the true P2V migration.
Raw device mapping or pass-through LUNs keep a direct dependency on the original SAN infrastructure rather than migrating the data into the private cloud, leaving the environment exposed to the same physical SAN constraints post-migration.
Concept tested: P2V migration of boot-from-SAN clusters minimizing downtime
Source: https://docs.vmware.com/en/VMware-vCenter-Converter-Standalone/6.2/com.vmware.vcenter.converter.doc/GUID-B5596733-3D6D-4C4E-9B6E-F4FFD7F85CBF.html
Topics
Community Discussion
No community discussion yet for this question.