Creating Database Backup Destinations for Oracle Exadata Database Service on Cloud@Customer
Oracle Exadata Database Service on Cloud@Customer provides a backup facility, which you can configure individually on each database.
To store database backups on a Recovery Appliance or on a network file storage (NFS) location that you manage, then you must first create a backup destination.
- About Managing Backup Destinations for Oracle Exadata Database Service on Cloud@Customer
For backups, you can either use the Oracle Exadata Database Service on Cloud@Customer backup facility, or you can configure a backup location on a location you manage. - Prerequisites for Backup Destinations for Oracle Exadata Database Service on Cloud@Customer
To configure backup destinations on a Zero Data Loss Recovery Appliance location, or an NFS backup location, review the prerequisites. - Using the Console for Backup Destinations for Oracle Exadata Database Service on Cloud@Customer
Learn how to use the console to create, edit, move, and terminate a backup destination for your infrastructure for Oracle Exadata Database Service on Cloud@Customer.
Related Topics
About Managing Backup Destinations for Oracle Exadata Database Service on Cloud@Customer
For backups, you can either use the Oracle Exadata Database Service on Cloud@Customer backup facility, or you can configure a backup location on a location you manage.
Oracle Exadata Database Service on Cloud@Customer provides a backup facility, which you can configure individually on each database.
See: Managing Databases on Exadata Cloud@Customer and Managing Database Backup and Recovery on Exadata Cloud@Customer.
If you want to store backups on a Recovery Appliance, or on a network file storage (NFS) location that you manage, then 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 Oracle Exadata Database Service on Cloud@Customer backup facility can also store backups on Oracle Cloud Infrastructure object storage, or on local Exadata storage on your Oracle Exadata Database Service on Cloud@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.
Related Topics
Prerequisites for Backup Destinations for Oracle Exadata Database Service on Cloud@Customer
To configure backup destinations on a Zero Data Loss Recovery Appliance location, or an NFS backup location, review the prerequisites.
- For a Zero Data Loss Recovery Appliance backup destination:
- The appliance must be configured with a virtual private catalog (VPC) user, which is used for taking the backups.
- The appliance must be configured with the unique database name of the database being backed up, and a mapping to the VPC user.
- The appliance must be accessible from the Oracle Exadata Database Service on Cloud@Customer system using the Oracle Net Services connection string, which is provided by the Zero Data Loss Recovery Appliance administrator.
- For an NFS backup destination:
- Oracle Exadata Database Service on
Cloud@Customer non-autonomous databases:
- You must mount the NFS server location to a local mount point directory on each node in the VM cluster.
- The local mount point directory and the NFS server must be identical across all nodes in the cluster.
- 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
operating system user on all of the VM cluster nodes.
- Autonomous Database on Cloud@Customer:
Note
Oracle Autonomous Database on Exadata Cloud@Customer supports NFS versions 3 and 4. Mounts with both versions enabled, however, default to version 4.- To ensure that the Autonomous VM cluster can access the NFS server over the (preferred) Backup Network, enter valid Backup Network IP addresses while configuring the VM Cluster Network.
If the backup destination is not accessible over the backup network but accessible over the client network, the backup traffic will be routed over the client network.
- The NFS-mounted file system must be readable and writable by the
oracle
operating system user on all of the VM cluster nodes. - If permissions are being controlled at the user level, then the
uid:gid
of theoracle
user for the Autonomous VM cluster is 1001:1001. - For NFSv4 servers that restrict port range, you must use the insecure option to enable clients other than an Administrator user to connect to the NFS server.
- To ensure that the Autonomous VM cluster can access the NFS server over the (preferred) Backup Network, enter valid Backup Network IP addresses while configuring the VM Cluster Network.
- Oracle Exadata Database Service on
Cloud@Customer non-autonomous databases:
Using the Console for Backup Destinations for Oracle Exadata Database Service on Cloud@Customer
Learn how to use the console to create, edit, move, and terminate a backup destination for your infrastructure for Oracle Exadata Database Service on Cloud@Customer.
- Using the Console to Create a Backup Destination
To create a backup destination, be prepared to provide values for the backup destination configuration. - Using the Console to Edit a Backup Destination
To edit a backup destination, be prepared to provide values for the backup destination configuration. - Using the Console to Move a Backup Destination to Another Compartment
To move a backup destination, be prepared to provide values for the backup destination configuration. - Using the Console to Delete a Backup Destination
To delete a backup destination, be prepared to provide values for the backup destination configuration.
Using the Console to Create a Backup Destination
To create a backup destination, be prepared to provide values for the backup destination configuration.
Using the Console to Edit a Backup Destination
To edit a backup destination, be prepared to provide values for the backup destination configuration.
You can only edit a backup destination if it is not currently associated with database.
Using the Console to Move a Backup Destination to Another Compartment
To move a backup destination, be prepared to provide values for the backup destination configuration.
You can change the compartment that contains your backup destination by moving it.
When you move a backup destination, the compartment change does not affect other associated resources. These other resources, such as the associated databases, remain in their current compartment.
Using the Console to Delete a Backup Destination
To delete a backup destination, be prepared to provide values for the backup destination configuration.
Before you can delete a backup destination, you must ensure that it is not associated with any databases.
- Does not remove any residual backups that are left in the backup destination
- Removes all references to the deleted backup destination from the Cloud Control Plane