Automated Failover Plan Execution Reducing Server Downtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of failover in computer networks, particularly for applications like Microsoft Exchange, is complex and time-consuming, often resulting in significant downtime due to the need for extensive technical knowledge and a high likelihood of human error, especially when reconstructing an entire primary site at a failover site.
Innovation Solution
A failover module generates a user interface to define and execute a failover plan, which includes details about the source, destination, storage resources, and mirroring relationships, allowing for automated failover with minimal human intervention, reducing downtime and error.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual failover process is used, then technical knowledge and control are required, but downtime and human error increase
Solution Approach 1:
The system performs preliminary actions by pre-configuring failover plans that define mirror relationships, storage resource mappings, and connection parameters before a failure occurs. When failover is needed, these pre-established configurations are automatically executed, eliminating the need for real-time manual configuration and significantly reducing downtime.
Solution Approach 2:
The failover system performs self-service by automatically detecting failures, selecting appropriate failover targets, and executing the failover process without human intervention. The system manages its own failover operations using stored configurations and automated scripts, removing the burden of manual technical knowledge requirements.
2Loss of time
If automated failover is implemented, then downtime is reduced, but system complexity increases
Solution Approach 1:
The failover system is segmented into distinct functional components: a failover module for automation control, a user interface for configuration, storage for configuring failover plans, and mirror relationships for data replication. This segmentation allows each component to be independently managed and simplified, reducing overall system complexity while maintaining automation capabilities.
Solution Approach 2:
The system uses copying by creating virtual copies of storage resources and configurations at the failover site before actual failover occurs. These copies include mirrored data, virtual machine images, and configuration files, which can be quickly deployed during failover without requiring physical reconfiguration, thus reducing complexity of the failover execution.
3Manufacturing precision
If detailed failover configuration is provided, then failover accuracy is improved, but ease of operation decreases
Solution Approach 1:
Detailed failover configuration is performed in advance through the user interface, where administrators define mirror relationships, storage mappings, and connection parameters. Once configured, these detailed settings are stored and automatically executed during failover, providing both high accuracy and ease of operation since the complex configuration is done once rather than repeatedly.
Solution Approach 2:
The system introduces an intermediary layer in the form of a failover plan data structure that mediates between the administrator's high-level failover initiation command and the detailed technical configuration. The failover plan acts as an intermediary that translates simple user actions into complex automated execution, maintaining both ease of operation and failover accuracy.
Data Source
AI summary
A failover module generates a user interface to enable an administrative user to define a failover plan for a primary site. The failover plan includes user-specified information for use by multiple operations of a failover process for failing over a server system from the primary site to a failover site. The failover plan can be stored as a data object on a computer system at the failover site. In the event of a serious failure at the primary site, the failover process can be invoked and carried out on the failover site with little or no human intervention, based on the failover plan, to cause the server system to be failed over to the failover site, thereby substantially reducing downtime of the server system and its data.