Backup System Override for Archival Storage Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Backup systems face compatibility issues when accessing data stored on older storage devices, as new systems may use different types or sizes of storage devices, requiring conversion of backups to maintain accessibility over time.
Innovation Solution
Implementing an override mechanism that allows backup systems to access files from storage devices of different types by reading file references and determining if an override is set, enabling the system to read files in a manner consistent with the new storage device type, even if the original device type has changed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If backup systems use new storage devices with different types or sizes, then storage capacity and performance are improved, but compatibility with archival backups from older storage devices deteriorates
Solution Approach 1:
The patent introduces a file reference table as an intermediary layer between the backup data and the storage device. This table maps logical file references to physical storage locations, allowing the backup system to access archival backups without needing direct compatibility with the original storage device type. The intermediary enables translation between different storage device types while maintaining data accessibility.
Solution Approach 2:
The patent creates a virtual copy of the file reference structure that maintains the logical mapping of files to storage locations. By copying the reference table rather than the actual data, the system preserves the structural information needed to access backups while adapting to different physical storage devices. This copying approach maintains compatibility without requiring conversion of the actual backup data.
2Adaptability or versatility
If backup systems perform conversion of backups to access new storage devices, then compatibility is improved, but processing time and system complexity increase
Solution Approach 1:
The patent performs preliminary action by pre-creating and maintaining the file reference table during the backup process. This reference table is built in advance with mappings between file references and storage locations, so that when access is needed later, the system can directly query the table without performing time-consuming conversion operations. The preliminary creation of reference mappings eliminates the need for real-time conversion.
Solution Approach 2:
The patent extracts the essential compatibility information into a separate file reference table that contains only the mapping relationships between logical files and physical storage locations. By taking out this reference information from the backup data itself, the system separates the compatibility layer from the actual data, allowing rapid access without reprocessing or converting the entire backup dataset.
3Duration of action of stationary object
If backup systems maintain archival backups for long periods, then data retention is improved, but the risk of obsolescence increases
Solution Approach 1:
The patent segments the backup system into two independent components: the archival backup data stored on long-term storage media and the file reference table maintained in the active backup system. This segmentation allows the data to be retained indefinitely while the reference table is periodically updated to maintain compatibility with evolving storage technologies. The separation enables long-term retention without permanent obsolescence.
Solution Approach 2:
The patent introduces dynamic updating of the file reference table to adapt to changing storage device types and configurations. Rather than static archival backups, the reference table is dynamically maintained and updated to reflect current storage architecture, allowing the system to adapt to new technologies while preserving historical backup data. This dynamic maintenance prevents obsolescence while maintaining long-term retention.
Data Source
AI summary
A backup system override may be specified to allow a backup system to access a backup created on an old storage device. For example, an archival backup may be accessed long after the storage device that created the backup has been decommissioned. The file history information in the backup may specify a storage device no longer accessible by the backup system. An override in the backup system allows the backup system to access the backup with the file history information through a different storage device than the storage device that created the backup. The different storage device may have a different name and/or be of a different type than the original storage device that created the backup. The override may also allow access to command scripts and links in the backup.