Stub File Prioritization in Data Replication Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional continuous data replication systems require significant storage space on both source and destination machines, making them less efficient for general data backup purposes and lacking transparency in user access to replicated data.
Innovation Solution
Implementing stubbing systems and methods in a continuous data replication environment, where de-duplicated data blocks are replaced with smaller stub files on the destination storage device, allowing for selective migration to secondary storage, and using priority tags to distinguish between original and migrated stub files, enabling transparent user access and efficient disk space management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If de-duplicated data blocks are replaced with stub files on destination storage, then storage space on destination system is reduced, but data access transparency and recovery timeliness may be impacted
Solution Approach 1:
The patent introduces stub files as intermediary objects that represent archived data blocks. These stub files contain metadata (original file path, block size, checksum) that enables the replication system to transparently access archived data without users needing to know the data is stored remotely. The stub files act as mediators between the user's access requests and the actual archived data blocks.
Solution Approach 2:
The patent creates lightweight stub file copies that reference the original archived data blocks. Instead of storing full data blocks on the destination system, the system stores small stub files containing references to the archived data. This copying approach maintains data accessibility while dramatically reducing destination storage requirements.
2Quantity of substance
If stub files are used to represent migrated data, then storage efficiency is improved, but distinction between original and migrated stub files becomes complex
Solution Approach 1:
The patent applies local quality by embedding distinct metadata characteristics within different types of stub files. Original stub files contain specific metadata patterns while migrated stub files contain different metadata patterns (such as archived block references). This allows the system to differentiate between stub file types based on their local metadata qualities without requiring complex external tracking mechanisms.
Solution Approach 2:
The patent changes parameters within stub files to indicate their origin. Migrated stub files contain additional parameters such as archived block identifiers, migration timestamps, and source location information. These parameter changes enable the replication system to automatically distinguish between original and migrated stub files, managing complexity through structured data rather than procedural complexity.
3Quantity of substance
If data is archived to secondary storage and replaced with stub files, then destination disk space is conserved, but data recovery speed may be reduced
Solution Approach 1:
The patent performs preliminary actions by pre-calculating and storing metadata in stub files during the archiving process. The stub files contain pre-computed information such as data block locations, checksums, and reconstruction instructions. This preliminary preparation enables rapid data recovery without requiring complex analysis during the recovery process, thus reducing data recovery time despite using secondary storage.
Solution Approach 2:
The patent substitutes mechanical data retrieval with information-based retrieval. Instead of physically searching for and copying archived data blocks during recovery, the system uses the metadata in stub files to directly locate and retrieve the required archived blocks. This substitution of mechanical search with information-guided retrieval significantly reduces data recovery time while maintaining space efficiency.
Data Source
AI summary
Stubbing systems and methods are provided for intelligent data management in a replication environment, such as by reducing the space occupied by replication data on a destination system. In certain examples, stub files or like objects replace migrated, de-duplicated or otherwise copied data that has been moved from the destination system to secondary storage. Access is further provided to the replication data in a manner that is transparent to the user and/or without substantially impacting the base replication process. In order to distinguish stub files representing migrated replication data from replicated stub files, priority tags or like identifiers can be used. Thus, when accessing a stub file on the destination system, such as to modify replication data or perform a restore process, the tagged stub files can be used to recall archived data prior to performing the requested operation so that an accurate copy of the source data is generated.