Automated Virtual Machine Backup Using Change Block Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current backup methods for virtual data centers are inadequate in terms of data security, resource optimization, and compliance with aggressive Service Level Agreements (SLAs), relying heavily on manual scheduling and hard-coded schedules, which can lead to sub-optimal storage usage and uncertain timely data backup.
Innovation Solution
An automated system utilizing change block technology (CBT) for dynamic backup and replication of virtual machines, allowing user-customized criteria-based data protection, with a polling engine to monitor and replicate VMs between vCenters, and the use of a cache device for efficient data transfer, especially to the cloud, ensuring robust security and timely data recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual scheduling and hard-coded schedules are used for backup operations, then backup operations can be performed with simple system configuration, but backup timing and storage usage become sub-optimal and cannot meet aggressive SLA requirements
Solution Approach 1:
The patent implements dynamic backup scheduling by replacing static hard-coded schedules with a polling engine that continuously monitors VM states and dynamically adjusts backup timing based on actual data changes, SLA requirements, and resource availability, thereby optimizing backup speed without requiring overly complex manual configuration
Solution Approach 2:
The system employs feedback mechanisms where the polling engine continuously monitors VM states, storage capacity, and backup status, then uses this feedback to dynamically adjust backup schedules and prioritize critical data, enabling the system to meet aggressive SLA requirements while maintaining manageable complexity through automated decision-making
2Reliability
If legacy backup methods with hard-coded schedules are used, then system configuration is straightforward, but storage resources are not optimized and critical data may not be backed up in timely manner
Solution Approach 1:
The backup system performs self-service by automatically monitoring VM states, determining which data requires backup, and executing backup operations without requiring continuous manual intervention or complex administrative management, thereby improving data security while keeping the system relatively simple to operate
Solution Approach 2:
The polling engine continuously monitors VM states and identifies data changes in advance, allowing the system to proactively initiate backup operations before SLA deadlines are approached, ensuring critical data is protected without requiring complex real-time decision-making during backup execution
3Loss of time
If dynamic change tracking and automated replication are implemented, then backup timing and storage optimization are improved, but system complexity increases
Solution Approach 1:
The patent segments the backup system into distinct functional components: a polling engine for monitoring, a change detection mechanism for identifying data modifications, and an automated replication system for executing backups. This segmentation allows each component to perform its specific function efficiently, reducing overall backup time while managing complexity through modular architecture
Solution Approach 2:
The polling engine acts as an intermediary between VM operations and the backup system, continuously monitoring for changes and triggering backup operations only when necessary. This intermediary layer reduces unnecessary backup operations, optimizes storage usage, and decreases overall backup time without requiring the entire system to become significantly more complex
Data Source
AI summary
Embodiments are described for automatic backup and replication of virtual machines in a virtual center. A system or processor-based operation defines policies governing backup conditions and criteria for backing up and recovering the virtual machines, continuously polls the VMs of the virtual center to determine the health or change in each virtual machine. A backup component backs up at least one VM by copying or transferring data including content and state information of the VM to a storage device or other virtual center. The system detects if a failure condition or change in excess of a defined threshold value exists for any virtual machine, and if so, initiates a recovery operation, and then sends a message to the system administrator regarding the backup and recovery.