Redo Repeater for Database No Data Loss Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems face challenges in providing no data loss protection without impacting primary database performance, especially when primary and standby databases are geographically distant, as current approaches either risk data loss or incur significant performance degradation due to network latency.
Innovation Solution
The introduction of a lightweight 'Repeater' entity that stores and forwards redo log records from the primary database to one or more standby databases, reducing network latency and allowing for no data loss protection without performance impact on the primary database, even across great distances.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the primary database directly transmits redo logs to geographically distant standby databases, then data loss protection is improved, but network latency increases and primary database performance deteriorates
Solution Approach 1:
The patent introduces an intermediary component (log shipping service or archive log destination) that receives redo logs from the primary database and forwards them to standby databases. This intermediary absorbs the network latency burden, allowing the primary database to commit transactions without waiting for remote standby confirmation, thus maintaining performance while ensuring data loss protection through reliable log transmission to the intermediary.
2Reliability
If the primary database waits for standby database acknowledgment before committing transactions, then data loss protection is improved, but transaction commit latency increases
Solution Approach 1:
The patent implements preliminary action by having the primary database transmit redo logs to an intermediary destination before transaction commit. The intermediary acknowledges receipt of the logs, allowing the primary database to commit the transaction immediately without waiting for remote standby application. This preliminary log transmission ensures data loss protection while eliminating the time penalty of synchronous remote commit waiting.
3Reliability
If redo logs are transmitted synchronously to remote standby databases, then data loss protection is improved, but network bandwidth consumption increases
Solution Approach 1:
The patent employs periodic action by implementing batched or periodic log shipping from the primary database to standby databases through the intermediary. Instead of transmitting every log record immediately and synchronously, the system accumulates logs and transmits them in periodic batches, reducing the frequency and volume of network transmissions while maintaining data loss protection through the intermediary's reliable receipt confirmation.
Data Source
AI summary
Disclosed are methods and apparatuses to provide a redo repeater that allows for no data loss protection without the performance impact to the primary database even when a significant geographical distance separates the primary and standby databases. The Repeater is a lightweight entity that receives redo from the primary database with the purpose of redistributing that redo throughout the primary/standby system configuration. The Repeater able to extend no data loss protection and switchover functionality to terminal standby databases even though the primary database does not need to have a direct connection with those destinations.