IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive ...

||||||TCP/IP port for administrative sessionsSpecifies a separate TCP/IP port number on which the server iswaiting for requests for administrative client sessions, allowingsecure administrative sessions within a private network. See“Tcpadminport” on page 360 for more information.Method 2:For the client scheduler in prompted mode, it is unnecessary to open anyports on the firewall. If you set the sessioninitiation option to serveronly,the client will not attempt to contact the server. All sessions will be initiatedby server prompted scheduling on the port defined on the client with thetcpclientport option. The sessioninitiation option only affects the behaviorof the client scheduler running in the prompted mode.The Tivoli Storage Manager server must set the SESSIONINITiationparameter on the register node and update node commands for eachnode. If the server specifies SESSIONINITiation=clientorserver, the default,the client can decide which method to use. If the server specifiesSESSIONINITiation=serveronly, all sessions are initiated by the server.Notes:1. If sessioninitiation is set to serveronly, the value for the tcpclientaddressclient option must be the same as the value for the HLAddress optionof the update node or register node server command. The value for thetcpclientport client option must be the same as the value for theLLAddress option of the update node or register node servercommand.2. Using the sessioninitiation option requires a Tivoli Storage ManagerVersion 5.2 or higher server.3. If you set the sessioninitiation option to serveronly, with the exceptionof CAD-managed schedulers, the command line client, backup-archiveclient Java GUI, and Web client GUI will still attempt to initiatesessions, but are blocked by the Tivoli Storage Manager server fornodes which have the sessioninitiation option set to serveronly.4. When configuring the Tivoli Storage Manager scheduler on a clientmachine for the first time, the scheduler service might be unable toauthenticate to the server when the server contacts client scheduler toexecute a schedule. This can happen when the passwordaccess is set togenerate and the Tivoli Storage Manager server is behind a firewall andthe encrypted password cannot be locally stored before the scheduler isstarted. To correct this problem, you need to run scheduler from thecommand line (dsmc schedule), wait until a scheduled operation starts,and enter the password for your node when prompted.Note: The Tivoli Storage Manager client cannot prompt for theencryption key password in scheduler mode. If you are usingTivoli Storage Manager data encryption, you must run an initialinteractive backup once to set up the encryption key by openingthe TCP/IP connection from the client machine to the servermachine. See 54 for more information about setting up thiscommunication. After the encryption key is set, you can useserver-initiated sessions to back up the files using Tivoli StorageManager encryption.If you set the sessioninitiation option to client, the client will initiatesessions with the server (Method 1) by communicating on the TCP/IP portChapter 2. Configuring Tivoli Storage Manager 55