Cloud Resource Disaster Recovery via Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud computing infrastructure faces system failures due to software, hardware, or network issues, leading to unavailability and impact on cloud system functionality, especially when the central service or resource providers fail, causing disruptions in resource management and access.
Innovation Solution
Implement methods for disaster recovery in cloud infrastructure where resource providers synchronize with the central service to update resource information, and the central service synchronizes with resource providers to rebuild metadata and subscription information, ensuring seamless recovery and resource access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the central service is implemented to manage all cloud infrastructure services, then centralized management and routing of requests is improved, but the system becomes vulnerable to single point of failure
Solution Approach 1:
The patent segments the monolithic central service into multiple distributed service instances that can operate independently. Each service instance maintains its own state and can handle requests autonomously, eliminating the single point of failure while preserving centralized management capabilities through coordinated communication between instances.
Solution Approach 2:
The patent implements local quality by enabling each service instance to maintain local state and make autonomous decisions regarding request routing and resource management. This distributed state management allows the system to continue operating even when individual instances fail, while still providing centralized coordination through inter-instance communication.
2Adaptability or versatility
If resource providers are designed to create and manage cloud resources autonomously, then service flexibility and scalability are improved, but coordination and consistency with the central service becomes complex
Solution Approach 1:
The patent implements feedback mechanisms where resource providers continuously report their state and resource status to the central service, and the central service provides routing information and management directives back to resource providers. This bidirectional feedback loop enables autonomous operation while maintaining coordination and consistency through real-time state synchronization.
Solution Approach 2:
The patent applies preliminary action by having resource providers pre-register their capabilities and resources with the central service before actual resource creation. This advance registration allows the central service to pre-compute routing strategies and coordination rules, reducing the complexity of real-time coordination when resources are actively being managed.
3Reliability
If disaster recovery mechanisms are implemented to restore failed services, then system reliability is improved, but recovery time and system downtime increase
Solution Approach 1:
The patent implements preliminary action through proactive backup creation and pre-positioning of recovery resources. Before failures occur, the system continuously creates backups of critical service state and pre-provisions standby service instances. When failures occur, these pre-prepared resources can be activated immediately, dramatically reducing recovery time while maintaining high reliability.
Solution Approach 2:
The patent applies beforehand cushioning by maintaining redundant service instances and backup data in advance, creating a buffer that absorbs the impact of failures. This cushioning mechanism ensures that when disasters occur, the system can switch to backup resources without significant downtime, thus improving reliability while minimizing time loss.
Data Source
AI summary
Embodiments of the present invention are directed to methods by which different services registered with cloud infrastructure may recover in case of disaster. Also directs procedures with which a resource provider may recover and rebuild its cloud resource information by scanning actual resources available. A resource provider will synchronize resources with a central service to get updated consumer and subscription information. In the scenario in which a central service fails and is recovered from backup, the central service should synchronize with resource providers to update its resource information.