|
|
Administrators can register Tivoli Storage Manager clients, Tivoli Data Protection application clients, and HSM clients as client nodes.
When a node is registered, Tivoli Storage Manager automatically creates an administrative user ID with client owner authority over the node. You can use this administrative user ID to access the Web backup-archive client from remote locations through a Web browser. If an administrative user ID already exists with the same name, an administrative user ID is not automatically defined. For more information, see Overview of Remote Access to Web Backup-Archive Clients.
Before a user can request Tivoli Storage Manager services, the node must be registered with the server.
Closed registration is the default. The administrator must register client nodes when registration is set to closed.
Open registration allows the client nodes to register their node names, passwords, and compression options. On UNIX systems, only the root user can register a client node with the server.
With either registration mode, by default, an administrative user ID with client owner authority is created over the node.
To add a node with closed registration, an administrator uses the REGISTER NODE command to register the node and specify the initial password. The administrator can also specify the following optional parameters:
To add a node with open registration, the server prompts the user for a node name, password, and contact information the first time the user attempts to connect to the server. With open registration, the server automatically assigns the node to the STANDARD policy domain. The server by default allows users to delete archive copies, but not backups stored in server storage.
You can enable open registration by entering the following command from an administrative client command line:
set registration open
For examples and a list of open registration defaults, refer to the Administrator's Reference.
To change the defaults for a registered node, use the UPDATE NODE command.
When you enable compression, it reduces network utilization and saves server storage, but causes additional central processing unit (CPU) overhead to the node. Data compression is recommended only when there is insufficient network capacity.
Attention: Use either client compression or drive compression, but not both. For details, see Using Data Compression.
To optimize performance or to ease memory constraints at the workstation, an administrator can restrict file compression. You can select one of three options:
Set the COMPRESSION option in the client system options file or in the application program interface (API) configuration file.
On a UNIX system, a root user can define the COMPRESSION option in the dsm.opt client options file.
Administrators can use client options sets in conjunction with the client options file to register nodes with the server. Client option sets are considered advanced implementation and are discussed in Modifying Client Option Files. You can specify an option set for a node when you register or update the node. For example:
register node mike pass2eng cloptset=engbackup
The client node MIKE is registered with the password pass2eng. When the client node MIKE performs a scheduling operation, the schedule log entries are kept for 5 days.
To include a NAS file server as a node that TSM can back up and restore with Tivoli Data Protection for NDMP support, you can register the file server as a NAS node. Data that is backed up from the NAS file server will be associated with the NAS node name.
The REGISTER NODE and UPDATE NODE commands have a default parameter of TYPE=CLIENT. To register a NAS file server as a node, you must specify the TYPE=NAS parameter. For example to register a NAS file server with a node name of NASXYZ and a password of PW4PW, enter the following:
register node nasxyz pw4pw type=nas
You must use this same node name when you later define the corresponding data mover name. For more information, see Chapter 6, Setting Up Tivoli Data Protection for NDMP.
A virtual volume is a volume that appears to be a sequential media volume on a source server. The volume is actually stored as an archive file on a target server.
To use virtual volumes, register the source server as a client node on the target server.
The REGISTER NODE and UPDATE NODE commands have a default parameter of TYPE=CLIENT. To register a source server as a node, you must specify the TYPE=SERVER parameter. For more information, see Using Virtual Volumes to Store Data on Another Server.
Workstation users can request TSM services by using an application that uses the TSM application programming interface (API). An administrator uses the REGISTER NODE command to register the workstation as a node.
For applications that use the TSM API, compression can be determined by:
For more information on setting options for the API and on controlling compression, see Tivoli Storage Manager Using the Application Program Interface.
For applications that use the TSM API, the file deletion option can be set by:
If an administrator does not allow file deletion, then an administrator must delete objects or file spaces that are associated with the workstation from server storage.
If an administrator allows file deletion, then Tivoli Storage Manager checks the client options file.
If the application uses the dsmDeleteObj or dsmDeleteFS program call, then objects or files are marked for deletion when the application is executed.