Tenant Re-direction During Data Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database systems face challenges in efficiently and minimally disruptively migrating data from one data center to another, especially across different geographic regions, while ensuring data security and user experience.
Innovation Solution
A data storage architecture that isolates and moves key datasets first, using a data move system to redirect users to a target data center, and then moves non-key datasets, with a data destruction component to clean up the source data center, ensuring minimal disruption and high security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all datasets are moved together from source to target data center, then data migration is completed in one operation, but user disruption increases and system availability decreases during migration
Solution Approach 1:
The patent divides datasets into two categories: key datasets and non-key datasets. Key datasets are moved first to enable partial system operation at the target data center, while non-key datasets remain at the source data center to maintain existing services. This segmentation allows progressive migration with minimal disruption to users.
Solution Approach 2:
The patent performs preliminary actions by first moving key datasets to the target data center before moving non-key datasets. This preliminary migration of critical data enables the system to become available at the target location while maintaining data integrity and service continuity through selective data availability.
2Loss of time
If data is moved in a single batch, then migration time is reduced, but data security and integrity verification become more difficult
Solution Approach 1:
The patent segments the data migration process into distinct phases: first migrating key datasets with high priority and security requirements, then migrating non-key datasets. This phased approach enables security verification and integrity checking at multiple checkpoints rather than requiring verification of all data at once.
Solution Approach 2:
The patent implements feedback mechanisms where the system monitors the migration status of key datasets, verifies data integrity at the target data center, and uses this information to determine when to proceed with migrating non-key datasets. This feedback-driven approach ensures security and integrity while maintaining efficient migration timing.
3Ease of operation
If tenants are redirected to target system immediately, then user experience is improved with seamless access, but access to non-migrated data is lost
Solution Approach 1:
The patent segments tenant data access by redirecting tenants to the target data center for key datasets while maintaining access to non-key datasets at the source data center. This selective redirection ensures users experience seamless access to critical data while preserving access to other data during the migration process.
Solution Approach 2:
The patent uses an intermediary approach where the system manages multiple data access paths: tenants are redirected to the target data center for key datasets through updated connection information, while non-key datasets remain accessible through the source data center. This intermediary management of data access paths maintains user experience while ensuring data availability.
4Reliability
If source data center is cleaned up immediately after migration, then data security is enhanced, but recovery options are reduced
Solution Approach 1:
The patent segments the data cleanup process by first securing and archiving migrated data at the target data center, then progressively cleaning up source data after verification. This segmented approach enhances security through verified data transfer while maintaining recovery options through staged deletion and archival processes.
Data Source
AI summary
Data to be moved from a source system to a target system, for a set of tenants, is first identified. The data is enumerated by a first computing instance in the source system to obtain an enumeration list. Data is copied from the source system to the target system based on the enumeration list by a second computing instance. The data in the source and target systems is then enumerated by a third computing instance to determine whether any data is still to be moved and another enumeration list is generated. The data still to be moved is then moved based on the other enumeration list.