High-Availability Recovery Pipeline With Preconfigured Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing recovery procedures for computing systems experiencing outages are time-consuming and result in excessive network signaling, leading to prolonged downtime and increased traffic utilization.
Innovation Solution
An automated recovery pipeline that pre-configures recovery parameters and stores network addresses and connection information, utilizing containerized redundant components to ensure rapid failover and minimize downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional recovery procedures are used to restart systems and re-initialize programs, then system recovery can be achieved, but the process is time-consuming and results in prolonged downtime
Solution Approach 1:
The patent implements preliminary action by pre-configuring recovery parameters, storing network addresses and connection information in advance, and maintaining containerized redundant components ready for immediate deployment. When an outage occurs, the system retrieves pre-stored configuration data and deploys redundant containers without performing time-consuming discovery or configuration procedures, thereby dramatically reducing downtime while ensuring reliable system recovery.
2Reliability
If traditional recovery procedures are used, then system recovery can be achieved, but excessive network signaling occurs leading to increased traffic utilization
Solution Approach 1:
The patent applies preliminary action by pre-storing network addresses, connection information, and recovery parameters in the system before outages occur. When recovery is needed, the system retrieves this pre-configured data locally and uses it to immediately deploy redundant components, eliminating the need for extensive network signaling during the recovery process and thereby reducing network traffic utilization while maintaining reliable recovery operations.
3Loss of time
If automated recovery with pre-configured parameters is implemented, then downtime is reduced and network signaling is minimized, but system complexity increases
Solution Approach 1:
The patent employs copying by creating and maintaining containerized redundant copies of system components that are pre-configured with all necessary parameters, network addresses, and connection information. These copies are stored in a ready state within the system architecture. When an outage occurs, the system simply retrieves and deploys these pre-copied components rather than rebuilding or reconfiguring them, thereby reducing downtime while managing complexity through standardized containerized templates rather than custom complex configurations.
Data Source
AI summary
In some implementations, a recovery system may detect a trigger to generate a system resource document for a target system. The recovery system may communicate, based on detecting the trigger to generate the system resource document, with a set of resources of the target system to perform an auto-discovery procedure. The recovery system may generate the system resource document identifying the set of resources of the target system. The recovery system may store the system resource document in a recovery archive. The recovery system may detect an outage event. The recovery system may obtain, based on detecting the outage event, the system resource document from the recovery archive. The recovery system may fail over the set of resources of the target system to a new target system. The recovery system may transmit a set of notifications associated with the new target system.