Federated Availability Group Restores Across Cluster Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current backup applications for availability groups lack the ability to restore backups to nodes other than the original node of creation, restrict users from viewing information from other nodes within the same cluster, and create additional copies, leading to storage waste and confusion, while also causing data loss during the restore process.
Innovation Solution
Implementing federated restores that allow backups of availability groups to be restored to any node within the cluster based on a cluster identifier, enabling users to view and restore database replicas across nodes without creating additional copies, and performing full backups to preserve data during the restoration process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If backup applications restore backups only to the original node of creation, then data integrity is maintained, but flexibility and adaptability are reduced
Solution Approach 1:
The restore operation is segmented into distinct phases: identification of backup metadata, selection of target node, execution of restore process, and validation of data integrity. This segmentation allows the system to maintain strict integrity checks while enabling flexible node selection for restoration.
Solution Approach 2:
The patent introduces an intermediary restoration management system that coordinates between the backup storage and target nodes. This intermediary validates restore requests, ensures data integrity protocols are followed, and manages the actual restoration process, thereby maintaining reliability while enabling cross-node restoration capability.
2Reliability
If backup applications create additional copies during restore operations, then data availability is improved, but storage efficiency deteriorates
Solution Approach 1:
The patent implements intelligent copying that creates temporary copies only when necessary for restore operations, rather than maintaining permanent additional copies. The system copies data from backup storage to target nodes only during active restore processes, and automatically cleans up temporary copies upon completion, thereby improving data availability while minimizing storage waste.
Solution Approach 2:
The system implements a discard and recover mechanism where temporary data copies are created during restore operations and then automatically discarded after successful restoration. This approach ensures data availability during the restore process while preventing permanent storage consumption, as the system recovers storage space by removing temporary copies once they serve their purpose.
3Loss of information
If backup applications restrict viewing information to the same node, then security is maintained, but information accessibility is reduced
Solution Approach 1:
The backup information management system is designed with universal access capabilities that allow any node within the cluster to view backup metadata and information. This multi-functional design enables centralized backup information storage with distributed read-access, improving information accessibility while maintaining security through controlled authentication and authorization mechanisms.
Solution Approach 2:
An intermediary information access layer is introduced that handles all requests for backup information. This intermediary validates user credentials, checks authorization permissions, and retrieves information from centralized storage, thereby enabling broad information accessibility while maintaining security through a controlled access gateway that filters and manages all information requests.
4Reliability
If backup applications perform restore operations on availability groups, then system recovery is improved, but data loss risk increases due to replication interruptions
Solution Approach 1:
The system performs preliminary actions before initiating restore operations on availability groups: it identifies and pauses ongoing replication processes, creates consistent snapshots of current data states, and prepares the target node to receive restore data. These preliminary steps ensure that restore operations can proceed without interrupting replication, thereby improving system recovery capability while preventing data loss.
Solution Approach 2:
The patent implements beforehand cushioning by creating protective snapshots and checkpoints before restore operations begin. These snapshots serve as cushioning layers that protect against potential data loss scenarios, allowing the system to resume or rollback if issues occur during restore. This approach enables safe restore operations on availability groups without risking data loss from replication interruptions.
Data Source
AI summary
Federated restores of availability groups are described. A system backs up an availability group from a node in a cluster of nodes based on an identifier of the cluster of nodes. The system outputs information associated with at least one database replica in any availability group which is backed up based on the identifier of the cluster of nodes in response to a user request for the information. The system restores a user-selected database replica to a user-selected node in the cluster of nodes based on a user selecting at least some of the information.