Shallow File Offloading for Data Protection Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data protection services in file systems often cause slow data processing, inconveniencing clients with blocked read-write access and decreased responsiveness during backup processes, especially when concurrent with data processing on electronic documents.

Innovation Solution

A data processing system with a first data processor for client access and a second data processor for offloading data protection services, utilizing a 'shallow file' type that includes data block mapping metadata and a link to the primary file, allowing direct access to data blocks without copying, thus avoiding slow data processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data protection services process the entire electronic document on the same data processor, then data protection is achieved, but client access speed and responsiveness deteriorate

Engineering Contradiction:
Improvedata protectionVSAvoidclient access speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system segments data protection services from client access services by using separate data processors. The primary data processor handles client access while the secondary data processor handles data protection services, allowing both functions to operate concurrently without interfering with each other's performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (the shallow file system with data block mapping metadata) that allows the secondary data processor to access and process document data without requiring the document to be physically copied or moved, thus maintaining fast access speeds while enabling data protection processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the entire electronic document is copied for data protection services, then data protection processing is enabled, but data processing time and storage resources increase

Engineering Contradiction:
Improvedata protection processingVSAvoiddata processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a shallow copy of the document metadata (data block mapping) rather than copying the actual document data. This shallow file contains only the metadata structure and links to the original data blocks, enabling data protection services to process the document without duplicating the entire data set, thus significantly reducing processing time and storage requirements.

Inventive Principle:
Principle #26Copying

3Speed

If data protection services are offloaded to a separate data processor, then client access performance is maintained, but system complexity increases

Engineering Contradiction:
Improveclient access performanceVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The shallow file system structure serves multiple functions: it enables fast client access through direct data block addressing, supports data protection services through metadata copying, and provides a unified interface for both read and write operations. This multi-functionality reduces the need for separate complex mechanisms for each function.

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

Data Source

PatentUS7653612B1Data protection services offload using shallow files
Publication Date: 2010.01.26 EMC IP HLDG CO LLC
  • US7653612B1 patent drawing
  • US7653612B1 patent drawing
  • US7653612B1 patent drawing

AI summary

A shallow file is adapted for intensive read-only access to data of a primary file. The primary file resides in another file system or file server. The shallow file includes the data block mapping metadata of the primary file and a link to the primary file. To open the shallow file, the file system manager of the shallow file obtains a read lock on the primary file from the file system manager of the primary file. Then the file system manager of the shallow file may use the data block mapping in the shallow file to access the file data from the primary file in storage without participation of the file system manager of the primary file. This permits offloading of data protection services for secure and efficient storage of a backup copy of the file data.