Restore Data - Oracle or Oracle RAC - Full System Restore

Topics | How To | Full System Restore | Troubleshoot | Related Topics

Overview

Full System Restore Considerations

Perform a Full System Restore

Overview

The difference between a normal restore and a full system restore is the severity of the problem. Normally, if data is lost or removed, it is recovered from the archives using the normal restore procedures. However, when a normal restore operation cannot correct a software and/or hardware corruption problem, some additional changes may be required.

The level of system restore required may be different as described below.

• When the database is corrupted and a restore is required, both the application software and database must be restored. This can be achieved by performing the following steps:
  • Restoring the application by using the file system iDataAgent restore options.
  • Restoring the database files using the restore options in the iDataAgent.
• When the client system (operating system, hardware, hard drives, etc.) is damaged or destroyed, a full system restore may be required.

Full System Restore Considerations

• When recovering an Oracle or Oracle RAC database with flashback enabled, make sure to disable the flashback option prior to recovery of the database, or else the recovery operation may fail. To disable the flashback, do the following:

  1. Restore the control file and the database using the CommCell Console.
  2. Start the database in MOUNT mode and disable the flashback option using the command:

     alter database flashback off

  3. Continue the recovery of the database from the CommCell Console.

Perform a Full System Restore

The following procedure demonstrates how to perform a full system restore when the client system is damaged or destroyed. The procedure assumes the following:

• That the latest file system and Oracle backups are available.
• That the file system backup does not include the Oracle database files. (This is achieved by establishing a backup filter for .dbf files in the appropriate file system subclients.)
• That the recovery catalog is available on a separate machine. If the recovery catalog is on the same machine, you should have:
  • Exported the user, who is the owner of the recovery catalog using the Oracle export command to an external flat file.
  • Included this external flat file in your file system backup.
• That the subclient used for backing up the entire database had the Resync Catalog option selected in the Subclient Properties (Backup Arguments) tab.

To perform a full system restore:

1. If necessary, rebuild the hardware as it existed before.
2. Perform a full system restore of your file system to rebuild your operating system and application files, using the procedures in the online help for the appropriate file system. In addition to restoring your operating system, this operation will restore the Oracle application files and the Oracle iDataAgent software (if applicable).
3. Reboot the machine.

   If there are any problems with the Oracle iDataAgent software, we recommend that you un-install and re-install the software in the same drive as it was previously installed. Use the same installation parameters, passwords, and backup type settings as were previously used.

4. Perform the following steps if the recovery catalog is on the same machine that you are rebuilding:
   • Create the recovery catalog database as it existed before the crash.
   • Create the user (who was the owner of the recovery catalog) with the same user privileges that existed for the user.
   • Import the user (which was exported to a flat file and was backed up as a part of the file system) using the Oracle import command.
5. Start the database in the NOMOUNT mode.
6. From the CommCell Browser, right-click the instance that contains the database you want to restore and recover, select All Tasks and then click Restore.
7. From the Oracle Restore Options (General) dialog, select the following options:
   • Select the client computer with the database that you want to restore in the Destination Client list (if it is not already selected).
   • Select the Restore Control File option.
   • Select the Restore Data and Recover options.
   • Select the entire database in The Latest Database View pane (if it is not already selected).
   • Verify that the Status of the database is displayed as STARTED; if necessary click on the Refresh button to refresh the status.
   • When restoring encrypted data, refer to Data Encryption.
8. Click on the Advanced button and verify the following options are selected in the appropriate tab of the Oracle Advanced Restore Options dialog box:
   • Click the Control and SP Files tab and ensure that the Restore Control File option is selected.
   • Click the Restore tab and ensure that the Restore Data and From the Latest Backup options are selected.
   • Click the Recover tab and ensure that the Recover and Current Time options are selected.
9. Select or specify any additional options in the Oracle Advanced Restore Options dialog box, then click OK.
10. Click Job Initiation tab and select the appropriate option to begin or schedule the restore, then click OK.
11. Once the job begins, the system will perform a full restore of the selected data, and you can track the status of the job in the Job Controller.
12. After the database is restored, perform a full backup of the Oracle database to ensure the existence of the current state.

Back To Top