Backing Up Oracle - Computing at Cornell

E.3.3.1 Backup
We performed both backups of the database using normal online RMAN
backups and TDP for ESS backup using the same RMAN backup script. Both
type of backups used the same RMAN catalog database. From the point of
view of RMAN, using TDP for ESS or just TDP for Oracle for our backups is
immaterial. As far as RMAN is concerned, the backups were performed using
‘sbt_tape’ (a media manager), and they are treated the same way.
When using only RMAN to do backup, we use the command as follows using
user oracle8 to perform the backup:
rman target / catalog rman2/rman@rman cmdfile
‘/orc8/app/oracle/product/815/admin/tokyo/adhoc/backup’
When using TDP for ESS backups, we use the procedure as discussed above
in E.3.2, “Backing up the database using TDP for ESS” on page 237. We ran
them from user root.
We also backed up the archive logs without using TDP for ESS. We used user
oracle8 to do the backup. The RMAN backup command looks like this:
rman target / catalog rman2/rman@rman cmdfile
‘/orc8/app/oracle/product/815/admin/tokyo/adhoc/backuplog’
The backuplog file that does the archive logs backup looks like this:
sql 'alter system archive log current';
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 (archivelog like '/orc8/app/oracle/product/815/admin/tokyo/arch/%'
channel t1 delete input);
release channel t1;
}
We also tested the TDP for ESS backup essorcp on the production machine
while updates were ongoing on a USERS tablespace. The FlashCopy phase
was quick. It did slow down the updates for a few seconds during the flash
copy phase, but overall, the impact on the database was very small.
240 Backing Up Oracle using Tivoli Storage Management