Skip to main content

How can we help you?

Druva Documentation

Restore an Oracle database to a point-in-time

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

 

When Oracle databases run in the ARCHIVELOG mode, the databases make copies of all online redo logs after the databases are filled. Druva backs up such archive logs, and you can use it to restore your databases to any point-in-time between the available range of the archived logs. It is a useful, lightweight approach to backup and restore. Archive log backups are incrementally triggered after a full backup job has completed, and a restore point exists. The archive log is backed up every few minutes based on your settings. 

Druva uses the restore point and the archive logs that were logged, to perform a point-in-time restore. When you restore the database using archive logs, databases are restored to the nearest, last available committed transaction before the specified point-in-time. 

You can choose to restore all database files or select 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 initiate a restore operation, the backup data is downloaded to the requested 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.  For more information, see Recover database from the downloaded backup data.

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 Point-in-Time Restore.
    SBTRestorePIT1.PNG
  6. In the Select Date and Time section, the Available Time Range section displays all available snapshots with the daily retention.
  7. Specify a date and time to which you want Druva to restore the databases. Click the Calendar icon to select a date of the restore point and select the restore point from the available range of restore points for the selected date. The timestamps of the archive logs are displayed according to the Oracle server time zone. For example, the timestamps for servers located in New York and London are displayed according to EST and UTC time zones, respectively.
    Databases will be restored to the last available committed transaction before the specified point in time.
  8. Click Show Databases.
    The Databases section displays all the available databases for restore based on the selected date and time.
  9. In the Database Files section, select the database or individual database elements that you want to restore.
  10. 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.
  11. If you selected the database check box, Druva provides the following two restore target options to restore the complete database.
    RestorePIT.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.
      On clicking Finish, 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.
    2. 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
      .Restore_manual1.PNG

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.

The backup data 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

After the restore job is successful, 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.