Backup Exec integrates with RMAN, an Oracle utility that does the following:
To restore SAP data using RMAN, the Backup Exec Oracle Agent is required, and the Remote Agent Utility must be run first.
See About the Remote Agent Utility for Windows Systems.
You must modify the rman_send parameters in the Init<SID>.sap file as follows:
rman_send = ( "channel sbt_1 'NBBSA_SAP_AGENT_CONFIG_PATH=<INI file Path>'")
where <INI Path > is the full path for the biparam.ini. For example: C:\oracle\ora92\database\biparam.ini.
See Configuring biparam.ini for the SAP Agent.
Ensure that the ini file path mentioned in the parameter ‘util_par_file’ in the init<sid>.sap is the same path specified in the rman_send command.
For restores done using RMAN, Symantec Backup Exec does not honor the configuration parameter (-r option) passed from BRBACKUP or BRRESTORE.
Update init<SID>.ora as follows:
control_file_record_keep_time <n>, (say n = 45)
This parameter controls the minimum number of days that a reusable record is kept in the control file.
When BRRESTORE is used to run full restores via RMAN, the database should be in mount state.
The command for restoring database files only is as follows:
brrestore -d rman_util -b last -m full
For restoring the control files, use the -m 0 [,00] option
For example, to restore the .ctl files type the following on the command line:
brrestore -d rman_util -b last -m 0
To restore the .dbf files, type the following on the command line:
brrestore -d rman_util -b last -m 00
When restoring with RMAN, make sure that the media server specified in the biparam.ini file is the media server on which the backup job was done.