Adaptive Copy-On-Write Snapshot Management for Distributed Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for preserving older versions of data in digital computing systems are inefficient, as they often require copying entire data systems, which is time-consuming and expensive, and do not allow for system flexibility, especially in large-capacity storage devices and distributed systems.
Innovation Solution
The implementation of a method that determines whether to use Copy-On-Write (COW) or Point-In-Time-Copy (PITC) operations to store multiple versions of files, allowing for efficient snapshot creation and management by deciding on the appropriate operation based on file modifications, thereby reducing the need for extensive data copying.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire contents of the storage device are copied to preserve older versions of data, then data version preservation is achieved, but the operation becomes time-consuming and delays write requests
Solution Approach 1:
The patent divides the storage device into multiple segments or portions, allowing snapshots to be taken of specific segments rather than the entire storage device. This segmentation enables selective copying of only the necessary data portions, significantly reducing the time required for snapshot operations while maintaining data version preservation capability.
Solution Approach 2:
The patent implements different copy strategies for different portions of the storage device based on local characteristics. Copy-on-write operations are performed selectively on specific data blocks that have changed, rather than uniformly copying all data. This local quality approach ensures that only necessary data is copied, reducing overall operation time while preserving data versions.
2Reliability
If the entire contents of the storage device are copied to preserve older versions of data, then data version preservation is achieved, but additional storage space is required which increases expense
Solution Approach 1:
The patent extracts only the necessary portions of data for snapshot creation rather than copying the entire storage device contents. By identifying and extracting only the changed data blocks, the system reduces the quantity of data that needs to be stored for version preservation, thereby reducing storage space requirements and associated expenses.
Solution Approach 2:
The storage device is divided into segments, allowing snapshots to be created for specific segments rather than the entire device. This segmentation reduces the total volume of data that must be copied and stored for version control, directly addressing the storage space consumption issue.
3Reliability
If traditional backup methods are used to preserve data versions, then data preservation is achieved, but system flexibility is reduced
Solution Approach 1:
The patent implements a dynamic snapshot system that can adapt to different operational requirements. The system can dynamically determine which portions of the storage device require snapshotting based on change detection, allowing flexible adjustment of snapshot scope and frequency. This dynamic approach maintains data preservation while enhancing system flexibility compared to static traditional backup methods.
Solution Approach 2:
Different snapshot strategies are applied to different portions of the storage device based on local characteristics and requirements. This allows the system to be flexible in applying copy-on-write operations only where necessary, rather than uniformly across the entire system, thereby maintaining adaptability while ensuring data preservation.
4Reliability
If copy-on-write operations are performed on large-capacity storage devices, then data version preservation is achieved, but the time required for the operation increases significantly
Solution Approach 1:
Large-capacity storage devices are divided into smaller segments or blocks, allowing copy-on-write operations to be performed on individual segments rather than the entire device. This segmentation reduces the time required for each snapshot operation while maintaining data version preservation across the full storage capacity.
Solution Approach 2:
The patent performs copy-on-write operations only on the necessary portions of data that have changed, rather than copying the entire storage device contents. This partial action approach significantly reduces snapshot creation time for large-capacity devices while still achieving complete data version preservation for the modified portions.
5Reliability
If traditional backup methods are used, then data preservation is achieved, but the expense increases due to additional storage space requirements
Solution Approach 1:
The patent extracts and copies only the necessary changed data blocks for snapshot creation rather than copying entire files or storage devices. This extraction approach reduces the total storage space required for data preservation, thereby reducing the financial expense associated with additional storage capacity.
Solution Approach 2:
Instead of performing complete backup operations, the system performs partial copy-on-write operations only on the portions of data that have changed. This partial action significantly reduces the storage space requirements for maintaining data versions, directly reducing the financial expense of additional storage infrastructure.
Data Source
AI summary
In one embodiment, a user or client device communicates with a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. In some embodiments, systems and methods intelligently choose whether to use copy-on-write or point-in-time copy when saving data in a snapshot version of a file whose current version is being overwritten. In some embodiments, systems and methods allow snapshot users to return from a snapshot directory to the immediate parent directory from which the user entered into the snapshot.