Datacenter Disaster Recovery Boot Sequence Prioritization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current disaster recovery methods for computing systems are inefficient, leading to prolonged downtime due to the lack of precise prioritization and sequencing of recovery tasks, especially in large data centers with shared resources and varying recovery time objectives.
Innovation Solution
A system and method that assigns weightings to applications based on criticality, recovery time objectives, and resource utilization to generate a prioritized disaster recovery boot sequence, which includes control signals for infrastructure devices, and includes a feedback mechanism to adjust recovery times based on actual performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all applications are recovered simultaneously in traditional disaster recovery methods, then complete system restoration is achieved, but recovery time is excessively prolonged
Solution Approach 1:
The patent segments the disaster recovery process by dividing applications into priority groups (critical, important, standard, low) and recovering them in sequential batches rather than simultaneously. This segmentation allows the system to restore critical functions first while progressively recovering less critical applications, thereby reducing overall recovery time without compromising complete system restoration.
Solution Approach 2:
The patent implements preliminary action by pre-calculating and storing recovery boot sequences that rank applications based on their priority metrics before disasters occur. These pre-established sequences enable immediate execution during disaster recovery operations, eliminating the need for time-consuming real-time decision-making and accelerating the recovery process while ensuring critical applications are restored first.
2Loss of time
If critical applications are prioritized for recovery, then recovery time for critical applications is reduced, but non-critical applications experience extended downtime
Solution Approach 1:
The patent implements periodic action by organizing disaster recovery into multiple sequential batches based on application priority levels. Critical applications are recovered in the first batch, followed by important applications in the second batch, standard applications in the third batch, and low-priority applications in the fourth batch. This periodic batching ensures that all applications are eventually recovered while systematically addressing critical needs first.
Solution Approach 2:
The patent uses preliminary action by pre-establishing comprehensive recovery boot sequences that include all applications ranked by priority before disasters occur. These pre-calculated sequences ensure that non-critical applications are not permanently excluded from recovery but are simply scheduled for later batches, guaranteeing complete system restoration while optimizing critical application recovery time.
3Ease of operation
If manual prioritization of applications is performed, then recovery sequencing can be customized, but operational complexity and time consumption increase
Solution Approach 1:
The patent implements self-service by enabling applications to automatically generate their own priority metrics based on pre-configured parameters such as recovery time objectives, asset types, and business criticality. The system autonomously ranks applications and generates recovery boot sequences without requiring manual intervention during disaster events, thereby reducing operational complexity and accelerating the prioritization process while maintaining customizable recovery strategies.
Solution Approach 2:
The patent applies preliminary action by requiring organizations to pre-configure application priority parameters, weightings, and recovery objectives before disasters occur. This advance preparation enables the system to automatically calculate priority metrics and generate optimized recovery sequences during actual disaster events, eliminating time-consuming manual prioritization while preserving customization capabilities through the pre-established parameters.
4Productivity
If recovery boot sequences are dynamically adjusted based on feedback, then recovery efficiency is improved, but system complexity increases
Solution Approach 1:
The patent implements feedback mechanisms that monitor actual recovery performance against estimated recovery times during disaster recovery operations. The system tracks which applications are recovered and their actual recovery durations, then uses this feedback to dynamically adjust priority metrics and regenerate recovery boot sequences for subsequent batches. This feedback loop continuously optimizes recovery efficiency by learning from actual performance data while maintaining manageable system complexity through automated adjustments.
Data Source
AI summary
An improved approach for disaster recovery is provided, along with corresponding systems, methods, and computer readable media. In the improved approach, a set of applications are assigned one or more application weightings (e.g., based upon asset type, a recovery time objective, a recovery time capability, a criticality to key business functions, vendor hosting, interfaces with other systems), etc. The one or more application weightings are utilized for ranking the applications, and the ranked set of applications is utilized to generate a disaster recovery boot sequence whereby specific recovery tasks and infrastructure device requirements are arranged temporally to achieve one or more recovery time conditions.