Defining a Server for Server-to-Server Communications

To define a server for server-to-server communication, first complete the following fields and then click Finish, or click Cancel to end the task.

Servers must first be defined to each other to enable server-to-server communication. You can define servers to each other by issuing separate definitions for each server or by cross defining the servers in one operation using the Crossdefine field. Server-to-server communications provides for the following server functions: enterprise configuration, server-to-server event logging, command routing, and virtual volumes.

Note: The use of virtual volumes is not supported when the source server and the target server are on the same Tivoli Storage Manager server.

Server Name

Enter the name to be used for the server definition. This field is required.

Description

Enter the server description. The maximum length of the description is 30 characters. This field is optional.

Server Password

Enter the password used to sign on to the target server. This field is required for server-to-server communications for virtual volumes.

Host Name or TCP/IP Address

Enter the host name or TCP/IP address (high level address) of the server for the TCP/IP communication method. This field is required for setting up communications for enterprise configuration, server-to-server event logging, command routing, and virtual volume support.

TCP/IP Port Number

Enter the TCP/IP port number (low-level address) of the server for the TCP/IP communication method. This field is required for setting up communications for enterprise configuration, server-to-server event logging, command routing, and virtual volume support.

URL

Enter the URL address for this server if you would like to link to it from the Network view. The URL address must be entered for the defined server to display in the Network view and for you to link to it. This field is optional.

Crossdefine

Select whether the server defines itself to the server being defined specified by this operation. This field is optional. The default is No.

Yes Specifies that the server running this operation defines itself to the server specified on the Define Server operation.
No Specifies that the server running this operation does not define itself to the server specified on the Define Server operation.

Validate Protocol

Select whether a cyclic redundancy check should be performed to validate the data sent between the storage agent and the server. The default is No.

No Specifies that data validation will not be performed on any data sent between the storage agent and the server.
All Specifies that data validation will be performed on all client file data, client file metadata, and server metadata that is sent between the storage agent and the server.  This mode of operation affects performance.  Additional overhead is required to compare CRC values between the storage agent and the server.

Node Name

Enter a 1-64 character node name to be used by the server to connect to the target server. This field is optional. If you specify the Node Name field, you must also specify the Password field. If you specify the Password field without specifying the Node Name field, the node name defaults to the server name specified with the Set Server Name operation.

Password

Enter the password used to identify this server to other servers. This field is required for enterprise configuration, command routing, and server-to-server event logging.

Grace Deletion Period

Enter a number of days that an object remains on the target server after it has been marked for deletion. This field is optional.