To modify the attributes of a registered client node, first complete the following fields, and then click Finish, or click Cancel to end the task.
Enter a 1-64 character new password for the client node. This parameter is optional.
Enter the name of the option set to be used by the client. This parameter is optional.
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"
Select the policy domain to which the client node is registered. This parameter is optional.
Select whether the client node should compress its files before sending them to the server for backup and archive. The parameter is optional. This parameter does not apply to NAS nodes.
Yes | Specifies that the client node compresses its files before sending them to the server for backup and archive. |
No | Specifies that 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. |
Select whether file spaces are renamed when the client system upgrades to a client that supports Unicode, or let the client decide if the file spaces should be renamed. 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. |
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
Tivoli Storage Manager 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). |
Select whether the client node can delete its own archived files from the server.
Yes | Allow the client node to delete archive files. |
No | Do not allow the client node to delete archive files. |
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. |
Select whether the administrator has the option to force a client to change or reset the password. The parameter is optional.
Yes | Specifies that the client node or administrator's password will expire at the next logon. The client must change or reset the password at that time. If a password is not specified, you will receive an error. |
No | Specifies that the password expiration period is set by the SET PASSEXP command. The storage administrator does not have the option to force a client to change or reset the password while attempting to logon to the server. |
Select whether the node should retain the tape 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. |
Enter a number from 0 to 999 to specify the maximum number of mount points a node is allowed to use on the server. A mount point must be defined for each primary and copy storage pool that is of sequential device type.
A value of 0 specifies that a 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. If the client stores its data to a storage pool that has copy storage pools defined for simultaneous backup, additional mount points may be needed. This parameter is optional.
Enter the client node's URL, if you want to link to it from the Network view. This parameter is optional. If you want to remove the value for this field, you must specify empty single quotes or empty double quotes with no spaces, ('' or "").
Select the name of the policy domain to use as a filter in combination with the node name. This parameter is optional.
Select the name of the client platform to use as a filter in combination with the node name. This parameter is optional.
Enter the number of days that a password stays valid. You can set the expiration period from 0 to 9999. A value of 0 means that the password never expires.
If a password expires, the server prompts for a new password when the administrator or client node contacts the server.
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. |