How to Create DR Solution for a Coherence Cluster Across DCs
(Doc ID 2875236.1)
Last updated on JUNE 23, 2022
Applies to:Oracle Coherence - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
A Customer is looking for disaster recovery solution for coherence. He has Data Center A and Data Center B as backup. Intended Coherence cluster of N size was split between the data centers, N/2. When DC-A goes down then DC-B will take capacity of N servers. These two datacenters are different physical location. The need to keep all coherence nodes in same cluster is to keep the cache sync. However, maintenance of N servers in two separate data centers over WAN can cause performance issues or cache loss with network delay. They like to keep cache in sync, but they like to use only N/2 app servers from data center A as cache nodes for this setup and cache should not be distributed over to data center B as part of the single stretch cluster. One of solution is to make data center B servers as non-storage, but that will not work for disaster recovery solution in a stretch cluster. Coherence and WebLogic are in the same JVM.
Q: Can you suggest the solution for this, how to keep the DR solution up and running with the latest cache but not work as part of the production cache cluster?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document