Backup Data Consistency During Primary Storage Failover

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Data management systems face challenges in switching from a primary copy to a backup copy while maintaining availability and consistency, especially when the backup copy is in an inconsistent state due to differences in synchronous and asynchronous replication methods, particularly in complex data sets with interdependencies.

Innovation Solution

A method is introduced that prepares a backup copy by updating it according to a defined protocol, which synchronously updates one type of data and asynchronously updates another, and identifies and corrects inconsistencies in interdependent data using a predefined schema and correction protocol, allowing the backup copy to replace the primary copy for servicing transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of moving object

If asynchronous replication is used to update backup copies, then data availability is improved, but data consistency deteriorates because the backup copy is in an inconsistent state relative to the primary copy

Engineering Contradiction:

Improvedata availabilityVSAvoiddata consistency

Core Design Contradiction:

Duration of action of moving objectVSLoss of information

Solution Approach 1:

The system performs preliminary actions by identifying inconsistencies in the backup copy before switching from primary to backup storage. The inconsistency identification process examines interdependent data in the backup copy against a schema to detect any inconsistencies prior to the failover event, ensuring data consistency is restored before availability is compromised.

Inventive Principle:

Principle #10Preliminary action

2Loss of information

If synchronous replication is used to update backup copies, then data consistency is improved, but data availability deteriorates because data transactions cannot be completed until changes are made to both primary and backup copies

Engineering Contradiction:

Improvedata consistencyVSAvoiddata availability

Core Design Contradiction:

Loss of informationVSDuration of action of moving object

Solution Approach 1:

The system segments the replication approach by applying different replication strategies to different types of data. The backup protocol specifies synchronously updating the backup copy for some data types while asynchronously updating for other data types, allowing the system to optimize for both consistency and availability based on data type requirements.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If complex data sets with interdependencies are replicated using mixed synchronous and asynchronous protocols, then adaptability is improved, but device complexity increases making it challenging to meet availability and consistency requirements

Engineering Contradiction:

Improvereplication flexibilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system applies local quality by tailoring the replication protocol to the specific requirements of each data type. The backup protocol specifies synchronously updating the backup copy for critical data types requiring consistency, while asynchronously updating for other data types where availability is prioritized, allowing differentiated treatment based on local data characteristics.

Inventive Principle:

Principle #3Local quality

4Productivity

If the backup copy is updated asynchronously, then productivity is improved, but measurement precision deteriorates as the backup copy falls behind the primary copy

Engineering Contradiction:

Improvetransaction processing speedVSAvoiddata synchronization accuracy

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

The system implements feedback by continuously monitoring the backup copy for inconsistencies after asynchronous updates. The inconsistency identification process acts as a feedback mechanism that detects when the backup copy has diverged from the primary copy, triggering corrective actions before the inconsistency affects data availability or integrity.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11068351B2Data consistency when switching from primary to backup data storage

Publication Date: 2021.07.20 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Switching from primary to backup data storage by preparing a backup copy of multiple data sets, where, prior to the preparing, the backup copy is updated in accordance with a backup protocol specifying synchronously updating the backup copy to reflect changes made to one type of data stored in a primary copy of the data sets, and asynchronously updating the backup copy to reflect changes made to another type of data stored in the primary copy, and where the preparing includes identifying any inconsistency in any interdependent data in the data sets of the backup copy in accordance with a predefined schema of interdependent data in the data sets, and correcting any identified inconsistency in the data sets of the backup copy in accordance with a predefined inconsistency correction protocol, and causing the backup copy to be used in place of the primary copy for directly servicing data transactions.