F5 Big IP for App Failover between Oracle Data Guarded Clusters

Hi Bill,

 

 

Thanks for the explanation. I'm not an Oracle expert by any means, so that was useful.

 

 

If the app client was configured only to open connections to the LTM VIP, LTM could select a new cluster if the primary first cluster went down. This would provide near-seemless resilience at the TCP layer. But do the other clusters have real time mirroring of the first cluster's data? If so, it seems like the failover between clusters could be seemless at the TCP and app layer.

 

 

If the data isn't mirrored between clusters, what would the app client need to get in response from the server end (either LTM or the database) to tell it to restart its session because the existing cluster died? Would a TCP reset suffice? Or a SQL level message? Or something entirely different?

 

 

Aaron