Clone File System Metadata Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for software maintenance and data updates in computer file systems often result in data loss due to inadequate detection and synchronization of changes between the original and clone file systems, particularly failing to distinguish between changes on the original and clone systems, leading to unsatisfactory exclusion of operating system and application changes, and requiring manual user intervention which is time-consuming and inaccurate.
Innovation Solution
An approach that saves metadata about the original file system at the time of cloning, allowing for later detection and automatic application of changes to the clone file system, including editable files, to ensure data synchronization across all files and directories, minimizing downtime and data loss during software maintenance and updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual comparison and synchronization methods are used between original and clone file systems, then data changes can be detected, but the process is time-consuming and inaccurate leading to data loss
Solution Approach 1:
The patent applies preliminary action by creating metadata snapshots of the original file system at the time of cloning. These snapshots contain file identifiers, timestamps, and other attributes that enable automatic change detection without manual intervention. The metadata is prepared in advance and stored for comparison, eliminating the need for time-consuming manual file-by-file comparison during synchronization.
Solution Approach 2:
The patent introduces metadata as an intermediary between the original and clone file systems. This metadata layer acts as a mediator that automatically tracks and communicates changes between the two systems. Instead of directly comparing files, the system uses metadata records to identify changes, significantly improving both accuracy and speed of the synchronization process.
2Reliability
If clone file system is created for software maintenance, then activity can continue on original system, but changes on original system are not applied to clone leading to data loss
Solution Approach 1:
The patent implements feedback mechanisms where the system continuously monitors changes in the original file system and automatically feeds this information back to the clone file system. Metadata snapshots are compared, and change information is automatically transmitted back to update the clone, ensuring data integrity is maintained while enabling parallel maintenance operations without manual intervention.
Solution Approach 2:
The synchronization process is designed to be self-service, where the system automatically detects changes, compares metadata, and applies updates from the original file system to the clone without requiring manual user intervention. This self-service capability ensures data integrity is automatically maintained while maximizing maintenance productivity by eliminating manual synchronization steps.
3Extent of automation
If metadata is saved and used for automatic change detection, then data synchronization is improved, but system complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the file system information into discrete metadata records, each representing a specific file or directory with its own attributes. This segmentation allows the system to manage complexity by handling individual file metadata separately rather than managing the entire file system as a single complex entity, enabling automated change detection through systematic comparison of discrete metadata elements.
Data Source
AI summary
Metadata about an original file system is saved at the time of creation of a clone file system of the original file system. The metadata is used at a later time to detect changes to the original file system. These changes are then applied to the clone file system which has its own changes different from the changes of the original file system. Changes made to the clone file system are merged into the original file system after at least one boot of a computer system from the clone file system.