1. Deploy Active Data Guard Far Sync to protect data across Oracle Database@Azure regions
  2. Configure Network Traffic for Active Data Guard

Configure Network Traffic for Active Data Guard

Configure the route tables and security lists to enable network communication for Active Data Guard and far sync instances between regions.

Establish the local peering between the hub VCN and the Exadata VCN in both regions and the remote peering between the hub VCNs across regions, as shown in the architecture diagram, following the OCI documentation. For more details, see Explore More.

Primary region (Toronto)

  1. Set up the primary region (Toronto).
    1. Configure the route rules in the route table associated with the Exadata client subnet.
      Destination Target type Target Route type Description
      0.0.0.0 Dynamic Routing Gateway   Static  
      10.0.1.0/24 Local peering gateway lpg_exavcn_toronto Static Traffic to Exadata client subnet Sydney
      10.10.0.0/16 Local peering gateway lpg_exavcn_toronto Static Traffic to hub VCN Toronto
      10.20.0.0/16 Local peering gateway lpg_exavcn_toronto Static Traffic to hub VCN Sydney
    2. Configure the ingress rules in the security list associated with the Exadata client subnet.
      Stateless Source IP protocol Source port range Destination port range Allows Description
      No 10.10.0.0/16 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from hub VCN Toronto
      No 10.20.0.0/16 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from hub VCN Sydney
      No 10.0.1.0/24 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from Exadata client subnet Sydney
    3. Configure the route rules in the route table associated with the subnet in the hub VCN.
      Destination Target type Target Route type Description
      10.0.1.0/24 Dynamic Routing Gateway drg_hubvcn_toronto Static Traffic to Exadata client subnet Sydney
      10.182.0.0/24 Local peering gateway lpg_hubvcn_toronto Static Traffic to Exadata client subnet Toronto
      10.20.0.0/16 Dynamic Routing Gateway drg_hubvcn_toronto Static Traffic to hub VCN Sydney
    4. Configure the ingress rules in the security list associated with the subnet in the hub VCN.
      Stateless Source IP protocol Source port range Destination port range Allows Description
      No 10.182.0.0/24 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from Exadata client subnet Toronto
      No 10.20.0.0/16 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from hub VCN Sydney
      No 10.0.1.0/24 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from Exadata client subnet Sydney
    5. Configure the route rules in the route table associated with the LPG of the hub VCN.
      Destination Target type Target Route type Description
      10.0.1.0/24 Dynamic Routing Gateway drg_hubvcn_toronto Static Traffic to Exadata client subnet Sydney
      10.20.0.0/16 Dynamic Routing Gateway drg_hubvcn_toronto Static Traffic to hub VCN Sydney
    6. Configure the route rules in the route table associated with the DRG of the hub VCN.
      Destination Target type Target Route type Description
      10.182.1.0/24 Local peering gateway lpg_hubvcn_toronto Static Traffic to Exadata client subnet Toronto
  2. Set up the standby region (Sydney).
    1. Configure the route rules in the route table associated with the Exadata client subnet.
      Destination Target type Target Route type Description
      0.0.0.0 Dynamic Routing Gateway   Static  
      10.0.1.0/16 Local peering gateway lpg_exavcn_sydney Static Traffic to Exadata client subnet Toronto
      10.182.0.0/24 Local peering gateway lpg_exavcn_sydney Static Traffic to hub VCN Toronto
      10.20.0.0/16 Local peering gateway lpg_exavcn_sydney Static Traffic to hub VCN Sydney
    2. Configure the ingress rules in the security list associated with the Exadata client subnet.
      Stateless Source IP protocol Source port range Destination port range Allows Description
      No 10.20.0.0/16 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from hub VCN Sydney
      No 10.10.0.0/16 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from hub VCN Toronto
      No 10.182.0.0/24 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from Exadata client subnet Toronto
    3. Configure the route rules in the route table associated with the subnet in the hub VCN.
      Destination Target type Target Route type Description
      10.0.1.0/24 Locl peering gateway lpg_hubvcn_sydney Static Traffic to Exadata client subnet Sydney
      10.10.0.0/16 Dynamic Routing Gateway drg_hubvcn_sydney Static Traffic to hub VCN Toronto
      10.182.0.0/24 Dynamic Routing Gateway drg_hubvcn_sydney Static Traffic to Exadata client subnet Toronto
    4. Configure the ingress rules in the security list associated with the subnet in the hub VCN.
      Stateless Source IP protocol Source port range Destination port range Allows Description
      No 10..0.1.0/24 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from Exadata client subnet Sydney
      No 10.10.0.0/16 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from hub VCN Toronto
      No 10.182.0.0/24 TCP 1521 1521 TCP traffic for ports: 1521 Ingress from Exadata client subnet Toronto
    5. Configure the route rules in the route table associated with the LPG of the hub VCN.
      Destination Target type Target Route type Description
      10.10.0.0/16 Dynamic Routing Gateway drg_hubvcn_sydney Static Traffic to hub VCN Toronto
      10.182.0.0/24 Dynamic Routing Gateway drg_hubvcn_sydney Static Traffic to Exadata client subnet Toronto
    6. Configure the route rules in the route table associated with the DRG of the hub VCN.
      Destination Target type Target Route type Description
      10.0.1.0/24 Local peering gateway lpg_hubvcn_sydney Static Traffic to Exadata client subnet Sydney