12.07.2015 Views

Installation and User's Guide

Installation and User's Guide

Installation and User's Guide

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

node. 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.Note: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 comm<strong>and</strong>. The value for thetcpclientport client option must be the same as the value for theLLAddress option of the update node or register node servercomm<strong>and</strong>.2. If you set the sessioninitiation option to serveronly, with the exceptionof CAD-managed schedulers, the comm<strong>and</strong>-line client, backup-archiveclient GUI, <strong>and</strong> Web client GUI still attempts to initiate sessions, but areblocked by the Tivoli Storage Manager server for nodes that have thesessioninitiation option set to serveronly.3. When installing Tivoli Storage Manager scheduler using the setupwizard, <strong>and</strong> the Tivoli Storage Manager server is behind a firewall, thenode password will not get stored on the client workstation. As aresult, the scheduler service might be unable to authenticate to theserver when the server contacts the client to run a schedule. In thiscase, you can run the scheduler from the comm<strong>and</strong> line (dsmcschedule), wait until a scheduled operation starts, <strong>and</strong> enter thepassword for your node when prompted.4. When installing Tivoli Storage Manager scheduler using the setupwizard or dsmcutil, <strong>and</strong> the Tivoli Storage Manager server is behind afirewall, the node password will not get stored on the clientworkstation. As a result, the scheduler service might be unable toauthenticate to the server when the server contacts the client to run aschedule. In this case, you can run the scheduler from the comm<strong>and</strong>line (dsmc schedule), wait until a scheduled operation starts, <strong>and</strong> enterthe password for your node when prompted. After you enter thepassword for your node, restart the scheduler service. You can also usethe following dsmcutil comm<strong>and</strong> to write the password into theregistry:dsmcutil updatepw /node:nnn /password:ppp /validate:noIf sessioninitiation option is set to serveronly in your client options file(dsm.opt), the client setup wizard <strong>and</strong> scheduler service is unable toinitiate authentication with the Tivoli Storage Manager server. To avoidthis problem, when configuring the client scheduler using the setupwizard, ensure that the Contact the TSM Server to validate passwordcheckbox on the TSM Authentication page is unchecked.A similar problem can occur if an encryption key is required for backupoperations. In this case, you can run the scheduler from the comm<strong>and</strong>line (dsmc schedule), wait until a scheduled backup starts, <strong>and</strong> enterthe encryption key when prompted. After the password <strong>and</strong> encryptionkey are updated, you must restart the scheduler.5. When configuring the Tivoli Storage Manager scheduler on a clientworkstation for the first time, the scheduler service might be unable toauthenticate to the server when the server contacts the client schedulerto run a schedule. This can happen when the passwordaccess is set togenerate <strong>and</strong> the Tivoli Storage Manager server is behind a firewall <strong>and</strong>the encrypted password cannot be locally stored before the scheduler isstarted. To correct this problem, you need to run the scheduler from the26 IBM Tivoli Storage Manager for Windows Backup-Archive Clients: <strong>Installation</strong> <strong>and</strong> <strong>User's</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!