Backup3G/DA-RMAN/User Guide/Searching and Restoring Oracle RMAN Backups

This page was last modified 07:15, 20 January 2012.

From Documentation

< Backup3G(Difference between revisions)

Current revision

Backup3G’s Recovery module lists all the current backups in the media database, including Oracle/RMAN backups.

Searching Oracle/RMAN Backups

You use the backup3G Recovery module to search for Oracle/RMAN backups. You can open a media set to view its contents. However, you must restore the data using Oracle RMAN on the Oracle host.

To launch the Oracle Recovery Manager

From the command line, login as the Oracle user.
Run RMAN with the appropriate connect strings:
rman target /
rman target <user>/<password>
rman target <user>/<password>@<service>
rman target <user>/<password>@<service> catalog <user>/<password>@<service>

Once you are in RMAN, you can list the "backupsets" that RMAN knows about using the LIST command. An RMAN backupset is stored as a single tape-file by backup3G. The name of the backup-piece in RMAN contains the backup3G Set_ID of the media set used for the original backup. For example, the backup-piece 12345/SYSTEM_2_1_772805994 is a backup (or part of a backup) of the SYSTEM tablespace on media set 12345. Note that if you duplicate the media set in backup3G, you can restore from either the original or the copy. Backup3G will choose which ever copy is most appropriate to use, based on its location and media type.

[edit]

Selecting Oracle Backups to Restore

Caution: Don’t restore backups to an online database. Only restore backups to a mounted database otherwise you will get an error and the restore will fail.

Specifying the Tape Drive

To specify that the backup3G tape drive or pool to use for the recovery, you must allocate an RMAN channel, and set the DRIVE environment variable as follows:

allocate channel 'backup3G' device type sbt parms="ENV=(DRIVE=XXXX)";

where XXXX is the name of the drive or drive-pool to use. Note that drive-pool names always end in "@".

You should always ensure that the tape(s) from which you want to restore are in the correct location for the tape drive. For example if the tape drive is in a tape library, then the tapes must also be in the library so that they can be loaded automatically. You may have to "move" the tape(s) to the correct location using the backup3G media window.

To Restore from an RMAN Backup

Once an sbt channel is allocated, specifying the DRIVE, you can perform the recovery using the normal RMAN RESTORE and RECOVER commands. Please refer to the RMAN manual on how to use these commands.

Each RMAN restore will create one or more backup3G recovery jobs. These jobs will be visible in the backup3G monitor window. They can also be controlled (cancelled, tape(s) loaded etc) from backup3G in the usual way, and each job also creates a logfile under backup3G. We recommend that you have a monitor window running while doing a restore via RMAN. If the tape is loaded manually, you will be requested to so from the monitor window.

Previous Section

Next Section

Retrieved from "https://documentation.fs.com.au/index.php/Backup3G/DA-RMAN/User_Guide/Searching_and_Restoring_Oracle_RMAN_Backups"

 <br>
+<p>Once you are in RMAN, you can list the "backupsets" that RMAN knows about using the '''LIST''' command. An RMAN backupset
+is stored as a single tape-file by backup3G. The name of the backup-piece in RMAN contains the backup3G '''Set_ID''' of the
+media set used for the original backup. For example, the backup-piece '''12345/SYSTEM_2_1_772805994''' is a backup (or part of a backup) of the SYSTEM tablespace on media set 12345. Note that if you duplicate the media set in backup3G, you can restore from either the original or the copy. Backup3G will choose which ever copy is most appropriate to use, based on its location and media type.</p>
 == Selecting Oracle Backups to Restore ==