Stub Files for Data Replication Space Reduction
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 data backup and recovery, and lack transparency in user access to replicated data.
Innovation Solution
Implementing stubbing systems and methods in a data replication environment, where de-duplicated data blocks are replaced with stub files on the destination storage device, allowing for selective migration to secondary storage, using priority tags to distinguish between original and migrated stub files, and utilizing a migration module to restore data from secondary storage when needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is continuously replicated from source to destination storage device, then data availability and recovery capability are improved, but storage space consumption on destination device increases significantly
Solution Approach 1:
The patent creates stub files that are copies or references to the actual data blocks stored on destination device. These stub files contain metadata (original file name, inode number, block locations) that allow the system to access and restore original data without storing complete duplicate copies of all data, thereby reducing storage space while maintaining data availability.
Solution Approach 2:
The patent extracts only the essential metadata from the original data blocks to create stub files. By taking out only the critical information needed for data recovery (file name, inode, block locations) and leaving the actual data blocks on the destination device, the system achieves space efficiency while preserving full recovery capability.
2Quantity of substance
If stub files are used to replace data blocks on destination storage device, then storage space is conserved, but user access transparency and replication process complexity increase
Solution Approach 1:
The patent introduces a replication manager as an intermediary component that handles all interactions between the stub files and the replication process. This mediator translates user access requests to stub files into appropriate operations (restoring data from destination device or accessing archived data), thereby managing the complexity centrally without burdening the user or requiring changes to the underlying file system structure.
Solution Approach 2:
The stub files are designed to be self-descriptive, containing all necessary metadata (original file name, inode number, block locations) within themselves. This self-service approach allows the system to automatically resolve stub file references without requiring external lookup tables or additional management overhead, reducing overall system complexity.
3Measurement precision
If stub files with priority tags are implemented to distinguish migrated data, then data restoration accuracy is improved, but file system complexity and access overhead increase
Solution Approach 1:
The patent applies priority tags selectively to specific stub files based on their origin and importance. Rather than uniformly tagging all stub files, the system assigns priority indicators only where needed (e.g., to distinguish between stubs representing archived data versus stubs for actively replicated data), thereby improving restoration accuracy for critical data while minimizing unnecessary complexity in the file system structure.
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.