Tivoli Storage Manager Installing the Clients


Chapter 3. Installing UNIX Clients

This chapter provides instructions to install and set up TSM UNIX clients. It includes required and optional tasks for a root user, optional tasks for users, and special considerations for setting up TSM to back up and archive Andrew File System (AFS) or Distributed File System (DFS) files from an AIX workstation. Table 8 lists the supported UNIX clients and the location of the installation instructions for each client.

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media. For current information concerning TSM, supported platforms, and documentation, refer to the TSM Web site at http://www.tivoli.com/storage.


Table 8. UNIX Client Installation Reference

Installation Instructions Page
Installing the AIX Clients Installing the AIX Clients
Installing the HP-UX Clients Installing the HP-UX Clients
See Program Directory for TSM Client for OS/390 UNIX GI10-4529
Installing the Linux Client Installing the Linux Client
Installing the NUMA-Q DYNIX/ptx Clients Installing the NUMA-Q DYNIX/ptx Clients
Installing the Silicon Graphics IRIX Clients Installing the Silicon Graphics IRIX Clients
Installing the Solaris Clients Installing the Solaris Clients
Installing the Tru64 UNIX Clients Installing the Tru64 UNIX Clients
Installing the UnixWare Clients Installing the UnixWare Clients

UNIX Installation Notes

A root user must install TSM on a UNIX workstation. Additional required setup tasks for the root user include the following:

Optional root user tasks are:

Optional user tasks are:

For special consideration when installing and configuring the AFS/DFS clients on an AIX workstation, see Appendix A, Special Considerations for AFS/DFS on AIX


Installing the Client Programs (Required)

This section includes the initial step for installing each TSM client program on UNIX workstations. This section is followed by installation information that applies to all UNIX clients and begins with Setting Environment Variables (Optional).

Installing the AIX Clients

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following packages are available on the installation media in the /usr/sys/inst.images directory:

tivoli.tsm.client.ba.aix43.32bit
Installs the backup-archive client files (command-line and GUI), administrative client (command-line) into the /usr/tivoli/tsm/client/ba/bin directory.

tivoli.tsm.client.image.aix43.32bit
Installs the image backup component into the /usr/tivoli/tsm/client/ba/bin directory.

tivoli.tsm.client.web.aix43.32bit
Installs the Web client into the /usr/tivoli/tsm/client/ba/bin directory.

tivoli.tsm.client.books
Installs the PDF and HTML book files into the /usr/tivoli/tsm/client/books directory.

tivoli.tsm.client.ba.msg.lang
Installs NL messages for the Backup-Archive client. Where lang is the language identifier, for example Ja_JP for Japanese. American English messages are already included in the backup-archive client code. The default installation directory is /usr/tivoli/tsm/client/ba/bin/lang, where lang is the language identifier.

tivoli.tsm.client.api.aix43.32bit
Installs the 32 bit API into the /usr/tivoli/tsm/client/api/bin directory.

tivoli.tsm.client.api.aix43.64bit
Installs the 64 bit API into the /usr/tivoli/tsm/client/api/bin64 directory.

tivoli.tsm.client.api.msg.lang
Installs the NL messages for API. Where lang is the language identifier, for example Ja_JP for Japanese. American English messages are already included in the API client code. The default installation directory is /usr/tivoli/tsm/client/api/bin/lang, where lang is the language identifier.

tivoli.tsm.client.afs.aix43.32bit
Installs the support for backing up AFS ACLs and recognizing AFS mount points into the /usr/tivoli/tsm/client/afs/bin directory.

tivoli.tsm.client.butaafs.aix43.32bit
Installs the support for backing up AFS volumes into the /usr/afs/buta directory.

tivoli.tsm.client.dfs.aix43.32bit
Installs the support for backing up DFS ACLs and recognizing DFS mount points into the /usr/tivoli/tsm/client/dfs/bin directory.

tivoli.tsm.client.butadfs.aix43.32bit
Installs the support for backing up DFS filesets into the /opt/dcelocal/var/dfs/buta directory.

Do not put any user created files into /usr/tivoli/tsm/client/ba/bin, the base directory into which the TSM product is installed. The directory /usr/tivoli/tsm/client/ba/bin is assumed to be owned by the install process, and any and all files in this directory might be deleted during installation processing. Include-exclude files, dsm.opt, and dsm.sys files should not reside in this directory.

If you are not installing from a CDROM, run the following command from the AIX command line:

   /usr/sbin/inutoc <dir>

where <dir> is the directory where the TSM image resides. A .toc file is created in the directory.

Use the following installation steps:

  1. Insert the CD-ROM into the CD-ROM drive device, and mount the CD-ROM drive.
  2. From the AIX command line, type smitty install and press Enter.
  3. Select Install and Update Software and press Enter.
  4. Select Install and Update From ALL Available Software and press Enter.
  5. At the INPUT device/directory for software prompt, press the F4 key and select the CD-ROM device containing the installation CD-ROM, or specify the directory containing the installation images, and press Enter.
  6. At the SOFTWARE to install prompt, press the F4 key. Select the TSM filesets you want to install and press Enter. A minimum installation requires the TSM Client - Common Files and at least one of the remaining client options.
  7. Select any option and press Enter to begin the installation.

The TSM files are installed in the /usr/tivoli/tsm/client/ba/bin directory. If you move the TSM files to another directory, you must perform the following steps:

  1. Make sure the permissions of the installed files have not changed.
  2. Update the symbolic links for the installed files in the /usr/bin directory and in the directory that contains symbolic links for each language package you install (for example, /usr/lib/nls/msg/en_US).
  3. Ensure that every user of TSM sets the DSM_DIR environment variable to the newly installed directory.

Installing the HP-UX Clients

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following installation options are available when installing the tsmcli/hp11/TIVsm package:

CLIENT
Installs the backup-archive client (command-line and GUI), administrative client (command-line), and the Web client.

CLIENT_API
Installs the API.

CLIENT_DOC
Installs the documentation.

TIVsm
Installs CLIENT, CLIENT_API, and CLIENT_DOC

To remove previous client versions, log in as the root user and enter the following command:

   /usr/sbin/swremove -x mount_all_filesystems=false -v IBMADSM

To install from the CD-ROM, Log in as the root user, mount the CDROM to /cdrom, and enter the following command:

   swinstall -x mount_all_filesystems=false -v -s /cdrom/tsmcli/hp11/
   TIVsm TIVsm
Note:pwd may be used instead of the absolute name of the current directory.

To install only the API or the documentation, omit the last TIVsm from the command above, and mark only the fileset for installation in the swinstall user interface you want to install. The Client needs the API for Raw Logical Volume backup. Therefore, if you mark CLIENT for installation the API must also be installed.

During installation:

Installing the Linux Client

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following installation options are available in uncompressed packages on the CD:

TIVsm-BA
Installs the backup-archive client (command-line and GUI), administrative client (command-line), and the Web client.

TIVsm-API
Installs the API.

If there is a previous unsupported Linux client installed, the user must uninstall the unsupported Linux client.

To delete previously installed TSM 3.7 client packages, log in as root and enter:

rpm -e TIVsm-BA
or
rpm -e TIVsm-API
Note:The version number is not needed for uninstall.

Use the following procedure to install the TSM clients:

  1. Log in as the root user and mount the CD-ROM to /cdrom.
  2. Enter the following directory path where the installation packages reside on the CD:
    /cdrom/tsmcli/linux
    
  3. Enter the following command to install the backup-archive client (command-line and GUI), the administrative client (command-line), and the Web client:
    rpm -i TIVsm-BA.i386.rpm
    
    Note:The --nodeps flag must be added to the rpm installation command, when installing the TSM client on Caldera Linux only.
  4. Enter the following command to install the API:
    rpm -i TIVsm-API.i386.rpm
    

During installation :

Installing the NUMA-Q DYNIX/ptx Clients

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following installation options are available when installing the tsmcli/numa-q/ptxtsmc.pkg package:

tsm
Installs the backup-archive client (command-line and GUI), administrative client (command-line), and the Web client.

tsmapi
Installs the API.

To remove previous TSM client versions, log in as the root user and enter the following command:

   pkgrm adsm adsmapi

Use the following procedure to install the TSM clients:

  1. Log in as the root user, insert the CD-ROM, and enter the following command:
       pkgadd -d /CD-ROM/tsmcli/numa-q/ptxtsmc.pkg
    
    Note:Replace the word CD-ROM with the file system of the CD-ROM drive on your system.
  2. Select the package to install or press enter to install both packages.

The TSM backup-archive files are installed in the /opt/tivoli/tsm directory. The API files are installed in the /opt/tivoli/tsm/client/api/bin directory. If you move the TSM files to another directory, you must perform the following steps:

  1. Ensure the permissions of the installed files are not changed.
  2. Update the symbolic links for the installed files in the /opt/bin directory.
  3. Ensure that every TSM user sets the DSM_DIR environment variable to the new installation directory.

Kernel Parameter SHMGAP

To indicate the amount of dynamic memory that a user-process is allowed to use, the NUMA-Q DYNIX/ptx system provides the kernel parameter SHMGAP. The default value of SHMGAP is 2 MB.

If the value of SHMGAP has not already been increased, perform the following:

  1. Increase the value of SHMGAP to 32 MB.
  2. Rebuild the kernel.
  3. Reboot the system.

Installing the Silicon Graphics IRIX Clients

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following packages are available within the install image on the installation media:

TSM.sw.base
Installs the backup-archive client (command-line and GUI) and administrative client (command-line).

TSM.sw.api
Installs the API.

TSM.sw.web
Installs the Web client.

Use the following procedure to install the TSM clients:

  1. Log in as the root user, insert the CD-ROM, and enter the following command:
       inst -A -f /CDROM/tsmcli/sgi/
    
    Note:Replace the word CD-ROM with the file system of the CD-ROM drive on your system.

During installation:

Installing the Solaris Clients

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following installation options are available in uncompressed packages on the CD:

TIVsmCba
Installs the backup-archive client (command-line and GUI), administrative client (command-line), and Web client.

TIVsmCapi
Installs the API.

TivsmCdoc
Installs the documentation.

To delete previously installed ADSM V2 client packages, log in as root and enter:

pkgrm IBMDSMba5 IBMDSMap5

To remove the ADSM V3.1 client version, log in as root and enter:

pkgrm IBMadsm-w IBMadsm-c IBMadsm-a IBMadsm-h

To remove the ADSM V2 administrative GUI, log in as root and enter:

pkgrm IBMDSMsa5

Use the following procedure to install the TSM clients:

  1. Log in as the root user and mount the CD-ROM to /cdrom.
  2. Enter the following command and include the package name. For example, to install the backup-archive client, enter:
       pkgadd -d /cdrom/tsmcli/sol26 TIVsmCapi TIVsmCba
    
    Note:The Client needs the API for Raw Logical Volume backup, so the API must installed before the client.
  3. If you want to install the documentation, enter:
       pkgadd -d /cdrom/tsmcli/sol26 TIVsmCdoc
    
  4. Answer Yes (y) to all questions during installation.
Note:To display the TSM help browser menus in your locale language, insure the NLSPATH environment variable in the /etc/profile file contains the following path:
   /usr/dt/lib/nls/msg/%L/%N.cat

During installation :

Installing the Tru64 UNIX Clients

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following packages are available on the installation media:

tsmcli/Tru64/DSMBAC310
Installs the backup-archive client (command-line and GUI), the administrative client (command-line), and the Web client (Tru64 UNIX 4.0 only).

tsmcli/Tru64/DSMAPI310
Installs the API.

To remove previous client versions, log in as the root user and enter the following command:

   /usr/sbin/setld -d DSMBAC310 DSMAPI310

Use the following procedure to install the TSM clients:

  1. Log in as the root user, insert the CD-ROM, and enter the following command:
       setld -l /CD-ROM/tsmcli/Tru64/ DSMBAC310 DSMAPI310
    
    Note:Replace the word CD-ROM with the file system of the CD-ROM drive on your system.

The TSM files are installed in the /usr/tivoli/tsm directory. The Web client files are installed in the client directory. If you move the TSM files to another directory, you must perform the following steps:

  1. Make sure the permissions of the installed files have not changed.
  2. Update the symbolic links for the installed files in the usr/bin directory.
  3. Ensure that every user of TSM sets the DSM_DIR environment variable to the new installation directory.

Installing the UnixWare Clients

Attention

For current installation and configuration information for the TSM program product, refer to the README file that is shipped on the product installation media.

The following installation options are available when installing the tsmcli/unixware/unixwaretsm.pkg package:

TIVsm-BA
Installs the backup-archive (command-line and GUI), administrative (command-line), and the Web client.

TIVsm-API
Installs the API.

To remove previous client versions, log in as the root user and enter the following command:

pkgrm adsm adsmapi

Use the following procedure to install the TSM clients:

  1. Log in as the root user, insert the CD-ROM, and enter the following command:
         pkgadd -d /CD-ROM/tsmcli/unixware/unixwareadsmc.pkg  
    
    Note:Replace the word CD-ROM with the file system of the CD-ROM drive on your system.
  2. Select the package to install or press enter to install both packages.

During installation:

If you move the TSM files to another directory, you must perform the following steps:

  1. Ensure the permissions of the installed files are not changed.
  2. Update the symbolic links for the installed files in the /usr/bin directory.
  3. Ensure that every TSM user sets the DSM_DIR environment variable to the new installation directory.

If you are using the backup-archive GUI, ensure that the CDE-libraries (libdt*) are in your library path. If they are missing, you can add them with the following command:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/dt/lib

Setting Environment Variables (Optional)

The language used for the AIX, HP-UX, and Solaris clients is specified using the LANG environment variable. For all other UNIX platforms, the default is American English.

There are three environment variables that you can set to point to files that TSM uses:

DSM_DIR
Points to the executable file dsmtca, the resource files, and the dsm.sys file. You cannot specify the root directory for DSM_DIR. If DSM_DIR is not set, the executables are expected in the default installation directory.

DSM_CONFIG
Points to the client user options file for users who create their own personalized options file. You cannot specify the root directory for DSM_CONFIG. If DSM_CONFIG is not set, the options file is expected in the directory pointed to by DSM_DIR. If DSM_DIR is not set, the options file is expected in the default installation directory. On Solaris, dsm.sys and dsm.opt are symbolic links to the actual files stored in /usr/bin which prevents the deletion of these files in the event that TSM is uninstalled.

DSM_LOG
Points to the directory where you want the dsmerror.log file to reside. The dsmerror.log cannot be a symbolic link. You cannot specify the root directory for DSM_LOG. The error log file contains information about any errors that occur during processing. The error log is intended for IBM service personnel to help you diagnose severe errors.

If you define DSM_LOG, TSM writes messages to dsmerror.log in the directory you specify.

If you do not define DSM_LOG, but DSM_DIR is defined, TSM writes messages to dsmerror.log in the directory specified by DSM_DIR.

If neither DSM_LOG or DSM_DIR is defined, TSM writes messages to dsmerror.log in the current directory.

TSM issues a warning message if it cannot write to the log file, and continues processing.

For UNIX platforms that require CDE: Running the backup-archive GUI outside the CDE desktop could result in errors due to unresolved fonts. Ensure all required fonts are available for your language environment when running the backup-archive GUI outside the CDE desktop. When running the backup-archive GUI under Motif, and outside of the CDE desktop, add the following entry to the .Xdefaults file in your home directory:

 dsm*fontList: -dt-interface system-medium-r-normal-xs*-*-*-*-*-*-*-*-*:
Note:To display the TSM help browser menus in your locale language, insure the NLSPATH environment variable in the /etc/profile file contains the following path:
   NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat:$NLSPATH
   export NLSPATH

Setting Bourne and Korn Shell Variables

For the Bourne or Korn shell, enter the environment variables in the .profile file in your $HOME directory. For example:

   DSM_DIR=/home/davehil
   DSM_CONFIG=/home/davehil/dsm.opt
   DSM_LOG=/home/davehil
   export DSM_DIR DSM_CONFIG DSM_LOG

where /home/davehil/dsm.opt is the path and file name for your client user options file, and /home/davehil is the directory where you want to store the dsmerror.log file, the executable file, the resource files, and the dsm.sys file.

Setting C Shell Variables

For the C shell, add the DSM_CONFIG and DSM_LOG variables to .cshrc in your $HOME directory. For example:

   setenv DSM_CONFIG /home/davehil/dsm.opt
   setenv DSM_LOG /home/davehil

where /home/davehil/dsm.opt is the path and file name for your client user options file, and /home/davehil is the directory where you want to store the dsmerror.log file.

Setting API Environmental Variables

If you have installed the API, set the following environment variables:

DSMI_DIR
Points to your installation directory. The files dsmtca, dsm.sys, and the language files must reside in the directory pointed to by DSMI_DIR. This environment variable must be present.

DSMI_CONFIG
Full path name of your own client user options file.

DSMI_LOG
Path for dsmerror.log. (cannot be a symbolic link)
Note:End users of applications developed with the API should consult the installation directions for that application for special path names or guidelines for options. Ensure that directories in the environment variables are specified in the path statement. The location of the API library is especially important.

Creating Options Files (Required)

The following sections provide instructions for the root user to set up TSM. These sections cover only the options essential for creating and modifying the client system options file, the client user options file, and the include-exclude options file. See Chapter 9, Setting Processing Options for detailed information about all the available options, their possible values, and the syntactic rules for using them.

Creating the Client System Options File (Required)

During the installation of TSM, a sample client system options file called dsm.sys.smp is provided. The dsm.sys file is used to specify one or more TSM servers to contact for services, and communications options for each server. It can also include authorization options, backup and archive processing options, scheduling options, and HSM space management options.

If you are a TSM authorized user you are responsible for copying the dsm.sys.smp file to dsm.sys in your TSM default installation directory, and editing this file to include the TSM server that you want to connect to. You can edit your dsm.sys file as appropriate for your system.

Attention: If you are reinstalling TSM, do not copy the dsm.sys.smp file to dsm.sys if you have already modified your dsm.sys file and do not want it overwritten.

The following is an example of a client system options file stanza which contains options for a server you want users to contact. You can specify options for more than one server:

   Servername                server_a
   COMMmethod                TCPip
   TCPPort                   1500
   TCPServeraddress          almvmd.almaden.ibm.com

Edit the file using the editor of your choice. You need to obtain server information from your TSM administrator.

All of the sample entries are entered as comments. Enter the appropriate value for an option, and then remove the leading asterisk (*).

For the servername option, enter the name you want to assign to a server to contact for services, for example, server_a. See Servername for more information about this option.

For each servername option entry, use the commmethod option to specify the communication method to use for client server communications. For example, to specify the TCP/IP communication method, enter:

   COMMmethod TCPip

See "Communication Options" for communication protocols supported for your UNIX client. See "Setting Options in a File" for more information about setting options in a file.

As the default, your client node contacts the first server identified in the client system options file. You can specify a different server to contact by entering the servername option in your own client user options files, or by entering that option with a TSM command.

You can also specify a default server and a migration server (if you have the HSM client installed on your workstation) in your client system options file. For more information, see Defaultserver and Migrateserver.

Optional Entries

There are many other options you can set in the client system options file. You are not required to set a value for each option. If you do not set a value for an option, TSM uses a default value. See Chapter 9, Setting Processing Options for a complete list of options.

Creating the Client User Options File

During installation, TSM installs a sample client user options file called dsm.opt.smp into the default installation directory. Figure 1 shows the contents of the sample client user options file.

Figure 1. Contents of the Sample Client User Options File


   * SErvername       A server name defined in the dsm.sys file 

If you are a root user, you can create a default client user options file that can be used by all users on your workstation.

If you did not create a client options file during installation, you can do so by using one of the following methods:

  1. Create a default client user options file by copying dsm.opt.smp to dsm.opt, or a new file name of your choice. The dsm.opt file must reside in the default installation directory or the directory pointed to by the DSM_CONFIG environment variable.
  2. You can also do the following:
    1. From the TSM GUI, select the Utilities menu> Setup Wizard item.
    2. Select the Help me configure the TSM Backup Archive Client checkbox.
    3. Select the create a new options file checkbox.
    4. Follow the instructions on the screen.

You can then edit your dsm.opt file as appropriate for your system, or use the TSM preferences editor by selecting the Edit menu> Preferences item from the TSM GUI. See "Setting Options in a File" for information about setting options in a file.

Attention: If you must reinstall TSM, do not copy the dsm.opt.smp file to dsm.opt if you have already modified your dsm.opt file, or it will be overwritten.

Creating a Customized Client User Options File

If you are a user and want to use different options than those specified in the default client user options file, you can create your own client user options file.

In the client user options file, you can set options for communication protocols between the client and server, and backup, archive, restore, and retrieve processing. For example, you can use the domain option to specify the file systems for which you want TSM to perform incremental backup services. The default is all locally mounted file systems except /tmp.

If you specified more than one TSM server in your client system options file, you can use the servername option to specify the server to use for backup-archive services. If you do not specify a particular server, the client program on your workstation contacts the default server in the client system options file. You can override the specified server for backup-archive services by entering the servername option with a TSM command.

For detailed information about options you can set in the client user options file, see Chapter 9, Setting Processing Options.

You can use one of the following methods to create a your own client user options file:

  1. Contact the root user on your workstation to determine the location of the sample client user options file dsm.opt.smp, and do the following:
    1. Copy dsm.opt.smp to your home directory as dsm.opt, or a new file name of your choice. You can store your client user options file in any directory to which you have write access.
    2. Set the DSM_CONFIG environment variable to point to your new client user options file. For instructions to set this variable, see section, Setting Environment Variables (Optional).
  2. You can also use the following method:
    1. From the TSM GUI, select the Utilities menu> Setup Wizard item.
    2. Select the Help me configure the TSM Backup Archive Client checkbox.
    3. Select the create a new options file checkbox.
    4. Follow the instructions on the screen.

You can then edit your dsm.opt file as appropriate for your system, or use the TSM preferences editor by selecting the Edit menu> Preferences item from the TSM GUI. See "Client Options Reference" for options that are supported on your platform, and detailed information about each option.

Creating an Include-Exclude Options File (Optional)

An include-exclude options file contains statements that identify any files you want to specifically include or exclude from backup services. For example, you can exclude core files, local caches of network file systems, files that contain compiled object code easily reproducible by other methods, and operating system files. You can enter broad statements that exclude entire groups of files. Then, if necessary, you can enter include statements to make exceptions to those broad statements.

Another important use for an include-exclude options file is to use include statements to assign specific management classes to specific files or groups of files. TSM uses a default management class for any files to which you do not explicitly assign a specific management class.

If you do not create an include-exclude options file, TSM considers all files for backup services and uses the default management class.

Figure 2 shows a sample include-exclude options file.

Figure 2. Sample Include-Exclude Options File


exclude /.../core
include /home/.../*  personal_files
include /home/davehil/dsnew/.../*
include /home/davehil/driver5/.../*  source_code
exclude /home/root/cron.log
 

The specification you enter for an include or exclude statement must end with a file name. You can use a wildcard in place of a specific file name. In the sample include-exclude options file, personal_files and source_code identify management classes to assign to specific files.

For more information about the include-exclude options file, see Chapter 8, "Creating an Include-Exclude List" and the user's guides listed in Table 2. For more information about management classes, see Using Management Classes with Include.

If you did not create an include-exclude list during installation, you can do so by using one of the following methods:

  1. From the TSM GUI:
    1. Select the Utilities menu> Setup Wizard item.
    2. Select the Help me configure the TSM Backup Archive Client checkbox.
    3. Follow the instructions on the screen.
  2. You can also create an include-exclude options file by performing the following steps:
    1. Determine your include and exclude requirements.
    2. Create a file with a name of your choice. The file can be located in any directory to which all users on your workstation have read access.
    3. Enter your include and exclude statements. For detailed information about the include and exclude options, see Chapter 8, Creating an Include-Exclude List.
    4. Enter the name of your include-exclude options file in your client system options file using the inclexcl option.

Registering Your Workstation with a Server (Required)

This is the final required step you must complete before you can use TSM. You can complete the optional setup steps before or after you complete this one.

If you plan to use a Web client with an enterprise management server, ensure that you are assigned an administrative user id with system privilege, policy privilege, client access, or clientowner authority.

Before you request services from a TSM server, you must register your workstation with that server. Your workstation is registered as a single client node for all users.

Your TSM administrator chooses whether registration is closed or open.

Using Closed Registration

With closed registration, a TSM administrator must register your workstation as a client node with the server.

If your enterprise uses closed registration, you need to provide the following information to your administrator (the administrator may provide some of this information):

Your administrator defines the following for you:

Using Open Registration

With open registration, a root user can register your workstation as a client node with the server. Your workstation must be registered before anyone can use TSM on that node.

Use the dsm command to start a session with TSM using the graphical user interface. Use a dsmc command to start a session with TSM using the command-line interface.

The first time you start a TSM session, TSM prompts you for information necessary to register your workstation with a server identified in your client system options file.

You need to supply the following information:

To register your workstation with additional servers, enter the dsm command or a dsmc command with the servername option for each server. For example:

   dsm -servername=dsmserv

where dsmserv is the name of a server identified in your client system options file.

TSM prompts you for the information necessary to register your workstation with the server you specify.

When you use open registration:

If necessary, your TSM administrator can change these defaults later.


Starting TSM

Before you can start a session with the TSM graphical user interface, the X Window System must be running on your workstation. If you do not have the X Window System running on your workstation, you can use the TSM command-line interface.

From your workstation, you can use the rlogin command to log on to OS/390 UNIX System Services instead of using the 3270 terminal emulation so its behavior and appearance is more like UNIX.

If the X Window System is running and the TSM icon is on your desktop, TSM is running. You can double-click on the icon to open the TSM window.

If the TSM icon does not appear on your desktop, you must start TSM using one of the following commands:

dsm
Starts a TSM graphical user interface session in the foreground.
dsm &
Starts a TSM graphical user interface session in the background.
dsmc
Starts a TSM command line session.

Your TSM administrator can require you to use a password to connect to the TSM server. TSM prompts you for the password if one is required. Contact your administrator if you do not know your password.

When the GUI client initially starts up, and does not find an options file, you are presented with a setup wizard that will guide you through the process of configuring your client. You can also use the setup wizard by selecting the Utilities menu> Setup Wizard item.

Note:If you are working on an AIX workstation, and you want to back up or archive AFS or DFS files, check with the root user responsible for setting up TSM on your workstation to find out whether you can use the AFS or DFS versions of TSM. See Appendix A, Special Considerations for AFS/DFS on AIX for more information.

Starting TSM Automatically

You can start the TSM client scheduler automatically when you start your operating system. If the TSM administrator has defined schedules for your client node, starting the client scheduler allows TSM to back up your machine automatically (or perform other scheduled actions). See TSM for UNIX Using the Backup-Archive Clients for more information about the client scheduler.

To start the client scheduler automatically, perform the following:

  1. Ensure that the passwordaccess option is set to generate in your client system options file.
  2. For non-OS/390 UNIX: Add the following command to the /etc/inittab file:
    adsm::once:/usr/bin/dsmc sched > /dev/null 2>&1 # TSM scheduler
    
    Note:You must include the redirection to /dev/null in the command.
  3. For the OS/390 UNIX do the following:
    1. Create a shell script called /usr/lpp/adsm/bin/rundsmc containing the following entries:
         cd /usr/lpp/adsm/bin
         ./dsmc schedule
      
      Note:This prevents two jobs with same name from being created, and enables automatic shutdown.
    2. Add the following entries in the /etc/rc file to set environment variables to retrieve the servername and nodename options from dsm.sys and to start the TSM client scheduler, as follows:
         # Set environment variables to retrieve the servername and
         # nodename options from dsm.sys.
         export DSM_DIR=/usr/lpp/adsm/bin
         export DSM_CONFIG=/usr/lpp/adsm/bin/dsm.opt
         # Start the TSM Client scheduler and redirect outputs to
         # schedule.out instead of the /etc/log file.
         _BPX_JOBNAME='ADSMCLNT' /usr/lpp/adsm/bin/rundsmc
         1>/usr/lpp/adsm/bin/schedule.out 2>&1 &
       
      
      Note:Enter the _BPX_JOBNAME entry on a single line in the /etc/rc file.

Starting TSM: Advanced Considerations

You can include TSM options when you issue dsm commands. For example, you can use options to modify the format used to display dates, times, and numbers, or you can use an option to include your password so that TSM does not prompt you for it. (However, if you include the password option, your password can be seen by anyone who sees you enter the command.)

You can use any of the following options when you start TSM:

For example, if more than one TSM server is available, and you want to use a different server for backup-archive services than the one specified in your client user options file, you can enter the following, where server_b is the name of the server you want to contact:

   dsm -servername=server_b

See Chapter 9, "Setting Processing Options" for detailed information about these options.


Starting the Web Client

You can use the Web client to perform backup, archive, restore, and retrieve operations from any machine, or platform that supports a Java 1.1.6-capable browser, such as Netscape Navigator 4.06 or higher, and Microsoft Internet Explorer 4.01 or higher. Using the Web client, you can back up and restore your own data, or a TSM administrator can centralize the backup or restore operations of many TSM clients. To use it, simply point your Web browser at any TSM client machine that is running the Web client. The Web client is only supported on a server that is Version 3 or higher.

To use the Web client, perform the following steps

  1. If you do not already have password files generated for TSM clients, specify passwordaccess generate in the dsm.sys options file. See Passwordaccess for more information about options files.
  2. To create the TSM password file, start the native backup-archive client by entering:

    dsmc query session
    

    and, when prompted, enter your user ID and password.

  3. Quit from the native TSM backup-archive client.
  4. Start the TSM Client Acceptor daemon by entering the dsmcad command. The TSM Web client agent service automatically starts when needed.

    The only options you can use with the dsmcad command are optfile, httpport, and httpsport.

    All the Web client messages are written to the Web client log file, dsmwebcl.log. Error messages are also written to the TSM error log file. The dsmwebcl.log file and the TSM error log file are located in the same directory specified by the errorlogname option.

    See Chapter 9, "Setting Processing Options" for more information.

  5. To use a Web client with an enterprise management server, ensure that you were assigned an administrative user id with system privilege, policy privilege, client access, or clientowner authority. If your server does not support enterprise management, then use your node name and password when prompted by the Web client. To determine whether your server supports enterprise management, contact your server administrator.
    Note:Use the revokeremoteaccess option to restrict an administrator with client access privilege from accessing your workstation through the Web client. Administrators with clientowner privilege, system privilege, or policy privilege can access the Web client. For more information see Revokeremoteaccess.
  6. You can access the TSM Web client using any browser that is Java1.1.6-capable by entering the following URL:
    http://your_machine_name:1581
    

    where your_machine_name is the hostname of the machine running the TSM Web client.

    Port 1581 is the default port number. The administrator can set a different port number using the httpport option. See Httpport for more information about the httpport option.

    The Web client workstation can also be accessed through the TSM system administrative GUI.

If you want to use the Web client with secure socket layer (SSL) communications, which is only supported on the AIX clients, then see Appendix E, "TSM Web Client Secure Socket Layer" for additional information.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]