Changing to a Different Backup Destination

With Oracle Database Exadata Cloud at Customer, you can change the backup destination for your database deployment after creating it.

The instructions in this topic describe how to switch backup destinations for an existing database deployment. Specifically, the following changes are possible using the instructions in this topic:

  • From None to Both Cloud Storage and Local Storage

  • From None to Cloud Storage Only

  • From Both Cloud Storage and Local Storage to Cloud Storage Only

  • From Cloud Storage Only to Both Cloud Storage and Local Storage

For background information on the destinations, see About Backing Up Database Deployments on Exadata Cloud at Customer.

Note:

The Oracle Database Cloud Service console does not recognize backup configuration changes made outside the console. Therefore, depending on what backup destination change you make, the console will not reflect the new backup destination and may not list any completed backups. If the backups are not displayed, you will not be able to use the Oracle Database Cloud Service console to perform recovery.

Prerequisites

Changing the Backup Destination

Oracle Database Exadata Cloud at Customer allows you to change the backup destination for your database deployments after creating them.

Before changing the backup destination, make sure you have performed applicable Prerequisites.

  1. Connect as the oracle user to a compute node that is associated with your database deployment.
  2. Configure your Oracle Database environment variable settings:
    $ . oraenv
  3. Start an RMAN session:
    $ rman target=/
    ...
    RMAN> 
  4. Delete any existing backups.
    RMAN> delete backup;
    All RMAN-managed backups for the database are deleted. This process may take several minutes.
  5. Exit the RMAN session:
    RMAN> exit;
  6. Close your connection to the compute node as the oracle user.
  7. Connect as the opc user to a compute node that is associated with your database deployment.
  8. Start a root-user command shell:
    $ sudo -s
    #
  9. Enter the bkup_api command to generate a file containing the current backup settings:
    # /var/opt/oracle/bkup_api/bkup_api get config [--file=filename] --dbname=dbname
    

    where filename is an optional parameter used to specify a name for the file that will be generated and dbname is the database name for the database that you want to act on.

  10. Edit the parameter values in the generated file to change the backup destination. The following parameters are used to customize the backup destination:
    Parameter Description

    bkup_disk

    Enables backups to local Exadata storage. Valid values are yes and no.

    bkup_disk_recovery_window

    Retention period for backups on local Exadata storage. Value is expressed as a number of days between 1 and 14. Only applicable when bkup_disk is set to yes.

    bkup_oss

    Enables backups to cloud storage. Valid values are yes and no.

    bkup_oss_l0_day

    Day of the week when a level 0 backup is taken and stored on cloud storage. Valid values are mon, tue, wed, thu, fri, sat, sun. Only applicable when bkup_oss is set to yes.

    bkup_oss_recovery_window

    Retention period for backups to cloud storage. Value is expressed as a number of days between 1 and 90. Only applicable when bkup_oss is set to yes.

    bkup_oss_url

    Location of the storage container that is used for backup to cloud storage. Only applicable when bkup_oss is set to yes.

    bkup_oss_user

    User name of the Oracle Cloud user having write privileges on the cloud storage container specified in bkup_oss_url. Only applicable when bkup_oss is set to yes.

    bkup_oss_passwd

    Password of the Oracle Cloud user having write privileges on the cloud storage container specified in bkup_oss_url. Only applicable when bkup_oss is set to yes.

  11. Enter the bkup_api command to update the backup settings using the file you generated:
    # /var/opt/oracle/bkup_api/bkup_api set config --file=filename --dbname=dbname
    

    where filename is used to specify the name of the file that contains the updated backup settings and dbname is the database name for the database that you are acting on.

  12. You can use this bkup_api command to check the status of the update:
    # /var/opt/oracle/bkup_api/bkup_api configure_status
    
  13. Exit the root-user command shell:
    # exit
    $