Вы находитесь на странице: 1из 8

TSM Client Installation UNIX LINUX AIX

1. Mount the Tivoli Storage Manager UNIX client DVD to /dvd. 2. Change to the directory where the packages are stored on the DVD: cd /dvd/client/linux86 3. Install the 64-bit GSKit packages. In this example, the "8.x.x.x" characters represent the GSKIT version on the DVD: rpm -U gskcrypt64-8.x.x.x.linux.x86_64.rpm gskssl648.x.x.x.linux.x86_64.rpm 4. Install the 64-bit Tivoli Storage Manager API, and optionally install the common inventory technology package needed to support processor value unit (PVU) calculations. a. Required: install the Tivoli Storage Manager API: rpm -i TIVsm-API64.x86_64.rpm b. Optional: Install the common inventory technology package used by the API. This package is dependent on the API so it must be installed after the API package is installed. rpm -i TIVsm-APIcit.x86_64.rpm 5. If you only need the API installed, you can stop here. The rest of the steps in this procedure describe how to install the Backup-Archive Client components and an optional client package that is needed only if you want the client to send PVU metrics to the server. Also described in subsequent steps are the installation of the packages that are needed if you want to perform journal-based backups, and the installation of additional languages. 6. Install the backup-archive Java client, command line client, administrative client, web client, and the documentation; optionally install the common inventory technology package needed to support processor value unit (PVU) calculations. a. Install the backup-archive client components. rpm -i TIVsm-BA.x86_64.rpm b. Optional: install the common inventory technology package the client uses to send PVU metrics to the server. This package is dependent on the client package so it must be installed after the client package is installed. rpm -i TIVsm-BAcit.x86_64.rpm 7. Optional: If you want to use journal-based backups, install the packages needed to support the filepath component and journal based backups. Install the filepath component first and ensure that you install the filepath package that is appropriate for the operating system on the client computer. Specify one of the following package names for the filepath package name: o TIVsm-filepath-version-rhel55.x86_64.rpm, for Red Hat Enterprise Linux 5.5. o TIVsm-filepath-version-rhel60.x86_64.rpm, for Red Hat Enterprise Linux 6.0 o TIVsm-filepath-version-sles10sp3.x86_64.rpm, for SUSE Linux Enterprise Server 10, SP 3, default kernel. o TIVsm-filepath-version-sles11sp1.x86_64.rpm, for SUSE Linux Enterprise Server 11, SP 1. rpm -i TIVsm-filepath-version_vendor.x86_64.rpm TIVsm-JBB.x86_64.rpm If none of the above packages matches your Linux version, you must compile Filepath from source code. The Linux Filepath kernel module is licensed pursuant to the terms of the GNU General Public License ("GPL"). To request the Linux Filepath source code, send an email totsmosreq@us.ibm.com. Note: The filepath component that is distributed for SUSE Linux Enterprise Server 10, SP3, is compiled for the default SLES kernel. If you have a multiprocessor system and use the SMP kernel, you need to compile filepath from the source.

8. Install the snapshot difference incremental backup support for NetApp and N-Series file servers by entering the following command: rpm -i TIVsm-BAhdw.x86_64.rpm 9. The default language installed with the backup-archive client is American English. Use the general syntax shown in this step to install additional languages. Substitute the language identifier shown in the following table for the language_ID variable in the sample command: rpm -i TIVsm-msg.language_ID.x86_64.rpm

Table 2. Language pack identifiers Language Czech French German Hungarian Italian Japanese Korean Polish Portuguese Russian Spanish Traditional Chinese (EUC) Traditional Chinese Big5 CS_CZ FR_FR DE_DE HU_HU IT_IT JA_JP KO_KR PL_PL PT_BR RU_RU ES_ES ZH_CN ZH_TW Language identifier

Configurations
For the other platforms, as the root user, copy the dsm.sys.smp file to dsm.sys and then edit that file to configure your settings. The client looks for dsm.sys in the directory specified by the DMS_DIR environment variable (if it is set and exported), and then in the installation directory. Important: If you are reinstalling and you want to keep your existing dsm.sys file intact, do not copy the dsm.sys.smp file to dsm.sys. Use the dsm.sys file to specify one or more servers to contact for services, and communications options for each server. This file can also include authorization options, backup and archive processing options, and scheduling options. Edit dsm.sys to include the server or servers to which you want to connect. The following is an example of a client system-options file stanza which contains the required options for a server you want users to contact. You can specify options for more than one server: Servername COMMMethod TCPPort TCPServeraddress server_a TCPip 1500 node.domain.company.com

Important: If you want to use the Web client, you must also specify the passwordaccess=generate option, and log in with the client to save the password. As the default, your client node contacts the first server identified in the dsm.sys file. You can specify a different server to contact by entering theservername option in your own client user-options file (dsm.opt), or by entering that option with a command. You can also specify a default server and a migration server (if you have the HSM client installed on your workstation) in your dsm.sys file. The dsm.sys file can also contain the following option categories: Communication options Backup and archive processing options Restore and retrieve processing options Scheduling options Authorization options Error processing options Transaction processing option Web client options

You can modify your dsm.sys file using one of the following methods: From the client Java GUI main window, select Edit > Client Preferences. Use your favorite text editor.

Creating a default client user-options file


During installation, a sample client user-options file called dsm.opt.smp is placed in the installation directory. Creating a default client user-options file (dsm.opt) is an optional root user or authorized user task. You can use the default client user-options file to define the following options: Backup and archive processing options Restore and retrieve processing options Scheduling options Format options Command processing options Authorization options Error processing options Transaction processing option Web client options

If you are a root user or a system administrator, you can create or modify a default client user-options file for all users on your workstation. From the UNIX command line: 1. Change to the directory containing the sample file. 2. For systems other than Solaris, copy the dsm.opt.smp file to dsm.opt or to a new file name of your choice. 3. For UNIX and Linux (other than Mac OS X), use the following information: o For the default client user-options file: You can store your default client user-options file in the same directory as the dsm.sys.smp file, or in any directory for which you have write access. If you rename your client user-options file or place it in a different directory, you can set the DSM_CONFIG environment variable or use the optfile option to point to your new client user-options file.

Creating a customized client user-options file


If you want to use different options than those specified in the default client user-options file (dsm.opt), you can create your own client user-options file. You can set all of the options that can be set in the default user options file. Creating a customized client user-options file (dsm.opt) is an optional root user or authorized user task. To create or modify a client user-options file, use the following method: 1. Contact the Tivoli Storage Manager administrator on your workstation to determine the location of the sample client user-options file dsm.opt.smp, and to get the TCP/IP address of the backup server you are connecting to and the port it listens on. 2. 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. 3. Set the DSM_CONFIG environment variable to point to your new client user-options file.

4. Edit your dsm.opt file as appropriate for your system or use the Tivoli Storage Manager Preferences editor by selecting Edit > Preferences from the Tivoli Storage ManagerJava GUI. Once you have created an options file, you can use the following steps to edit your options file from the GUI. 1. Open the Edit menu and select Preferences. 2. Make any necessary changes, then click OK to save those changes.

Set processing environment variables


There are some circumstances where you must set the environment variables. You must set the environment variables in either of the following circumstances: You want to invoke Tivoli Storage Manager from a directory other than the directory where Tivoli Storage Manager is installed You want to specify a different options file for the backup-archive client, the administrative client, or both. Tip: You can also specify an alternate client options file for the command-line client (not the administrative client) using the optfile option. There are three environment variables you can set which affect Tivoli Storage Manager processing: PATH Includes the directory where the executable file dsmc resides. DSM_DIR Specifies the directory where the executable file dsmc, the resource files, and the dsm.sys file reside. You cannot specify the root (/) directory for DSM_DIR. Refer to the installation section for your operating system to find the default installation directory information. When you request an image backup, image restore, snapshot-based file backup, NAS backup, or NAS restore, Tivoli Storage Manager uses the DSM_DIR environment variable to locate the corresponding plug-in library. If DSM_DIR is not set, the client looks for the plug-in library in the following directories: AIX /usr/tivoli/tsm/client/ba/bin/plugins HP-UX, all Linux clients, and Solaris /opt/tivoli/tsm/client/ba/bin/plugins DSM_CONFIG Specifies the fully-qualified path and file name of the client user options file for users who create their own personalized options file. The root directory is not a valid value for DSM_CONFIG.

Specify a directory other than the root directory. If DSM_CONFIG is not set, or the -optfile option is not used, the client user options file is expected to satisfy these requirements: 1. The options file must be named dsm.opt. 2. For UNIX clients other than Mac OS X, if DSM_DIR is not set, then the file must reside in the default installation directory. If DSM_DIR is set, then the file must reside in the directory specified by DSM_DIR.

Set Bourne and Korn shell variables


Enter the environment variables in the .profile file (Korn shell) or .bash_profile file (Bourne shell) in your $HOME directory. The following is an example, where /home/davehil/dsm.opt is the path and file name for your client user-options file, and the /home/davehildirectory is where you want to store the dsmerror.log file, executable file, resource files, and dsm.sys file. DSM_DIR=/home/davehil DSM_CONFIG=/home/davehil/dsm.opt DSM_LOG=/home/davehil export DSM_DIR DSM_CONFIG DSM_LOG

Set C shell variables


For the C shell, add the DSM_CONFIG, DSM_LOG and DSM_DIR variables to the .cshrc file in your $HOME directory. The following is an example, where /home/davehil/dsm.opt is the path and file name for your client user-options file, and the /home/davehildirectory is where you want to store the dsmerror.log file, executable file, resource files, and dsm.sys file. setenv DSM_DIR /home/davehil setenv DSM_CONFIG /home/davehil/dsm.opt setenv DSM_LOG /home/davehil

Set API environment variables


If you installed the Tivoli Storage Manager client 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 (dsm.opt). DSMI_LOG Path for dsierror.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.

Configuring the Web client


This task guides you through the steps to configure the Web client. To configure the Web client from the command line, perform the following steps: 1. 2. 3. If MANAGEDServices schedule is set, specify MANAGEDServices webclient schedule in the dsm.sys file. Ensure that you specify passwordaccess generate in the dsm.sys file. To generate the Tivoli Storage Manager password, start the backup-archive client by entering the following command: dsmc query session When prompted, enter your user ID and password. Start the client acceptor daemon (CAD) by entering the following command: dsmcad To access the Web client, enter the following URL from any supported browser, where your_machine_name is the host name of the workstation running the Web client.: http://your_machine_name:1581 Port 1581 is the default port number. You can set a different port number using the httpport option. The Tivoli Storage Manager Remote Client Agent daemon must not be started manually. It is automatically started by the Tivoli Storage ManagerClient Acceptor daemon when needed. The options applicable only to the dsmcad program are httpport, managedservices, and webports. You can also use options such as optfile orerrorlogname. You can use the managedservices option to specify whether the Tivoli Storage Manager client acceptor daemon also manages the Tivoli Storage Manager scheduler. All Web client messages are written to the Web client log file, dsmwebcl.log. Error messages are written to the error log file dsmerror.log, or the file you specify with the errorlogname option. The dsmwebcl.log and dsmerror.log files reside in the directory you specify with the DSM_LOG environment variable or in the current working directory. Set this environment variable to the directory where the log files should reside. The root directory is not a valid value for DSM_LOG. Specify a directory other than the root directory.

4.

5.

After installing and configuring the Web client on your workstation you can use the Web client to perform backup, archive, restore, and retrieve operations.