2V0-622 · Question #190
An administrator needs to migrate a legacy physical application server to a virtual machine within a vSphere 6 cluster. As part of the conversion, the administrator must reduce the size of the virtual
The correct answer is D. Use VMware Converter hot cloning with volume-based cloning at the file level.. When performing a P2V conversion that requires reducing disk size, file-level cloning must be used because it copies individual files rather than raw sectors, allowing the destination disk to be specified smaller than the source.
Question
An administrator needs to migrate a legacy physical application server to a virtual machine within a vSphere 6 cluster. As part of the conversion, the administrator must reduce the size of the virtual disks. What action should the administrator take to create a virtual machine with smaller virtual disks than the original physical server?
Options
- AShut down the physical server and use VMware Converter cold cloning with volume-based
- BUse VMware Converter hot cloning with volume-based cloning at the block level.
- CShut down the physical server and use VMware Converter cold cloning with volume-based
- DUse VMware Converter hot cloning with volume-based cloning at the file level.
How the community answered
(31 responses)- A3% (1)
- B6% (2)
- C6% (2)
- D84% (26)
Why each option
When performing a P2V conversion that requires reducing disk size, file-level cloning must be used because it copies individual files rather than raw sectors, allowing the destination disk to be specified smaller than the source.
Cold cloning with block-level volume cloning copies raw disk sectors in a 1:1 manner, which prevents reducing the destination disk size below the original physical disk size.
Block-level hot cloning duplicates raw disk blocks directly and cannot reorganize or reduce the target virtual disk size below the original physical disk size.
Cold cloning requires shutting down the source server, introducing unnecessary downtime when hot cloning is available, and block-level cloning still prevents disk size reduction because it duplicates raw sectors.
Hot cloning with file-level volume-based cloning allows VMware Converter to copy individual files to the destination VM rather than duplicating raw disk blocks, which enables specifying a smaller target virtual disk size. File-level cloning reorganizes data into the reduced destination space during the conversion process. Hot cloning also keeps the source physical server online throughout the conversion, avoiding unnecessary downtime.
Concept tested: VMware Converter P2V disk resize with file-level cloning
Source: https://docs.vmware.com/en/VMware-vCenter-Converter-Standalone/index.html
Topics
Community Discussion
No community discussion yet for this question.