Cloud-Based Disaster Recovery for Server Restoration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing server backup and recovery methods are time-consuming and complex, requiring manual intervention and varying solutions for each server, making it challenging to manage and restore multiple inoperable servers efficiently.
Innovation Solution
A cloud-based disaster recovery system that configures and categorizes servers into workload steps, stores backup information, and automatically restores servers using stored backup sets upon failure indication, minimizing user intervention and streamlining the recovery process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual backup and recovery methods are used for each server, then each server can be restored individually, but the restoration process becomes time-consuming and complex when multiple servers fail
Solution Approach 1:
The patent segments the restoration process into distinct phases: identification of failed servers, retrieval of backup images, and sequential restoration operations. By dividing the complex restoration task into manageable segments, the system can efficiently handle multiple server failures without overwhelming manual intervention requirements
Solution Approach 2:
The system performs preliminary actions by pre-configuring backup images and restoration parameters before failures occur. Backup images are created and stored in advance, and restoration templates are prepared beforehand, enabling rapid restoration when failures happen without needing to configure everything from scratch during the emergency
2Reliability
If individual backup solutions are used for each server, then each server has its own backup capability, but managing multiple backup solutions increases system complexity
Solution Approach 1:
The patent implements a universal backup and restoration platform that can handle multiple server types and failure scenarios through a single integrated system. The cloud-based architecture provides multi-functional capabilities including backup creation, storage, retrieval, and restoration across diverse server environments, eliminating the need for separate specialized solutions for each server
Solution Approach 2:
The system introduces a cloud-based intermediary platform that mediates between individual servers and backup storage. This intermediary layer abstracts the complexity of backup management, providing a standardized interface for backup operations while handling the intricate details of storage management, retrieval logic, and restoration coordination centrally
3Adaptability or versatility
If manual user intervention is required for server restoration, then customization is possible, but the process becomes challenging and time-consuming
Solution Approach 1:
The system enables self-service restoration by automatically identifying failed servers, retrieving appropriate backup images, and executing restoration operations without requiring extensive manual user intervention. The platform autonomously manages the restoration workflow while providing users with simple initiation commands and progress monitoring capabilities
Solution Approach 2:
The system allows flexible parameter configuration for restoration operations, including selectable backup versions, restoration targets, and configuration options. Users can modify restoration parameters through simplified interfaces that translate high-level preferences into detailed restoration commands, maintaining adaptability while reducing operational complexity
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; determining, at the cloud-based computing platform, servers associated with the workload based on information provided by a user; generating steps for the workload; categorizing the determined servers into the generated steps; storing the workload; and restoring the servers using the stored workload upon receiving a failure indication from the client machine.