Edit

Share via

Network topology and connectivity for Oracle Database@Azure - Core network design

  • Article

Understanding the core networking concepts of Oracle Exadata Database@Azure is foundational for successful adoption. Unlike most Azure services, Oracle Database@Azure has a unique architecture. It's hosted within an Azure datacenter and provides default connectivity to the Oracle Cloud Infrastructure (OCI) control plane. This article covers key design considerations and recommendations for how to configure and manage network connectivity to support Oracle Exadata Database@Azure workloads effectively.

The following diagram illustrates the core networking architecture and relationship between Azure virtual networks and OCI virtual cloud networks (VCNs) for Oracle Exadata Database@Azure.

Diagram that shows the core network design.

The client subnet in the OCI VCN maps to the Oracle Database delegated subnet in Azure. A backup subnet is also created within the OCI VCN that's used solely for OCI-managed backups.

Design considerations

When you design your network topology for Oracle Exadata Database@Azure, consider the following Oracle-specific factors:

  • Availability zone selection: Deploy Oracle Exadata Database@Azure services into subscription-specific availability zones. This deployment affects latency and resilience. The physical datacenter might differ between subscriptions. For more information, see Physical and logical availability zones.

  • Inherited region and availability zone settings: When you deploy an Exadata Infrastructure instance, the region and availability zones are effectively mapped to it, and any virtual machine (VM) clusters created within the Exadata Infrastructure instance inherit the same settings.

  • VM cluster limits: Each Oracle Exadata Database@Azure SKU can include up to eight VM clusters. Ensure that your virtual network is configured before VM cluster creation, and decide whether to connect clusters to the same virtual network or separate virtual networks.

  • Internet access requirements: Exadata has no direct internet access by default. If internet access is required, like for patching or outbound dependencies, you must configure it.

  • Subnet sizing: Define subnet sizes according to Oracle's SKU specifications, which differ based on the chosen instance type. For more information about sizing guidelines, see Plan for IP address space for Oracle Exadata Database@Azure.

  • Delegated subnet limitation: You can create only one Oracle Database@Azure delegated subnet for each virtual network. This constraint influences how you plan your virtual network layout, especially if you anticipate multiple database deployments. For more information, see Network planning for Oracle Database@Azure.

  • Azure network security group limitation: Network security groups (NSGs) on the Oracle Database delegated subnet must be configured through OCI. For more information, see Create an NSG.

  • Split Domain Name System (DNS) model: Oracle Database@Azure follows a split DNS model. DNS must be configured on both Azure and OCI. For more information, see Oracle Database@Azure DNS setup.

  • Private DNS naming rules: When default DNS settings are used to create VM clusters, the private DNS zone is automatically named based on the virtual network and subnet that you choose for the VM cluster. The name of this zone is "oci" plus the first 10 alphabetic characters of the virtual network and subnet names. For example, if the virtual network is "vnet-exadata-prod" and the subnet is "snet-exadata-prod", the private DNS zone name is ocisnetexadat.ocivnetexadat.oraclevcn.com.

Design recommendations

  • Plan virtual network configuration: Ensure that your virtual network is configured before you create your VM cluster and determine the workload topology based on the documentation across application, business continuity and disaster recovery (BCDR), and migration connectivity.

  • Minimize network virtual appliances (NVAs): Minimize the use of NVAs in the network path because each extra hop introduces latency that can degrade database performance. Use NVAs only when required, such as for traffic inspection or compliance purposes, and ensure that their placement is optimized to reduce unnecessary routing.

  • Optimize for bandwidth and latency: Optimize bandwidth and latency by colocating resources that interact with Oracle Database@Azure – Exadata Database Service within the same availability zone.

  • Configure NSGs: Configure NSGs on the Oracle subnet through OCI to enable connectivity with source and destination networks.

  • Use unique DNS names: When you use the default DNS settings, ensure that the first 10 characters of the virtual network and subnet names for any Exadata environments are unique. If not, a DNS resolver can't distinguish between the environments.

Other guidance

Beyond the core network design concepts for Oracle Exadata Database@Azure, also consider the connectivity requirements for your applications, other Azure services (like Azure Blob Storage or Azure NetApp Files), on-premises environments, and your BCDR configuration.

Next step

Proceed to the application connectivity design guidance to learn how to connect your applications to Oracle Exadata Database@Azure efficiently and securely.