Context-Based Disaster Recovery Service Layer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current disaster recovery systems in virtualized computing environments face challenges in managing disaster recovery operations across multiple computing resource entities and backup service providers due to the need for specific programming capabilities and limited functionality of existing APIs, which restricts user flexibility in selecting providers based on performance, security, and cost.
Innovation Solution
A provider-agnostic disaster recovery service layer is introduced, which exposes a uniform API to facilitate context-based disaster recovery of groups of computing resource entities, allowing for efficient replication and recovery operations across multiple entity types and providers, reducing the burden on users and improving resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple backup service providers are used for disaster recovery operations, then provider flexibility and performance optimization are improved, but device complexity and programming burden increase
Solution Approach 1:
The patent introduces a disaster recovery service layer as an intermediary component that sits between the virtualized computing environment and multiple backup service providers. This service layer provides a unified, provider-agnostic API that abstracts the complexity of interacting with different backup providers, allowing users to access multiple providers without bearing the programming burden of their individual complexities.
Solution Approach 2:
The disaster recovery service layer implements a universal API that can interface with multiple different backup service providers through a single standardized interface. This multi-functional approach allows the same API to work across diverse providers (e.g., AWS, Azure, Google Cloud) without requiring separate programming for each, thereby improving provider flexibility while maintaining consistent usability.
2Ease of operation
If provider-agnostic disaster recovery service layer is implemented, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The disaster recovery service layer acts as a mediating component that simplifies disaster recovery management by providing a unified interface. While it adds a layer to the system architecture, this intermediary absorbs the complexity of provider-specific operations, presenting a simplified interface to users and thereby improving ease of operation despite the increased architectural complexity.
Solution Approach 2:
The service layer creates an abstracted copy or representation of the underlying provider-specific interfaces through a standardized API. This abstraction layer copies only the essential disaster recovery operations needed by users, filtering out provider-specific complexities and presenting a simplified operational interface.
3Productivity
If context-based disaster recovery is implemented for multiple computing resource entities, then productivity is improved, but use of energy increases
Solution Approach 1:
The patent merges the disaster recovery operations for multiple computing resource entities (virtual machines, virtual disks, virtual network interfaces) into a single contextualized operation. By grouping related entities and managing them together as a unit, the system improves productivity through streamlined operations while reducing redundant energy consumption that would occur if each entity were managed separately.
Solution Approach 2:
The service layer performs preliminary actions by pre-establishing context relationships between computing resource entities and their corresponding backup providers. This preliminary organization allows for more efficient disaster recovery execution, reducing the computational energy needed during actual recovery operations by having the contextual framework already in place.
Data Source
AI summary
Systems and methods for unified application-level backup and restore using heterogeneous cloud-based backup service providers. An application programming interface is configured to process both data level replication operations as well as application-level operations that are executed to carry out high-level commands between a virtualized computing environment and any one or more of the heterogeneous cloud-based backup service providers. The API receives commands from applications in the virtualized computing environment. The API processes commands from the applications so as to facilitate replication of data to selected one or more cloud-based backup service providers. The commands perform data level replication operations as well as application-level operations for storing content to the cloud-based service provider. After a failure event and/or upon receipt of a restore command, the API initiates application-level operations that restore the application and its constituent entities. The data state is restored by the API using data level restore operations.