Undo Log Mechanism for Atomic Data Protection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data protection methods in storage systems are inadequate in ensuring data integrity and recovery from corruption, as they rely on point-in-time backups and manual restoration processes, which can be inefficient and prone to errors.

Innovation Solution

Implementing an undo log mechanism that uses a 'read before write' technique to maintain atomic operations, allowing for the creation of a single command that ensures data consistency and automatic recovery to a previous point in time, thereby eliminating intermediate updates and enhancing data protection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If point-in-time backups are used for data protection, then data recovery capability is provided, but data integrity cannot be ensured and recovery processes are manual and error-prone

Engineering Contradiction:
Improvedata integrityVSAvoidrecovery process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by copying previously written data to a second storage location before the new data is written to the first storage location. This creates a backup of the previous state that can be used for recovery without requiring manual intervention, thereby ensuring data integrity while simplifying the recovery process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service recovery by automatically maintaining backup copies of previously written data in the second storage location. When data corruption is detected, the system can automatically restore the previous state from the backup without requiring manual intervention, thus ensuring data integrity while making the recovery process easier.

Inventive Principle:
Principle #25Self-service

2Productivity

If manual restoration processes are used for data recovery, then data can be restored to previous state, but the process is inefficient and time-consuming

Engineering Contradiction:
Improverecovery efficiencyVSAvoidrecovery time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary copying of previously written data to the second storage location before new data is written. This pre-prepared backup enables rapid automatic recovery without manual intervention, significantly improving recovery efficiency and reducing recovery time compared to manual restoration processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the previously written data in the second storage location before overwriting it with new data. This copy can be quickly retrieved and used for restoration, enabling efficient automatic recovery and reducing the time required compared to manual restoration processes.

Inventive Principle:
Principle #26Copying

3Reliability

If read before write operations are performed separately, then data consistency can be maintained, but system performance is reduced due to multiple operations

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system merges the read before write operations into a single atomic command that performs both the read (copying previously written data) and write (storing new data) operations in one unified instruction. This maintains data consistency by ensuring the previous state is captured before the new state is written, while improving system performance by reducing the number of separate operations.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The single command performs multiple functions: it reads the previously written data, copies it to the second storage location, and writes the new data to the first storage location. This multi-functional approach maintains data consistency while improving system performance by consolidating multiple operations into one atomic command.

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

Data Source

PatentUS7761732B2Data protection in storage systems
Publication Date: 2010.07.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US7761732B2 patent drawing
  • US7761732B2 patent drawing
  • US7761732B2 patent drawing

AI summary

Provided are a method, system, and article of manufacture wherein a command is received for writing data to a first storage location. A determination is made that previously written data is stored in the first storage location. The previously written data is copied to a second storage location, in response to determining that the previously written data is stored in the first storage location. The data is written to the first storage location, in response to copying the previously written data to the second storage location.