IBM Tivoli Storage Manager for Windows Backup-Archive Clients ...

|
|
|
|
|
|
|
|
|
v
v
v
v
v
v
management key is in the registry in HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM.
– The dsmc query systeminfo command is left running.
– The deployment process cannot start, so no messages are sent to the server.
The client is deployed from the server as a scheduled task; the client scheduler
must be running.
The scheduler must be started as a Windows service and not from the command
line. To minimize the chance of a restart, the deployment manager shuts down
the scheduler service before the new client is installed, and restarts the scheduler
service after the installation. If the scheduler is not run as a Windows service, a
restart is required when the client is deployed.
The automatic client deployment feature stops and restarts scheduler and CAD
processes on the client, but it does not stop or restart any client operations such
as backup or restore. It is possible that in-process client operations could be
affected during an automatic deployment. To prevent an automatic deployment
from interfering with client operations, schedule automatic client deployments to
occur when it is not likely that the client is performing a backup or restore, or
archive or retrieve operation.
The client is deployed as a postschedule operating system command; scheduled
operating system commands must be enabled on the client.
You must configure your server to perform Backup-Archive Client automatic
deployments. See the Tivoli Storage Manager Administrators Guide for instructions.
The command-line Windows registry utility (reg.exe) is required. This tool is
generally installed as part of the operating system installation on supported
Windows platforms.
The Windows cluster services environment is not supported.
To turn off automatic client deployment, add autodeploy no to the client options
file.
The autodeploy option is only available for Tivoli Storage Manager clients
version 6.2 and later.
|
|
|
|
|
|
|
|
|
|
|
|
|
The deployment manager writes log and trace data for a deployment operation to
the client’s disk. The default location of the logs is in the following directory on
the client’s disk: C:\Program Files\Tivoli\TSM\IBM_ANR_WIN\Vxxxx\log\; where
xxxx represents the version, release, modification, and fix pack information for the
deployed Backup-Archive Client.
A lock file is also created on each client to prevent a client from being updated by
different deployment managers at the same time. Before a deployment begins, the
deployment manager looks on the client for the lock file. If the file exists and is
less than 24 hours old, the deployment is canceled. If the lock file is more than 24
hours old or does not exist, the deployment is started. The lock file is deleted
when the deployment completes. If the deployment manager fails to delete the
lock file, you can manually delete it from the client’s disk. The lock file location is
install_dir\..\IBM_ANR_WIN\mutext.txt.
Related reference
“Autodeploy” on page 306
Client environment requirements
This 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