This image shows a cross-availability-zone deployment of Oracle AI Database@Azure in one Azure Region that uses Oracle Data Guard to replicate data between a primary database and a local standby, with an observer in a different availability zone.

The architecture has the following components:

• Connectivity and data movement: The Oracle AI Database runs on an Exascale VM cluster in the primary availability zone.
• Connectivity and data movement: For data protection, Data Guard replicates changes to a local standby in another availability zone within the same region.
• Connectivity and data movement: An observer runs in a different availability zone to coordinate fast-start failover for Data Guard.
• Connectivity and data movement: Azure virtual network (VNet) peering connects the virtual networks that support the deployment.
• Connectivity and data movement: Replication traffic uses the Azure network path defined for Data Guard between the primary and standby databases.
• Azure AZ1 (availability zone, AZ): VNet1 10.10.0.0/16 with Delegated subnet 1 10.10.1.0/24 provides connectivity for primary resources.
• Azure AZ1 (AZ): A Network Interface links VNet1 to Oracle AI Database@Azure.
• Azure AZ1 (AZ): Oracle AI Database@Azure uses virtual cloud network (VCN) 1 with a Client subnet and a Backup subnet.
• Azure AZ1 (AZ): Oracle Exadata Database Service on Exascale Infrastructure (Primary) hosts the primary database.
• Azure AZ2 (AZ): VNet1 10.20.0.0/16 with Delegated subnet 2 10.20.1.0/24 provides connectivity for standby resources.
• Azure AZ2 (AZ): A Network Interface links VNet1 to Oracle AI Database@Azure.
• Azure AZ2 (AZ): Oracle AI Database@Azure uses VCN 2 with a Client subnet and a Backup subnet.
• Azure AZ2 (AZ): Oracle Exadata Database Service on Exascale Infrastructure (Standby) hosts the local standby database.
• Azure AZ3 (AZ): VNet3 10.30.0.0/16 with Fast-Start Failover subnet 3 10.30.1.0/24 hosts the Observer component.