Manage Long-Term Backups

You can view the list of long-term backups for an Autonomous Database on Dedicated Exadata Infrastructure and modify or delete them from its Details page.

Required IAM Policies

  • read autonomous-databases
  • manage autonomous-backups

Procedure

  1. Go to the Details page of the Autonomous Database for which you want to modify a long-term backup.
  2. Click Backups.
    All the existing backups for this Autonomous Database are listed with the details such as its name, state, type, retention period, Database version, backup destination, expiration date, and encryption key.
  3. Long-term backups are listed with Long-term as their Type. You can perform the following actions on a long-term backup by clicking the Actions menu next to it.
    Action Steps
    Clone a long-term backup

    Click the actions icon, and select Create Clone.

    The Clone Autonomous Database page opens with Clone Source defaulted to this long-term backup.

    Provide the remaining details on this page, and click Clone Autonomous Database.

    Refer to Clone Autonomous Database from Backup

    for more details.
    Edit the retention period

    Click the actions icon, and select Edit retention period.

    Choose the Retention period of your choice from the Edit long-term backup retention period dialog, and click Save.

    The long-term backup's Expiration date updates accordingly.

    On Oracle Public Cloud and Exadata Cloud@Customer deployments:
    • If the parent ACD has retention lock enabled, the retention period can only be increased from the original value.
    • If the retention lock is not enabled, you can either increase or decrease the retention period by days, months, or years.
    Delete a long-term backup

    Click the actions icon, and select Delete.

    Click Delete on the confirmation dialog that appears. The backups State changes to Deleted.

    On Oracle Public Cloud and Exadata Cloud@Customer deployments:
    • If the parent ACD has retention lock enabled, then the retention lock applies to all long-term backups for the Autonomous Databases inside the ACD. These long-term backups cannot be deleted and can only expire. If you choose NFS as a backup destination type while creating a long-term backup, then you have to manually delete the backups after they expire if the corresponding ACD is already terminated.
    • If the retention lock is not enabled, the long-term backups can be deleted at any time or can be allowed to expire. You can also choose to delete them when the Autonomous Database gets terminated. However, if you have configured NFS for storing the long-term backup and the corresponding ACD is terminated, then you have to manually delete the backups after they expire.

    Note:

    A long-term backup cannot be deleted for 7 days from the date of creation, as the Object storage bucket the backup is in has a 7-day lock.

    You can see all the long-term Autonomous Database backups in your current compartment under Autonomous standalone backups on the OCI console. On Oracle Public Cloud and Exadata Cloud@Customer deployments, the long-term backups continue to be listed under Autonomous standalone backups even after the corresponding Autonomous Database is terminated.

Related Topics