Backing Up Oracle - Computing at Cornell

shark_target_volume
We only used one volume for our test. If your database uses many ESS
volumes for your datafiles, and other Oracle files, you should specify this
parameter for each volume you use.
We initially put in here the serial number of the FlashCopy device,
followed by two dashes (‘- -’). The dashes was updated later with the
source volume serial number, and the size of the volume when the backup
script was run on the production machine.
You must note that the FlashCopy device must be accessible to the
backup machine, but must not be known to the operating system when the
backup process is running. When the backup process starts on the backup
machine, TDP for ESS runs the Configuration Manager and makes the
disks and filesystems known to the operating system, runs the backup,
then removes the file system and disks from the operating system.
We had problems because of this and the errors produced in the trace file
were not that obvious.
Our backup script file as specified in database_backup_script_file in the
production machine looks like this:
run {
allocate channel t1 type 'sbt_tape' parms
'ENV=(DSMO_NODE=auckland,DSMI_ORC_CONFIG=/usr/tivoli/tsm/client/api/bin/dsm.opt,
DSMI_LOG=/orc8/app/oracle/product/815/admin/tokyo/adhoc,DSMO_OWNER=oracle8)';
backup
(database);
release channel t1;
}
Here are some things to note on the backup script:
TDP for Oracle environment variables
The environment variables used by channel t1 are what you would
normally use for TDP for Oracle.
DSMO_NODE
This is the TSM node name to be used to backup the database. This is the
node name for TDP for Oracle and not TDP for ESS.
236 Backing Up Oracle using Tivoli Storage Management