Database Patching with Cloned Testing for Minimal Downtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database patching processes often result in unintended negative side effects due to insufficient quality assurance, leading to system failures and extended downtime, especially in critical business environments where testing in diverse database environments is not feasible.
Innovation Solution
A method and system for generating a patching model that includes uptime and downtime processes, cloning the model to customize it for specific database parameters, executing pre-patching, patching, and post-patching steps, and determining if a rollback is necessary, with automatic rollback and notification of failures to minimize downtime and side effects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database patching is performed manually with quality assurance processes, then security and bug fixes are applied, but unintended negative side effects occur and extended downtime results
Solution Approach 1:
The patent applies preliminary action by creating a clone of the database system and executing pre-patching steps on the clone before applying patches to the production system. This allows quality assurance processes to be performed in advance on the cloned system, identifying potential side effects before they impact the production database, thereby reducing unintended negative effects and minimizing required downtime.
Solution Approach 2:
The patent uses copying by creating a clone of the production database system. This clone serves as a test environment where patches can be applied and quality assurance processes executed without affecting the production system. If issues are detected, the clone can be discarded and the production system remains unaffected, eliminating extended downtime and negative side effects.
2Reliability
If patches are applied to fix security vulnerabilities and bugs, then system security is improved, but new security vulnerabilities or feature failures may be introduced
Solution Approach 1:
The patent implements feedback by executing post-patching steps that include quality assurance processes and monitoring systems after patches are applied to the production database. These processes detect new security vulnerabilities or feature failures that may have been introduced by the patches, providing feedback that triggers automatic rollback procedures to restore the system to its previous stable state, thereby preventing new vulnerabilities from persisting.
Solution Approach 2:
The patent applies preliminary action by performing quality assurance processes and executing pre-patching steps on a cloned database system before deploying patches to production. This preliminary testing identifies potential new security vulnerabilities or feature failures in advance, allowing the system to avoid applying problematic patches to the production environment altogether.
3Productivity
If quality assurance processes are performed in a computing environment that does not factor target database environment aspects, then testing efficiency is improved, but accurate testing becomes infeasible and faulty patches are applied
Solution Approach 1:
The patent applies local quality by customizing the cloned database system to match the specific target database environment parameters, such as operating system configurations, hardware components, network settings, and memory configurations. This customization ensures that quality assurance processes are performed in an environment that accurately reflects the production system, enabling precise testing while maintaining efficiency through automation.
Solution Approach 2:
The patent uses parameter changes by dynamically configuring the cloned database system with the same parameters as the target production environment. This includes setting identical operating system parameters, hardware configurations, network settings, and database parameters, thereby creating a test environment that accurately mirrors production conditions and enables both efficient and accurate testing.
4Reliability
If a standby system is maintained to take over primary operations, then system availability is improved, but the standby system also requires patching and security updates
Solution Approach 1:
The patent applies universality by using the same cloning and automated patching infrastructure for both the primary production database system and the standby system. The automated patching system can apply patches to both systems simultaneously or sequentially using identical processes, reducing the complexity of managing patching for multiple systems while maintaining high availability through the standby system.
Data Source
AI summary
A method and system are disclosed for preparing and providing database patching as a service. At least one computing device generates a model for implementing steps for database patching. The model includes steps for uptime processes and downtime processes. The computing device(s) determine a new patch to be applied to a respective database and clones the model. Further, the computing device(s) customize the cloned model as a function of parameters associated with the respective database and generates a clone of the respective database. Additionally, the computing device(s) execute, via the model, pre-patching steps on the clone of the respective database, patching steps on the clone of the respective database, and post-patching steps on the clone of the respective database. The computing device(s) determine whether a rollback is indicated, and implements a rollback process where the rollback is indicated or does not implement a rollback process if not indicated.