Registering New Nodes

To register a client node (machine) with the server, first complete the following fields and then click Finish, or click Cancel to end the task.

Node Name

Enter a 1-64 character node name.

Node names:

Example: JSMITH

Password

Enter a 1-64 character node password. A password is required.

Contact

Enter information identifying the node, such as a telephone number or E-mail address. This parameter is optional.

Example: "Administrator for M47 - contact Shirley Jones at 9-1111"

Policy Domain Name

Select the name of the policy domain to which the node is assigned. This field is optional. If you do not specify a policy domain name, the node is assigned to the default policy domain (STANDARD).

Client Compression Setting

Select whether the client node should compress its files before sending them to the server for backup and archive. 

NOTE:  This field is not valid for a NAS node.

Yes Specifies that the client node compresses its files before sending them to the server for backup and archive.
No Specifies that the client node does not compress its files before sending them to the server for backup and archive.
Client Specifies that data sent to the server should be compressed if compression is specified in the client options file. The default is Client.

Auto Filespace Rename Setting

Select whether all file spaces are automatically renamed, no file spaces are renamed, or let the client decide if file spaces are renamed when the client system upgrades to a client that supports Unicode.  The renaming, if allowed, occur when the client runs one of the following operations:  archive, selective backup, full incremental backup, or partial incremental backup.  The renaming changes the names of existing backed-up file spaces that are not in Unicode in server storage.  Then the file spaces are backup up in Unicode.  This parameter is only valid for client systems using Windows NT,  Windows.NET, Windows 2000, Windows 2002, and Windows XP operating systems.

Yes Specifies that the server automatically renames existing file spaces when the client system upgrades to a client that supports Unicode, and the client runs one of the following operations:  archive, selective backup, full incremental backup, or partial incremental backup.  The renaming occurs whether the client uses the graphical user interface, the command line, or the client scheduler.
No Specifies that the server does not rename file spaces automatically when the client system upgrades to a client that supports Unicode, and the client runs one of the following operations:  archive, selective backup, full incremental backup, or partial incremental backup.  This is the default.
Client Specifies that the option AUTOFSRENAME in the client's option file determines whether file spaces are renamed.  By default, the client option is set to PROMPT.  When the client upgrades to a client that supports Unicode and the client runs a TSM operation with the graphical user interface or the command line, the program prompts the user only once about renaming the file space in the current operation.

When the client scheduler runs an operation, the program does not prompt for a choice about renaming, and does not rename file spaces.  Backups of existing file spaces are sent as before (not in Unicode).

Archive Delete Allowed

Select whether the client node can delete its own archived files from the server.

Yes Allow the client node to delete archive files. The default is Yes.
No Do not allow the client node to delete archive files.

Backup Delete Allowed

Select whether the client node can delete its own backup files from the server.

Yes Allow the client node to delete backup files.
No Do not allow the client node to delete backup files. The default is No.

Client Option Set

Enter the name of the option set to be used by the client. This parameter is optional.

Force Password Reset

Select whether the client's password will expire at the next logon attempt. The client must reset the password to complete the logon.

Yes Forces the client to enter new password.
No Allows the client to continue using the existing password. The default is No.

Node Type

Select whether to register the node as type client, server, or NAS.

Client Specifies that the user is registered as a client node on the server. The default is client.  The client node can be a backup-archive client, HSM client, or TDP application client.
Server Specifies that the node is a source server being registered on a target server.
NAS Specifies that the node is a network-attached storage (NAS) file server whose data will be protected using Tivoli Data Protection for NDMP.  (This option does not apply to PASE)

Keep Mount Point

Select whether the node should retain the mount point for the entire session.

Yes Specifies that the node must retain the tape mount point during the entire session.
No Specifies that the node will release the tape mount point if policy definitions cause data to be stored in a disk storage pool after storing data in a sequential storage pool. The default is No.

Maximum Mount Points Allowed

Enter a number from 0 to 999 to specify the maximum number of mount points this node is allowed to use on the server or storage agent.  This parameter is optional.  The default is 1. A value of 0 specifies that the node cannot acquire any mount point for a backup or archive operation. However, the server still allows the node a mount point for a restore or retrieve operation.  

The storage agent independently tracks the number of points used during a client session.  Therefore, if a node has a storage agent installed it may exceed this limit.  This value may also be exceeded under conditions where the mount point is available, and the node does not have to wait for a mount point.  A node uses a mount point when it stores data to a sequential access storage pool  for example, tape, optical,  or FILE on disk.   If a client stores its data to a storage pool that has copy storage pools defined for simultaneous backup, additional mount points may be needed.  

If a node stores data on primary storage pools that have a list of copy storage pools defined for simultaneous backup, you must specify one mount point for each storage pool that is of sequential device type.  This includes the primary storage pool if it is of sequential device type.

For server-to-server backup, if the two servers differ in versions, set the number of mount points on the target server to a value higher than 1, or you will receive an error.

Note:  The server may preempt a client's operation for a higher priority operation and the client may lose a mount point if no other mount points are available.  You can disable preemption by specifying NOPREEMPT in the server options file.  When this option is specified, only a BACKUP DB operation can preempt other operations.

URL

Enter the URL address for this Tivoli Storage Manager client node if you would like to link to it from the Network view. The URL address must be entered for the defined client node to display in the Network view and for you to link to it. This parameter is optional.

User ID for Remote Access

Enter an administrative user ID with client owner authority. If you do not enter an ID, an administrative user ID with client owner authority is created using the node name of the client node to be registered by default. Enter none if you do not want to automatically create an administrative ID. This parameter is optional.

Password Expiration Period

Enter the number of days that a password stays valid. If you do not specify a node or administrator, you can set the password 
expiration period from 1 to 9999. If you specify a node or administrator, you can set the expiration period from 0 to 9999.  If a password expires, the server prompts for a new password when the administrator or client node contacts the server. If you do not specify this parameter, the server uses the common expiration period to determine when to expire a password. The common expiration period is set by the SET PASSEXP command. The default common expiration period for SET PASSEXP is 90 days. 

Validate Protocol

Select whether the node's data should have a cyclic redundancy checking operation performed to validate the data sent between the client and the Tivoli Storage Manager server.  This parameter is optional.  Specifying data validation impacts performance because additional overhead is required to calculate and compare CRC values between the client and the server.

No Specifies that data validation not be performed on any data sent between the client and server.  The default is No.
Data only Specifies that data validation be performed only on file data that is sent between the client and server.  This does not include the file meta data.
All  Specifies that data validation be performed on all client file data, client file meta data, and Tivoli Storage Manager server meta data that is sent between the client and server.