Incremental Data Restore via Active Block Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data restoration methods are cumbersome, bandwidth-intensive, time-consuming, and inefficient, particularly in enterprise networks, as they involve sequential restoration of entire disk systems without prioritizing frequently accessed data blocks.

Innovation Solution

The implementation of a background restore module that uses logical volume manager (LVM) snapshots to incrementally restore data by prioritizing frequently accessed blocks and allowing concurrent backup operations, enabling simultaneous data retrieval and writing of restore blocks from secondary storage to primary storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If conventional sequential restore operation is used, then data restoration can be performed, but restoration time is excessive and system performance is degraded

Engineering Contradiction:
Improverestoration timeVSAvoidsystem performance
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The restore operation is segmented into two independent streams: a high-priority stream for active data blocks and a low-priority stream for inactive blocks. This segmentation allows the system to restore critical data quickly while continuing to restore less critical data in the background, thereby reducing overall restoration time and minimizing impact on system performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary identification and classification of data blocks into active and inactive categories before the restore operation begins. By pre-determining which blocks require high-priority restoration based on access patterns and importance, the system can optimize the restore sequence and reduce total restoration time without compromising data completeness.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If entire disk is restored sequentially from secondary storage, then data restoration is completed, but bandwidth consumption is excessive and restoration is time-consuming

Engineering Contradiction:
Improvedata transfer volumeVSAvoidrestoration duration
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The invention extracts only the necessary active data blocks from the secondary storage for immediate restoration, rather than transferring the entire disk image. By identifying and extracting only the high-priority blocks that are currently in use or recently accessed, the system significantly reduces the volume of data that requires immediate bandwidth consumption, thereby shortening restoration duration.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The restore operation transitions from a static sequential process to a dynamic parallel process where active and inactive block restoration occur simultaneously at different priorities. This dynamic approach allows the system to adapt data transfer operations to current workload conditions, optimizing bandwidth usage and restoration time based on real-time system state.

Inventive Principle:
Principle #15Dynamics

3Reliability

If conventional backup and restore operations are performed, then data protection is maintained, but operational complexity and administrative burden increase

Engineering Contradiction:
Improvedata protectionVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service functionality by automatically identifying active and inactive data blocks based on access patterns and restore priorities without requiring manual administration. The backup and restore operations are performed autonomously by the system, reducing operational complexity and administrative burden while maintaining robust data protection through intelligent, automated decision-making.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If sequential restore starts from beginning of secondary disk, then restore operation is simple, but frequently accessed blocks are not prioritized and performance is reduced

Engineering Contradiction:
Improverestore operation simplicityVSAvoiddata access speed
Core Design Contradiction:
Ease of operationVSSpeed

Solution Approach 1:

The invention applies local quality by treating different data blocks differently based on their characteristics. Active blocks that are frequently accessed receive high-priority restoration treatment, while inactive blocks receive low-priority treatment. This differentiated approach optimizes data access speed for critical blocks without fundamentally complicating the overall restore operation, maintaining ease of use while significantly improving performance.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7913116B2Systems and methods for incremental restore
Publication Date: 2011.03.22 RED HAT INC
  • US7913116B2 patent drawing
  • US7913116B2 patent drawing
  • US7913116B2 patent drawing

AI summary

An embodiment relates generally to a method of restoring data in storage systems. The method includes providing for a current snapshot of a primary storage system at a secondary storage system and mounting an empty volume in the primary storage system. The method also includes receiving a request for a selected block of data in the primary storage system and retrieving a restore block from the secondary storage system, where the restore block encompasses the selected block of data. The method further includes writing the restore block to the empty volume in the primary storage system as an incremental restore process.