Backing Up Oracle - Computing at Cornell

4.8 Node considerations
A TSM client program must authenticate to the TSM server using a previously
defined node. A TSM client can be a backup-archive client or an API client.
There may be more than one TSM client on a single machine.
We strongly recommend registering a dedicated node for the Oracle backups
that is separate from the node that is used with the backup-archive client.
If you have a separate policy domain for Oracle backups, this is required,
since a node can only belong to one domain.
When registering a node, be sure to specify the following parameters:
NODENAME
PASSWORD
BACKDELETE
MAXNUMMP
DOMAIN
4.8.1 Choosing a nodename
The TSM backup-archive client defaults the nodename to be the hostname of
the machine. We chose to register separate nodes for the Oracle backups,
and we used the naming convention of hostname_oracle.
4.8.2 Choosing a password
This password will be used with the aobpswd command to encrypt the
password for future use when PASSWORDACCESS is set to GENERATE
with TDP for Oracle for Windows. With TDP for Oracle for UNIX,
PASSWORDACCESS is set to PROMPT; however, the aobpswd command
generates an encrypted password in the TDP directory, which accomplishes
the same purpose.
4.8.3 Setting the BACKDELETE option
The node that is used to backup the database objects to TSM must be able to
manually delete the backup objects. To do so specify BACKDELETE=YES
when registering the node. You can update a node that has this value set to
NO and set it to YES with the update node command.
If this value is set to NO, RMAN will not be able to manually inactivate the
Oracle backup objects, and they will reside in TSM storage forever.
52 Backing Up Oracle using Tivoli Storage Management