Backup File Attribution via Metadata Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managers of electronic networks face challenges in accurately determining which files are backup files, especially when the original file is corrupted or under attack, and existing systems require file conversion to determine backup files, which is time-consuming and infeasible for large networks.
Innovation Solution
A system that determines and applies backup file attribution to files in an electronic network by using a processing device to receive file data, generate file attributes, and identify backup files without requiring file conversion, by considering file types such as tape, WORM, and disk files, and applying immutability features.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If file conversion is used to determine backup files, then compatibility with different backup determination tools is improved, but processing time and resource consumption increase significantly
Solution Approach 1:
The patent extracts the essential identification features (file extensions, directory paths, metadata) from files without requiring full file conversion. This allows backup determination tools to identify backup files by examining only the necessary identifying characteristics rather than converting entire files, thus maintaining compatibility while reducing processing time.
Solution Approach 2:
The patent creates simplified copies or representations of file identification data (such as metadata structures, file headers, or path information) that can be processed quickly without converting the actual file contents. This enables fast backup identification while preserving the ability to determine compatibility across different systems.
2Measurement precision
If file conversion is performed to conform to backup determination tools, then identification accuracy is improved, but the process becomes infeasible for large networks with constantly updating files
Solution Approach 1:
The patent segments the file identification process into discrete, manageable components such as file extension analysis, path pattern matching, and metadata extraction. This segmentation allows the system to process files efficiently in large networks by handling each identification aspect separately without requiring complete file conversion, thus maintaining accuracy while enabling scalability.
Solution Approach 2:
The patent performs preliminary actions by pre-processing and indexing file identification characteristics (such as creating lookup tables for file extensions, path patterns, and metadata structures) before backup determination is needed. This preliminary preparation enables fast, accurate identification in large networks without requiring time-consuming file conversion during actual backup operations.
3Measurement precision
If manual backup file identification is used, then precision in determining backup files is improved, but the complexity and time consumption of the process increase
Solution Approach 1:
The patent enables files to self-identify as backup files through inherent characteristics such as specific file extensions, directory path conventions, or embedded metadata markers. This self-service approach allows the system to automatically determine backup status without complex manual intervention or sophisticated analysis tools, thus maintaining high identification precision while reducing system complexity.
Data Source
AI summary
Systems, computer program products, and methods are described herein for determining and applying a backup file attribution to files in an electronic network. The present invention is configured to receive data associated with at least one file, wherein the file is stored in at least one data store; and generate at least one file attribute for the file, wherein, in an instance where the file is a tape file type, generate a backup file attribute, wherein, in an instance where the file is not a tape file type, generate a non-backup file attribute, wherein, in an instance where the file is not a type file type and the file comprises a backup feature in the data, generate the backup file attribute, or wherein, in an instance where the file is a tape file type and the file comprises a non-backup feature in the data, generate the non-backup file attribute.