Data Migration System for Zero-Downtime Enterprise Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise computer systems require upgrades, which often result in system downtime, discouraging users and violating Service Level Agreements (SLAs), especially as data storage increases, complicating metadata system upgrades due to complex data structure changes and client-specific processes.
Innovation Solution
A method and system for upgrading a computer system by migrating data from a first system to a second system in stages, allowing for minimal downtime by copying initial data, then incremental changes until a threshold is reached, with options for untransformed data writing, application installation, and data transformation using handlers, while enabling access during the process and finally disabling it for the remaining data migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is migrated in a single batch during system upgrade, then data consistency is improved, but system downtime increases
Solution Approach 1:
The patent divides the data migration process into multiple segments: an initial full data copy, followed by incremental migration of changed data in batches, and finally a synchronization phase. This segmentation allows the system to maintain data consistency across partitions while minimizing downtime by processing migrations in manageable stages rather than a single lengthy operation.
Solution Approach 2:
The patent performs preliminary actions by creating an initial full copy of data to the new partition before the system needs to switch over. This preliminary data copy establishes a baseline state, allowing subsequent incremental updates to be applied without requiring complete system downtime, thus resolving the contradiction between consistency and availability.
2Ease of operation
If the system remains accessible during data migration, then user availability is improved, but data consistency becomes more difficult to maintain
Solution Approach 1:
The patent implements continuous data migration by establishing replication streams that continuously copy changed data from the old partition to the new partition while both systems remain operational. This continuous action ensures that data consistency is progressively achieved without interrupting user access to the system, maintaining both availability and eventual consistency.
Solution Approach 2:
The patent introduces an intermediary replication mechanism that acts as a mediator between the old and new partitions. This intermediary process handles data synchronization in the background, allowing the system to remain accessible to users while maintaining data consistency through controlled replication and conflict resolution protocols.
3Manufacturing precision
If complete data transformation is performed during migration, then data accuracy is improved, but migration time and complexity increase
Solution Approach 1:
The patent applies partial transformation during the initial migration phase, transforming only critical data structures that are essential for system operation. Non-critical or optional transformations are deferred to later phases, allowing the migration to proceed with reduced complexity while maintaining sufficient data accuracy for core functions.
Solution Approach 2:
The patent performs preliminary data transformation for essential fields before migration to ensure data accuracy is maintained for critical operations. By pre-transforming only the necessary data elements, the system achieves required accuracy without the complexity of complete data transformation, resolving the contradiction between precision and complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and corresponding system upgrades a live computer system. The method begins with migrating a copy of data from a first system to a communicatively coupled second system at a first time. Next, at one or more subsequent times, a copy of changed data is migrated from the first system to the second system until a threshold is reached. Finally, in response to reaching the threshold, a copy of the remaining changed data is migrated from the first system to the second system. A further embodiment of the method comprises: disabling access to the first system during the migration of data at the first time, enabling and maintaining access to the first system at the one or more subsequent times during the migration of the copy of changed data, and disabling access to the first system during the migration of the copy of the remaining changed data. In this manner, the system being upgraded is still highly available throughout the upgrade process.