Skip to main content
druva_logo.pngDruva
|
Documentation

How can we help you?

 

Trending articles:
Druva Documentation

Manage Oracle backups

  1. Last updated
  2. Save as PDF
Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

 

Enable and disable backup

By default, the backup on the Oracle database is enabled, when you configure the database for backup. You can disable the backup of the Oracle database at any time based on your requirement.

Druva suspends backups after disabling backups on the Oracle databases. The disabled backups resume after you enable the backup from this Oracle database. 

Notes:

  • The most recent snapshot cannot be deleted as long as the database server exists in the Management Console, regardless of whether the server is marked as inactive or disabled.

  • The retention period would not be honored for the most recent snapshot when a database server is disabled. This allows you to restore the latest snapshot later if required.

Procedure

  1. Click the Configured Databases tab. 
  2. On the Configured Databases page, click the database for which you want to enable or disable the backup.
  3. On the Configured database details page, click the more More icon.png icon and click Enable Backup or Disable Backup depending on your requirement.
  4. Confirm your changes and the status is updated in the Backup Enabled column.

Manually back up a database

If you want to backup databases at a given point in time, you can trigger a full or an incremental backup manually on the database. After the backup is complete, the next backup happens as per the schedule defined in the backup policy.

Considerations

  • A manual backup is not restricted by the backup window that you defined in the backup policy; it continues till all the data is backed up.
  • If you restart or reboot your databases during backups, the backup operation is aborted. Hybrid Workloads agent starts a fresh backup following the backup schedule. Alternatively, you can start a manual backup at any time.
  • A manual backup is not restricted by bandwidth, it uses maximum bandwidth available.

Procedure

  1. Click the Configured Databases tab. 
  2. On the Configured Databases page, click the database that you want to back up.
  3. On the Configured database details page, perform the following:
    1. To perform a full backup, click Backup Now > Full Backup.
      BackupNowFull.PNG
    2. To perform an incremental backup, click Backup Now.
      BackupNowIncremental.PNG

Note: If your databases are getting backed up for the first time, the Backup Now will trigger a Full backup.

The backup of the selected database starts. You can track the progress and details about the backup job in progress on the Jobs details page. To access the Jobs details page, see View Jobs details page. 

Delete snapshot

If you are a cloud administrator, you can delete warm snapshots from Oracle databases that you no longer require. If you are a group administrator, you can delete warm snapshots for the Oracle databases belonging to the administrative groups that you manage. After you delete a snapshot, Druva purges the snapshot data from the warm storage, thus freeing up space.

Note: You cannot delete the most recent snapshot of the Oracle database.

Procedure

  1. Click the Configured Databases tab. 
  2. On the Configured Databases page, click the database for which you want to delete the configuration.
  3. On the Configured database details page, click the Backups tab.
  4. Select the snapshot(s) that you want to delete and click Delete.

Note: If the Oracle database has just one snapshot, it cannot be deleted.

Reconfigure database

You can reconfigure a database for backup by changing the backup policy or administrative group associated with the database.

Procedure

  1. Click the Configured Databases tab. 
  2. On the Configured Databases page, click the database that you want to reconfigure for backup.
  3. On the Configured database details page, click the more More icon.png icon and click Reconfigure.
  4. On the Update Database page, reconfigure the following values based on your configuration requirement:

    1. Backup policy

    2. Administrative group

    3. Local storage

    4.  Authentication type

       For a RAC database, if you change the authentication type from OS or Wallet to Oracle, make sure you reconfigure the database and provide a TNS alias for each node to avoid backup failure. Likewise, if you change the authentication type from OS or Oracle to Wallet, make sure you reconfigure the database and provide a Wallet alias for each node to avoid backup failure.

    5. RAC node details

Druva applies backup settings of the selected backup policy to all the existing snapshots.

Delete configuration

You must delete the database configuration before deleting a database. Druva deletes all snapshots of the database, and cancels any backup, restore, and other jobs running for the database.

Procedure

  1. Click the Configured Databases tab. 
  2. On the Configured Databases page, click the database for which you want to delete the configuration.
  3. On the Configured database details page, click the more More icon.png icon and click Delete Configuration.
  4. A confirmation dialog is displayed. Provide a reason in the Reason for deletion box and click Delete. The reason is required to confirm your action and to prevent any accidental deletion. This is a mandatory field, and you can use a minimum of 10 characters and a maximum of 150 characters to provide the reason for deletion. Note that all deletion requests with a reason will be reported to the Audit Trails.
    For more information, see View Admin Audit Trails page.

Delete a database

If you are a cloud administrator, organization administrator, group administrator,  or a derived custom, organization, or group administrator, you can delete a database. When you delete a database, Druva deletes all the snapshots corresponding to that database. Druva also deletes the ongoing backup or restore jobs for that database. However, Druva retains the completed jobs, reports, and alerts corresponding to the deleted database.

If you are a cloud administrator, organization administrator, group administrator,  or a derived custom, organization, or group administrator, you can delete a database. A database can only be deleted after 7 days of unconfiguring the database. When you delete a database, Druva deletes all the snapshots corresponding to that database. Druva also deletes the ongoing backup or restore jobs for that database. However, Druva retains the completed jobs, reports, and alerts corresponding to the deleted database.

Note: Ensure that you delete the database configuration before deleting the database. To delete the configuration, see Delete configuration. 

Procedure

  1. Click the All Databases tab. The Databases page opens.
  2. In the Database Name column, select the database that you want to delete, and click the more More icon.png icon and click Delete.
  3. Click Yes on the confirmation message displayed.