Tooling on an Exadata Cloud Service instance. Service endpoints required for backing up databases, patching, and updating the cloud Resolution of those hostnames by resources in the VCN. It enables hostname assignment to the nodes, and DNS Route on the compute nodes (for VM clusters, the virtual machines) toĮnable access to Object Storage by way of the backupįor the nodes to communicate, the VCN must use the InternetĪnd VCN Resolver. See Security Rules for the Exadata Cloud Service instance.
Rule enables the backup subnet to reach the regional Object Storage for backups.Įnable the desired traffic to and from the Exadata nodes. Services Network, and target = the service gateway. The same rule as for the client subnet: for the service CIDR label called All.Separate custom route table for the private backup subnet, with one rule:.A rule for 0.0.0.0/0, and target = NAT gateway.Also see Option 2: Service Gateway Access to Both Object Storage and YUM Repos. The rule enables the client subnet to reach the regional Oracle The Oracle Services Network is a conceptual network in Oracle Cloud Infrastructure that is reserved for Oracle services.
You will create custom route tables for each subnet. For more information, see Overview of VCNs and Subnets. The important thing to know for your Exadata Cloud Service instance is that the resources youĬreate in the two subnets must be in the same availability domain. If you instead use AD-specific subnets, both the client andīackup subnets must be in the same availability domain. In general, Oracle recommends using regionalĭomains in the region. Instances using DB system resource model, networking is configured on the DB system Model, networking is configured on the cloud VM cluster resource. For Exadata Cloud Service instances using the new Exadata resource