IBM Tivoli Storage Manager, Version 7.1

Automatic backup-archive client deployment

The Tivoli® Storage Manager server administrator can automatically deploy a backup-archive client to workstations that already have the backup-archive client installed.

When you schedule automatic Backup-Archive client deployments, the updated client packages (which include the client components and the API library) are installed on the workstations that receive them. A dependency check is performed by the client installation program to ensure that the API library does not conflict with the client package that is already installed.

Tivoli Data Protection for Enterprise Resource Planning applications do not use the same installation technology that is used by the client installation program. Because of that, the client installation dependency check is not able to detect whether the API library that is being used by the Tivoli Data Protection for Enterprise Resource Planning applications is compatible with the API library that will be installed by automatic client deployments. If a client package is automatically deployed to and installed on a workstation, the API library that is installed might not be compatible with the API library that was installed by the Tivoli Data Protection for Enterprise Resource Planning application. The newly deployed API library can cause the Tivoli Data Protection for Enterprise Resource Planning applications to fail.

Do not schedule automatic client deployments to workstations that have a Tivoli Data Protection for Enterprise Resource Planning application installed on them.

The Tivoli Storage Manager server can be configured to automatically upgrade backup-archive clients on Windows computers. The existing clients must be at version 5.4, or later.

You can use the autodeploy option to conditionally enable automatic client deployment, if the deployment does not require a restart of the client workstation.

By default, the autodeploy option is enabled, and the client workstation is restarted if required.

The autodeploy option can be set in the following places:

In the Administration Center. However, starting with Tivoli Storage Manager Version 7.1, the Administration Center component is no longer included in Tivoli Storage Manager distributions. If you have an Administration Center from a previous server release, you can continue to use it to set the autodeploy option on schedules that deploy client updates. If you do not already have an Administration Center installed, you can download the previously-released version from ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/admincenter/v6r3/LATEST. For information about the Administration Center, see the Tivoli Storage Manager Version 6.3 server documentation.
On a schedule definition. Schedules are defined on the server. Schedule definitions that deploy client software updates have an action=deploy statement. On those schedules, you can include the autodeploy option as part of the command that you include on the –postnschedulecmd statement.
On the client node, in an options file that is associated with the client scheduler or client acceptor daemon. The deployment manager detects options files that are associated with the scheduler or client acceptor daemon. If there are multiple scheduler or client acceptor daemon processes running on the same computer at the same time, and the processes use different options files, the deployment manager uses the autodeploy value that is set in one of the options files.
On the client in the client options file (dsm.opt). The autodeploy option that is set in the client options file overrides any other autodeploy setting.

To use automatic deployment but not restart the system, specify the autodeploy noreboot option.

Important: For automatic client deployment to be operational, the following conditions apply:

The client computer must have a minimum of 2 GB free disk space.
The passwordaccess option must be set to generate.
To store the password in the local Windows registry, a user must log on from the local workstation once, to provide the password. If the client automatic deployment process cannot find the node password in the registry, the following events occur:
- The deployment process does not start.
- A warning message is logged in the setup.log file.
  The following messages are examples of the messages that can be logged during a deployment.
```
Sun 10/11/2009 10:16:04.35 The deployclient.bat script is started.
Sun 10/11/2009 10:16:04.37 deployclient.bat is removing the deployment 
  manager and temporary files possibly left from the previous installation.
Sun 10/11/2009 10:17:10.53 WARNING: Still waiting for the result of query 
  system information. 
  Ensure that "PASSWORDACCESS GENERATE" is set in the client options file 
  and that a connection to the server can be made without being prompted 
  for a password.
```
  If you see these errors and PASSWORDACCESS is set to GENERATE, the errors are probably caused by a network problem (the client cannot be reached) or there might be a problem with the digital rights management subkey. The digital rights 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 a backup or a 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.

When you perform automatic client deployments from the Tivoli Storage Manager Server, the scheduler installs the updated client by running a command that is specified on a postschedulecmd option that is associated with the schedule. By default, the log and trace files for a deployment operation are written to the client's disk in C:\Program Files\Tivoli\TSM\IBM_ANR_WIN\Vxxxx\log; where xxxx represents 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 the deployment operation are still copied to the IBM_ANR_WIN\Vxxxx\log folder, and this folder is created one directory level up (../) from where the client executable files (dsm.exe, dsmc,exe, dsmcad.exe, and so on) were installed. For example, if you originally installed the client into E:\IBM\Tivoli\baclient, the log and trace files resulting 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 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.

The Tivoli Storage Manager server can be configured to automatically upgrade backup-archive clients on supported Linux and UNIX systems. The existing clients must be at version 5.5 or later.

Oracle Solaris operating systems Tivoli Storage Manager client distributions that are delivered with version 6.1 (and newer) clients no longer contain the TIVsmCIBc (Traditional Chinese, Big 5) language pack. On Solaris x86 and Solaris SPARC systems, if you upgrade a version 5.5.x client that uses the TIVsmCIBc language pack to version 6.1 (or newer), the TIVsmCIBc language pack is uninstalled. If you have the Traditional Chinese language pack installed (TIVsmCITc) no further action is needed to display text that contains Traditional Chinese characters. If you do not have the TIVsmCITc language pack installed, install it after the upgrade completes.

Important: For automatic client deployment to be operational, the following conditions apply:

The client computer must have the minimum free disk space as shown in Table 1.

Table 1. Minimum disk space needed for automatic client deployment
Operating systems	Free disk space required
AIX®	1500 MB
Solaris (SPARC)	1200 MB
HP-UX	900 MB
Linux on Power®	350 MB
Linux x86_64	950 MB
Linux on System z®	350 MB
Mac OS X	200 MB

In Tivoli Storage Manager 6.3 and later, 32-bit backup-archive clients are no longer supported. If the deployment manager detects a 32-bit backup-archive client running on a 64-bit operating system, it upgrades the client to the 64-bit version.
The passwordaccess option must be set to generate.
To store the password on the client, a user must log on to local workstation once, to provide the password. If the client automatic deployment process cannot find the node password, the following events occur:
- The deployment process does not start.
- A warning message is logged in the setup.log file.
  The following messages are examples of the messages that can be logged during a deployment.
```
Sun 10/11/2009 10:16:04.35 The deployclient.sh script is started.
Sun 10/11/2009 10:16:04.37 deployclient.sh is removing the deployment 
  manager and temporary files possibly left from the previous installation.
Sun 10/11/2009 10:17:10.53 WARNING: Still waiting for the result of query 
  system information. 
  Ensure that "PASSWORDACCESS GENERATE" is set in the client options file 
  and that a connection to the server can be made without being prompted 
  for a password.
```
  If you see these errors and PASSWORDACCESS is set to GENERATE, the errors are probably caused by a network problem (the client cannot be reached).
- 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 daemon must be running.
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 Administrator's Guide for instructions.

The deployment manager writes log and trace data for a deployment operation to the client’s disk. The default location of the logs is shown in Table 2. The xxxx represents the version, release, modification, and fix pack information for the deployed backup-archive client.

Table 2. Default log file location.
Operating System	Directory
AIX	/usr/tivoli/client/IBM_ANR_UNX/V`xxxx`/log/
Solaris, HP-UX, Linux	/opt/tivoli/tsm/client/IBM_ANR_UNX/V`xxxx`/log/
Mac	/Library/Application Support/tivoli/tsm/client/ba/bin/IBM_ANR_MAC/V`xxxx`/log

AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems When you define a schedule to deploy the client updates, you can specify a non-default retrieval target location for UNIX and Linux platforms. Specifying a non-default retrieval target location changes the location of the log and trace files. For example, the default retrieval target location for AIX is /usr/tivoli/client/. If you specify /tmp/tivoli/client as the target location, the log and trace files will be under /tmp/tivoli/client/IBM_ANR_UNX/Vxxxx/log.

Mac OS X operating systems On the Mac OS X platform, you cannot change the retrieval target location. The deployment manager's working directory is relative to the working directory of the client scheduler. For example, if the user starts the client scheduler from /mydir, the log and trace files will be under /mydir/IBM_AMR_MAC/Vxxxx/log.

A semaphore is used to prevent a client from being updated by different deployment managers at the same time. The semaphore expires 24 hours from the last client deployment. New clients cannot be deployed until the semaphore expires.

Feedback