Automated Cloud Disaster Recovery Decommissioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Disaster recovery decommissioning for cloud-based applications is a time-consuming and convoluted process requiring frequent manual intervention, especially after enabling disaster recovery measures to minimize data loss and downtime in case of cloud platform failures.
Innovation Solution
A system and method that automates the decommissioning of disaster recovery measures by reconfiguring the DNS service to map a custom domain to the URL of the primary instance of a cloud-based application, and reconfiguring the GTM cluster to remove routing configurations, allowing requests to be directed directly to the primary instance, even if it is unavailable, thereby ceasing replication and removing the secondary instance from the secondary cloud platform.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual intervention is used for decommissioning disaster recovery measures, then flexibility and control are maintained, but the process becomes time-consuming and complex
Solution Approach 1:
The system enables self-service automation where the disaster recovery engine automatically executes decommissioning tasks without requiring manual intervention. The engine monitors the secondary cloud platform landscape, automatically removes the secondary instance, and manages the entire decommissioning process autonomously, transforming a manual complex process into an automated self-service operation.
Solution Approach 2:
The system performs preliminary actions by pre-configuring the disaster recovery engine with automation capabilities and pre-establishing the monitoring and execution frameworks. This preliminary setup enables the automated decommissioning process to execute without requiring manual intervention during the actual decommissioning operation, reducing time and complexity.
2Reliability
If disaster recovery measures are enabled with GTM cluster routing, then application availability and fault tolerance are improved, but the decommissioning process becomes more complex
Solution Approach 1:
The system extracts and removes the secondary instance from the secondary cloud platform landscape during decommissioning. By taking out the secondary instance and removing its routing configurations from the GTM cluster, the system simplifies the decommissioning process while maintaining the reliability benefits of having had disaster recovery measures in place during operation.
Solution Approach 2:
The disaster recovery engine performs preliminary monitoring and identification of the secondary instance before decommissioning. This preliminary action enables the system to automatically locate and remove the secondary instance without manual intervention, reducing the complexity of decommissioning while maintaining application availability during the operational phase.
3Productivity
If manual decommissioning is performed, then control over the process is maintained, but time consumption increases
Solution Approach 1:
The disaster recovery engine performs self-service automation by automatically monitoring, identifying, and removing the secondary instance without requiring manual intervention. This self-service approach eliminates the time-consuming manual decommissioning process while maintaining control through automated engine execution, significantly improving decommissioning speed and reducing time loss.
Solution Approach 2:
The system maintains continuity of useful action through automated monitoring and execution. The disaster recovery engine continuously monitors the secondary cloud platform landscape and automatically executes decommissioning tasks without interruption or manual intervention, ensuring continuous productivity and eliminating time losses associated with manual process pauses.
Data Source
AI summary
A method may include disabling disaster recovery for a cloud-based application by determining that a domain name system (DNS) service has been reconfigured to map a custom domain of the cloud-based application to a uniform resource locator (URL) of a first instance of the cloud-based application deployed at a first cloud platform landscape instead of a URL of a global traffic management (GTM) cluster. The GTM cluster may be reconfigured to remove configurations for directing, based on an availability of the first instance of the cloud-based application, requests for the cloud-based application to the first instance of the cloud-based application and/or a second instance of the cloud-based application deployed at the second cloud platform landscape. The DNS service and/or the GTM cluster may be reconfigured such that future requests for the cloud-based application are routed to the first instance of the cloud-based application and not the GTM cluster.