Private-Network Backup and Recovery With Two-Phase Disaster Restoration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Private-network data backup and recovery systems face challenges in automatic recovery without external intervention, particularly during disasters, due to their inaccessibility and potential corruption, which complicates the restoration of both infrastructure and application-level services.
Innovation Solution
A two-phase recovery approach is implemented, where infrastructure components are first restored to a crash-consistent state, followed by application-level recovery, ensuring data integrity and independence from other services, enabling automated recovery within the private network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If private-network backup and recovery systems are isolated from external networks for security, then security is improved, but automatic recovery capability deteriorates due to inaccessibility during disasters
Solution Approach 1:
The system performs preliminary actions by creating and storing snapshots of the backup and recovery system state before disasters occur. These snapshots are preserved within the private network and can be automatically restored when disasters happen, enabling automatic recovery without external intervention while maintaining network isolation for security.
Solution Approach 2:
The backup and recovery system is designed to be self-service capable by implementing automated detection of disaster conditions, automatic selection of appropriate snapshots, and self-execution of recovery operations. The system monitors its own health status and triggers recovery procedures autonomously when failures are detected, eliminating the need for external manual intervention.
2Manufacturing precision
If infrastructure components are recovered first to ensure consistency, then data integrity is improved, but recovery time increases due to sequential recovery process
Solution Approach 1:
The recovery process is segmented into distinct phases: infrastructure recovery and application-level service recovery. This segmentation allows each phase to be optimized independently - infrastructure components are recovered first to establish a consistent baseline, then application services are recovered in parallel where possible, maintaining data integrity while reducing overall recovery time compared to fully sequential approaches.
Solution Approach 2:
The system performs preliminary actions by pre-validating snapshot consistency and pre-planning recovery sequences. Before actual recovery begins, the system checks snapshot integrity and prepares recovery configurations, so that when recovery starts, it can proceed efficiently with minimal delays while ensuring data integrity is maintained throughout the process.
Data Source
AI summary
Methods, systems, and devices for data management are described. A client of a backup and recovery system may recover a virtual machine (VM) within a private network based on a previously-obtained snapshot of the VM. The VM may host a backup and recovery system for one or more computing objects within the private network prior to a disaster scenario. The backup and recovery system may recover, in response to a trigger, infrastructure of the backup and recovery system based on the snapshot. The infrastructure may include components and core services that operate the backup and recovery system. The core services may be operable to execute independent of other services. The backup and recovery system may subsequently recover data associated with one or more second services provided by the backup and recovery system. The second services may depend on at least one of the core services for execution.