Backing Up Oracle - Computing at Cornell

E.3.2.1 Backup on the production machine
Our backup script in the production machine looks like this:
essorcp /orc8/app/oracle/product/815/admin/tokyo/adhoc/tokyo.ess swiss
/tmp/tokyotmp
The following is an explanation of the command and its parameters:
essorcp
This is the TDP for ESS backup executable for the production machine.
setup filename
This is our setup file:
/orc8/app/oracle/product/815/admin/tokyo/adhoc/tokyo.ess.
TSM node name of the backup machine
Because the node name was not explicitly specified in the dsm.sys of
backup machine, it defaulted to the hostname. In our case the backup
machine’s node name is swiss. This is the TDP for ESS node name and
not the TDP for Oracle node name.
temporary file name
A temporary file is created by essorcp which contains parameters that are
needed by the backup machine to perform its backup. This file is backed
up in the TSM server, and later on transported to the backup machine by
the backup process. We put the temporary file in /tmp/tokyotmp.
From our observation, the backup process basically performs the following:
1. Makes an RMAN backup to TSM of the control files
2. Performs a FlashCopy of the source volumes
3. Backs up the backup script and configuration files to TSM
4. Creates a temporary file
5. Performs backup of the temporary file
E.3.2.2 Backup on the backup machine
We did not use a backup script on the backup machine, We ran our backup
directly on the shell, and the command looks like this:
[root@swiss> /] $ essorcb auckland /tmp/tokyotmp
238 Backing Up Oracle using Tivoli Storage Management