Installation and User's Guide

vvvvvthe scheduler service before the new client is installed, and restarts the schedulerservice after the installation. If the scheduler is not run as a Windows service, arestart is required when the client is deployed.The automatic client deployment feature stops and restarts scheduler and CADprocesses on the client, but it does not stop or restart any client operations suchas backup or restore. It is possible that in-process client operations could beaffected during an automatic deployment. To prevent an automatic deploymentfrom interfering with client operations, schedule automatic client deployments tooccur when it is not likely that the client is performing a backup or restore, orarchive or retrieve operation.The client is deployed as a postschedule operating system command; scheduledoperating system commands must be enabled on the client.You must configure your server to perform Backup-Archive Client automaticdeployments. See the Tivoli Storage Manager Administrators Guide for instructions.The command-line Windows registry utility (reg.exe) is required. This tool isgenerally installed as part of the operating system installation on supportedWindows platforms.The Windows cluster services environment is not supported.To turn off automatic client deployment, add autodeploy no to the client optionsfile.The autodeploy option is only available for Tivoli Storage Manager clientsversion 6.2 and later.When you perform automatic client deployments from the Tivoli Storage ManagerServer, the scheduler installs the updated client by running a command that isspecified on a postschedulecmd option that is associated with the schedule. Bydefault, the log and trace files for a deployment operation are written to the client'sdisk in C:\Program Files\Tivoli\TSM\IBM_ANR_WIN\Vxxxx\log; where xxxxrepresents the version for the newly deployed client.If you did not use the default installation directory when you installed the client,when an automatic client deployment is performed, the log and trace data for thedeployment operation are still copied to the IBM_ANR_WIN\Vxxxx\log folder, andthis folder is created one directory level up (../) from where the client executablefiles (dsm.exe, dsmc,exe, dsmcad.exe, and so on) were installed. For example, if youoriginally installed the client into E:\IBM\Tivoli\baclient, the log and trace filesresulting from the automatic deployment are created in E:\IBM\Tivoli\IBM_ANR_WIN\Vxxxx\log folder.A lock file is also created on each client to prevent a client from being updated bydifferent deployment managers at the same time. Before a deployment begins, thedeployment manager looks on the client for the lock file. If the file exists and isless than 24 hours old, the deployment is canceled. If the lock file is more than 24hours old or does not exist, the deployment is started. The lock file is deletedwhen the deployment completes. If the deployment manager fails to delete thelock file, you can manually delete it from the client’s disk. The lock file location isinstall_dir\..\IBM_ANR_WIN\mutext.txt.Related reference:“Autodeploy” on page 302Client environment requirementsThis section contains Tivoli Storage Manager client environment information,components, and hardware and software requirements.Chapter 1. Installing the Tivoli Storage Manager backup-archive clients 5