Hierarchical Identification Files for Folder Restore
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional backup systems are inefficient in restoring groups of files to a previous state, often requiring significant storage and bandwidth, and are not suitable for remote backup over wide area networks due to the need for high-speed data connections and inefficient de-duplication and compression algorithms.
Innovation Solution
The system employs identification files to track changes in file hierarchies, allowing incremental backup and restore of files and folders by creating and managing identification files that store hash values of files and folders, enabling efficient tracking and restoration without the need for high-speed connections or extensive data transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional backup systems back up entire storage devices or individual files, then file version recovery is possible, but the restore process becomes tedious and time-consuming when restoring groups of files
Solution Approach 1:
The backup system segments the file system into hierarchical folders and tracks changes at each folder level using identification files. When restoring, users can select specific folders rather than individual files, and the system automatically restores the entire folder hierarchy including all subfolders, dramatically reducing the time and effort required for bulk file restoration.
Solution Approach 2:
The system performs preliminary actions by creating identification files that pre-document the state of folders and their contents at each backup point. These identification files contain hash values and metadata that allow the system to quickly determine what has changed without having to analyze entire folders during restore operations, enabling rapid selection and restoration of folder groups.
2Reliability
If remote backup systems transfer encrypted images to client devices for file selection, then security is maintained, but network bandwidth is consumed and decryption is required before file browsing
Solution Approach 1:
The system extracts only the necessary identification information (folder names, file hashes, timestamps) from the backup data and stores it in lightweight identification files on the client device. This allows users to browse and select files for restoration without downloading or decrypting the actual backup images, dramatically reducing network bandwidth consumption while maintaining security since the identification files contain no sensitive data.
Solution Approach 2:
The identification files serve as intermediaries between the encrypted backup storage and the user interface. They provide a metadata layer that enables file browsing and selection without requiring direct access to or transfer of the encrypted backup data, thus maintaining security while minimizing network bandwidth usage.
3Productivity
If Time Machine backup software uses sparse bundle images with directory structures stored within images, then backup functionality is achieved, but high-speed connections are required and cross-bundle de-duplication is inefficient
Solution Approach 1:
The system segments backup tracking into folder-level identification files distributed across the file system hierarchy, rather than storing all metadata within a single sparse bundle image. This segmentation allows for more efficient storage utilization and enables selective backup of only changed folders, reducing both storage requirements and bandwidth consumption while maintaining backup productivity.
Solution Approach 2:
The system performs partial backup actions by only backing up folders that contain changes, as identified by comparing hash values in identification files. Instead of backing up entire bundles or images, the system selectively transfers only the necessary data, reducing bandwidth requirements and storage needs while maintaining effective backup productivity.
Data Source
AI summary
The present disclosure describes systems and methods for hierarchical, iterative backup and restoration of files in a hierarchy. Upon backup of a new or modified file, an identification file is created with entries identifying the new or modified file and current versions of all other files in the same directory. The identification file may be stored on the local system and marked for backup. This triggers standard backup routines, such that the identification file is then backed up as if it were a new file in the parent directory. Accordingly, a second identification file is created with entries identifying the first identification file (and thus the child directory) as well as any other current versions of files in the parent directory and identification files for other child directories. This process is iteratively repeated, climbing through the directory structure, until reaching a top-most or root folder.