Backing Up Oracle - Computing at Cornell

9.7.3.1 Coexistence of backup-archive client and TDP for Oracle
When using the incremental command of the backup-archive client, you
should exclude the database objects that are backed up using TDP for
Oracle. While the database is running, you will not get a consistent backup
using the backup-archive client.
In our environment, all the files that were backed up using TDP for Oracle
where in the c:\oracle\oradata directory. To prevent them from being backed
during a full incremental backup, we added an exclude.dir statement to the
dsm.opt file:
exclude.dir c:\oracle\oradata
To prevent those files from being backed up with a selective command, we
also added this statement:
exclude c:\oracle\oradata\...\*
You may wish to use additional exclude statements to prevent other files from
being backed up during your incremental backups. However, you should
consider using an include statement to back up Oracle.ORA files
(tnsnames.ora, init.ora, etc..) These files would make a disaster recovery
restore much easier:
include c:\oracle\admin\...\*.ora
include c:\oracle\ora81\...\*.ora
After making these changes, our resulting dsm.opt file looked like this:
COMMMETHOD TCPIP
TCPSERVERADDRESS 193.1.1.11
TCPPORT 1500
NODENAME JAMAICA
PASSWORDACCESS GENERATE
exclude.dir c:\oracle\oradata
include c:\oracle\admin\...\*.ora
include c:\oracle\ora81\...\*.ora
exclude c:\oracle\oradata\...\*
With these include/exclude statements, the Oracle database files will not be
backed up in the TSM backup-archive client incremental.
152 Backing Up Oracle using Tivoli Storage Management