Storing Backups in Custom Locations

A default location is created when you install the Oracle Database Cloud Backup Module for OCI or Oracle Database Cloud Backup Module for OCI Classic and backups are stored as objects in this location. You can also store backups in custom locations you've created yourself.

With the Oracle Database Cloud Backup Module for OCI, a default bucket is created. With the Oracle Database Cloud Backup Module for OCI Classic, a default storage container is created.

Custom containers and custom buckets can be created using REST calls or third-party tools such as CloudBerry Explorer (see How to Use CloudBerry Explorer with Oracle Cloud Storage from CloudBerry Lab).

To create containers using the REST API, see the tutorial Oracle Storage Cloud Service: Creating Containers Using the REST API. For related Oracle Storage Cloud Service documentation, see Creating Containers and Authenticating Access to Oracle Storage Cloud Service in Using Oracle Storage Cloud Service.

To create buckets using the REST API or Console, see Creating Buckets.

Note:

If you’re using Oracle Database Cloud Service or Oracle Database Exadata Cloud Service and want to automatically store backups in cloud storage, you need to create an Oracle Storage Cloud Service container before you create your database deployment. For information about backing up your deployment to the cloud, see Backing Up and Restoring Databases on Database Cloud Service in Using Oracle Database Cloud Service or Backing Up and Restoring Databases on Exadata Cloud Service in Using Oracle Database Exadata Cloud Service.

Note:

Containers that are used by Recovery Manager (RMAN) cannot have server-side encryption enabled. Because RMAN backups are already encrypted at the client side, server-side encryption is not required.

Example 2-8 Using Custom Buckets with Oracle Cloud Infrastructure

You can specify that backups must be stored in custom containers either while installing the Oracle Database Cloud Backup Module for OCI or after the installation.

  • While running the Oracle Database Cloud Backup Module for OCI installer, include the -bucket parameter and the custom bucket name.

    For example:

    -bucket SALES_DB

    This automatically adds the OPC_CONTAINER parameter to the opcSID.ora configuration file so the custom bucket is used for backups, where SID is the system identifier of the Oracle database being backed up to Oracle Database Backup Cloud Service.

  • To specify a custom container after you’ve installed the Oracle Database Cloud Backup Module for OCI, add the OPC_CONTAINER parameter and the bucket name to opcSID.ora.

    For example:

    OPC_CONTAINER=SALES_DB

Example 2-9 Using Custom Containers with Oracle Cloud Infrastructure Classic

Specify that backups must be stored in a custom container either while installing the Oracle Database Cloud Backup Module for OCI Classic or after the installation.

  • While running the Oracle Database Cloud Backup Module for OCI Classic installer, include the —container parameter and the custom container name.

    For example:

    -container PAYROLL_DB

    This automatically adds the OPC_CONTAINER parameter to the opcSID.ora configuration file so the custom container is used for backups, where SID is the system identifier of the Oracle database being backed up to Oracle Database Backup Cloud Service.

  • To specify a custom container after you’ve installed the Oracle Database Cloud Backup Module for OCI Classic, add the OPC_CONTAINER parameter and the container name to opcSID.ora.

    For example:

    OPC_CONTAINER=PAYROLL_DB

For information about parameters used by the installer, see Parameters Used to Run the Oracle Database Cloud Backup Module for OCI Classic Installer.

For information about the opcSID.ora configuration file, see Files Created When the Oracle Database Cloud Backup Module for OCI Classic is Installed.

For information about the opcSID.ora configuration file, see Files Created when Oracle Database Cloud Backup Module for OCI is Installed.