Managing Backup Destinations for Exadata Cloud at Customer

This topic explains how to manage backup destinations for Exadata Cloud at Customer on Oracle Zero Data Loss Recovery Appliance or Network File System (NFS).

Exadata Cloud at Customer provides a backup facility, which can be individually configured on each database. See Managing Databases on Exadata Cloud at Customer and Managing Database Backup and Recovery on Exadata Cloud at Customer.

However, if you want to store backups on a Recovery Appliance or NFS location that you manage, you must first create a backup destination. Each backup destination defines the properties that are required to connect to the Recovery Appliance or NFS location, and each backup destination must be accessible in your data center from the VM cluster nodes.

The Exadata Cloud at Customer backup facility can also store backups on Oracle Cloud Infrastructure object storage or local Exadata storage on your Exadata Cloud at Customer system. However, you do not need to create a backup destination for any of these other locations. Instead, applicable options for backup to cloud object storage or local Exadata storage are available directly when you create a database.


Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in.

For administrators: The policy in Let database admins manage DB systems lets the specified group do everything with databases and related Database resources.

If you're new to policies, see Getting Started with Policies and Common Policies. If you want to dig deeper into writing policies for databases, see Details for the Database Service.


  • For a Recovery Appliance backup destination:

    • The Recovery Appliance must be configured with a virtual private catalog (VPC) user, which is used for taking the backups.
    • The Recovery Appliance must be configured with the unique database name of the database being backed up, and a mapping to the VPC user.
    • The Recovery Appliance must be accessible from the Exadata Cloud at Customer system using the Oracle Net Services connection string, which is provided by the Recovery Appliance administrator.
  • For an NFS backup destination:

    • You must mount the NFS server location to a local mount point directory on each node in the VM cluster.
    • The local directory path and the NFS server location must each be the same across all of the VM cluster nodes.
    • You must ensure that the NFS mount is maintained continuously on all of the VM cluster nodes.
    • The NFS-mounted file system must be readable and writable by the oracle OS user on all of the VM cluster nodes.

Using the Console

To create a backup destination
To edit a backup destination
To move a backup destination to another compartment
To terminate a backup destination

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use these API operations to manage Exadata Cloud at Customer backup destinations:

For the complete list of APIs, see Database Service API.