Verify that your environment meets the system requirements for deploying the Commvault Cloud backup gateway on Oracle Cloud Infrastructure (OCI).
Note
For information about creating a new backup gateway for OCI, see "Backup Gateway" in Configuring Backups for Oracle Cloud Infrastructure (OCI) Virtual Machines.
Configuring an HTTP Proxy for Oracle Cloud Infrastructure
You can configure a different HTTP proxy to communicate with your cloud account. By default, if an HTTP proxy is configured for the CommServe computer, that HTTP proxy is used by all clients in the CommCell group. See, Configuring an HTTP Proxy.
Instance Size
| Component | Extra small | Small | Medium |
|---|---|---|---|
| Backup data size | Up to 50 TB | Up to 100 TB | Up to 150 TB |
| Oracle Compute Units (OCPUs) | 1 | 2 | 4 |
| Memory | 16 | 32 | 32 |
| Index cache size | 400 GB local disk space with 200+ random IOPs | 400 GB local disk space with 200+ random IOPs | 1 TB SSD class local disk with 400+ random IOPS |
| DDB size |
|
|
|
| VM shape | VM.Standard3.Flex | VM.Standard3.Flex | VM.Standard3.Flex |
Network
-
TCP 443 outbound must be open to access the Commvault Cloud backup service (*.metallic.io). This is only control traffic and not data traffic.
-
TCP 8403 must be open between the backup gateway and any protected resources.
-
If the backup gateway and the Oracle resources are deployed in different VCNs or in different accounts, VCN peering is required.
-
By default, Oracle does not allow internet access to the public subnet unless there is a public IP assigned to that virtual machine (internet gateway). The private subnet has access to the internet by default without a public IP. This is an Oracle limitation, not a Commvault Cloud limitation. For more information, see "Internet Gateway" in Oracle Cloud Infrastructure Documentation.