Archival Load Balancing via Registry Key Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for archival load balancing, such as EMC's DiskXtender, face bottlenecks and latency issues when multiple extended drives are on the same server, and require time-consuming data re-migration and additional storage space creation, especially when dealing with rapid data growth and compliance tracking across departments.
Innovation Solution
The system copies registry keys from a source hard disk drive to a target server, modifies them for compatibility, and migrates data to the target server without re-migrating from secondary storage back to the original hard disk drive or migrating a second time, allowing the target server to function as a new extended drive, thus avoiding the need for additional space and reducing the complexity of compliance and audit tracking.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is migrated from source hard disk drive to target hard disk drive through secondary storage, then data migration is achieved, but time consumption increases and storage requirements increase
Solution Approach 1:
The system performs preliminary actions by copying registry keys before data migration, and prepares the target server configuration in advance. This allows the migration process to proceed more efficiently without requiring time-consuming re-migration operations from secondary storage back to the original hard disk drive.
Solution Approach 2:
The invention extracts and utilizes registry keys that contain metadata about migrated data, allowing the system to understand and transfer archival data relationships without physically re-migrating the actual data through secondary storage. This extraction of control information (registry keys) from the physical data migration process significantly reduces time consumption.
2Productivity
If data is migrated through secondary storage, then data transfer is achieved, but storage requirements increase
Solution Approach 1:
The system copies registry keys and configuration information from the source hard disk drive to the target server, rather than copying actual data through secondary storage. This copying of metadata and configuration allows the target server to function as a new extended drive without requiring additional storage space for intermediate data holding.
Solution Approach 2:
The invention uses registry keys as an intermediary that carries information about migrated data without requiring the actual data to be physically present during the migration process. This intermediary mechanism allows data transfer capability while minimizing storage requirements by avoiding the need to hold data in secondary storage.
3Adaptability or versatility
If multiple extended drives are on the same server, then resource utilization is improved, but bottlenecks and latency issues occur
Solution Approach 1:
The system segments extended drives across different servers, with each server managing its own extended drives independently. This segmentation prevents bottlenecks by distributing the load across multiple servers, allowing each server to handle archival operations for its assigned extended drives without interference from other drives on the same system.
Solution Approach 2:
The invention distributes extended drives across multiple servers in the network, adding a dimensional aspect to resource allocation. Instead of concentrating multiple extended drives on a single server, the system utilizes the network dimension to spread drives across different server nodes, thereby improving reliability and reducing latency while maintaining resource utilization.
Data Source
AI summary
Archival load balancing is described. A selection of data stored on a source hard disk drive is received via a user interface. The selection of data stored on the source hard disk drive is associated with data migrated from the source hard disk drive to a backend storage device. Registry keys associated with the selection of data are copied from the source hard disk drive to a target server. Information in the registry keys on the target server is modified to be compatible with settings on the target server. The selection of data is copied from the source hard disk drive to a target hard disk drive on the target server. The selection of data stored on the target hard disk drive is associated with the data migrated to the back end storage device.