Physical to Virtual Machine Conversion Using Volume Shadow Copy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Converting physical machines to virtual machines is inefficient and often requires significant downtime and resource expenditure due to inconsistencies in file states, system registries, and disk drivers, making it difficult to create usable virtual machines without shutting down physical machines.
Innovation Solution
The method involves creating application- and file system-consistent snapshots of physical machine volumes using Volume Shadow Copy Service while the machine is online, transferring these snapshots to a virtual hard disk file, and modifying operational information to make the snapshots bootable, allowing for quick and efficient conversion without downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If physical machine conversion is performed using conventional methods (copying drive contents), then virtual machine creation is achieved, but file state inconsistencies and system registry errors occur
Solution Approach 1:
The patent applies preliminary action by creating a consistent snapshot of the physical machine's file system and registry before conversion begins. This snapshot captures the state at a specific point in time, ensuring consistency before any data transfer or modification occurs, thereby preventing file state inconsistencies in the resulting virtual machine
Solution Approach 2:
The patent introduces an intermediary conversion process that acts as a mediator between the physical machine and virtual machine creation. This intermediary layer handles the complexity of ensuring file system consistency, registry validation, and driver configuration, shielding the user from these complexities while ensuring reliable conversion
2Reliability
If physical machine is shut down for conversion, then consistent file states are achieved, but conversion time and downtime increase
Solution Approach 1:
The patent takes a preliminary snapshot of the file system in a consistent state before the conversion process begins. This allows the conversion to proceed without requiring the physical machine to be shut down, as the snapshot captures the necessary consistency information while the machine remains operational
Solution Approach 2:
The patent creates a copy of the physical machine's file system state through snapshot technology. This copy can be processed and converted to a virtual machine independently of the original physical machine's operational state, allowing conversion to occur without downtime while maintaining file state consistency
3Productivity
If hundreds of physical machines are converted manually, then conversion is achieved, but resource expenditure and time consumption increase significantly
Solution Approach 1:
The patent enables automated copying and conversion of physical machines to virtual machines through a standardized process. Once the conversion process is established for one machine, it can be replicated across hundreds of machines with minimal additional resources, dramatically increasing productivity while reducing per-machine resource expenditure
Solution Approach 2:
The patent creates a universal conversion framework that can handle multiple physical machines with different configurations through a single standardized process. The system automatically adapts to various machine types, operating systems, and hardware configurations, eliminating the need for manual customization for each conversion and enabling high-volume processing
Data Source
Figure 1A~1B
Figure 1C
Figure 2
AI summary
Physical (or prior virtual) machine volumes can be converted to virtual machines at a virtual machine host while the physical machines are running. In one implementation, a volume shadow copy service can be used to create an application (and/or file system)-consistent snapshot of one or more physical machine volumes while the one or more volumes are running. The snapshot data can then be transferred to a mounted virtual hard disk file (dynamic or fixed) at a virtual machine host. Operational information (e.g., boot record, system registry, drivers, devices, configuration preferences, etc.) associated with the virtual hard disk file and the operating system(s) within the virtual machine can then be modified as appropriate to ensure that the corresponding virtual machine is bootable and functional at the virtual machine host. The virtual hard disk file can then be un-mounted, and used as a new virtual machine.