File System Snapshot Coverage Management via Object-Level Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern distributed file systems face challenges in managing snapshot coverage due to their large size and asynchronous state changes, making it difficult to establish a stable data state and perform backup or restore operations efficiently.
Innovation Solution
A file system engine is instantiated to manage snapshot coverage by generating snapshots based on file system objects and their descendants, updating coverage sets, and providing read-only access, while also handling snapshot creation, deletion, and garbage collection to maintain data integrity and efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If snapshots are taken of entire file systems, then complete backup coverage is achieved, but storage size and generation time become prohibitively large
Solution Approach 1:
The patent divides the file system into individual objects (files and directories) and tracks snapshots at the object level rather than taking snapshots of the entire file system. Each object maintains its own coverage set indicating which snapshots include that object, enabling selective backup of only the necessary data portions.
Solution Approach 2:
The patent applies different snapshot coverage tracking to different file system objects based on their individual needs. Each object can have its own coverage set independent of others, allowing localized snapshot management where only modified or relevant objects are included in snapshots, reducing overall storage requirements.
2Reliability
If snapshots are taken of entire file systems, then complete backup coverage is achieved, but generation time becomes prohibitively large
Solution Approach 1:
The patent segments the snapshot creation process into individual object-level operations. Instead of freezing and copying the entire file system state, the system tracks which objects changed since the last snapshot and only processes those objects, dramatically reducing snapshot generation time while maintaining complete backup coverage.
Solution Approach 2:
The patent maintains coverage set information in advance, tracking which file system objects are included in each snapshot before the snapshot is actually needed. This preliminary tracking allows the system to quickly determine what needs to be backed up without performing a full file system scan at snapshot time.
3Measurement precision
If coverage sets are maintained for all file system objects, then snapshot management accuracy is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal coverage set data structure that serves multiple functions: tracking snapshot inclusion, determining backup requirements, and managing object lifecycle. This multi-functional approach consolidates what could be multiple separate tracking systems into a single unified mechanism, reducing overall system complexity while maintaining precise coverage tracking.
Data Source
AI summary
Embodiments are directed to managing data in a file system. An object from the file system that has parent objects may be provided. A snapshot in a current epoch may be generated such that the first snapshot may be based on the object and descendants of the object. A coverage set may be provided for the object that references the snapshot and also references each other snapshot that includes the parent objects. Read-only access to a version of the object may be provided based on a correspondence of the version and a snapshot referenced by the coverage set of the object. A coverage engine compares the update to a coverage update epoch (cue) associated with the parent objects. The coverage engine updates coverage sets of the parent objects based on grandparents of the object.