Stub File Migration Automation via Database Segregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data migration techniques lack automation for segregating stub files from non-stub files, leading to unwanted delays and errors during data sharing and exporting, as both types of files are typically migrated together without distinction.
Innovation Solution
The implementation of an automated method that selects stub files for migration based on database entries, allowing them to be moved to a new storage location while keeping non-stub files in the source location, using a migration appliance and policy engine to manage the process without rehydrating data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional data migration approaches are used to migrate all files from source to target location, then complete data migration is achieved, but stub files and non-stub files cannot be distinguished leading to unnecessary migration of non-stub files and increased migration time
Solution Approach 1:
The patent segments the file population into two distinct categories: stub files and non-stub files. This segmentation is achieved by querying a database to identify which files are stub files, allowing the migration process to treat these two file types differently. Stub files are migrated to the target location while non-stub files remain at the source location, eliminating unnecessary data transfer and improving migration efficiency.
Solution Approach 2:
The patent extracts the identification logic for stub files from the general file migration process. By querying the database to determine which files are stub files before migration, the system separates the stub file migration task from the non-stub file handling, allowing only the necessary stub files to be migrated while leaving non-stub files untouched at the source location.
2Measurement precision
If manual segregation of stub files from non-stub files is performed, then accurate file selection for migration is achieved, but manual intervention increases operational complexity and time consumption
Solution Approach 1:
The patent implements a self-service mechanism where the database automatically maintains information about which files are stub files. The migration system queries this database to identify stub files without requiring manual intervention. This automated self-identification process eliminates the need for manual file-by-file inspection while maintaining high accuracy in distinguishing stub files from non-stub files.
Solution Approach 2:
The patent introduces a database as an intermediary between the file system and the migration process. This database stores and manages metadata about files, including which files are stub files. The migration system queries this intermediary database to obtain accurate file identification, eliminating the need for complex manual segregation processes while maintaining precision.
3Ease of manufacture
If all files are migrated together without distinction, then simple migration process is maintained, but computational resources are wasted migrating non-stub files that should remain at source location
Solution Approach 1:
The patent applies partial action by migrating only the necessary subset of files (stub files) rather than all files. By querying the database to identify which files are stub files, the system performs migration only where needed, avoiding the waste of computational resources on non-stub files while maintaining process simplicity through automated identification.
Solution Approach 2:
The patent changes the parameter of file selection from a blanket approach (migrate all files) to a selective approach (migrate only stub files). This parameter change is enabled by querying database metadata that identifies stub files, allowing the migration process to optimize resource usage by transferring only the necessary data while maintaining operational simplicity through automated identification.
Data Source
AI summary
A method comprises selecting at least a given stub file of one or more stub files for migration from a source storage location to a target storage location. The selection of the given stub file is based at least in part on a database entry comprising source storage location path information for the given stub file. The one or more stub files correspond to one or more archived files, and the one or more stub files and one or more non-stub files are stored in the source storage location. In the method, the given stub file is migrated to the target storage location without migrating the one or more non-stub files to the target storage location. The method further includes modifying the database entry by replacing the storage location path information with target storage location path information for the given stub file.