Manual Backups on Autonomous Database
In addition to automatic backups that Autonomous Database regularly performs, you can take manual backups at any time.
Configure Manual Backups on Autonomous Database
Follow these steps to configure the Oracle Cloud Infrastructure Object Storage credentials and tenancy URL for manual backups and to create the Oracle Cloud Infrastructure Object Storage bucket to store manual backups.
To configure your database for manual backups, do the following:
-
Create an Oracle Cloud Infrastructure Object Storage bucket for manual backups
-
Set database property
DEFAULT_BACKUP_BUCKET
to specify the manual backup bucket on the Oracle Cloud Infrastructure Object Storage -
Define the Oracle Cloud Infrastructure Object Storage credentials
-
Set the database property
DEFAULT_CREDENTIAL
database property
These manual backup configuration tasks are a one-time operation. After you define your credentials and your tenancy URL you can initiate manual backups without doing the same operations again unless the URL, the credentials, or the bucket change.
To perform the manual backup configuration tasks you need to connect to your database and perform the required DDL commands. For example, connect to your database with SQL Developer or SQL*Plus. See Connect to Autonomous Database Using Oracle Database Tools.
Use the following command to show the value for
DEFAULT_BACKUP_BUCKET
:
SELECT PROPERTY_VALUE FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME='DEFAULT_BACKUP_BUCKET';
See Manual Backup Notes for more information.
Perform Manual Backups on Autonomous Database
In addition to automatic backups, Autonomous Database also allows you take manual backups and store the backups to Oracle Cloud Infrastructure Object Storage.
Perform the following prerequisite steps as necessary:
-
Open the Oracle Cloud Infrastructure console by clicking the
next to Oracle Cloud.
- From the Oracle Cloud Infrastructure left navigation list click either Autonomous Data Warehouse, Autonomous Transaction Processing, or Autonomous JSON Database depending on the workload type of your Autonomous Database.
-
On the Autonomous Databases page select an Autonomous Database from the links under the Display Name column.
See Manual Backup Notes for more information.
Manual Backup Notes
Provides notes for manual backups and for manual backup configuration.
Notes for manual backup configuration:
-
If you previously configured manual backups using the
DEFAULT_BUCKET
property, you do not need to make any changes to perform manual backups with your existing configuration. In this case, theDEFAULT_BUCKET
property is set to the value of Oracle Cloud Infrastructure Object Storage tenancy URL and the required bucket name is in the format ofbackup_
databasename. Where databasename is lowercase. However, Oracle recommends that you configure Autonomous Database for manual backups using theDEFAULT_BACKUP_BUCKET
database property. See Configure Manual Backups on Autonomous Database for more information. -
If you previously configured Autonomous Database to use manual backups using the
DEFAULT_BUCKET
property and created backups, then after configuring theDEFAULT_BACKUP_BUCKET
property to use a new manual backup bucket, the old manual backups in the old bucket are not available for restore. If you want to use the old backups then you must change the value of theDEFAULT_BACKUP_BUCKET
property to specify the URL of the old manual backup bucket. -
If you previously configured Autonomous Database to use manual backups and you rename your Autonomous Database, then your backups will continue to work without changes.
Notes for manual backups:
-
Each manual backup creates a full backup on your Oracle Cloud Infrastructure Object Storage bucket and the backup can only be used by the Autonomous Database instance when you initiate a point-in-time-recovery.
-
The retention period for manual backups is the same as for automatic backups, which is 60 days.
-
While backing up a database, the database is fully functional. However, during the backup the lifecycle management operations, such as stopping the database, are not allowed.