Detailed description of Oracle disaster recovery using Backup Exec

Shutdown database (do not use shutdown abort to force shutdown), implement a file-level backup, back up all Oracle related files, including Windows system files, system status and Oracle program files and data files. This cold backup is critical for quick recovery of the Oracle database system. Without it, the system can only be reinstalled and restored after it is damaged, which is much slower and more complex than direct recovery of cold backup. This cold backup should be re-created whenever the physical or logical structure of the database or form changes.

1. full closed backup:

Shutdown database (do not use shutdown abort to force shutdown), implement a file-level backup, back up all Oracle related files, including Windows system files, system status and Oracle program files and data files.

This cold backup is critical for quick recovery of the Oracle database system. Without it, the system can only be reinstalled and restored after it is damaged, which is much slower and more complex than direct recovery of cold backup.

This cold backup should be re-created whenever the physical or logical structure of the database or form changes.

2. full online backup:

This Backup should be completed through Backup Exec Agent for Oracle Server. to back up all tablespaces, archive logs and control files, Oracle will write all the cached content to the file after Backup, archive the online redo log, so the database backup contains the real-time information of the database during backup, which is complete and effective. You can restore the status of the last full online backup later.

Recovery Process:

1. reinstall Windows and Remote Agent for Windows Server to prepare the environment for restoring the Oracle Server.

2. Restore the last full closed backup and restart the computer. In Windows, the Oracle database system is complete, but the Oracle database may not be the latest data. Backup Exec Agent for Oracle Server does not need to be re-installed.

3. Use SQLPlus to connect to the database system as sysdba and close the database. Shutdown immediate + <enter>

4. Use the Media Server to Restore the latest full online backup. Make sure that the "Restore over Existing files (overwrite Existing files)" option is selected in the advanced options for restoring job properties.

To recover the database successfully, all redo logs after the last full closed backup must have been archived and backed up. If the database is missing, the database cannot be restored to the status of the last full onli ne backup.

The alert log of Oracle shows the archive logs required for database recovery and where you should restore them.

5. After the restoration is complete, use the SYS user to connect to the database as sysdba and load the database to the mount stage: startup mount + <enter>.

6. After the database is mounted, execute the recover process: recover database using backup controlfile + <enter>.

The database prompts you which logs are required:

ORA-00279: Change 36579 generated at needed for thread 1ORA-00289: Suggestion : \Oracle_Home\Oradata\\%SID%T00036579.ARCORA-00280: {=Suggested | filename | AUTO | FROM logsource | CANCEL}

1 2 Next Page

[Content navigation]
Page 1: Recovery Process	Page 1: Automatic Recovery