Event-Driven File System Snapshot Management

Solution Overview

Problem

Time-based management strategies for file systems can be inefficient, leading to either inadequate data restoration or unnecessary resource waste, as they may not adapt well to frequent data modifications.

Innovation Solution

A method that involves receiving events associated with file system operations, determining counter values based on execution information, and triggering specific actions according to predefined strategies, allowing for finer granularity and flexibility in file system management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If the cycle of creating a snapshot is too long, then resources are saved, but data restoration capability deteriorates

Engineering Contradiction:

Improveresource consumptionVSAvoiddata restoration capability

Core Design Contradiction:

Loss of energyVSReliability

Solution Approach 1:

The patent implements dynamic snapshot creation by transitioning from fixed time-based cycles to event-driven triggering. The system dynamically adjusts snapshot creation timing based on file system events and configured policies, creating snapshots only when necessary (e.g., on file system mount, unmount, or specific operation triggers) rather than following rigid time intervals. This resolves the contradiction by optimizing resource usage while maintaining data restoration capability through context-aware snapshot creation.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of snapshot creation from time-based intervals to event-based triggers. By monitoring file system events and using configurable policies, the system transforms the snapshot creation mechanism from a static time-driven process to a dynamic event-driven process, allowing snapshots to be created based on actual file system state changes rather than predetermined time schedules.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If the cycle of creating a snapshot is too short, then data restoration capability is improved, but resource consumption increases

Engineering Contradiction:

Improvedata restoration capabilityVSAvoidresource consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system implements dynamic snapshot creation by transitioning from fixed time-based cycles to event-driven triggering. The system dynamically adjusts snapshot creation timing based on file system events and configured policies, creating snapshots only when necessary (e.g., on file system mount, unmount, or specific operation triggers) rather than following rigid time intervals. This resolves the contradiction by optimizing resource usage while maintaining data restoration capability through context-aware snapshot creation.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of snapshot creation from time-based intervals to event-based triggers. By monitoring file system events and using configurable policies, the system transforms the snapshot creation mechanism from a static time-driven process to a dynamic event-driven process, allowing snapshots to be created based on actual file system state changes rather than predetermined time schedules.

Inventive Principle:

Principle #35Parameter changes

3Ease of operation

If time-based management strategies are used, then implementation simplicity is maintained, but management efficiency deteriorates

Engineering Contradiction:

Improveimplementation simplicityVSAvoidmanagement efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The system changes the parameter of snapshot creation from time-based intervals to event-based triggers. By monitoring file system events and using configurable policies, the system transforms the snapshot creation mechanism from a static time-driven process to a dynamic event-driven process, allowing snapshots to be created based on actual file system state changes rather than predetermined time schedules.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The system implements feedback mechanisms by monitoring file system events and using this information to trigger snapshot creation. The event-driven architecture continuously observes file system state changes and uses this feedback to determine when snapshots should be created, enabling the system to adapt to actual usage patterns and optimize management efficiency while maintaining ease of operation through configurable policies.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11886383B2Method, device and computer program product for managing file system

Publication Date: 2024.01.30 EMC IP HLDG CO LLC

AI summary

Techniques for managing a file system involve: receiving an event published by the file system, the event being associated with an operation on an object in the file system; determining a value of a counter corresponding to the event based on execution information of the operation; determining a target action corresponding to the value of the counter based on a trigger strategy associated with the counter, the trigger strategy defining at least one action that can be triggered by the counter; and generating an indication for causing the file system to execute the target action. Accordingly, file system management in finer granularity can be provided.