Database Disaster Recovery via Independent Data Protection Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed databases, when multiple data processing nodes become abnormal, the synchronized logs for database operations can be lost, leading to potential data loss even if other nodes provide services, as existing disaster recovery systems do not effectively ensure data consistency and availability.
Innovation Solution
A database disaster recovery system with independent data processing nodes and data protection nodes that synchronize logs under a distributed consistency protocol, where data protection nodes receive and store logs, allowing anomaly-free nodes to provide services based on stored logs, and optionally synchronize logs to a secondary database for continued service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If logs are synchronized only to data processing nodes in a distributed database, then system complexity is reduced, but data reliability deteriorates when multiple nodes become abnormal simultaneously
Solution Approach 1:
The system segments data protection functions by introducing dedicated data protection nodes separate from data processing nodes. Each node type has specialized responsibilities: processing nodes handle database operations while protection nodes handle log storage and recovery, reducing overall system complexity while improving reliability through functional separation.
Solution Approach 2:
Data protection nodes act as intermediary components between data processing nodes and the disaster recovery system. They receive logs from processing nodes, store them safely, and provide them during recovery operations, serving as a buffer that improves reliability without requiring direct complex interactions between all processing nodes.
2Reliability
If independent data protection nodes are introduced to store logs, then data availability improves during anomalies, but system complexity increases
Solution Approach 1:
Data protection nodes are designed with multi-functionality: they store logs during normal operations, provide logs during partial failures, and enable full system recovery when multiple nodes are abnormal. This universal design improves data availability across different failure scenarios while maintaining a manageable system architecture through standardized node behavior.
3Stability of the object's composition
If logs are synchronously transmitted to all nodes, then data consistency is improved, but system performance deteriorates due to increased synchronization overhead
Solution Approach 1:
The system extracts the log storage function from the data processing nodes and places it in dedicated data protection nodes. This separation removes the synchronization overhead burden from processing nodes, allowing them to maintain data consistency with protection nodes through simpler log transmission while preserving overall system performance.
Data Source
AI summary
The present specification discloses a database disaster recovery system, method, and apparatus, a storage medium, and an electronic device. In the database disaster recovery system provided in the present specification, the system includes a first database. A data processing node in the first database synchronizes a log generated for a database operation to at least one data protection node based on a distributed consistency protocol. The data protection node receives and stores the log. In response to some data processing nodes in the first database experiencing an anomaly, a data processing node without an anomaly in the first database provides a database service based on logs stored in the data protection node, thereby implementing disaster recovery for the first database. It can be learned from the above system that, the system can implement disaster recovery without data loss for the first database based on the distributed consistency protocol by using the data protection node independent of the data processing node.