Managing Backup Destinations for Exadata Cloud@Customer

Learn to manage backup destinations for Exadata Cloud@Customer on Oracle Zero Data Loss Recovery Appliance or Network File System (NFS).

About Managing Backup Destinations for Exadata Cloud@Customer

For backups, you can either use the Exadata Cloud@Customer backup facility, or you can configure a backup location on a location you manage.

Exadata 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 Exadata Cloud@Customer backup facility can also store backups on Oracle Cloud Infrastructure object storage, or on local Exadata storage on your Exadata 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.

Required IAM Policy for Backup Destinations

Review the identity access management (IAM) policy for backup destinations for Oracle Exadata Cloud@Customer Systems.

A policy is An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources.

A compartment is a collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization.

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 a software development kit (SDK), a command-line interface (CLI), or some other tool. If you try to perform an action, and receive a message that you don’t have permission, or are unauthorized, then 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, then see "Getting Started with Policies" and "Common Policies". If you want to dig deeper into writing policies for databases, then see "Details for the Database Service".

Prerequisites for Backup Destinations for Exadata 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 Exadata 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:
    • Exadata 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 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 operating system user on all of the VM cluster nodes.
    • Exadata Cloud@Customer Autonomous Databases:
      • Ensure that the NFS server is accessible from the Autonomous VM cluster over the IP addresses that you have specified.
      • The NFS-mounted file system must be readable and writable by the oracle operating system user on all of the VM cluster nodes.

Using the Console for Backup Destinations for Exadata Cloud@Customer

Learn how to use the console to create, edit, move, and terminate a backup destination for your infrastructure for Oracle Exadata 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.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
  2. Choose the Region that contains your Exadata infrastructure.
  3. Click Backup Destinations.
  4. Click Create Backup Destination.
  5. Provide the requested information in the Create Backup Destination page:
    1. Choose a compartment.

      From the list of available compartments, choose the compartment that you want to contain the backup destination.

    2. 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.

    3. Choose either a Zero Data Loss Recovery Appliance or a network file system (NFS) backup destination.

      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.
        • 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.
          • NFS export share: Specify the directory path where the exported file system is mounted.
    4. 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.
  6. 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.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
  2. Choose the Region and Compartment that contains the backup destination that you want to edit.
  3. Click Backup Destinations.
  4. Click the name of the backup destination that you want to edit.

    The Backup Destination Details page displays information about the selected backup destination.

  5. Click Edit.
  6. 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.
  7. Click Save Changes.

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.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
  2. Choose the Region and Compartment that contains the backup destination that you want to move.
  3. Click Backup Destinations.
  4. Click the name of the backup destination that you want to move.

    The Backup Destination Details page displays information about the selected backup destination.

  5. Click Move Resource.
  6. In the resulting dialog, choose the new compartment for the backup destination and click Move Resource.

Using the Console to Terminate a Backup Destination

To terminate a backup destination, be prepared to provide values for the backup destination configuration.

Terminating a backup destination removes it from the Cloud Control Plane. Before you can terminate a backup destination, you must ensure that it is not associated with any databases.

  1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
  2. Choose the Region and Compartment that contains the backup destination that you want to terminate.
  3. Click Backup Destinations.
  4. Click the name of the backup destination that you want to terminate.

    The Backup Destination Details page displays information about the selected backup destination.

  5. Click Terminate.
  6. In the resulting dialog, enter the backup destination name and click Terminate Backup Destination to confirm the action.

Using the API for Backup Destinations for Exadata Cloud@Customer

Review the list of API calls to manage your Exadata Cloud@Customer backup destinations.

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@Customer backup destinations:
  • CreateBackupDestination
  • DeleteBackupDestination
  • GetBackupDestination
  • ListBackupDestination
  • UpdateBackupDestination
  • ChangeBackupDestinationCompartment

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