Filesystem Snapshot COW Disable for Backup Performance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current snapshot-backup processing in file systems requires continuous Copy On Write (COW) activity for all file system changes, leading to high I/O, CPU cycles, and disk space consumption, which is costly and inefficient, especially for active file systems.
Innovation Solution
The method involves generating a snapshot and initiating a backup by duplicating data, then disabling COW functionality for each file as soon as the backup is complete, allowing subsequent updates to occur without COW operations, thereby reducing overhead and optimizing disk space usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If copy-on-write functionality is maintained for all files during backup, then snapshot consistency is preserved, but I/O consumption and disk space utilization increase significantly
Solution Approach 1:
The patent segments the file system into two categories: files that are being actively modified and files that are not. By identifying and separating these file types, the system applies copy-on-write selectively only where necessary, rather than uniformly across all files. This segmentation allows the system to maintain snapshot consistency for modified files while avoiding unnecessary I/O operations for static files, directly resolving the contradiction between reliability and energy loss.
Solution Approach 2:
The patent implements local quality by making copy-on-write behavior file-specific rather than system-wide. The system dynamically determines which individual files require copy-on-write protection based on their modification status, allowing different parts of the file system to have different quality characteristics. This localized approach maintains data integrity where needed while minimizing I/O consumption in areas where it is not required.
2Reliability
If copy-on-write functionality is maintained for all files during backup, then snapshot consistency is preserved, but disk space consumption increases
Solution Approach 1:
The patent segments the file system into modified and non-modified files, applying copy-on-write selectively. This segmentation prevents the creation of redundant copies for files that do not change, thereby reducing disk space consumption while maintaining snapshot consistency for files that actually require it.
Solution Approach 2:
The patent implements a mechanism to discard copy-on-write allocations for files that are not being modified during the backup process. By identifying static files and recovering the disk space that would have been allocated for their copy-on-write operations, the system reduces overall disk space consumption while preserving snapshot integrity for active files.
3Loss of energy
If copy-on-write activity is reduced during backup, then I/O and disk space consumption decrease, but snapshot consistency may be compromised
Solution Approach 1:
The patent segments files into modified and non-modified categories, applying copy-on-write only to modified files during backup. This selective approach reduces overall I/O consumption while maintaining snapshot consistency for the subset of files that require it, preventing the compromise of reliability that would occur with blanket reduction of copy-on-write activity.
Solution Approach 2:
The patent implements local quality by making copy-on-write protection file-specific based on modification status. This allows the system to reduce I/O consumption system-wide while maintaining local snapshot consistency where actually needed, preventing the reliability compromise that would result from uniform reduction of copy-on-write operations.
4Reliability
If continuous copy-on-write monitoring is performed for all files, then data integrity is maintained, but CPU cycle consumption increases
Solution Approach 1:
The patent segments the file system into modified and non-modified files, eliminating the need for continuous copy-on-write monitoring of non-modified files. This segmentation reduces CPU cycle consumption by focusing monitoring efforts only on files that actually require integrity protection, while maintaining data integrity for the relevant subset of files.
Solution Approach 2:
The patent extracts and removes the unnecessary copy-on-write monitoring overhead for static files from the system. By identifying and taking out the monitoring requirement for non-modified files, the system reduces CPU cycle consumption while preserving data integrity monitoring for files that actually need it.
Data Source
AI summary
Reducing copy on write activity during snapshot backup processing in computer system. A snap shot of the data is created. As the backup of each file is successfully completed, the copy-on-write functionality for the file is disabled. As the backup of each other file is successfully completed, the copy-on-write for each other file is disabled.