The image shows four regions: Canada central, Canada southeast (Toronto), Australia east, and Australia east (Sydney).

• Canada central includes:
  • An Azure VNet with an application subnet hosting an app, and a delegated subnet with a VNIC.
  • Oracle Database@Azure with an OCI VCN spanning across into the Toronto region. The VCN includes a backup subnet and a client subnet with Exadata Database Service, and a local peering gateway.
• Canada southeast (Toronto) includes a hub VCN with a local peering gateway, a Dynamic Routing Gateway, and a hub subnet with a far sync instance.
• Australia east mimics Canada central, and includes:
  • An Azure VNet with an application subnet hosting an app, and a delegated subnet with a VNIC.
  • Oracle Database@Azure with an OCI VCN spanning across into the Toronto region. The VCN includes a backup subnet and a client subnet with Exadata Database Service, and a local peering gateway.
• Australia east (Sydney) mimics Canada southeast (Toronto), and includes a hub VCN with a local peering gateway, a Dynamic Routing Gateway, and a hub subnet with a far sync instance.

From the Canada central region, data flows from the app to the VNIC, which has a bidirectional connections to the Exadata Database Service, from there it passes through the hub VCNs and through Oracle Data Guard which exists between the Canada and Australia regions, on to the Exadata Database Service in Australia east. A bidirectional connection extends to the VNIC, which also receives data from the app.

In Canada central, there is a bidirectional connection between the application subnet and the backups subnet. In Australia east, there is a bidirectional connection between the delegated subnet and the client subnet.

In both cases, local peering gateways connect the OCI VCNs with the hub VCNs. And the DRGs connect via a remote peering gateway.