Backing Up Oracle - Computing at Cornell

A TSM administrator also uses an administrative client to administer the TSM
server. Typical tasks include backups of the TSM database, adding additional
storage to storage pools, daily monitoring, and managing authorization.
4.4 TSM server base functionality explained
The TSM server base functionality is to provide storage and retrieval of data
objects (that is, files, directories, databases tables, and so on).
In order to store and retrieve objects at an application level, the application
needs to provide native support for TSM. Or a TDP product needs to interface
between the application and the TSM API. (See Figure 8.)
Figure 8. Native support or Tivoli Data Protection interfacing with the TSM API
There are three basic steps that must take place before you can use the TSM
server. These steps will be covered in greater detail in subsequent chapters:
1. Register a node with the TSM server.
2. Install the TSM client (backup-archive client, TDP or API client).
3. Configure the TSM client.
Following is a brief look into why these steps are necessary.
4.4.1 Registering a node with the TSM server
Before a TSM client can use the storage services of a TSM server, it must
first authenticate to the TSM server using a nodename and password. A node
is created by the TSM Administrator using the REGISTER NODE command.
When the node is registered, it is given six key values that play an important
role for performing backups and restores. NODENAME, PASSWORD,
DOMAIN, ARCHDELETE, BACKDELETE, MAXNUMMP.
These values are explained in 4.8, “Node considerations” on page 52.
Chapter 4. TSM server considerations 35