Reference Map Repair for Cross-Group Database Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems face challenges in handling dangling references that are outside the replication group, leading to failed replication operations and metadata corruption during failover, especially in cloud-based environments.
Innovation Solution
The method involves creating a reference map to record associations between objects within a source group and external objects, preserving and repairing dangling references during failover, allowing for robust replication and disaster recovery by maintaining functional relationships with external objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If replication operations are performed with cross replication group references, then data replication capability is improved, but metadata corruption and replication failure occur
Solution Approach 1:
The patent segments the reference management by creating a reference map that separates internal references from external references. This segmentation allows the system to handle cross-replication-group references differently from internal references, preventing metadata corruption while maintaining replication capability.
Solution Approach 2:
The reference map acts as an intermediary data structure that mediates between objects within the replication group and external objects. It records and manages cross-replication-group references, allowing the replication system to maintain functional relationships with external objects without causing metadata corruption.
2Productivity
If failover group is promoted to primary status, then system availability is improved, but unresolved dangling references cause operational failures
Solution Approach 1:
The system performs preliminary actions by recording all external references in the reference map before failover occurs. This advance preparation ensures that when the failover group is promoted to primary status, the dangling references are already identified and can be resolved, preventing operational failures.
Solution Approach 2:
The reference map provides feedback information about external references to the failover group. This feedback mechanism allows the system to identify and resolve dangling references after promotion, ensuring operational reliability while maintaining high system availability.
3Adaptability or versatility
If external references are replicated, then functional relationships are improved, but replication complexity and metadata management burden increase
Solution Approach 1:
The patent extracts external reference information from the replication process by recording it separately in the reference map. This extraction allows the system to maintain functional relationships with external objects without increasing replication complexity, as the external references are managed independently from the core replication operations.
Data Source
AI summary
This disclosure provides methods and techniques of data replication involving cross replication group (RG) references. Example methods, systems, and techniques are disclosed regarding batch database replication (e.g., backup) and failover (e.g., automatic transition to a backup) between multiple database deployments or database providers. For example, a system causes database data to be stored in a primary deployment and replicated in one or more secondary deployments. In the event that data in the primary deployment is unavailable, transactions may be executed on one or more of the secondary deployments. When the original primary deployment becomes available again, any transactions executed on secondary deployments may be propagated to the primary deployment. The system may be configured such that queries on the database data are executed on the primary deployment at any time when the primary deployment is available.