Virtual Machine Backup via Write IO Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtual machine backup methods require significant downtime to replicate and transmit data, which can lead to substantial losses due to prolonged service disruptions and data loss when physical machines fail.
Innovation Solution
A backup method and system where a first virtual machine management module replicates write IO requests to a second virtual machine while running, allowing for continuous disk synchronization and snapshot operations during pause states, eliminating the need for data replication during downtime by using a second virtual machine management module to control data write operations and store dirty pages in a backup temporary storage area.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If data replication is performed during virtual machine downtime, then backup data consistency is improved, but backup time and service disruption are increased
Solution Approach 1:
The system performs preliminary data replication during the virtual machine running state before the actual backup operation. The first virtual machine management module replicates write IO request data to a second virtual machine management module while the first VM is still running, so that when the backup is initiated, the data is already prepared and consistent, eliminating the need for replication during downtime.
Solution Approach 2:
The system dynamically adjusts the backup process by pausing the virtual machine at appropriate checkpoints only when necessary for snapshot operations, rather than maintaining a static downtime approach. The pause duration is minimized by performing snapshot operations quickly on the second VM, and the system dynamically manages the transition between running and paused states to optimize backup efficiency.
2Manufacturing precision
If virtual machine is paused for snapshot operation, then data consistency is improved, but service availability is worsened
Solution Approach 1:
The second virtual machine management module serves as an intermediary that holds the replicated data and performs snapshot operations independently. When the first VM needs to be paused for consistency, the second VM (which has already received replicated data) performs the snapshot operation, minimizing the impact on service availability while ensuring data consistency.
3Reliability
If backup frequency is increased, then data loss prevention is improved, but system performance and IO load are worsened
Solution Approach 1:
The system maintains continuous data replication in the background during the virtual machine running state, so that backup operations can be performed frequently without requiring intensive data transfer at each backup moment. The useful action of data protection continues uninterrupted through ongoing replication, allowing frequent backups with minimal additional IO load.
Data Source
AI summary
A backup method and a backup system for virtual machines are provided. A first virtual machine management module replicates data of a write IO request of a first virtual machine to generate replication data, and the write IO request is configured to request a data write operation to a disk of the first virtual machine. The first virtual machine management module transmits the replication data to a second virtual machine management module while the first virtual machine is running. The second virtual machine management module receives the replication data and controls or performs a data write operation to a disk of the second virtual machine of the second virtual machine management module according to the replication data. When the first virtual machine is paused, the second virtual machine management module performs a snapshot operation on the disk of the second virtual machine to generate snapshot data.