Database Migration System Using Catalog and Data Delta Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Migrating enterprise software and databases between hardware platforms with different configurations often results in significant downtime, disrupting production and violating service level agreements due to binary incompatibility and the need for extended downtime for seamless switch-over.
Innovation Solution
Implementing a method that uses a catalog delta and data delta to periodically assess and migrate differences between source and target systems, determining completion time based on the last-determined data delta, and halting production to complete the migration, ensuring near-zero downtime by minimizing the duration of system unavailability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional database migration methods are used between hardware platforms with different configurations, then data can be migrated, but significant downtime is required which disrupts production and violates service level agreements
Solution Approach 1:
The patent applies preliminary action by performing most data migration operations during the production run before the actual switch-over. The system continuously migrates data in the background during normal operation, so that by the time production must be halted, the majority of data transfer is already complete, minimizing the downtime required for migration.
Solution Approach 2:
The patent implements dynamics by making the migration process adaptive and flexible. The system dynamically adjusts migration strategies based on real-time conditions, using configurable parameters to control migration speed, data types, and timing. This allows the migration to be optimized for each specific scenario, balancing completeness with minimal disruption.
2Loss of time
If continuous migration during production is attempted, then downtime is minimized, but migration completeness and data consistency become difficult to ensure
Solution Approach 1:
The patent applies feedback by continuously monitoring migration progress and comparing source and target database states. The system uses configurable parameters to track what has been migrated and what remains, allowing it to detect when migration is complete or if data consistency issues arise. This feedback mechanism ensures that the migration can be stopped at the optimal moment when both completeness and consistency are achieved.
Solution Approach 2:
The patent implements periodic action by performing migration operations in controlled intervals rather than continuously or all at once. The system can pause and resume migration, allowing time for data consistency checks between source and target systems. This periodic approach ensures that migration completeness can be verified at regular intervals while minimizing overall downtime.
3Productivity
If migration is performed during production use, then system availability is maintained, but migration speed and completion time are extended
Solution Approach 1:
The patent applies partial action by migrating only the necessary data and operations during production, rather than attempting to migrate everything at once. The system uses configurable parameters to identify and migrate critical data first, allowing production to continue while essential data is transferred. This selective approach maintains availability while reducing the total migration duration.
Solution Approach 2:
The patent implements parameter changes by allowing dynamic adjustment of migration parameters such as migration speed, data types to migrate, and timing configurations. The system can change these parameters based on real-time conditions, optimizing the balance between maintaining production availability and achieving migration completion within acceptable timeframes.
Data Source
AI summary
Methods, systems, and computer-readable storage media for executing a first application on a source system during production use of the source system, providing a second application on a target system, during the production use of the source system: migrating data from the source system to the target system based on a catalog delta, and a data delta, each of the catalog delta, and the data delta being periodically determined, and determining whether a completion time exceeds a threshold time, the completion time being determined based on a last-determined data delta, and, in response to determining that the completion time does not exceed the threshold time: halting production use of the source system, and completing migration to the target system based on the last-determined data delta.