Database Point-in-Time Restoration via Configuration Data Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database management systems face challenges in maintaining operational compatibility and reducing costs associated with standby database nodes, which consume resources and incur licensing fees, even when not frequently used, due to potential compatibility issues and unnecessary resource allocation.
Innovation Solution
A distributed system provides a point-in-time restoration capability without instantiating a standby node, replicating transaction and configuration data between operating environments using a distributed storage service, allowing for operational compatibility safeguards and reducing technical and monetary costs by only allocating resources when needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a standby database node is instantiated to maintain operational compatibility, then reliability is improved, but computing capacity consumption and licensing costs increase
Solution Approach 1:
The patent creates a logical copy of the database instance through configuration data replication rather than instantiating a physical standby node. The configuration data includes transaction logs and schema information that enable restoration of the database to any point in time, providing operational compatibility without the need for a continuously running standby instance.
Solution Approach 2:
The patent segments the database into configurable components that can be independently restored. By separating the database instance from its operating environment and replicating only the necessary configuration data (transaction logs, schema, parameters), the system enables selective restoration without maintaining a full standby node.
2Reliability
If a standby database node is maintained to ensure data integrity, then reliability is improved, but licensing costs increase
Solution Approach 1:
Instead of licensing a full standby database instance, the patent replicates only the essential configuration data including transaction logs and schema information. This selective copying approach maintains data integrity through point-in-time restoration capability while significantly reducing licensing requirements.
Solution Approach 2:
The patent applies partial action by replicating only the necessary configuration data components (transaction logs, schema, parameters) rather than the entire database instance. This partial replication is sufficient for restoration purposes while avoiding the costs of a complete standby node.
3Adaptability or versatility
If configuration data is replicated between operating environments, then operational compatibility is improved, but device complexity increases
Solution Approach 1:
The patent creates a universal configuration data structure that can be applied across different operating environments. The replicated configuration data (transaction logs, schema, parameters) serves multiple purposes: it enables point-in-time restoration, ensures operational compatibility, and supports database migration between different environments without requiring environment-specific replication mechanisms.
4Reliability
If resources are allocated continuously for standby node operation, then reliability is improved, but loss of energy increases
Solution Approach 1:
The patent implements periodic action by restoring the database to a specific point in time when needed rather than maintaining continuous standby operation. The configuration data is replicated and stored, then applied periodically or on-demand through point-in-time restoration, eliminating the need for continuous resource allocation to a standby node.
Data Source
AI summary
A distributed system responds to a request to enable restoration capability for a database instance by beginning a process for monitoring configuration changes made to a first operating environment of a first database instance. The system identifies a configuration change on which the database instance is dependent, and stores a record of the configuration change. The record is provided to a second operating environment. The second operating environment is configured, based on the record of the configuration change, to have configuration settings corresponding to the first operating environment as of the restoration point in time. The database instance is restored to the second operating environment.