Backup Availability Group Databases on Multi-Node Virtual Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Backup/restore applications face challenges when attempting to back up data objects on multi-node virtual servers, as they need to identify the correct active node to ensure successful execution, but existing solutions can fail due to the presence of multiple nodes and prioritization issues, leading to frustration of administrator preferences and potential backup failures.
Innovation Solution
A system that identifies an availability group scheduled for backup, determines if it is configured on a multi-node virtual server, retrieves configuration information, identifies a preferred database replica, and selects an active node within the virtual server to execute the backup job, ensuring seamless backup operations without disrupting administrator preferences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a backup/restore application attempts to back up data objects on a multi-node virtual server, then backup coverage is improved, but the complexity of identifying the correct active node increases
Solution Approach 1:
The backup/restore application automatically queries the virtual server to obtain the active node identifier and uses this information to direct backup operations. The system self-services by retrieving and processing node configuration information without requiring manual administrator intervention for node selection.
Solution Approach 2:
The application queries the virtual server for active node information and uses this feedback to dynamically adjust backup operations. The system continuously monitors node availability and directs backup jobs to the appropriate active node based on real-time system state.
2Reliability
If the backup application sends backup jobs to an inactive node, then backup operations may fail, but manually configuring backup targets increases administrator workload
Solution Approach 1:
The virtual server automatically provides its active node identifier to the backup application through a query interface. The system self-determines the correct backup target without requiring administrator configuration or manual node selection, eliminating the workload of tracking active nodes while ensuring backup jobs are sent to the correct node.
Solution Approach 2:
The virtual server acts as an intermediary that mediates between the backup application and the actual backup target node. The application queries the virtual server to obtain the active node identifier, and this intermediary mechanism ensures backup jobs are correctly routed without requiring direct administrator knowledge of node states.
3Reliability
If backup operations are performed on the primary database replica, then data consistency is maintained, but production server performance deteriorates
Solution Approach 1:
The backup system dynamically selects the backup target based on the active node identifier provided by the virtual server. When the primary node is active, backups occur on the primary replica maintaining data consistency; when a secondary node becomes active, backups automatically shift to the secondary replica, dynamically adapting to failover scenarios and reducing load on the production primary server.
Solution Approach 2:
The system changes the backup target parameter based on the active node state. By querying the virtual server for the active node identifier and using this information to direct backup operations, the system can shift backup operations between primary and secondary replicas, changing the backup target parameter to optimize both data consistency and production server performance.
Data Source
AI summary
Backing up availability group databases configured on multi-node virtual servers is described. A system identifies an availability group scheduled for backup. The system determines whether the availability group is configured on at least one virtual server in a cluster of nodes associated with the availability group. If the availability group is configured on at least one virtual server in the cluster of nodes, the system retrieves information from a server in the cluster of nodes. The system uses the retrieved information to identify a database replica that is preferred for backing up the availability group. The system identifies a virtual server, in the cluster of nodes, that is associated with the identified database replica. The system identifies a node for backing up the availability group by identifying an active node from the nodes in the identified virtual server. The system backs up the availability group via the identified node.