Backing Up Oracle - Computing at Cornell

The following is an explanation of the command and its parameters:
essorcb
This is the TDP for ESS backup executable for the backup machine.
TSM node name of the production machine
Because the nodename was not explicitly specified in the dsm.sys of
production machine, it defaulted to the hostname. In our case the
production machine’s node name is auckland.
temporary file name
The backup process restores the temporary file created the backup
process in the production machine on the files specified by this parameter.
We kept the temporary file name the same as the one in the production
machine. In our case, this is /tmp/tokyotmp.
From our observation, the backup process basically performs the following:
1. Makes the FlashCopy volumes and filesystems available to the operating
system
2. Restores the temporary file that was created by the backup process in the
production machine
3. Restores the backup script and configuration files
4. Restores the controlfile
5. Performs an RMAN offline backup of the database to TSM
6. Removes the filesystems and devices from the operating system
It also appears that the admin/tokyo branch was recreated on
ORACLE_HOME or ORACLE_BASE when restoring the backup script and
configuration file (inittokyo.ora). It is therefore recommended that
ORACLE_HOME or ORACLE_BASE exists in the backup machine before
running the backup command.
Here we encountered problems as mentioned in E.3.1.3, “TDP for ESS setup”
on page 233. We recommend using the trace file to determine the cause of
the problem. Remember to turn off tracing later.
E.3.3 TDP for ESS testing
In this section we discuss the tests we have made for backup and recovery.
Appendix E. TDP for IBM ESS for Oracle databases 239