Snapshot Conscious File Modification for NAS Storage Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional NAS technologies inefficiently utilize storage space due to inability to distinguish between internal and external file modifications during snapshot operations, leading to unnecessary data duplication.

Innovation Solution

Implementing a file system with components that modify storage for data blocks without altering content perceived externally, and prevent snapshot copies by using timestamps and locks to manage data compression and archival operations, ensuring only necessary data is preserved for snapshots.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional snapshot technologies are used to record file system state, then data recovery capability is provided, but storage space efficiency deteriorates due to unnecessary data duplication

Engineering Contradiction:
Improvedata recovery capabilityVSAvoidstorage space utilization
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments file modifications into two categories: internal modifications (compression, archival) and external modifications (user requests). By distinguishing between these segments, the system applies different snapshot handling rules - internal modifications do not trigger snapshot copies while external modifications do, thereby eliminating unnecessary data duplication while preserving data recovery capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary component (the file system layer) that sits between the snapshot mechanism and file modifications. This intermediary intelligently determines whether a modification should trigger a snapshot copy by checking if it's an internal or external modification, thus mediating between the snapshot system and storage space to prevent unnecessary duplication.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If compression data services are performed on file data, then storage density is improved, but snapshot service complexity increases due to inability to distinguish internal modifications

Engineering Contradiction:
Improvestorage densityVSAvoidsnapshot service complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent uses metadata tags (analogous to color changes) to mark file data as either 'internally modified' or 'externally modified'. This tagging system allows the snapshot service to quickly identify and differentiate between modification types without complex analysis, reducing snapshot service complexity while maintaining compression benefits.

Inventive Principle:
Principle #32Color changes

3Reliability

If snapshots create copies of all modified data, then data recovery is ensured, but storage space consumption increases due to copying internally modified data

Engineering Contradiction:
Improvedata recoveryVSAvoidstorage space consumption
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent implements a dynamic snapshot creation mechanism that adapts its behavior based on the modification type. Instead of a static rule that copies all modifications, the system dynamically determines whether to create a snapshot copy based on real-time analysis of the modification source (internal vs. external), thereby optimizing storage space consumption while ensuring data recovery for relevant changes.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10452641B1Snapshot conscious internal file data modification for network-attached storage
Publication Date: 2019.10.22 EMC IP HLDG CO LLC
  • US10452641B1 patent drawing
  • US10452641B1 patent drawing
  • US10452641B1 patent drawing

AI summary

Performing snapshot conscious internal file modification for network-attached storage is presented herein. A file system can comprise a first component configured to modify, during a service request, storage for a subset of data blocks of a file—the service request not being recognized by an external entity as a change of content of the file. Further, the file system can comprise a second component configured to prevent, based on the service request, a copy of the storage from being created for servicing of a snapshot—the snapshot comprising a point-in-time copy of the file system.