In this example, the following assumptions are made:
You have two two-node clusters with MySQL installed, and the disaster recovery framework already configured with partnership gg-ps.
The Oracle GoldenGate resources are configured in the MySQL resource group mys-rg.
For replication, a separate network is dedicated between the clusters. This is optional. However, if it is done this way you will need separate logical hosts for the replication network.
The nodes on cluster nyc are pnyca and pnycb.
The logical host used for replication on cluster nyc is nyc-gg.
The nodes on cluster sfo are psfoa and psfob.
The logical host used for replication on cluster sfo is sfo-gg.
The logical hosts used by the Disaster Recovery Framework are on clusters nyc and sfo, so we need the IP aliases for logical hosts to be created automatically such that nyc is on cluster nyc and sfo is on cluster sfo.
Both MySQL databases listen on port 3306.
The shared storage are two ZFS file systems - /mys for MySQL and /gg for Oracle GoldenGate on the nodes.
Both clusters have the HAStoragePlus resources, mys-hsp-rs and gg-hsp-rs, already configured.
The application is in the resource group app-rg. In this case, it is only a logical host named app.
The logical host for applications, app-rg, are defined on both clusters.
This deployment example results in the following:
A highly available Oracle GoldenGate installation in an active-active replication topology.
A protection group gg-pg providing business continuity capabilities consisting of:
A replication component, gg-comp.
A replication status resource group, rep-rg.
A replication status resource, rep-rs.