Cross-Zone VPC Server Failover via Dynamic IP Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing redundant storage solutions fail to provide seamless failover between servers located in different zones within a Virtual Private Cloud (VPC), leading to potential disruptions in data communication when one server experiences a failure.
Innovation Solution
Implementing a method that enables automatic failover between primary and backup servers by creating a new route table, updating the internet protocol address, and synchronizing data across zones using snap replication, ensuring continuous communication and data access without disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If redundant storage servers are deployed in different zones within a VPC, then data availability and reliability are improved, but seamless failover between zones cannot be achieved
Solution Approach 1:
The patent introduces a network controller as an intermediary component that manages IP address allocation and route table configuration between primary and secondary storage servers in different availability zones. This mediator enables automatic failover by dynamically updating network routing when the primary server fails, allowing seamless transition without direct complex interactions between the storage servers themselves.
Solution Approach 2:
The system implements dynamic IP address assignment and route table updates that automatically adapt when failover occurs. The secondary server dynamically becomes the primary by receiving the primary's IP address and having route tables updated in real-time, enabling the system to flexibly respond to failure conditions rather than requiring static pre-configured failover paths.
2Reliability
If automatic failover mechanisms are implemented, then communication continuity is improved, but system complexity increases due to route table management and IP address updates
Solution Approach 1:
The network controller serves as a centralized intermediary that handles all complex route table management and IP address update operations. By concentrating these complex functions in a single control component rather than distributing them across multiple servers, the system achieves automatic failover while managing complexity through centralized control logic.
Solution Approach 2:
The system pre-configures route tables and IP address allocation schemes before failover events occur. The network controller maintains ready-to-use route table templates and IP address mappings that can be rapidly deployed during failover, eliminating the need for complex real-time calculations and reducing the complexity of on-the-fly decision-making.
3Reliability
If cross-zone data synchronization is implemented, then data accessibility is improved, but data communication disruptions occur during zone failures
Solution Approach 1:
Data synchronization between primary and secondary servers is performed continuously in advance before failures occur. The secondary server maintains up-to-date copies of data through ongoing replication processes, so when failover happens, there is no need to transfer data during the transition - the data is already synchronized and ready for immediate access.
Solution Approach 2:
The system maintains continuous data replication and synchronization operations running in the background throughout normal operation. This continuous useful action ensures that data consistency is preserved across zones at all times, and the synchronization process continues uninterrupted during failover events, preventing communication disruptions.
Data Source
AI summary
Method and apparatus for switching between a first server and a second server, each located within a virtual private cloud and the first server being located within a first zone and the second server being located within a second zone that is physically separate from the first zone. The method and apparatus further configured to determine that the first server has experienced a failure to send or receive data. The method and apparatus further configured to enable a second port on the second server. The method and apparatus further configured to create a new route table at the second server and flush the previous route table. The method and apparatus further configured to transmit, via the second port, a request to a virtual private cloud controller to update an elastic internet protocol address with the second port information and receive data from the virtual private cloud controller.