Hot Backup System with Delay Server for Disaster Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current hot backup technologies are inadequate in addressing disaster recovery, misoperation, and overload issues, requiring improved reliability and maintainability in data communication systems.
Innovation Solution
A hot backup system comprising a centralized management module, master server, slave server, and delay server, where the centralized management module performs data transmission, data synchronization, and delay backup, and switches server identities based on abnormal operating states to ensure data integrity and rapid recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional hot backup technology is used, then system simplicity is maintained, but disaster recovery capability and system reliability are insufficient
Solution Approach 1:
The system divides the backup architecture into distinct functional modules: master server for data writing, slave server for data synchronization and reading, and delay server for delayed backup operations. This segmentation allows each component to specialize in specific tasks, improving overall disaster recovery capability while maintaining manageable system complexity through clear functional separation.
Solution Approach 2:
The centralized management module serves as an intermediary that coordinates between the master server, slave server, and delay server. It manages data flow, monitors system state, and triggers switching operations when abnormalities are detected, thereby enhancing reliability without requiring complex direct interactions between all system components.
2Reliability
If real-time data synchronization is implemented between master and slave servers, then data consistency is improved, but system complexity and resource consumption increase
Solution Approach 1:
The slave server continuously synchronizes with the master server in real-time before any failure occurs, maintaining up-to-date backup data proactively. This preliminary action ensures data consistency is already established when disasters strike, eliminating the need for complex post-failure data reconciliation mechanisms.
Solution Approach 2:
The centralized management module monitors the operating states of both master and slave servers, providing continuous feedback on system health. When abnormalities are detected in the master server, the feedback mechanism triggers automatic switching to the slave server, ensuring data consistency is maintained through closed-loop control rather than complex open-loop synchronization protocols.
3Reliability
If automatic switching between master and slave servers is enabled, then system availability is improved, but control complexity increases
Solution Approach 1:
The system implements automatic self-switching capability where the centralized management module autonomously detects master server abnormalities and triggers switching to the slave server without human intervention. This self-service mechanism improves system availability by eliminating manual switching delays while keeping control logic centralized and manageable rather than distributed and complex.
Solution Approach 2:
The centralized management module acts as an intermediary controller that simplifies the switching logic by centralizing decision-making. Rather than requiring complex distributed consensus protocols between multiple servers, a single intermediary component manages the switching decision, reducing control complexity while maintaining high availability through automated responses to failures.
4Adaptability or versatility
If delay backup functionality is added to the system, then disaster recovery options are improved, but system complexity increases
Solution Approach 1:
The delay backup function is implemented as a separate, dedicated server component rather than being integrated into the master or slave servers. This segmentation allows the delay backup server to provide additional disaster recovery options (delayed backup and restoration capabilities) without complicating the core backup management structure of the primary servers.
Data Source
AI summary
Embodiments of the present disclosure provide a hot backup system, a hot backup method, and a computer device. The hot backup system includes a centralized management module, a master server, a slave server and a delay server. The master server is configured to receive a write instruction sent by the centralized management module, and write first data to a database of the master server based on the write instruction. The slave server is configured to perform data synchronization with the master server in real time, receive a read instruction sent by the centralized management module, and send second data read based on the read instruction to the centralized management module to cause the centralized management module to send the second data to the service server.