Snapshot Database Re-sync Using Version Number Tracking

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for re-syncing snapshot databases with base databases are inefficient, particularly for large databases, as they require time-consuming data comparisons or additional processing costs, and are resource-intensive, especially in clustered systems.

Innovation Solution

The method involves tracking version numbers for data units in both databases, where changes are marked with a second version number, allowing only modified units to be synced, reducing the need for comprehensive data comparisons and processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If data block comparison method is used to re-sync snapshot database, then data synchronization accuracy is improved, but computational cost and time consumption increase significantly for large databases

Engineering Contradiction:

Improvedata synchronization accuracyVSAvoidtime consumption

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The database is divided into multiple data units with individual version numbers. Instead of comparing all data blocks, only data units with version number changes are identified and synchronized. This segmentation approach maintains synchronization accuracy while dramatically reducing the time and computational resources required by limiting comparisons to only changed segments.

Inventive Principle:

Principle #1Segmentation

2Reliability

If comprehensive data comparison is performed for re-sync, then data consistency is ensured, but resource consumption increases

Engineering Contradiction:

Improvedata consistencyVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Version numbers are assigned to data units in advance before synchronization occurs. This preliminary action of version tracking allows the system to identify which data units have changed without performing comprehensive comparisons during the re-sync process, thereby ensuring data consistency while reducing computational resource consumption.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If change logging is implemented to track database modifications, then re-sync efficiency is improved, but additional processing overhead is introduced

Engineering Contradiction:

Improvere-sync efficiencyVSAvoidprocessing overhead

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

Instead of maintaining detailed change logs with timestamps, the system uses version numbers as a simplified parameter to track data unit modifications. This parameter change approach maintains re-sync efficiency by quickly identifying changed data units while reducing the complexity and processing overhead associated with comprehensive change logging mechanisms.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS10353920B2Efficient mirror data re-sync

Publication Date: 2019.07.16 ORACLE INT CORP

AI summary

Techniques are described herein for re-syncing a snapshot database with a base database. Data units of each database are associated with version numbers. When a data unit is modified, the data unit is associated with the current version number. When a snapshot database is re-synced with a base database, particular data units are copied from the base database to the snapshot database, based on the version number associated with the particular data units.