Enterprise Workloads Editions: ✅ Business ✅ Enterprise ✅ Elite

As an administrator, you can recover databases from the warm recovery points that are stored in the Druva Cloud and cold recovery points stored in the AWS glacier. You can restore a complete database automatically either to the Original Oracle server or to an alternate server. You can also 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 recovery point 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 recovery point 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 recovery point from the recovery points drop-down list. The list displays the timestamp of all the recovery points 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

While restoring to an alternate server:
1. Make sure you have registered an alternate server with version 6.1.0 or later.
2. Make sure you have the SYSDBA/SYSBACKUP permission.
3. If you want to restore a database from ASM to an ASM storage, make sure that you select the Restore SP File check box. Also, make sure that you have configured ASM on the target server and the path variables such as Oracle Home and Oracle Base of the source and target server are same.
4. While restoring wallet files, make sure the user, group, and their respective permissions are the same on the source and the destination servers.
  Also, make sure that the Oracle user on the destination server has access to the wallet location.
For automated restore of RAC databases, make sure that the directories of the following files are present on the shared storage (ASM):

Server Parameter file
Control File
Archive log files

We can then restore these files from the recovery points.

Procedure

Log in to the Management Console.
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.
In the left navigation pane, click Configured Databases.
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.
On the Restore Database page, click recovery point Restore.
Click the timestamp drop-down list to list the available recovery points to restore databases from.
Select the required recovery point, and then in the Database Files section select the complete database or database elements that you want to restore.
Click Restore.

📝 Note
If a backup job for the database selected for recovery point restore is already running, Druva prompts a message to cancel the backup job and trigger restore.

The following screen is displayed:

If you choose to restore the complete database in Step.7, you can restore the selected database either automatically or manually. If you choose to restore individual database elements, you can restore them manually only.
To restore database automatically, select either of the following options:
1. Automatically restore and recover the original database: Select to restore the complete database automatically to the original Oracle server from where it was backed up. Provide the following details and click Finish:
  - #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.

b. Restore to alternate standalone instance: Select to restore the database to a standalone instance. Provide the following details and click Finish.

Field	Description
Destination Target	The target Oracle server where you want to restore the database. 📝 Note You can perform an automated alternate restore to an alternate server with version 6.1.0 later only.
Restore SP File	Select to restore the SP File. 📝 Note If you select this field, make sure that the source and the target server are the same in terms of the directory structure, memory configuration, and so on. If not, you can specify values for fields such as Oracle Home, Oracle Base, custom SP file parameters, and restore location from the Console. In this case, these values overwrite the values mentioned in the original SP file, while retaining all other values.
Restore location	The location on the selected server where you want to restore the database or type the absolute path to the restore location. By default, Oracle base is used as the restore location.
Oracle Home	The directory structure where the Oracle database is installed.
Oracle Base	The directory structure of the location where Oracle software and configuration files are stored.
Other Server Parameters	The list of custom SPFile parameters that can be used for the restored database. Provide the parameters in the `<parameter=value`> format. For example, open_cursors=300. In case of multiple custom parameters, provide each parameter on a new line. For example: <parameter1=value1> <parameter2=value2> . . <parametern=valuen> To restore a standalone database to an alternate server using an ASM storage, pass the following parameters in the Other Server Parameters field: db_create_file_dest=+Data log_archive_dest=+Data/<sourceDBName> Where <sourceDBName> is the name of the database that you want to restore to an alternate server. 📝 Notes The Other Server Parameters field is visible only if you have upgraded the agent to version 6.1.1 or higher. The following SPFile parameters will not be overwritten even if you pass custom values from the user interface: Db_name Undo_management Enable_pluggable_database If the compatible parameter is set on the source database and you pass another value through Other Server Parameters , the compatible parameter will not be overwritten by this new value on the restored database. Make sure the parameter value does not contain “=”.
#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.
Restored Database Name	The name of the database that is to be restored to an alternate server. ❗ Important For automated restore to an alternate server, Druva first restores the database to an alternate server with the source database name. Once the database is successfully recovered and opened, Druva changes its name to the target database name. Do not provide $ or # in the restored database name, else the restore fails.
Restore Wallet Files	Select to restore the wallet files. If you select this checkbox, a new directory is created for wallet files. If the wallet directory exists already, the existing wallet files are retained for future reference, and new files are downloaded in the directory. 📝 Notes The Restore and recover Wallet Files checkbox is visible only if you have wallet files. While restoring the database to an alternate server, for restoring wallet files, make sure the user, group, and their respective permissions are the same on the source and the destination server. Also, make sure that the Oracle user on the destination server has access to the wallet location.

For more information about restoring to an alternate server, see Restore database to an alternate server.

10. To restore the complete database or individual database elements manually, select the Restore database files checkbox. 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 database files are downloaded 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.
The backup database is downloaded to the location you specify. After you click Finish, restore prechecks are run and 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.
You can view the details of the completed job on the Audit Trails page. For more information, see View Admin Audit Trails page .

About restore of Oracle Databases
Restore database to an alternate server
Restore databases to a point-in-time
Recover database from the downloaded backup data

Related keywords

recoverpoint, recovery point

Oracle database restore workflow

About restore of Oracle Direct to Cloud Servers

Restore an Oracle database to a point-in-time

Manage Oracle databases

Restore databases using PBS

Before you begin

Procedure

Next Steps

Related articles

Related keywords