Skip to main content

How can we help you?

Druva Documentation

Restore an Oracle database from a snapshot

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

 

You can recover databases from the warm snapshots that are stored in the Druva Cloud and cold snapshots stored in the AWS glacier. Druva allows you to restore a complete database automatically on your Oracle server host. Druva also enables DBAs to manually recover individual database elements, such as data files, control files, system parameter files, archive logs, wallet files, and metadata. For more information about restoring wallet files, see Restore Oracle Wallet files.

When you restore a complete database from a snapshot back to the original server host, Druva overwrites all the existing content of the database. When you choose to recover individual database elements, Druva downloads the requested snapshot on the restore location specified during the restore operation. DBA can manually recover the required database elements by running scripts.  For more information, see Recover database from the downloaded backup data.

To restore databases, you select a snapshot or a restore point from the snapshots drop-down list. The list displays the timestamp of all the snapshots available for restore. Based on the requested resource (complete database or individual database elements), Druva restores data by overwriting all of the existing content of the database or downloading the backup data to the specified restore location. The DBA can run RMAN commands to fetch backup data downloaded to the restore location and recover the database on the required Oracle server host.

The following video illustrates the process.  

Before you begin

For automated restore of RAC databases, make sure that the directories of the following files are present on the shared storage (ASM):

  • 1. Server Parameter file

  • 2. Control File

  • 3. Archive log files

We can then restore these files from the restore points.

Procedure

  1. Log in to the Management Console. 
  2. Click Oracle > Direct to cloud from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then click Oracle > Direct to Cloud.
  3. In the left navigation pane, click Configured Databases.
  4. On the Configured Databases page, select the database that you want to restore and click Restore.
    Note: To quickly search and select a database, you can use the search box on the top-right corner of the Configured Databases page to filter the listed database. Type the name of the database, Oracle server, or the availability group in the search tab to narrow down on the database that you want to select.
  5. On the Restore Database page, click Snapshot Restore.
  6. Click the timestamp drop-down list to list the available snapshots to restore databases from.
  7. Select the required snapshot, and then in the Database Files section select the database or database elements that you want to restore.
    Snapshot-Select elements1.png
  8. Click Restore.
    Note: If a backup job for the database selected for snapshot restore is already running, Druva prompts a message to cancel the backup job and trigger restore. 
  9. If you selected the database check box, Druva provides the following two restore target options to restore the complete database.
    RestoreSnapshot.png 
    1. Automatically restore and recover the original database:  Allows you to restore the complete database automatically to the original Oracle server from where it was backed up. Provide the following details and click Finish:
      Field Description
      #RMAN Channels The number of channels to be established between RMAN and the databases to be restored. The default value for the number of channels is set to ‘4’. Druva recommends you to specify a maximum of 32 RMAN channels. For more information about RMAN Channels, see About RMAN Channels.
      Restore and recover Wallet Files For wallet files, select the Restore and recover Wallet Files checkbox if you want to restore the wallet files. If you select this checkbox, and if there is an existing wallet directory at the restore location, it is renamed and a new directory is created with the restored wallet files, thereby retaining the existing wallet files for future reference.
      Note: The Restore and recover Wallet Files checkbox is visible only if you have wallet files.
      Destination Target This field is visible for standby databases only. To restore data from a standby database, provide the destination target where you want to restore the database. You can restore to a standby or primary database.
      Notes: 
      • To restore on a primary database, make sure the primary database is registered and authentication is assigned to it. Also, after assigning authentication, perform discovery.
      • After restoring to a standby database, the Database Administrator must make sure the standby database is in sync with the primary database to avoid discrepancies in the data.
       Druva prompts you with a warning message that the original database on your Oracle server will be replaced with the restored data. Click Yes on the confirmation dialog.

Druva terminates connections to the database on the original server host and then replaces the database with the restored database.
For wallet files, select the Restore and recover Wallet Files checkbox if you want to restore the wallet files. If you select this checkbox, and if there is an existing wallet directory at the restore location, it is renamed and a new directory is created with the restored wallet files, thereby retaining the existing wallet files for future reference.

b. Restore database files: Allows you to download the requested database files to the selected server and location. The database needs to be manually recovered on the server. For more details, see Recover database from the downloaded backup data.
Provide the following details and click Finish:

Field Description
Destination Server The Oracle server host to download the backup data to. By default, the original Oracle server host is selected where the database was backed up. When you restore a database to its original location, Druva replaces the database on the Oracle server host with the restored database.
Restore Location The location on the selected server where you want to download the backup data or type the absolute path to the restore location.

 

  1. If you selected check box(es) of the individual database element(s) to restore, Druva provides only the Restore database files option to download the requested database files to the selected server and location. The database need(s) to be manually recovered on the required server.
    Restore_manual1.PNG

The backup database is downloaded to the location you specify. After you click Finish, Druva generates a restore job. You can track the progress of the job by viewing the progress log. For more information, see View progress logs.

Next Steps

The DBA can run RMAN scripts to fetch backup data downloaded to the restore location and recover the database on the required Oracle server host. For more information, see Recover database from the downloaded backup data.