Hyperconverged Database Backup Node Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual computing systems face challenges in efficiently protecting highly available source databases, particularly when copies of the database are spread across multiple nodes and clusters, leading to redundancy, high resource consumption, and user intervention requirements.
Innovation Solution
A system is implemented with a plurality of nodes distributed between two clusters, where each node stores a copy of a source database. A processor designates a primary node and secondary nodes to ensure continuity upon primary node failure, and automatically switches to a next active node based on a predefined policy, allowing for seamless backup and restoration of the source database without user intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database copies are distributed across multiple nodes and clusters for high availability, then system reliability is improved, but redundancy and resource consumption increase
Solution Approach 1:
The system segments the database protection function by designating specific nodes as primary or secondary backup nodes, rather than maintaining full redundancy across all nodes. This segmentation allows the database to be protected across multiple clusters while reducing overall redundancy by having each node serve a specific protective function.
Solution Approach 2:
Secondary backup nodes are designed to serve multiple purposes: they can back up from a primary node, take over if the primary fails, and potentially serve as primary nodes for other databases. This multi-functionality reduces the need for dedicated backup infrastructure, thereby reducing redundancy while maintaining reliability.
2Ease of operation
If manual intervention is required for backup switching between nodes, then backup control flexibility is improved, but operational complexity and user burden increase
Solution Approach 1:
The system implements self-service through automated backup switching mechanisms. When a primary node fails, the system automatically detects the failure and switches to a secondary backup node without requiring manual user intervention. This automation reduces operational complexity while maintaining flexible backup control through predefined switching policies.
Solution Approach 2:
The system employs feedback mechanisms where the backup system continuously monitors the health and availability of primary nodes. Based on this feedback, the system automatically triggers backup switching when failures are detected, enabling flexible and responsive backup control without manual intervention.
3Reliability
If automated backup switching is implemented based on policies, then system availability is improved, but system complexity increases
Solution Approach 1:
The system implements preliminary action by pre-configuring backup policies that define which nodes serve as primary or secondary backup nodes and under what conditions switching should occur. These policies are established in advance, allowing the system to automatically execute backup switching based on predefined criteria, thereby improving availability without requiring complex real-time decision-making logic.
Data Source
AI summary
A system and method includes a plurality of nodes distributed between a first cluster and a second cluster, each of the plurality of nodes storing a copy of a source database and a processor executing computer-readable instructions stored on a memory to designate a first node of the plurality of nodes as a primary node, designate remaining ones of the plurality of nodes as secondary nodes to take over from the primary node upon failure of the primary node, designate a second node of the plurality of nodes as an initial active node, backup the source database from the initial active node, automatically designate, based on a switch over policy, a third node of the plurality of nodes as a next active node upon the initial active node becoming unavailable, and continue backups of the source database from the next active node upon the initial active node becoming unavailable.