Excluding Directory Trees from Snapshot Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing filesystem snapshot technologies often incur high file I/O costs and space consumption due to the inclusion of highly active directories, which can slow down systems and consume excessive resources.
Innovation Solution
The implementation of a domain framework that allows for the exclusion of specific directory trees from snapshot operations by creating exclusion domains, enabling granular control over which files are included or excluded from snapshot policies through domain membership management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all directories are included in snapshot operations, then complete data backup is achieved, but file I/O costs and space consumption increase significantly
Solution Approach 1:
The patent segments the filesystem into multiple domains with different snapshot policies. By dividing the namespace into domain groups, the system can apply snapshot operations selectively to specific domains rather than universally to all directories, thereby reducing unnecessary I/O on high-activity directories while maintaining backup completeness for critical data domains.
Solution Approach 2:
The patent implements local quality by allowing different snapshot policies to be applied to different domains. Each domain can have customized snapshot settings based on its specific requirements, enabling critical domains to receive full snapshot protection while non-critical domains with high activity can be excluded or have reduced snapshot frequency, optimizing the balance between backup reliability and I/O cost.
2Reliability
If all directories are included in snapshot operations, then complete data backup is achieved, but system performance slows down
Solution Approach 1:
By segmenting the filesystem into domains, the patent enables selective snapshot application. This segmentation allows the system to maintain complete backup coverage for critical domains while excluding or reducing snapshots in non-critical domains, thereby preserving system performance during snapshot operations.
Solution Approach 2:
The domain-based approach allows local quality optimization where different performance characteristics can be applied to different parts of the filesystem. Critical domains can have robust snapshot policies while performance-sensitive domains can have optimized or excluded snapshot policies, maintaining overall system productivity.
3Reliability
If highly active directories are included in snapshots, then data backup completeness is maintained, but space consumption increases excessively
Solution Approach 1:
The patent segments the filesystem into domains, enabling selective snapshot application. By excluding highly active directories from snapshot domains or placing them in domains with reduced snapshot policies, the system avoids copying large amounts of changing data, thereby significantly reducing space consumption while maintaining backup completeness for static or less-active critical data.
Solution Approach 2:
The domain framework allows local quality differentiation where critical data domains receive full snapshot protection ensuring backup completeness, while highly active non-critical domains can be configured with excluded or reduced snapshot policies, optimizing storage space utilization.
Data Source
AI summary
The described technology is generally directed towards domains that data services can use to collect files of a global filesystem namespace into groups, and domains that can be used to exclude certain files or metadata. A data service (a domain patron) creates a domain, e.g., for a particular directory, and a domain manager associates files under that directory with domain membership information. The data service can relate exclusion information to the domain, e.g., to exclude part of the directory. This can be done by an exclusion domain instance, e.g., a child to a parent domain, or can be done in metadata, by having the data service (e.g., a snapshot data service) exclude certain metadata such as snapshot identifiers from a larger set of snapshot identifiers.