Synchronized Target Database via Real-Time Transaction Log Replay
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for creating a backup database are inefficient as they often require taking the primary database offline, leading to downtime and storage issues with transaction logs that accumulate during the copying process, causing the backup system to fall behind the primary system.
Innovation Solution
A method to create a synchronized target database with an online source database without taking it offline, where updates are applied in real-time to both databases, and transaction logs are managed by immediately providing information to the target database, suppressing errors and ignoring duplicates to prevent log accumulation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If the primary database is taken offline to create a backup database, then data consistency is ensured, but system availability is reduced
Solution Approach 1:
The system performs preliminary actions by capturing and storing transaction log information in real-time before the backup process is initiated. This allows the backup database to be constructed without taking the primary database offline, as all necessary data changes are already recorded in the transaction logs.
Solution Approach 2:
The invention creates a copy of the primary database by applying transaction log information to a backup database. Instead of copying data directly from the primary database (which would require it to be offline), the system copies data by replaying transaction logs, thereby maintaining system availability while ensuring data consistency.
2Reliability
If data is copied from the primary database to the backup database, then backup is created, but transaction logs accumulate and exceed storage capacity
Solution Approach 1:
The system extracts only the necessary transaction information from the transaction logs and applies it to the backup database. Once the transaction log information has been successfully applied to the backup, the corresponding log entries are removed or archived, preventing unlimited accumulation of transaction logs.
Solution Approach 2:
The invention discards transaction log entries after their information has been successfully applied to the backup database. This allows the system to maintain an accurate backup while preventing transaction logs from accumulating beyond storage capacity, as old log entries are discarded after serving their purpose.
3Manufacturing precision
If transaction logs are retained for a long period to ensure backup accuracy, then data integrity is maintained, but storage requirements increase significantly
Solution Approach 1:
The system performs preliminary actions by continuously capturing transaction log information during the backup process. This ensures that all data changes are recorded before the backup is completed, maintaining data integrity without requiring long-term retention of transaction logs.
Solution Approach 2:
The invention discards transaction log entries after their information has been successfully applied to the backup database. This prevents excessive accumulation of transaction logs while ensuring that all necessary data changes are captured and applied, thereby maintaining data integrity with minimal storage requirements.
Data Source
AI summary
One embodiment is a method that builds a target database with transaction logs from an online source database. The transaction logs include both existing data in the source database and updates that occur to the source database while the target database is being built.