Skip to main content


 

 

How can we help you?

 

Druva Documentation

Oracle database backup workflow

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

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

 

This article explains how data flows during the Oracle database backup.

Backup workflow

The following diagram depicts the data flow at the time of backing up Oracle databases.

BackupWF1.png

Step Operation

Step 1

A backup request is initiated and forwarded to the Druva Oracle agent. Druva checks if the Hybrid Workloads agent is running. 

  • If the agent is running, Druva performs the backup operation.
  • If the agent is not running, Druva performs the backup operation based on the type of backup job.
    • For a manually triggered backup job, Druva fails the backup request.
    • For a scheduled job, Druva waits until the expiry window of the backup request, else fails the backup request

Step 2

Druva determines the type of backup.

If you or another administrator initiates the first backup, Druva performs a full backup. All subsequent backups triggered by administrators are incremental backups. Druva also performs archive log backups based on the settings configured to back up archive logs.

Step 3

Hybrid Workloads agent estimates the data files to back up.

Step 4

Hybrid Workloads agent uses the configured backup settings to create corresponding RMAN scripts.   Hybrid Workloads agent performs some pre-checks on the configured instances for the RAC databases and only the eligible instances are used for backup. For more information about the pre-checks, see Backup configuration pre-checks.

Step 5

Hybrid Workloads agent backs up data using the Oracle RMAN and streams the deduplicated backup data directly to the Druva Cloud.

For the RAC databases, if the primary instance on which backup was initiated goes down, the backup fails.
If any of the secondary instances goes down, an alert is raised stating that the instance has gone down during backup and the backup continues from other instances. However, depending on the phase of the backup on the primary instance, if the secondary instance goes down during backup, the backup might fail.

After the transfer completes, the recovery point is created.

Related articles

  • Was this article helpful?