Private-Network VM Recovery Using Two-Phase Backup Restore
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Private-network data backup and recovery systems face challenges in recovering from disasters without external intervention, particularly when the system becomes corrupted and is inaccessible to external networks.
Innovation Solution
A two-phase recovery process is implemented, where the infrastructure level is first recovered, followed by application-level recovery, ensuring crash-consistent operation and dependency on core services, enabling automated recovery within the private network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If the backup and recovery system operates in a private network without external network access, then security and network isolation are improved, but the ability to recover from system corruption without external intervention deteriorates
Solution Approach 1:
The patent applies preliminary action by creating bootable recovery media (CDs, USB drives, or local storage) that contain the necessary recovery infrastructure and services before a disaster occurs. This pre-prepared recovery environment enables the system to restore itself from corrupted states without requiring external network access during the recovery process, thus resolving the contradiction between network isolation security and disaster recovery capability
2Productivity
If automated recovery processes are implemented within the private network, then recovery speed and automation are improved, but system complexity increases
Solution Approach 1:
The patent implements self-service by designing a recovery system where the backup and recovery infrastructure automatically restores itself from corrupted states using pre-configured recovery media and automated service orchestration. The system performs self-diagnosis, self-restoration, and automatic service reactivation without requiring manual intervention or complex external coordination, thereby achieving fast automated recovery while keeping the system architecture manageable
Solution Approach 2:
The recovery process is segmented into distinct phases: infrastructure recovery (restoring core services and system components), application recovery (restoring user applications and data), and validation (verifying recovery success). This segmentation allows each phase to be handled by specialized components, reducing overall system complexity while enabling parallel processing and faster total recovery time
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.