Distributed Availability Group Backup Chain Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current backup systems fail to recognize high-availability database systems, leading to unprotected databases and inefficient backup processes during failovers, resulting in potential data loss and prolonged recovery times.
Innovation Solution
Implementing a distributed availability group architecture that uses a common name for the distributed availability group to maintain the backup chain across multiple nodes, allowing for incremental or differential backups even after a failover, thereby ensuring continuous data protection and efficient recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current backup systems are used on high-availability database systems, then the backup process is simple to implement, but the database may be left unprotected or treated as a new database after failover, leading to data loss risk and prolonged recovery time
Solution Approach 1:
The backup system monitors failover events in real-time and automatically adjusts backup operations based on the current primary replica identification. When a failover is detected, the system receives feedback about the new primary replica and continues the backup chain without interruption, ensuring the database remains protected throughout the failover process.
Solution Approach 2:
The backup system automatically detects failover events and identifies the new primary replica without requiring manual intervention. The system self-adjusts by continuing the backup chain with the new primary replica, treating it as the same logical database through consistent naming conventions, thereby maintaining data protection autonomously.
2Productivity
If the database is treated as a new database after failover, then backup operations can be performed on the new primary replica, but a new full backup must be conducted even though much data may already have been backed up, increasing backup time and storage requirements
Solution Approach 1:
The backup system uses a consistent logical name for the database that remains unchanged across failovers. This universal identifier allows the backup system to recognize that the database on the new primary replica is the same logical database as before, enabling incremental backups instead of requiring full backups and maintaining backup efficiency.
Solution Approach 2:
The system changes the parameter used for database identification from physical server-specific identifiers to logical database names that persist across failovers. This parameter change allows the backup system to maintain the backup chain by recognizing that the logical database identity remains the same even though the physical primary replica has changed.
3Ease of operation
If the database is treated as a new database after failover, then backup operations can be initiated, but the backup will not be linked to previous backups, making recovery very difficult and time-consuming
Solution Approach 1:
The backup system maintains the backup chain continuously across failovers by using consistent logical database names. Each backup operation is linked to the previous one through this continuous identification, preserving the backup chain information and enabling easy recovery by allowing administrators to restore from any point in the continuous backup history.
Data Source
AI summary
A determination is made that a relational database management system (RDBMS) is configured as a distributed availability group. The distributed availability group spans first and second availability groups. Each availability group includes a cluster of servers hosting replicas of a database. One of the first or second availability groups functions as a primary availability group. Another of the first or second availability groups functions as a secondary availability group that is available as a failover target should the primary availability group become unavailable. A name of the distributed availability group is obtained. A first server in the first availability group is directed to backup a replica of the database being hosted by the first server. The directing includes instructing the first server to index the backup against the name of the distributed availability group.