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.

To create containers using the REST API, see the tutorial Oracle Cloud Infrastructure Object Storage Classic: Creating Containers Using the REST API. For related Oracle Cloud Infrastructure Object Storage Classic Service documentation, see Creating a Container.

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

Note: If you’re using Oracle Cloud Infrastructure Object Storage or Oracle Exadata Database Service on Dedicated Infrastructure and want to automatically store backups in cloud storage, you need to create buckets or containers before you create your database deployment. For information about backing up your deployment to the cloud, see OCI Object Storage or Manage Database Backup and Recovery on Oracle Exadata Database Service on Dedicated Infrastructure.

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 3-4 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 3-5 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.