SATC Modules for Synchronous Database Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current disaster-recovery systems are resource-intensive and complex due to their component-to-component configuration, making them difficult to manage and inefficient in recovering data from catastrophic losses, especially when dealing with thousands of databases, as they lack a unified control for resource utilization and often fail to recover transactions that did not reach backup sites before a failure.
Innovation Solution
The implementation of a disaster-recovery system with synchronous-to-asynchronous converters (SATCs) that consolidate data streams into a single stream, allowing for synchronous replication and reverse tracing of transactions, enabling efficient data backup and recovery by managing entire site traffic as a single consolidated stream and ensuring all transactions are stored across multiple nodes before recovery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If component-to-component connections are used for each database, then data replication can be performed, but the system complexity and resource consumption increase enormously
Solution Approach 1:
The patent merges multiple individual database replication connections into a single consolidated data stream that carries transactions from multiple source databases through a shared network path to multiple target databases. This consolidation dramatically reduces system complexity while maintaining replication reliability, as the single stream approach eliminates the need for managing thousands of individual component-to-component connections.
Solution Approach 2:
The shared network path and consolidation mechanism serve multiple functions simultaneously: they replicate data from multiple source databases to multiple target databases, enable centralized resource management, provide aggregate task prioritization, and allow efficient bandwidth utilization. This multi-functionality resolves the contradiction by making the replication infrastructure versatile rather than specialized for single pairs.
2Ease of operation
If independent backup procedures are implemented for each source component, then data recovery can be performed, but resource utilization control and task prioritization become difficult
Solution Approach 1:
The consolidation mechanism enables centralized monitoring and control of all replication and recovery operations through a single data stream. This provides feedback capabilities for aggregate resource utilization management and task prioritization, allowing administrators to control bandwidth allocation and recovery priorities across the entire datacenter rather than managing each component independently.
3Reliability
If synchronous replication is used for all transactions, then data consistency is maintained, but network bandwidth consumption increases
Solution Approach 1:
By consolidating replication traffic from multiple databases into a single shared stream, the system achieves efficient bandwidth utilization through multiplexing. This allows synchronous replication to be performed for multiple databases simultaneously over the same network path, reducing total bandwidth consumption compared to dedicated connections while maintaining data consistency through the synchronous-to-asynchronous conversion capability.
Data Source
AI summary
A disaster-recovery system contains a networked array of synchronous-to-asynchronous converter (SATC) modules that connect source databases to target backup databases. During backup, the system replicates each source-database transaction through a chain of these SATCs to a corresponding target, storing a local copy of the transaction on each SATC along the way. Each transaction's path between its source-target pair is identified by a set of tracking entries, where each entry identifies one SATC in the path. Every backup transfer between two SATCs in a chain is performed synchronously, such that a successor SATC confirms a successful transfer to a predecessor SATC only after the successor can confirm a successful transfer to the next SATC in the chain. During a subsequent recovery operation, tracking entries are regenerated to locate locally stored transactions that had not time to be fully replicated before a catastrophic failure had occurred.