Cloud-Based Disaster Recovery Workload Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing server backup and recovery solutions require manual intervention and are time-consuming, especially when multiple servers become inoperable, as each server has its unique backup solution, leading to increased restoration time.
Innovation Solution
A cloud-based disaster recovery method that configures a workload with pre-restore and post-restore scripts, along with manual input options, to restore servers efficiently by listing associated servers and executing necessary scripts upon receiving failure indications, using a cloud-based computing platform and web-based application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual backup solutions are used for each server, then each server can be restored individually, but the restoration process becomes time-consuming and requires significant manual intervention when multiple servers fail
Solution Approach 1:
The patent segments the restoration process into distinct phases: pre-restore scripts execute before server restoration to prepare the environment, the actual restoration occurs, then post-restore scripts execute afterward to complete configuration. This segmentation allows parallel execution of multiple servers through automation while maintaining proper sequencing of restoration steps, reducing overall restoration time without sacrificing reliability
Solution Approach 2:
The patent introduces an intermediary automation layer (the cloud-based platform with pre-configured workloads and scripts) that mediates between the failure event and the restoration process. This intermediary automatically coordinates the complex sequence of operations across multiple servers, eliminating manual intervention time while ensuring reliable restoration through standardized procedures
2Adaptability or versatility
If unique backup solutions are implemented for each server, then each server's specific requirements are met, but the complexity of managing multiple backup solutions increases significantly
Solution Approach 1:
The patent creates a universal cloud-based workload template that can be replicated across multiple servers with different requirements. The workload structure serves multiple functions: it defines server relationships, specifies pre- and post-restore scripts, and configures automation rules. This universal template maintains adaptability to server-specific needs while centralizing management, thereby reducing complexity
Solution Approach 2:
The patent applies preliminary action by pre-configuring workload templates with all necessary restoration parameters, script executions, and server dependencies before failures occur. These templates are prepared in advance with specific configurations for different server types, allowing rapid deployment during incidents without requiring complex real-time decision-making or manual setup
3Productivity
If automated restoration processes are implemented, then restoration speed increases, but the need for manual verification and intervention may be reduced or eliminated
Solution Approach 1:
The patent incorporates feedback mechanisms where post-restore scripts execute automatically after server restoration to verify successful completion and gather status information. This feedback loop provides automated confirmation that restoration occurred correctly, maintaining ease of operation by eliminating the need for manual verification while preserving the ability to intervene if anomalies are detected
Data Source
AI summary
Methods, apparatuses and systems for cloud-based disaster recovery are provided. The method, for example, includes configuring, at a cloud-based computing platform, a workload associated with a function-based service used by a client machine, the workload including generated steps listing servers associated with the function-based service and configured based on information provided by a user at the client machine; and restoring the servers for each of the generated steps of the workload including executing at least one of a pre-restore script, a post-restore script, or a manual input upon receiving, from the client machine, a failure indication associated with the servers.