Skip to main content
Druva Documentation

Oracle database backup workflow

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

The availability of this feature is limited based on the license type, region, and other criteria. To access this feature, contact your Druva Account Manager or Druva Support. This article/documentation is subject to change based on the continuous improvements to this feature.

The Phoenix backup workflow for Oracle is described below:


Step Description
Step 1 An Oracle Database Administrator triggers the RMAN script with the name of the mount on the Phoenix Backup Store. The RMAN creates an Oracle RMAN backup and stores it on the mount. 

The Phoenix Backup Store creates a snapshot of the Oracle RMAN backup stored on the mount. 
Step 2 The Phoenix Backup Store creates a ZFS snapshot of the Oracle RMAN backup and applies a timestamp to the snapshot. 

The timestamp corresponds to the PUT request made to the Phoenix Backup Store after RMAN completes writing the Oracle RMAN backup to the backup mount. For more information, see Phoenix Backup Store API reference.
Step 3 Phoenix Backup Store uploads the snapshot to the Phoenix Cloud. This snapshot serves as a restore point.
After the snapshot is uploaded to the cloud, it is deleted from the Phoenix Backup Store.

Every time the Database Administrator runs the RMAN script, the RMAN creates an Oracle RMAN backup on the mount. The Phoenix Backup Store creates a new snapshot of every new Oracle RMAN backup that RMAN creates and stores on the mount and uploads the snapshot to the cloud creating a new restore point. 

RMAN can store backup data until sufficient storage is available on the Phoenix Backup Store.  If sufficient storage is not available, RMAN cannot store backups and the backup jobs fail. Ensure that you periodically remove Oracle RMAN backups from the the Phoenix Backup Store or increase storage capacity on it.