Dual-Active Database Disk Segmentation for Maintenance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing dual-active database systems face challenges in ensuring efficient data protection against software or hardware failures, disasters, and temporary unavailability during system maintenance, leading to potential data inconsistency and Single Point of Failure (SPOF) risks.

Innovation Solution

A dual-active database system is deployed with two active database sites, each comprising multiple sub-groups of disks that form consistency pairs, where one pair remains operational while the other stops for maintenance, ensuring real-time synchronization within a threshold latency time to maintain data consistency and prevent SPOF.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If database maintenance is performed on a single active database site, then system maintenance can be conducted, but data inconsistency and Single Point of Failure risks occur

Engineering Contradiction:
Improvemaintenance capabilityVSAvoiddata consistency
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The database system is segmented into multiple consistency pairs of disk sub-groups across two active database sites. Each consistency pair can be independently maintained, allowing maintenance operations to be performed on one pair while other pairs continue to serve data requests, thus maintaining overall system availability and data consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different sub-groups of disks are assigned different functional qualities - some are designated for data storage while others are designated for maintenance operations. This local differentiation allows maintenance to occur on specific sub-groups without affecting the overall database availability or consistency.

Inventive Principle:
Principle #3Local quality

2Reliability

If real-time synchronization is implemented between consistency pairs, then data consistency is maintained, but system complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system pre-establishes consistency pairs with predetermined synchronization relationships. By preparing the synchronization infrastructure in advance and organizing disks into predefined pairs, the actual real-time synchronization operation becomes a straightforward execution of pre-planned relationships rather than complex dynamic coordination.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If multiple consistency pairs are used for maintenance flexibility, then system availability improves, but device complexity increases

Engineering Contradiction:
Improvemaintenance flexibilityVSAvoidconsistency pair management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The disk group is segmented into multiple independent consistency pairs, each capable of independent maintenance operations. This segmentation allows maintenance flexibility while keeping each pair's management simple and isolated from others.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each consistency pair is designed with universal functionality to handle both data storage and maintenance operations independently. This multi-functionality reduces the need for specialized management mechanisms for different operational modes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11604807B2Dual-active database for data protection
Publication Date: 2023.03.14 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11604807B2 patent drawing
  • US11604807B2 patent drawing
  • US11604807B2 patent drawing

AI summary

In an embodiment, a computer-implemented method comprises deploying a dual-active database on a first active database site and a second active database site. The first active database site comprises a first group of disks including a first sub-group of disks and a second sub-group of disks respectively corresponding to a third sub-group of disks and a fourth sub-group of disks included in a second group of disks in the second active database site. The method further comprises storing a first set of database logs on the first sub-group of disks while a second set of database logs is being written on the second sub-group of disks. Contents of the second set of database logs are consistent with contents of the first set of database logs and function as a duplication of the first set of database logs.