High-Frequency Virtual Machine Restore Points via Metadata Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern computing systems face inefficiencies in processing high-frequency snapshots due to the combination of rapidly changing system data and slow-changing application configurations, leading to unnecessary processing, storage, and network bandwidth usage.
Innovation Solution
Implementing techniques to timestamp changes in application configuration metadata, allowing for reduced frequency of snapshots without losing data changes, by skipping duplicative snapshot operations and using asynchronous snapshot change detection to determine if metadata has changed since the last backup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If high-frequency snapshots are taken to capture rapidly changing system data, then data restoration capability is improved, but unnecessary processing of slow-changing application configuration data increases
Solution Approach 1:
The patent segments the snapshot data into two distinct categories: system data (rapidly changing) and application configuration data (slow-changing). By separating these data types, the system can apply different snapshot frequencies to each, taking high-frequency snapshots of system data while reducing the frequency of application configuration data snapshots, thereby improving processing efficiency without compromising restoration capability.
Solution Approach 2:
The patent implements dynamic snapshot frequency adjustment based on data change characteristics. System data undergoes frequent snapshotting due to its rapid change nature, while application configuration data is snapshot at lower frequencies since it changes slowly. This dynamic approach optimizes resource utilization by adapting snapshot operations to the actual change rates of different data types.
2Reliability
If high-frequency snapshots are taken to ensure near-zero data loss, then data protection is improved, but storage requirements and processing costs increase
Solution Approach 1:
The patent divides backup data into system data and application configuration data, applying different retention and snapshot strategies to each segment. This segmentation reduces overall storage requirements by avoiding redundant storage of frequently unchanged configuration data while maintaining high-frequency snapshots of critical system data for near-zero loss protection.
Solution Approach 2:
The patent changes the snapshot frequency parameter differently for system data versus application configuration data. By adjusting this parameter based on data type and change characteristics, the system achieves effective data protection with reduced storage consumption compared to uniform high-frequency snapshotting of all data.
3Reliability
If application configuration data is snapshot at high frequency along with system data, then complete system state capture is improved, but network bandwidth usage and communication overhead increase
Solution Approach 1:
The patent segments the data capture process into system data capture and application configuration data capture, with different frequencies for each. This allows complete system state capture to be achieved through high-frequency system data snapshots while reducing network bandwidth consumption by lowering the snapshot frequency for application configuration data.
Solution Approach 2:
The patent maintains continuous high-frequency snapshotting of system data to ensure complete and current system state capture, while applying less frequent snapshots to application configuration data. This continuous action on critical data ensures reliability without the full network overhead of frequent configuration data transfers.
Data Source
AI summary
Systems for application configuration backup and restore. Techniques establish high frequency restore points of application configuration metadata. Processing commences upon receiving instructions to periodically take snapshots of application configuration metadata. To avoid incurring unnecessary costs to process snapshots of application configuration metadata when the application configuration metadata is slow-changing, the method performs a low-cost check to get the latest update time of the application configuration metadata. That time is compared to the time of the most recent snapshot of the application configuration metadata. When the time of the latest update time of the application configuration metadata is equal to the time of the most recent snapshot of the application configuration metadata, then rather than incurring the cost of generating a duplicate snapshot, the method waits for a duration without generating a new snapshot. High frequency restore points for application configuration metadata are emulated by pointing to corresponding lower frequency snapshots.