How to Restore And Recover Oracle Backups Using NMC Recovery Wizard (NMDA)

Discover the streamlined process of restoring and recovering Oracle backups using the NetWorker Management Console (NMC) Recovery Wizard. Ensure you meet all prerequisites, including NetWorker nsrauth authentication and the creation of the NetWorker Client resource. Learn how to manage the recovery options and perform the recovery efficiently. Whether you’re restoring to a duplicate or original database, this guide covers all the necessary steps for a successful Oracle recovery with NMDA. For more Information, check our Knowledge Base click here. For Oracle Documentation click here.

Hello and welcome to the Dell Technologies How to Video series. In this video we will review how to perform an Oracle restore using the NMC Recovery Wizard. The NMC Recovery Wizard provides a NetWorker data zone with a centralized recovery method for NMDA, Oracle backups, file system backups, and more.

Although it is possible to perform various different types of Oracle restores using the NMC Wizard, in this video we will be illustrating how to perform or restore back to the original source location and most current point in time. Before you start, ensure that the Oracle Client has performed backups and that these backups are in a browsable state. Although not mandatory, it is recommended that the client was previously created using the NMC Wizard and finally the Oracle database should be in the appropriate mount mode as per Oracle documentation here.

We can see that we have connected to our database that we wish to restore, and the database has been placed in the appropriate mount mode before starting our restore operation. Please refer to Oracle documentation for further assistance on this part. Next, you can view the Oracle backups that are available to the NetWorker server by selecting Media, Save Sets and then filtering on the Oracle client in question.

You can filter based on additional criteria such as save time. Here you can see a list of Oracle backup pieces that are available for the restore and their corresponding status which is browsable. This is necessary for the restore to be successful. To initiate the restore, go to the protection tab, client, right click on the client in question and select Recover. Next, You’ll be prompted with a series of slides to specify the different restore type you wish to perform. Here we’re going to be selecting to recover the database back to the original host and a restore type of Oracle application type.

In this slide we specify the various different Oracle variables necessary to connect to the Oracle database, such as Oracle HOME and the credential method we’re going to use to connect to our target database. Here we’re going to select Oracle OS Authentication. Thus, we specify the OS username and the Oracle SID. We’re going to choose to select the entire database for restore and select next. Here you can see a list of all the tablespaces that are part of the database backup previously done.

Since our database is already in the necessary mount mode, we can select No here. Next, this slide allows you to relocate the database files to a different directory other than where they were backed up from. However, we will select the default location to restore the database back to its original location. Here you can have the opportunity to specify the degree of parallelism for the number of restore channels that you wish to allocate.

We’ll also select to open the database after the recovery is completed. You can also see the different restore type points that you can select. We’re going to recover the database to the most current point in time available based on our backups. Additional recovery options are possible such as diagnostic destination and debug level. Here you can see that the summary of the RMAN script that will be generated based on the previously selected choices in the various slides. Here you can see that there’s four channels being allocated, and the database will be restored, then recovered and then finally database will be opened.

This slide allows you to specify from a particular media pool should the Oracle backup exist in multiple different pools. For example, if the backup was performed on one backup pool and then it was later cloned, the backup would exist in two different media pools. This slide allows you to specify from which media pool you wish the restore to be taken from. We’re going to allow NetWorker to make the decision of the required volumes used for the recovery. Next, you give the recovery a name and you can choose to start the restore immediately or specify a scheduled time later on. We’re going to go ahead and start it off now. Now, based on the size of the database backup previously performed, the restore could take several minutes to several hours based on the size of the database.

In our example, the database was only a few gigabytes, so the restore should take a relatively short period of time. Here you can see that there are four channels being allocated for our restore based on the RMAN script generated and the restorer begins to read the data from the NetWorker server. You could select Finish here although the restore is still running, and then you can come back to the recovery tab up top and view the progress and the status of your currently running restore by double clicking the currently running restore. As you can see here, the restore is still executing. Moving forward a little bit, you can see here now that the restore has completely finished and the recovery has applied all necessary transaction logs and the database was put into open mode as from our previous selection in the wizard. You can also review that by connecting to the Oracle database from the command line. Our database is once again in an open status.

Thank you for viewing this video.