Database Cloning via Backup Instance Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current distributed computing systems face challenges in maintaining optimal performance and efficiently managing and analyzing large amounts of transactional and dimensional data, particularly in cloning database instances across multiple servers and networks.
Innovation Solution
The system employs a control device coupled to computerized servers that perform a cloning operation by identifying the most recently updated backup database instance and selecting it as the source for cloning based on time, distance, or logical criteria, minimizing the impact on the data source and optimizing data freshness and copy time by using backup databases corresponding to primary and standby databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is copied directly from the primary database for cloning operations, then the cloning speed is improved, but the impact on the data source increases and data freshness may be compromised
Solution Approach 1:
The patent uses backup database instances as intermediary sources for cloning operations. Instead of copying directly from the primary database, the system selects an appropriate backup instance (based on recency and other criteria) to serve as the source. This intermediary approach reduces the direct impact on the primary database while still enabling efficient cloning operations with relatively fresh data.
2Reliability
If the most recently updated backup database instance is selected as the source for cloning, then data freshness is improved, but the complexity of selecting the appropriate source instance increases
Solution Approach 1:
The system implements a feedback mechanism that continuously tracks and evaluates backup database instances based on multiple criteria including recency of updates, distance from the target instance, and logical compatibility. The control device uses this feedback information to automatically select the most appropriate backup instance as the source for cloning operations, balancing data freshness with operational feasibility without requiring manual intervention.
3Reliability
If multiple backup database instances are maintained across distributed servers, then data availability and redundancy are improved, but the difficulty of managing and analyzing transactional data increases
Solution Approach 1:
The patent creates a universal control device that can manage multiple backup database instances across different servers and locations. This control device provides multi-functional capabilities including automated source selection, cloning orchestration, and data integrity verification. By centralizing management functions in a universal control system, the patent reduces the complexity of managing distributed backup instances while maintaining high data availability and redundancy.
Data Source
AI summary
When multiple backup database instances most recently experienced an update is determined. If a most recently updated backup database instance was updated within a defined time period of one or more other backup database instances, a source instance for cloning is selected as the backup database instance that satisfies at least one of a physical or logical proximity criteria relative to a designated database instance. If a difference in update times is greater than the defined time period, e.g., for the two most recent backup database instances, the source instance for cloning is selected to be the most recently updated backup database instance. Cloning to a target instance is performed using the selected backup database instance as a source instance as long as preparatory operations all pass. If not, the source databases are used for the cloning while still being accessible to clients.