Restoring an Oracle Online Backup to a New Host (Cross-Machine Restore) with a New Directory Structure
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.
You can restore a database that is in ARCHIVELOG or NOARCHIVELOG mode.
Before You Begin
- Perform a full backup of an online subclient.
- Copy the init<SID>.ora file or the spfile<SID>.ora file from the old host to the new host.
- On the new host, edit the init<SID>.ora file or the spfile<SID>.ora file to change the path for control files, archive log destination, and *dump destinations.
- On the new host, create the directory structures for all the paths defined in the init<SID>.ora file or the spfile<SID>.ora file.
- Configure the Source and Destination Hosts for Cross-Machine Restores.
- From the CommCell Browser, expand Client Computers > client > Oracle.
- Right-click the instance, point to All Tasks and then click Browse and Restore.
- Select Latest Backup and click View Content.
- Optional: Use non-default Browse and Restore options. See Browse and Restore.
- In the Browse view, select the database to restore in the right pane and click Recover All Selected.
- On the General tab of the Restore Options dialog box:
- From the Destination Client list, select the name of the client computer.
- Select the Restore Control File check box.
- Click Advanced.
The Advanced Restore Options dialog box appears.
- When the database is in NOARCHIVELOG mode, on the Options tab, select the No Redo Logs check box.
- Optional: Select the restore options.
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.
Open the database after the restoreAfter a restore, set the SnapProtect 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 NORESTLOGS 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 Re-do Logs, RMAN restores the data from the incremental backup and not the archived redo logs.
On the Options tab, select the No Re-do Logs check box.
Prevent RMAN failovers to the previous backup for Oracle 10g databases or higherSelect 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 restoreValidation 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.
Configuring Pre- and Post-ProcessesRun 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 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.
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 generated from the selected options. For more information, 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.