Defining a schedule for an automatic deployment

You can schedule a backup-archive client deployment after you import the packages to the server.

1. Issue the DEFINE SCHEDULE command. For example:
   

   define schedule domain_name schedule_name action=deploy
   objects="deployment_package_location destination_for_package" 
   options="-fromnode=IBM_CLIENT_DEPLOY_WIN 
   -postnschedulecmd='relative_path\deployclient.bat schedule=schedule_name
   autodeploy=noreboot nodeinfo=TBD' -subdir=yes -replace=all"
   startdate=4/20/2013 perunits=onetime

   where

   • deployment_package_location is the path to the deployment package
   • destination_for_package is the path to where you want to store the deployment package
   • IBM_CLIENT_DEPLOY_WIN is the predefined name (for a Windows deployment) for the -fromnode option
   • AUTODEPLOY can be YES, NO, or NOREBOOT. The default is YES.
   • nodeinfo=TBD must be entered exactly as shown.
   Note: The -fromnode option can have the following values:

   • IBM_CLIENT_DEPLOY_WIN
   • IBM_CLIENT_DEPLOY_UNX
   • IBM_CLIENT_DEPLOY_MAC
   

   define schedule domain_name schedule_name action=deploy
   objects='deployment_package_location destination_for_package duration=1 
   durunits=hours perunits=onetime startdate=today starttime=now 
   options='-fromnode=IBM_CLIENT_DEPLOY_UNX 
   -postnschedulecmd='relative_pathdeployclient.sh>
   /opt/tivoli/tsm/client/IBM_ANR_UNX/v63011/upminx#schedule=schedule_name
   #domain=domain_name#nodeinfo2=TBD'-subdir=yes -replace=all'

   where

   • deployment_package_location is the path to the deployment package
   • destination_for_package is the path to where you want to store the deployment package
   • IBM_CLIENT_DEPLOY_UNX is the predefined name (for a UNIX deployment) for the -fromnode option
   • nodeinfo2=TBD must be entered exactly as shown.

   If your current backup-archive client is AIX®, Linux, Solaris, or HP-UX and is at version 6.1 or later, use nodeinfo2=TBD in the POSTNSCHEDULECMD command. Macintosh Backup-Archive Clients at version 5.5 and later also must use nodeinfo2=TBD.

   Important: Not all backup-archive clients can process post-schedule commands that contain spaces. Use the number sign (#) in place of blank spaces in the -postnschedulecmd command. If your command fails and a log file is not available, reissue the command and use the number sign instead of spaces.

   The target location for the backup-archive client packages is in relation to the location of the working client scheduler directory. If the directory is C:\program files\tivoli\tsm\baclient, the client deployment package target location is C:\program files\tivoli\tsm\IBM_ANR_WIN\v6300\. This location is also the deployment manager’s working directory. Here is an example post-schedule command for Windows servers:

   -postnschedulecmd='..\relative_path\deployclient.bat
   schedule=schedule_name domain=domain_name autodeploy=noreboot nodeinfo=TBD'

   The target location for backup-archive client packages on Macintosh operating systems is in relation to the location of the working client scheduler directory. This location is also the deployment manager’s working directory. Here is an example post-schedule command for Macintosh:

   -postnschedulecmd='../relative_path/deployclient.sh>
   ./IBM_ANR_MAC/V6303/upmin#schedule=schedule_name#domain=standard#nodeinfo2=TBD'

   For operating systems that are not Windows, the locations are determined by the default installation directory of the backup-archive client. You can specify a different directory from the Administration Center. For example, on operating systems such as AIX, the default, working directory is /usr/tivoli/tsm/client/IBM_ANR_UNX/VXXXX. On operating systems such as UNIX and Linux, you can replace the "/usr" file path with one of the following names:

   • /tmp
   • /opt
   • /home
   Important: If you use AUTODEPLOY=NOREBOOT in your command, the client operating system does not restart after the deployment completes. Restarting can affect any critical applications that are running on the client operating system. Applications that are not Tivoli® Storage Manager applications that are running on the client operating system might not be restarted automatically. In most cases, the installation can complete without restarting the client operating system. There are rare cases where the deployment manager cannot detect the restart.
   For example, if client processes are started from a script. In these cases, the new backup-archive client installation continues, but a manual restart of the client computer is required.
2. Issue the DEFINE ASSOCIATION command to associate nodes with the deployment schedule.