Perform a cross-machine restore when the original database host has been damaged or destroyed, and you need to restore the data to a different host from the backup.
By default, the database is restored to the same location from where it was backed up. When the database is restored, it is recovered to the current time.
The destination instance can be the same SID as the one in the backup, or a new SID (cross-instance). If you want to restore to a new SID, then the destination client must be different from the source client.
When you restore to a new destination, you can configure the software to mask the data on the destination. For more information, see Oracle Data Masking.
If you are restoring from a lower version of Oracle to a higher version, use the STARTUP UPGRADE command. After STARTUP UPGRADE, refer to the Oracle documentation for detailed instructions.
Before You Begin
-
Configure the Source and Destination Hosts for Cross-Machine Restores.
-
If you are restoring to a new instance, see Configuring the Source and Destination Instance for Cross-Instance Restores.
-
Place the database in NOMOUNT mode, or select the Switch Database Mode for Restore check box (Options tab).
-
The Commvault software moves the database to the correct mode before the restore.
-
Optional: When the backup pieces are unknown to the RMAN repository, catalog the backup pieces. For more information, see Cataloging RMAN Backup Pieces.
-
Optional: To mask the data, create a masking policy. For more information, see Managing Oracle Data-Masking Policies.
Procedure
Restore to the Same Oracle SID
-
From the CommCell Browser, go to Client Computers > client > Oracle.
-
Right-click the instance, then go to All Tasks > Browse and Restore.
The Browse and Restore Options dialog box appears.
-
Select Latest Backup, and then click the View Content button.
-
Optional: Use non-default browse and restore options. For more information, see Browse and Restore.
-
Select the database, and then click the Recover All Selected button.
The Oracle Restore Options dialog box appears.
-
Click Restore out of place, and then click Next.
The Oracle Out of Place Restore Options dialog box appears.
-
On the General tab, from the Destination Client list, select the name of the client computer.
-
Select the Restore Control File check box, and then click Advanced.
The Advanced Restore Options dialog box appears.
-
Optional: Have the Commvault software mask the data on the destination. Click Advanced.
-
On the General tab, select the Mask Sensitive Data check box.
-
From the Data Masking Policy list, select the policy that the software uses to mask the data.
-
-
When the database is in NOARCHIVELOG mode, on the Options tab, select the No Redo Logs check box.
-
Set the database ID. On the Options tab, select the Set DBID check box.
-
Optional: Select the restore options.
Restore from a copy precedence
If the backup is corrupted, restore from a storage policy copy instead of the backup.
For more information on modifying the copy precedence of a storage policy copy, see Copy Precedence.
On the Copy Precedence tab, select the Restore from Copy Precedence number check box and enter a copy precedence number.
Have the Destination DBID Be Different from the Source DBID
When you select this check box, the software changes the destination database DBID after a cross-machine restore.
On the Options tab, select the Change DBID check box.
Open the database after the restore
After a restore, set the Commvault software to automatically open the Oracle database. When the database is open, it records transactions.
On the Options tab, select the Open DB check box.
Reset the database and logs.
By default, the database is automatically set to open, and the logs are reset.
If you reset the logs to an open state, you can then reset the database.
On the Options tab, select the Reset Database check box and one of the following Reset Log options:
-
To open the database without the RESETLOGS option, select None.
-
To open the database with the RESETLOGS option, select Yes.
-
To open the database with the NORESETLOGS option, select No.
Perform a point-in-time restore of a database that was backed up in NOARCHIVELOG mode
If the database was backed up in NOARCHIVELOG mode, enable the redo logs.
When the no redo log is disabled, RMAN searches archived redo logs after applying the incremental backup data during a restore. When you set No Redo Logs, RMAN restores the data from the incremental backup and not the archived redo logs.
On the Options tab, select the No Redo Logs check box.
Prevent RMAN failovers to the previous backup for Oracle 10g databases or higher
Select this option if you want to increase the speed.
During restore operations, RMAN automatically looks for another copy of the backup file under the following circumstances:
-
A backup piece is corrupted or deleted
-
A MediaAgent is offline
-
A block in the backup is corrupted within the latest full backup
If another copy is not available in the other copy, RMAN uses an older version of the file. When multiple channels are available for the same device type, RMAN automatically retries on another channel and searches all prior backups until it has exhausted all possibilities.
On the Options tab, select the Disable Oracle Channel Restore Failover check box.
Validate the restore
Validation verifies that the backup copies of the data and logs are intact and usable for restores. RMAN simulates the restore job without the media to determine whether the restore can be successfully performed.
When a validate job is complete, you can view the job log files to identify and correct any issues.
On the Options tab, select the Validate check box.
Have the Destination Online Redo Log Location Be Different from from the Source Location
Use this option when you want the online redo log location on the destination to be different from the source location.
On the Redirect tab, in the Redirect Online Redo Logs box, type the path to the location where the software creates the online redo logs for a cross machine restore.
Configuring Pre- and Post-Processes
Run scripts before or after the restore.
Enter the full path for the pre-recovery and post-recovery script.
You can choose to run the post-process script even if the restore job failed. You can use the post-process script to bring a database online or to release a snapshot.
To pass the database instance name to the script, see Passing the Instance Name to Pre and Post Scripts for Databases.
On the Pre/Post tab:
-
In the Pre-Recovery Command box, type the full path name for the script.
-
In the Post-Recovery Command box, type the full path name for the script.
-
To run the post recovery process regardless of the job's outcome, select the Run Post Process for all attempts check box.
-
In Windows configurations, specify the user that runs the process, in the Pre/Post Impersonation section, select one of the options:
if the local account has permission to execute the processes on the destination client, select the Use Local Accounts option.
To impersonate another user with permission, select the Impersonate User option and enter the credentials.
Restore from a specific backup
On the Restore tab, select the By Tag check box and enter the tag.
-
-
Click OK to close the Advanced Restore Options dialog box.
-
Optional: View or customize the RMAN script that is automatically generated from the selected options, see Viewing Oracle Restore RMAN Scripts and Customizing Oracle Restore RMAN Scripts.
-
Click OK to close the Restore Options dialog box and start the restore.
After the restore optionally recover the database to a different time.
Restore to a Different Oracle SID
-
From the CommCell Browser, go to Client Computers > client > Oracle.
-
Right-click the instance, then go to All Tasks > Browse and Restore.
The Browse and Restore Options dialog box appears.
-
Select Latest Backup, and then click the View Content button.
-
Optional: Use non-default browse and restore options. For more information, see Browse and Restore.
-
Select the database, and then click the Recover All Selected button.
The Oracle Restore Options dialog box appears.
-
Click Restore out of place, and then click Next.
The Oracle Out of Place Restore Options dialog box appears.
-
On the General tab of the Restore Options dialog box:
-
From the Destination Client list, select the name of the client computer.
Note
The destination client must be different from the source client (the client where you performed the backup).
-
From the Destination Instance list, select the new instance on the destination.
-
Select the Restore Control File check box.
-
Click Advanced.
The Advanced Restore Options dialog box appears.
-
-
Optional: Have the Commvault software mask the data on the destination. Click Advanced.
-
On the General tab, select the Mask Sensitive Data check box.
-
From the Data Masking Policy list, select the policy that the software uses to mask the data.
-
-
When the database is in NOARCHIVELOG mode, on the Options tab, select the No Redo Logs check box.
-
Optional: Select the restore options.
Restore from a copy precedence
If the backup is corrupted, restore from a storage policy copy instead of the backup.
For more information on modifying the copy precedence of a storage policy copy, see Copy Precedence.
On the Copy Precedence tab, select the Restore from Copy Precedence number check box and enter a copy precedence number.
Set the Oracle Database ID
The Oracle DBID is an internal, uniquely generated number that distinguishes the target database from the rest of the databases with the same name, in the recovery catalog. Oracle creates this number automatically when you create the database.
You can use this option when:
-
There is no control file and you need to restore the control file or SP file from the autobackup
-
Multiple databases exist in the recovery catalog and you need to restore the control file
On the Options tab, select the Set DBID check box.
Have the Destination DBID Be Different from the Source DBID
When you select this check box, the software changes the destination database DBID after a cross-machine restore.
On the Options tab, select the Change DBID check box.
Open the database after the restore
After a restore, set the Commvault software to automatically open the Oracle database. When the database is open, it records transactions.
On the Options tab, select the Open DB check box.
Reset the database and logs.
By default, the database is automatically set to open, and the logs are reset.
If you reset the logs to an open state, you can then reset the database.
On the Options tab, select the Reset Database check box and one of the following Reset Log options:
-
To open the database without the RESETLOGS option, select None.
-
To open the database with the RESETLOGS option, select Yes.
-
To open the database with the NORESETLOGS option, select No.
Perform a point-in-time restore of a database that was backed up in NOARCHIVELOG mode
If the database was backed up in NOARCHIVELOG mode, enable the redo logs.
When the no redo log is disabled, RMAN searches archived redo logs after applying the incremental backup data during a restore. When you set No Redo Logs, RMAN restores the data from the incremental backup and not the archived redo logs.
On the Options tab, select the No Redo Logs check box.
Prevent RMAN failovers to the previous backup for Oracle 10g databases or higher
Select this option if you want to increase the speed.
During restore operations, RMAN automatically looks for another copy of the backup file under the following circumstances:
-
A backup piece is corrupted or deleted
-
A MediaAgent is offline
-
A block in the backup is corrupted within the latest full backup
If another copy is not available in the other copy, RMAN uses an older version of the file. When multiple channels are available for the same device type, RMAN automatically retries on another channel and searches all prior backups until it has exhausted all possibilities.
On the Options tab, select the Disable Oracle Channel Restore Failover check box.
Validate the restore
Validation verifies that the backup copies of the data and logs are intact and usable for restores. RMAN simulates the restore job without the media to determine whether the restore can be successfully performed.
When a validate job is complete, you can view the job log files to identify and correct any issues.
On the Options tab, select the Validate check box.
Have the Destination Online Redo Log Location Be Different from from the Source Location
Use this option when you want the online redo log location on the destination to be different from the source location.
On the Redirect tab, in the Redirect Online Redo Logs box, type the path to the location where the software creates the online redo logs for a cross machine restore.
Configuring Pre- and Post-Processes
Run scripts before or after the restore.
Enter the full path for the pre-recovery and post-recovery script.
You can choose to run the post-process script even if the restore job failed. You can use the post-process script to bring a database online or to release a snapshot.
To pass the database instance name to the script, see Passing the Instance Name to Pre and Post Scripts for Databases.
On the Pre/Post tab:
-
In the Pre-Recovery Command box, type the full path name for the script.
-
In the Post-Recovery Command box, type the full path name for the script.
-
To run the post recovery process regardless of the job's outcome, select the Run Post Process for all attempts check box.
-
In Windows configurations, specify the user that runs the process, in the Pre/Post Impersonation section, select one of the options:
if the local account has permission to execute the processes on the destination client, select the Use Local Accounts option.
To impersonate another user with permission, select the Impersonate User option and enter the credentials.
Restore from a specific backup
On the Restore tab, select the By Tag check box and enter the tag.
-
-
Click OK to close the Advanced Restore Options dialog box.
-
Optional: View or customize the RMAN script that is automatically generated from the selected options, see Viewing Oracle Restore RMAN Scripts and Customizing Oracle Restore RMAN Scripts.
-
Click OK to close the Restore Options dialog box and start the restore.
After the restore optionally recover the database to a different time.