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.
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.
Note
Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.
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 the oracle 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.
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.
Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
Choose the Region that contains your Exadata
infrastructure.
Click Backup Destinations.
Click Create Backup Destination.
Provide the requested information in the Create Backup
Destination page:
Choose a compartment.
From the list of available compartments, choose the compartment that
you want to contain the backup destination.
Name your backup destination.
Specify a user-friendly name that you can use to identify the backup
destination. The name doesn't need to be unique because an Oracle
Cloud Identifier (OCID) uniquely identifies the backup
destination.
Choose either a Zero Data Loss Recovery Appliance or a network file
system (NFS) backup destination.
Note
You can also set
OCI Object Store as a backup destination. However, you cannot set it
from this screen. You can configure OCI Object Store as a backup
destination when creating a database. For more information, see
Backup Destination Type in Using the Console to Create a
Database.
Select Recovery Appliance or
Network Storage (NFS).
If you select Recovery
Appliance, then you must also specify the
following for Zero Data Loss Recovery Appliance:
Provide the Recovery Appliance
connection string: Specify the Oracle Net
Services connection string that connects to the
appliance. This information is typically provided by the
Zero Data Loss Recovery Appliance
administrator.
Note
ADB customers must ensure to
provide the connection string that connects to the
recovery appliance in an Oracle "easy connect"
string format, as shown
below:
host:port/service name
Where
host is the
SCAN hostname of the Zero Data Loss Recovery
Appliance.
Provide the Virtual Private
Catalog (VPC) Users: Provide a VPC user
name for connecting to the Zero Data Loss Recovery
Appliance. You can specify multiple VPC user names in
case you want to use the appliance as a backup
destination for multiple databases. This information is
typically provided by the Zero Data Loss Recovery
Appliance administrator.
If you select Network Storage
(NFS), then you must also specify the
following:
Self-mount for non-autonomous
databases:
Provide the local NFS mount
point path: Specify the local directory path on
each VM cluster node where the NFS server location is
mounted. The local directory path and the NFS server
location must each be the same across all of the VM
cluster nodes.
Auto-mount for Autonomous
Databases:
Use this destination for
Autonomous Databases:
NFS server: Specify the IP address of the NFS server. Optionally, you can specify up to four IP addresses. These are just extra paths to the same NFS server. Note that Oracle supports only one NFS device for backups.
NFS export share: Specify
the directory path where the exported file system
is mounted.
Configure Advanced Options.
Tags: (Optional) You can choose to apply tags. If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, refer to information about resource tags. If you are not sure if you should apply tags, then skip this option (you can apply tags later), or ask your administrator.
Click Create Backup Destination.
The Backup Destination Details page
displays the newly created backup destination.
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.
Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
Choose the Region and Compartment
that contains the backup destination that you want to edit.
Click Backup Destinations.
Click the name of the backup destination that you want to edit.
The Backup Destination Details page displays
information about the selected backup destination.
Click Edit.
Use the Edit Backup Destination dialog to edit the
backup destination attributes:
Note
You cannot edit a Backup Destination if there is already a database
attached to it.
If you are editing a Zero Data Loss Recovery Appliance
backup destination:
Provide the Recovery Appliance
connection string: Specify the Oracle Net
Services connection string that connects to the Recovery
Appliance. This information is typically provided by the
Recovery Appliance administrator.
Provide the Virtual Private Catalog
(VPC) Users: Provide a VPC user name for
connecting to the Recovery Appliance. You can specify multiple
VPC user names in case you want to use the Recovery Appliance as
a backup destination for multiple databases. This information is
typically provided by the Recovery Appliance administrator.
If you are editing an NFS backup destination:
Self-mount for non-autonomous
databases:
Provide the local NFS mount point
path: Specify the local directory path on each VM
cluster node where the NFS server location is mounted. The local
directory path and the NFS server location must each be the same
across all of the VM cluster nodes.
Auto-mount for Autonomous
Databases:
Use this destination for Autonomous
Databases:
NFS server: Specify the IP address of
the NFS server. Optionally, you can specify up to four
IP addresses.
NFS export share: Specify the
directory path where the exported file system is
mounted.
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.
Open the navigation menu. Under Oracle Database, click Exadata Database Service on Cloud@Customer.
Choose the Region and Compartment
that contains the backup destination that you want to move.
Click Backup Destinations.
Click the name of the backup destination that you want to move.
The Backup Destination Details page displays information about the selected
backup destination.
Click Move Resource.
In the resulting dialog, choose the new compartment for the backup destination
and click Move Resource.