Database Backup Reconciliation for Repairless Restore
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional NoSQL database systems require time-consuming repair operations to reconcile data inconsistencies during backup and restore processes, especially in large clusters with extensive data, leading to inefficient data restore operations.
Innovation Solution
A method and system for performing a database backup that involves a reconciliation node receiving replica data records from multiple nodes, processing them in parallel without inter-node communication, merging updates, identifying and discarding stale or redundant records, and restoring a single consistent copy of updated records to the production cluster, thereby eliminating the need for subsequent repair operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional repair operations are performed to reconcile data inconsistencies during backup and restore, then data consistency is improved, but restore time and processing resources are significantly increased
Solution Approach 1:
The system performs data reconciliation and consistency checks during the backup operation itself, preparing the backup data in a consistent state before restore is needed. The backup process includes merging updates, identifying stale records, and creating a single consistent copy of updated data records, so that when restore occurs, no additional repair operations are required.
Solution Approach 2:
The invention creates a specialized copy of the database during backup that is specifically prepared for restore operations. This backup copy is generated with all consistency issues already resolved, making it a self-sufficient restoration source that eliminates the need for post-restore repair operations on the production cluster.
2Reliability
If repair operations are performed to reconcile data across the system cluster, then data consistency is improved, but processing resources and memory usage are significantly increased
Solution Approach 1:
The system performs data reconciliation and consistency checks during the backup operation itself, preparing the backup data in a consistent state before restore is needed. The backup process includes merging updates, identifying stale records, and creating a single consistent copy of updated data records, so that when restore occurs, no additional repair operations are required.
3Quantity of substance
If traditional backup methods back up data records from different nodes individually, then complete data coverage is achieved, but data inconsistencies and redundant records are generated
Solution Approach 1:
The system receives replica data records from multiple data storage nodes and merges them together during the backup process. The reconciliation node combines data from different nodes, merges updates, and consolidates the information into a single consistent backup copy, eliminating the fragmentation and inconsistency that would result from backing up each node separately.
Solution Approach 2:
The system identifies and discards stale or redundant data records during the backup process. The reconciliation node examines the merged replica data records, removes outdated or duplicate entries, and retains only the current, consistent data, thereby eliminating redundancy while maintaining complete data coverage.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The disclosed computer-implemented method for performing a database backup for repairless restore may include (1) receiving replica data records representing copies of a database from each of a group of data storage nodes in a production cluster, (2) processing the replica data records in parallel without inter-node communication between the data storage nodes, (3) merging updates to the replica data records, (4) identifying stale or redundant data records in the updated replica data records, (5) discarding the stale or redundant data records from the updated replica data records to create a single copy of updated data records, and (6) restoring the copy of the updated data records to the production cluster by replicating the updated data records to the data storage nodes such that each of the updated data records is consistent thereby obviating subsequent repair. Various other methods, systems, and computer-readable media are also disclosed.