VM Snapshot Backup Agent Avoiding Log Truncation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current snapshot backup systems in virtualized environments face challenges such as application-awareness protection, time windows for snapshot generation, and support for heterogeneous disks, leading to potential data loss or corruption due to failed backups and incomplete snapshots.
Innovation Solution
A data protection backup system with an in-guest data protection agent and a host-level snapshot data mover coordinates snapshot generation, extends time windows for snapshot completion, and intelligently manages disk types to ensure application-consistent backups, avoiding unwanted log truncation and excluding unsupported disks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the snapshot generation time window is extended to complete application-consistent backups, then backup completeness is improved, but system resource consumption and operational complexity increase
Solution Approach 1:
The system dynamically adjusts the snapshot generation time window based on application consistency requirements. The copy service monitors backup progress and extends the time window when needed to ensure application-consistent snapshots are completed, rather than using a fixed time window. This dynamic adaptation resolves the contradiction by allowing extended operation only when necessary for backup completeness.
Solution Approach 2:
The system performs preliminary actions by notifying applications of upcoming snapshot operations in advance, allowing them to prepare for consistent state capture. The copy service proactively manages the snapshot process, initiating preparations before the actual snapshot is taken, which ensures completeness without requiring excessive operational complexity during the snapshot execution itself.
2Measurement precision
If the copy service waits for snapshot completion confirmation, then backup accuracy is improved, but time window for snapshot generation is reduced
Solution Approach 1:
The copy service implements a feedback mechanism where it waits for confirmation that snapshot generation is complete before marking the backup as successful. This feedback loop ensures backup accuracy by verifying completion, while the service manages the time window efficiently by only waiting for essential confirmation signals, not indefinitely. The feedback resolves the contradiction by providing just enough waiting time to ensure accuracy without unnecessarily extending the time window.
3Reliability
If all disk types are included in snapshot operations, then backup completeness is improved, but system stability deteriorates due to unsupported disk types
Solution Approach 1:
The system applies local quality by treating different disk types differently in snapshot operations. Supported disk types are included in snapshot operations with full consistency checks, while unsupported disk types are handled separately or excluded from certain operations. This localized differentiation maintains system stability by avoiding incompatible operations on unsupported disks while still achieving comprehensive backup coverage through alternative methods for those disks.
Data Source
AI summary
A data protection agent is installed within a virtual machine (VM). A request to freeze an application in the VM is issued to a copy service. A request for a snapshot is issued to a snapshot data mover, external to the VM. Upon receiving an identifier for the snapshot, communications are exchanged with the copy service to thaw the application, the snapshot identifier is passed to the agent thereby allowing the agent to access the snapshot and rollover data from the snapshot to secondary storage for the backup, and notification to the copy service about a success of the backup is withheld. During the rollover, listening begins for status updates concerning a progress of the rollover. Based on the status updates, the copy service is notified that the backup failed or succeeded.