How To Disable Automatic Database Backups Using DBAASCLI on ExaCC

In this blog post, I will show you how to disable Automatic database backups on ExaCC using dbaascli.

There are 3 types of database backups in ExaCC:

1. Cloud Tooling: We can take database backup using cloud tooling like OCI Console, OCI CLI, JDKs, and Rest APIs. This can be enabled automatically or we can set it manually.

2. bkup_api or dbaascli: If we need more customization ExaCC provides a command line tool (dbaascli) to set up our backup strategy.

NOTE: bkup_api will be deprecated in a future release and we can use dbaascli instead to backup the database.

3. Manual backup: We can use RMAN to take manual backup, same as on-premises.

Why we need to disable automatic backup:

Before manual backups are started, the cloud-managed backup functionality should be disabled. This is needed so the cloud backup jobs do not purge archive logs before they are manually backed up and do not conflict with the manual backups.

How to disable Automatic Backup:

1. Generate a Config file (In my case DB name is BANERPOC)

dbaascli database backup –dbName <db_name> –getConfig –configFile /tmp/configfile1.txt

2. Edit the values in the generated file to change the following parameters.

This will remove the backup crontab entries and disable all automatic backups. If the values are set        to   yes, then set to no.

bkup_cron_entry=no

bkup_archlog_cron_entry=no

bkup_nfs=no

bkup_oss=no

bkup_disk=no

bkup_zdlra=no

bkup_dbrs=no

3. Update the backup settings using the edited Config file.

dbaascli database backup –dbName BANERPOC –configure –configFile /tmp/banerpoc_config.txt

4. Verify that the configure command is completed successfully :

dbaascli database backup –dbName <db_name> –status –uuid <UUDI from above command>

5. Monitor the next backup attempts, they must not run anymore.

dbaascli database backup –dbName <db_name> –show history –all | tail -100

also, we can see the crontab entry deleted from the/etc/crontab output.

NOTE: After making these changes, no backups, including archive log backups, are made by the cloud automation. Ensure that manual RMAN backups are in place to avoid filling the archive log location.