Data Restoration Sequence Optimization for Backup Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data restore processes in backup/archive systems impose a heavy load due to servicing multiple data chunk requests sequentially, which is inefficient and resource-intensive.

Innovation Solution

A system and method that identifies and services multiple data retrieval requests using shared unique data chunks, determining an optimized sequence for consecutive servicing to minimize resource usage and improve efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system services multiple data retrieval requests sequentially in the order they arrived, then each request is serviced individually, but the load on the data backup/archive system increases significantly

Engineering Contradiction:
Improverequest servicing completenessVSAvoidsystem throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple data retrieval requests that share common data chunks into a single optimized servicing sequence. By identifying overlapping data chunk requirements across multiple requests and servicing them together in a determined sequence, the system reduces redundant operations and lowers overall system load while maintaining complete request fulfillment.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If the system locates and transfers all pieces required for each request before servicing the next request, then each request is completed fully, but the retrieval process becomes inefficient and resource-intensive

Engineering Contradiction:
Improvedata retrieval accuracyVSAvoidsystem resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent performs preliminary analysis to identify multiple data retrieval requests that can share common data chunks before actually servicing them. By pre-determining an optimized servicing sequence that consolidates shared data chunk transfers, the system avoids redundant locating and transferring operations, reducing resource consumption while ensuring accurate data retrieval for each request.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If the system processes each data retrieval request independently in arrival order, then the processing logic is simple, but the overall data restoration performance is poor

Engineering Contradiction:
Improverequest processing simplicityVSAvoiddata restoration efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent introduces dynamic request sequencing by analyzing the relationships between multiple data retrieval requests and reordering them based on shared data chunk patterns. Instead of static first-come-first-served processing, the system dynamically determines an optimized servicing sequence that consolidates common operations, improving data restoration efficiency while maintaining operational clarity through systematic request management.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9329942B2Optimizing restoration of deduplicated data
Publication Date: 2016.05.03 KYNDRYL INC
  • US9329942B2 patent drawing
  • US9329942B2 patent drawing
  • US9329942B2 patent drawing

AI summary

A computer identifies a plurality of data retrieval requests that may be serviced using a plurality of unique data chunks. The computer services the data retrieval requests by utilizing at least one of the unique data chunks. At least one of the unique data chunks is utilized for servicing two or more of the data retrieval requests. The computer determines a servicing sequence for the plurality of data retrieval requests such that the two or more of the data retrieval requests that are serviced utilizing the at least one of the unique data chunks are serviced consecutively. The computer services the plurality of data retrieval requests according to the servicing sequence.