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 7 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/support/storage_mgr/tivolimain.html. |
Table 7. 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 |
Installing the Linux Client | Installing the Linux Client |
Installing the NUMA-Q DYNIX/ptx Clients | Installing the NUMA-Q DYNIX/ptx Clients |
For information on Installing the OS/390 UNIX System Services Client, see
the following publications:
|
|
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 |
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.
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).
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:
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:
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:
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:
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:
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:
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:
/cdrom/tsmcli/linux86
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. |
rpm -i TIVsm-API.i386.rpm
During installation :
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/ptx/ptxtsmc.pkg package:
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:
pkgadd -d /CD-ROM/tsmcli/ptx/ptxtsmc.pkg
Note: | Replace the word CD-ROM with the file system of the CD-ROM drive on your system. |
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:
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:
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:
Use the following procedure to install the TSM clients:
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:
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:
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:
pkgadd -d /cdrom/tsmcli/solaris TIVsmCapi TIVsmCba
Note: | The Client needs the API for Raw Logical Volume backup, so the API must installed before the client. |
pkgadd -d /cdrom/tsmcli/solaris TIVsmCdoc
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 :
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:
To remove previous client versions, log in as the root user and enter the following command:
/usr/sbin/setld -d TIVsmCba TIVsmCapi
Use the following procedure to install the TSM clients:
setld -l /CD-ROM/tsmcli/tru64/ TIVsmCba TIVsmCapi
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:
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:
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:
pkgadd -d /CD-ROM/tsmcli/unixware/unixwaretsm.pkg
Note: | Replace the word CD-ROM with the file system of the CD-ROM drive on your system. |
During installation:
If you move the TSM files to another directory, you must perform the following steps:
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
The language used for the AIX, HP-UX, and Solaris clients is specified using the LANG environment variable. For all other UNIX platforms you can use American English only.
There are three environment variables that you can set to point to files that TSM uses:
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 |
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.
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.
If you have installed the API, set the following environment variables:
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. |
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 8, "Setting Processing Options" for detailed information about all the available options, their possible values, and the syntactic rules for using them.
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 must reinstall TSM, and you want to keep your existing dsm.sys file intact, do not copy the dsm.sys.smp file to dsm.sys.
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.
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 8, Setting Processing Options for a complete list of options.
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:
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, and you want to keep your existing dsm.opt file intact, do not copy the dsm.opt.smp file to dsm.opt.
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 8, Setting Processing Options.
You can use one of the following methods to create a your own client user options file:
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.
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 is 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 7, "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:
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.
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:
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.
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.
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:
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.
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. |
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:
adsm::once:/usr/bin/dsmc sched > /dev/null 2>&1 # TSM scheduler
Note: | You must include the redirection to /dev/null in the command. |
cd /tivoli/tsm/client/ba/bin ./dsmc schedule
Note: | This prevents two jobs with same name from being created, and enables automatic shutdown. |
# Set environment variables to retrieve the servername and # nodename options from dsm.sys. export DSM_DIR=/tivoli/tsm/client/ba/bin export DSM_CONFIG=/tivoli/tsm/client/ba/bin/dsm.opt # Start the TSM Client scheduler and redirect outputs to # schedule.out instead of the /etc/log file. _BPX_JOBNAME='ADSMCLNT' /tivoli/tsm/client/ba/bin/rundsmc 1>/tivoli/tsm/client/ba/bin/schedule.out 2>&1 &
Note: | Enter the _BPX_JOBNAME entry on a single line in the /etc/rc file. |
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 8, "Setting Processing Options" for detailed information about these options.
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
dsmc query session
and, when prompted, enter your user ID and password.
The only options you can use on the dsmcad command line 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 8, "Setting Processing Options" for more information.
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. |
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 system 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 C, "TSM Web Client Secure Socket Layer" for additional information.