Dynamic Prioritized Recovery for Data Sub-Objects

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data protection schemes are either too slow or too expensive and require complete recovery before allowing access to data systems, which is not feasible given the increasing expectation of continuous accessibility in modern data systems.

Innovation Solution

A method that segments data into sub-objects and assigns priorities for recovery, allowing partial access through Local I/O or Remote I/O during recovery, with the option to pin sensitive data for integrity and use Intercept to manage access, enabling dynamic prioritization and partial recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional data protection schemes are used to restore data systems, then data integrity is ensured, but recovery time is too long and access is blocked until complete recovery

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

Solution Approach 1:

The patent segments the data system into multiple priority levels or partitions, allowing selective recovery of critical data segments first while non-critical segments are recovered in the background. This enables partial system access during recovery, reducing overall recovery time while maintaining data integrity through controlled access mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial recovery by allowing access to recovered data segments before complete recovery is finished. Critical segments are recovered and made accessible immediately, while non-critical segments continue recovering in the background, thus reducing the perceived recovery time for essential operations.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If complete recovery is required before allowing access to data systems, then data consistency is maintained, but business continuity is disrupted

Engineering Contradiction:
Improvedata consistencyVSAvoidbusiness continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces dynamic access control that adapts during the recovery process. Access permissions are dynamically adjusted based on recovery progress and data segment priority, allowing read-only or restricted access to recovered segments while write access remains blocked until full recovery completes, thus maintaining consistency while enabling business continuity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces an intermediary access layer or gateway that mediates between users and the recovering data system. This intermediary validates access requests, redirects to available recovered segments, and manages access permissions, enabling partial business operations during recovery while ensuring data consistency through controlled access.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If faster recovery is implemented, then accessibility is improved, but data integrity risks increase

Engineering Contradiction:
Improverecovery speedVSAvoiddata integrity
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent applies different quality levels of recovery validation to different data segments. Critical segments undergo rigorous integrity validation before access is permitted, while non-critical segments may be made accessible with lighter validation or deferred validation, thus enabling faster overall recovery while maintaining data integrity for essential operations.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11294770B2Dynamic prioritized recovery
Publication Date: 2022.04.05 EMC IP HLDG CO LLC
  • US11294770B2 patent drawing
  • US11294770B2 patent drawing
  • US11294770B2 patent drawing

AI summary

A method, article of manufacture, and apparatus for recovering data. In some embodiments, this includes selecting an object to be recovered, recovering sub-objects of the object based on the priorities assigned to the sub-objects, and reprioritizing the sub-objects based on an application's I/O during recovery. In some embodiments, reprioritizing the sub-objects the sub-objects includes assigning a lower priority to the sub-objects when an application has completed I/O on the object. In some embodiments, recovering sub-objects includes recovering sub-objects to a remote location.