Fileshot Metadata for File-Level Backup Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current backup and restore techniques are inefficient as they often require replicating entire data sets, wasting resources and limiting users to volume-level backups, which restrict fine-grained control and accessibility, especially through file structures.

Innovation Solution

Implementing fileshots as metadata within a file structure, allowing users to manage backups and restores through a directory interface, enabling file-level backup management by storing backup data as hidden streams linked to files, accessible via command or graphical user interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If volume-level backup techniques are used, then backup coverage is comprehensive, but fine-grained control and accessibility are restricted

Engineering Contradiction:
Improveaccessibility through file structureVSAvoidbackup management granularity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments backup management from volume-level operations into file-level operations. By implementing fileshots as metadata within the file structure, each file can be independently backed up, managed, and restored. This segmentation allows users to access and manage specific file backups through the directory interface without being constrained by volume-level backup limitations, thereby improving accessibility and fine-grained control.

Inventive Principle:
Principle #1Segmentation

2Reliability

If entire data sets are replicated for backup, then data protection is comprehensive, but resource usage increases

Engineering Contradiction:
Improvedata protectionVSAvoidresource usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary backup information (fileshots) from the entire data set and stores it as metadata within the file structure. Instead of replicating entire volumes or data sets, the system captures and stores file-level backup data selectively. This extraction approach maintains data protection reliability while significantly reducing the resources required for backup operations.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If application-specific backup features are used, then backup functionality is provided, but accessibility is restricted to application user interface

Engineering Contradiction:
Improvebackup accessibilityVSAvoidbackup management flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal backup management system that works across multiple applications and contexts through the file structure's directory interface. By storing fileshots as file metadata rather than application-specific data, the system enables backup management through standard file operations (copy, move, delete, rename) that are universally accessible regardless of which application created or is managing the file. This multi-functionality provides both broad accessibility and flexible adaptability.

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

Data Source

PatentUS9183208B1Fileshot management
Publication Date: 2015.11.10 NETAPP INC
  • US9183208B1 patent drawing
  • US9183208B1 patent drawing
  • US9183208B1 patent drawing

AI summary

Many applications and computing environments, such as data storage systems, provide data backup and restoration features. It may be advantageous to provide file level backups that may be accessible to a user through a directory structure of a file system. Accordingly, fileshots comprising backup data of a file may be stored as metadata of the file. For example, a fileshot may be stored within a stream directory as a hidden stream linked off of the file. Fileshots may be associated within a directory interface (e.g., a command prompt or graphical user interface), which may be presented to a user. In this way, the user may access and/or manage fileshots through the directory interface (e.g., the user may create fileshots, restore files with fileshots, copy fileshots, etc.). Additionally, fileshot metadata may be maintained for fileshots. The fileshot metadata may be used to locate fileshot and/or perform fileshot commands.