File Version Retrieval via Capture Manifest Indexing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In large-scale data centers, retrieving specific files or file versions from block-level storage requires reconstituting entire captures, which is resource-intensive and inefficient, as existing systems must rebuild the entire capture to access a single file or multiple file versions.

Innovation Solution

The implementation of a capture manifest and file retrieval logic that identifies the data chunks in a high durability data store where the requested files or file versions are stored, allowing for selective retrieval without reconstituting the entire capture, thereby reducing the need for expensive resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If entire captures are reconstituted to retrieve specific files or file versions, then data accessibility is improved, but resource consumption and time cost increase significantly

Engineering Contradiction:
Improvedata accessibilityVSAvoidretrieval time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent segments the capture data into discrete blocks and creates an index structure that maps file metadata to specific block locations. This allows the retrieval system to access only the specific blocks containing the requested file or file version, rather than reconstituting entire captures. The segmentation enables selective retrieval by breaking down the monolithic capture structure into accessible, addressable units.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by pre-processing capture data during the capture phase: organizing data into blocks, generating metadata, and creating an index structure that maps files to block locations. This preliminary organization is stored in the data store, enabling rapid retrieval operations later without requiring reconstitution of entire captures. The index structure is built in advance to facilitate efficient querying and selective block retrieval.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If entire captures are reconstituted to access specific files, then complete data integrity is ensured, but computational resources and cost increase

Engineering Contradiction:
Improvedata integrityVSAvoidcomputational resource usage
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the specific blocks containing the requested file or file version from the captured data, rather than processing entire captures. The index structure enables the retrieval system to identify and extract only the necessary blocks, leaving the rest of the capture data untouched. This extraction approach maintains data integrity for the retrieved portions while avoiding the computational overhead of processing complete captures.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by retrieving only the specific blocks needed for the requested file, rather than performing the excessive action of reconstituting entire captures. The index structure enables precise identification of the subset of blocks required, allowing the system to perform exactly the amount of work necessary (partial action) rather than the full reconstitution process (excessive action), thereby reducing computational resource usage while maintaining the integrity of the retrieved data.

Inventive Principle:
Principle #16Partial or excessive action

3Quantity of substance

If block-level storage with captures is used, then storage efficiency is improved, but retrieval efficiency for specific files deteriorates

Engineering Contradiction:
Improvestorage efficiencyVSAvoidretrieval efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent introduces an index structure as an intermediary between the block-level storage system and the retrieval operation. This index contains metadata that maps files to specific block locations, acting as a mediator that translates high-level file access requests into low-level block retrieval operations. The intermediary enables efficient navigation to specific blocks without requiring full capture reconstitution, thereby improving retrieval efficiency while maintaining the storage efficiency benefits of block-level organization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10936225B1Version history of files inside a backup
Publication Date: 2021.03.02 AMAZON TECH INC
  • US10936225B1 patent drawing
  • US10936225B1 patent drawing
  • US10936225B1 patent drawing

AI summary

A system includes a storage volume configured to store a data set in a plurality of data blocks, a data store configured to store a plurality of captures of the data set in a plurality of data chunks, and file retrieval logic. The data set includes a file stored in a data block of the plurality of data blocks. The plurality of captures includes the file captured at different points in time. The file retrieval logic is configured to identify the plurality of data chunks in which the data block as captured in the plurality of captures is stored in the data store, retrieve the plurality of data chunks from the data store, and read the data block as captured in the plurality of captures from the plurality of data chunks to produce a plurality of file versions.