File System Historical Data Modification via Replicas

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods lack the ability to modify specific files or folders in a file system without losing the entire history, especially when protection is at the block level, due to the read-only nature of journal points in time, making it difficult to delete or change data securely and extend such modifications to replicas and journals.

Innovation Solution

The technique provides access to historical data of a file system through a replica or activity log, allowing irreversible alterations or deletions to apply changes to all previous points in time, using a secure API that interacts with the replica file system and journal component, ensuring modifications are propagated across all relevant snapshots.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If block-level protection is used to protect the file system, then the file system reliability is improved, but the ability to modify specific files or folders without losing entire history deteriorates

Engineering Contradiction:
Improvefile system reliabilityVSAvoidability to modify specific files or folders
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the file system into individual files and folders that can be independently managed. Instead of treating the entire file system as a single protected unit, the system allows selective identification and modification of specific files or folders within the replicated data, enabling granular control while maintaining overall system reliability through block-level protection.

Inventive Principle:
Principle #1Segmentation

2Reliability

If journal points in time are made read-only to maintain data integrity, then the data integrity is improved, but the ease of operation deteriorates

Engineering Contradiction:
Improvedata integrityVSAvoidease of modification
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary mechanism that allows users to request modifications to historical data. When a modification request is received, the system retrieves the specific file or folder from the replicated data, applies the modification, and then propagates the changes back to the journal points in time. This intermediary process maintains data integrity by controlling the modification flow while providing operational flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If conventional replication methods are used, then the system reliability is improved, but the loss of information deteriorates

Engineering Contradiction:
Improvesystem reliabilityVSAvoidloss of file system history
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent creates copies of the file system at different points in time through replication. These replicas serve as historical snapshots that can be selectively modified without affecting the original file system or other replicas. By maintaining multiple copies and allowing selective modification of specific files or folders in each replica, the system preserves the complete history while enabling flexible modifications.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10719481B1Modification of historical data of file system in data storage environment
Publication Date: 2020.07.21 EMC IP HLDG CO LLC
  • US10719481B1 patent drawing
  • US10719481B1 patent drawing
  • US10719481B1 patent drawing

AI summary

Access to historical data of a file system in a data storage environment is provided, wherein the historical data corresponds to one or more points in time occurring in the past. The historical data of the file system is modified, wherein the historical data comprises at least one of a component from a replica of the file system and an element of an activity log of the file system.