Database Log Management with Delimiter-Based Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database systems face challenges in quickly switching over to a backup database during disasters and in efficiently recovering data after a main center becomes unavailable, as existing methods require time-consuming matching processes and data copying, leading to prolonged interruptions in operations.

Innovation Solution

A database system management method that involves generating and transmitting log information with delimiter information to facilitate easy matching and recovery, allowing the system to switch over to a backup database without copying all operation data, enabling prompt recovery and minimizing downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the matching process is executed by collating journal data with operation data to ensure data consistency during disaster recovery, then data consistency is improved, but the time required for recovery is excessively long

Engineering Contradiction:
Improvedata consistencyVSAvoidrecovery time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-incorporating delimiter information into log data during normal database operations. This delimiter information marks transaction boundaries and data generation points in advance, so that during disaster recovery, the matching process can quickly identify and correlate transactions between journal data and operation data without performing extensive real-time collation, thus reducing recovery time while maintaining data consistency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses delimiter information as an intermediary element that facilitates the matching process. The delimiter information acts as a mediator between journal data and operation data, providing clear markers that enable rapid identification of transaction boundaries and corresponding data points, thereby streamlining the recovery matching process

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If all operation data is copied to the backup database to ensure complete data availability, then data completeness is improved, but the complexity and time of data copying is excessive

Engineering Contradiction:
Improvedata availabilityVSAvoiddata copying time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies the extraction principle by selectively transferring only the necessary log data containing delimiter information to the backup database, rather than copying all operation data. This extraction of essential recovery information reduces the volume of data that needs to be copied and stored, thereby decreasing data copying time and resource requirements while ensuring complete data availability for recovery

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial action by performing only the minimal necessary data copying operation - transferring log data with delimiter information - rather than copying the entire operation dataset. This partial copying approach provides sufficient information for complete recovery without the overhead of copying all data

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the synchronous mode is used to ensure consistency between main center and sub-center database updates, then data consistency is improved, but the operational complexity and manual intervention required during failures increases

Engineering Contradiction:
Improvedata consistencyVSAvoidoperational simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies self-service by enabling the backup database to automatically perform the matching and recovery processes using the pre-incorporated delimiter information in the log data. The system autonomously identifies transaction boundaries, matches journal data with operation data, and restores consistency without requiring system operators to manually input commands or execute complex procedures, thereby simplifying operations while maintaining consistency

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7650369B2Database system management method and database system
Publication Date: 2010.01.19 FUJITSU LTD
  • US7650369B2 patent drawing
  • US7650369B2 patent drawing
  • US7650369B2 patent drawing

AI summary

A control device 10 at a main center, in order for an update carried out in an operation database device M to be also conducted in an operation database device S at a sub-center, generates and transmits a differential log file 16 to a control device 20 at the sub-center. The control device 20 at the sub-center, when receiving a differential log file 22, updates the operation database device S on the basis of the log information in the differential log file 22, and accumulates the log information in a recovery log file 26. The log information of a recovery point set at the main center is incorporated into this recovery log file 26.