Remote data replication is a critical component for any plan to ensure effective and efficient protection and rapid recovery from a major interruption. Synchronous replication of data is good internally for the cluster but its impact on performance becomes a significant consideration when two clusters of cache are geographically separated. Bridge topology is designed for the scenarios which involve replication of data from one on-site cache to one/multiple and on-site/off-site disaster recovery cache(s) across the WAN. Due to asynchronous replication, all clients connected to the active cache(s) get an impression that the operations are being performed on the active cache while a complete backup is taken to the other cache(s) seamlessly.
When an operation is performed on source cache, it is asynchronously handed over to the bridge cache. This operation is then enqueued to a queue maintained by the bridge cache. Operations from the queue are transferred to the other cache(s) when bridge finds the cache(s) available and ready to accept operations. With the bridge topology, it is ensured that:
-
There is no performance degradation.
-
Operations are performed in same sequence as they were on original cache.
-
Operations are not lost in case of connection failure.
Below are the main bridge topologies provided by NCache:
In This Section
Explains what is meant by Active-Passive Bridge topology provided by NCache.
Explains what is meant by Active-Active Bridge topology provided by NCache.