Zero Downtime ERP Upgrade via Shadow System and Bridge Schema
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Upgrading persistent data in ERP systems often requires significant downtime, leading to disruptions in business operations and conflicts when users access or modify data during the upgrade process, as existing methods typically involve taking the system offline for an extended period.
Innovation Solution
Implementing a zero-downtime upgrade approach by creating a shadow system and bridge schema that allows for parallel operation with the production system, enabling selective locking of database tables and minimizing disruptions, while replicating and adjusting data structures to support the new software version without interrupting service.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If the ERP system is taken offline for persistent data upgrade, then the data structure and content can be adjusted to the new version, but the system experiences excessive downtime impacting business operations
Solution Approach 1:
The patent segments the monolithic upgrade process into distinct phases: creating a shadow system with new version data structures, selectively copying and adjusting specific database tables, and gradually transitioning functionality. This allows data structure adjustments to occur in isolated segments rather than requiring complete system shutdown.
Solution Approach 2:
The shadow system is prepared in advance with the new version data structures and schema before the production system is taken offline. This preliminary preparation allows the actual upgrade to proceed faster since the target structure is already ready, reducing the critical downtime period.
2Adaptability or versatility
If the persistent data is upgraded after the software upgrade, then the new version software can be deployed, but users are restricted to limited up-to-date data until the upgrade is complete
Solution Approach 1:
The shadow system acts as an intermediary between the old production system and the new version requirements. It provides the new version data structures that the upgraded software needs while allowing the original production system to continue operating with existing data, thus bridging the compatibility gap without restricting user access.
Solution Approach 2:
Specific database tables are selectively copied from the production system to the shadow system. This copying approach allows the new version software to access and operate on copied data while the original data remains accessible to users through the production system, maintaining ease of operation during the transition.
3Manufacturing precision
If the persistent data is upgraded prior to the software upgrade, then the new version data structure is ready, but conflicts occur when users change persistent data and data locking is required
Solution Approach 1:
The patent segments the data upgrade process by selectively copying only specific database tables that need to be upgraded to the shadow system, rather than locking and upgrading all persistent data at once. This table-level segmentation reduces conflicts with user operations and minimizes the need for extensive data locking mechanisms.
Solution Approach 2:
The shadow system serves as an intermediary layer that handles the new version data structures without requiring direct modification of the production system data. Users continue to operate on production data without conflicts, while the shadow system maintains the upgraded structure ready for transition, eliminating the need for complex locking protocols.
4Reliability
If extensive data locking is performed during persistent data upgrade, then data consistency is maintained, but system availability and user experience are significantly reduced
Solution Approach 1:
The shadow system acts as an intermediary that maintains data consistency through controlled copying and adjustment processes rather than extensive locking. It provides a isolated environment where data consistency can be ensured during the upgrade while the production system remains fully available to users with no locking restrictions.
Solution Approach 2:
By copying specific database tables to the shadow system rather than modifying production data in place, the patent maintains data consistency in the copied structures without requiring locks on the original data. This copying approach allows the production system to remain fully operational while consistency is preserved in the upgrade target.
Data Source
AI summary
The present disclosure describes methods, systems, and computer program products for providing multi-level user interface theming. One computer-implemented method includes instantiating a shadow system and database schema for a new version software application in a shared database, the shadow system database schema containing aliases pointing to tables instantiated in a production database schema, instantiating a bridge database schema containing aliases pointing to each database table within the production database schema, preparing a bridge sub-system connected to the bridge database schema aliases, replicating database tables within the production database schema, for use by the bridge sub-system and adjusting the original database tables for structure and content consistent with the new version software application, deploying an upgrade sub-system and tools to complete adjustment of structure and content of the original database tables, and connecting an instantiated instance of the new version software application to adjusted database tables.