Tivoli Storage Manager Installing the Clients


Chapter 4. Installing Windows 95, 98, NT, and 2000 Clients

This chapter provides instructions to install and set up TSM for Windows 95, Windows 98, Windows NT, or Windows 2000 as a client workstation.

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.


Installing the Client Program (Required)

The following instructions assume that Windows NT, Windows 95, Windows 98, or Windows 2000 is already running on the client workstation. To install the Windows NT, Windows 95, Windows 98, or Windows 2000 client portion of TSM, do the following:

Note:For Windows NT and 2000: If you are using a Windows Terminal Server, you can optionally install the client program by selecting Settings> Control Panel> Add/Remove Programs, and specify that the installation is to be shared by all users.
  1. Insert the CD-ROM containing the TSM Windows client into your CD-ROM drive.
  2. Select Run from the Start menu.
  3. Type the name of the setup program in the Open field.

    For Intel: type x:\tsmcli\win32\intel\setup where x is your CD-ROM drive. Click OK.

  4. Follow the instructions displayed on the screen. If previous TSM client installations exist, see "Reinstalling the Client" for more information.

    Installation Setup Types:
    There are two setup types:
    • Complete: This setup gives you the Backup-Archive Client, the API, and the Web Client.
    • Custom- This setup lets you select the options you need, including the Administrative command line client and the ODBC driver.

      In the Select Components window, highlight the Client Files item and click the Change button to select the clients you want to install.

      Notes:

      1. The Backup-Archive Client, the API, and the Web Client are interdependent and are pre-selected. If you select the Backup-Archive Client, you must also select the API. Simularly, if you select the Web client, you must also select the Backup-Archive Client and the API.

      2. The Backup-Archive Client component includes the client scheduler files. See "Starting the Client Scheduler" for more information about the client scheduler.

      3. The TSM installation program automatically detects the language version of Windows that you are running, and installs the TSM language files for that language. By default, U.S. English language support is also installed.

      4. If you select the backup-archive client and the administrator client, install both clients into a single directory. Both clients will share an options file. Both clients must be uninstalled at the same time; neither client can be uninstalled independently.

      5. Install support files for your communication method, if support files are required.

    If you selected the Custom setup option, the exact amount of disk space required for this option and the amount of space available appear at the bottom of the window. Make sure there is enough disk space for the TSM client files on the destination drive. The installation program will not allow installation to a destination drive with insufficient disk space.

  5. Click on Finish once the installation process has completed.
    Note:When the installation process completes, the setup wizard is launched automatically if no dsm.opt file is present, to help you configure an initial options file. See "Client Options Reference" for options supported on your platform, and detailed information about each option.

For more information on using the ODBC driver and the Administrative client, see Tivoli Storage Manager for Windows Administrator's Guide, GC35-0410.

TSM in the Windows 95, 98, NT, and 2000 Environments

The installation process creates a program group containing client components that you select. This program folder allows easy access and running of the TSM client within the Windows environment.

If there are other TSM clients installed on the same system, use caution when changing from one client to another because environment variables such as DSM_DIR can be shared by more than one client of different platforms.

Reinstalling the Client

Back up any files you want to retain before you reinstall the client. Existing dsm.opt files are preserved and the new sample options file is copied to dsm.new.

To reinstall the TSM client, we recommend that you use the installation CD-ROM to install any files (the files on the installation CD-ROM are in compressed format).

If previous TSM client installations exist, TSM advises you to reinstall into the same directory. This will install the new TSM client over a previous TSM client installation. If an ADSM V3R1 Administrative GUI exists, it will not be removed.

If you install the TSM client files in a different directory than the one where you previously installed them, you should uninstall previous versions first, before installing the new version to save disk space. To uninstall, and then reinstall TSM:

  1. Select the Start menu> Settings> Control Panel> Add/Remove Programs.
  2. Select the Tivoli Storage Manager client from the list of installed programs.
  3. For Windows 95, 98, and NT: Click the Add/Remove button. For Windows 2000: Click the Remove button. Click OK.
    1. For components that were installed using TSM 4.1 or higher: Click the Next button until you see a panel containing the Modify, Repair, and Remove options.
      1. To remove all TSM components, click Remove then click the Next button. Complete the setup wizard.
      2. To remove TSM individual components, select Modify then click the Next button. The Custom Setup panel displays:
        1. Select component you want to remove and select This feature will not be available.
        2. Complete the setup wizard
    2. For TSM components installed prior to TSM V4.1: The TSM uninstall program displays:
      1. Select Uninstall from the program folder containing TSM.
      2. Select the items to uninstall from the uninstall list.
      3. Click the Remove button.
      4. Restart the Windows session, failure to do so prior to installing the new client may result in files inadvertently removed at the restart of a new session.
  4. Start the reinstallation the same way you started the previous installation. See Installing the Client Program (Required) for instructions.

Setting Environment Variables (Optional)

No change of the environment variables is necessary, except for the following conditions:

  1. You want to run TSM from a directory other than the one specified during installation.
  2. You want to specify a different options file for the Backup-Archive Client, the Administrator Client, or both.
  3. You elected to install the clients into separate directories, but you want to use a common options file.

If one of these conditions exist, then you need to set the following environment variables:

PATH
This is the default search path the operating system uses to locate executable files. Set this to include the fully qualified paths of the TSM client directories.

DSM_CONFIG
TSM uses this environment variable to locate the client options file.
Note:Keep the client options file in a common location if both the backup-archive and administrative clients use it.

DSM_DIR
TSM uses this environment variable to locate all other client files.

Ensure the environment variables meet the following guidelines:

  1. Include the directory where the TSM executable files (for example, dsm.exe) reside in the current PATH statement. For example:
       SET PATH=c:\"program files"\tivoli\tsm\baclient;%PATH%
    
  2. Define the DSM_CONFIG environment variable to point to where your options file resides. For example:
       SET DSM_CONFIG=c:\program files\tivoli\tsm\baclient\dsm.opt
    
  3. Define the DSM_DIR environment variable to point to the directory where all other TSM files reside. For example:
       SET DSM_DIR=c:\program files\tivoli\tsm\baclient
    

Creating the Options File (Required)

TSM uses an options file to specify certain information related to your TSM session. This information includes your choice of communication protocols, the name of your node, authorization options, backup and archive processing options, and scheduling options. These options are in effect for the entire TSM session, but can be overridden by using command line options.

TSM provides sample options files called ba_dsm.opt (backup-archive client) and sa_dsm.opt (administrator client). These are generic configuration files that contain communication parameters normally used in a Windows environment.

When the installation process completes, the setup wizard is launched automatically if no dsm.opt file is present, to help you configure an initial options file. See "Client Options Reference" for options supported on your platform, and detailed information about each option.

You can use one of the following methods to edit your client options file:

Creating a Shared Directory Options File

A TSM Windows NT or Windows 2000 server administrator can generate client options files in a shared directory. Windows 95, 98, NT, and 2000 clients can access the shared directory and create the client options file. For more information see Tivoli Storage Manager for Windows Quick Start, GC35-0409.

Enabling Communications (Required)

One of the most important purposes of the options file is to define the communication method used between your workstation and the TSM server.

Use the commmethod option to specify a communication protocol. For example, to use the TCP/IP communication method, enter:

   COMMmethod TCPIP

The default value for commmethod is TCP/IP. Therefore, you do not need to define COMMmethod in the options file. However, either a dsm.opt file or the options file you pointed to in the DSM_CONFIG environment variable must exist and must contain the required communication options. See "Communication Options" for communication protocols that are supported for Windows 98, Windows 98, Windows NT, and Windows 2000 clients.

Setting Your Node Name (Required for Backup-Archive Client Only)

Use the nodename option to indicate the name of your node so that you can register with the TSM server. If you do not specify a node name, TSM uses the machine name. For more information about registration requirements, see Registering Your Workstation with the Server (Required).

Creating an Include-Exclude List (Required for Backup-Archive Client Only)

An include-exclude list contains statements that identify any specific files you want to include or exclude from backup services. This list is contained in the dsm.opt file.

For example, you might want to exclude all swap files, easily reproducible files (such as object files), and operating system files. You can enter broad statements in the dsm.opt file that exclude entire groups of files. Then, you can enter include statements to make exceptions to those broad statements.

The ba_dsm.opt sample file provided at installation time contains a sample include-exclude list. See "Excluding System Files" for a minimum include-exclude list that you should include in your dsm.opt file.

Another important use for an include-exclude list is to use include statements to assign specific management classes to specific files or groups of files (for more information on management classes refer to Using Management Classes with Include). TSM uses a default management class for any files to which you do not explicitly assign a specific management class.

If an include-exclude list does not exist in the options file, TSM considers all files for backup services and uses the default management class for backup and archive services.

For information that can help you decide whether to create an include-exclude list, see Chapter 7, Creating an Include-Exclude List.

If you did not create an include-exclude list after installation, you can use 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. Select the update my options file checkbox.
    4. Follow the instructions on the screen to create your include-exclude list.
  2. You can also create an include-exclude list, by performing the following steps:
    1. Determine your include and exclude requirements.
    2. Locate the include-exclude section in your dsm.opt file.
    3. Enter your include and exclude statements. See Chapter 7, Creating an Include-Exclude List for details.
    4. Save the file as dsm.opt or as the file specified in the DSM_CONFIG environment variable.

To modify the options file, use the preferences editor by selecting the Edit menu> Preferences item.

Creating Multiple Options Files (For Backup-Archive Client Only)

You can create multiple options files if you have to work with multiple servers, or find that you need multiple sets of parameters to perform TSM tasks.

Suppose you want to back up your files to one TSM server (server a), and archive files to another TSM server (server b). Instead of editing the dsm.opt file each time you want to connect to a different server, set up two options files. For example, create the options files a.opt for server a, and b.opt for server b, then do one of the following:

  1. Use the copy command to replace the dsm.opt file with the appropriate options file before you start the TSM session. For example:
       copy a.opt dsm.opt
       dsm
    
  2. Use the optfile option on the command line to specify the options file you to use. For example:
       dsm -optfile=b.opt
    
Note:The directory path where the TSM executable files are located must be included in the PATH environment variable or you must enter a fully qualified path. For example, d:\win32app\dsm.

You can also override the server specified in dsm.opt by using command line options. For example:

   dsm -TCPS=myserver -NODE=mynode -TCPPORT=1599

Registering Your Workstation with the Server (Required)

If you plan 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.

Before you can begin requesting services from a TSM server, the server must recognize your workstation. TSM uses a node name and a password to identify each workstation. TSM maintains a password for each node name. The process of setting up a node name and password is called registration. After you register your workstation with a server, you can begin using TSM to back up, archive, restore, and retrieve files.

TSM provides two types of registration: open and closed. Your TSM administrator chooses the type of registration for your site. If the TSM server administrator sets the authentication option to off, a TSM password is not required.

Using Closed Registration

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

If the TSM server uses closed registration, you need to provide contact information, such as your name, user ID, and contact information, to your administrator.

Your administrator defines the following for you:

Using Open Registration

With open registration, you can register your workstation as a client node with the server.

The first time you start a session, TSM prompts you for contact information necessary to register your workstation with the server identified in your options file. If your administrator has set authentication to on, you need to supply a password.

When you use open registration:

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


Starting TSM

To start the TSM Backup-Archive client:

To start the TSM Administrator client:

When using the Administrative client command line, you must start the TSM client from the TSM directory or include the directory in the issued command, unless you update your environment using the SET command on the command line, or the Environment tab under the System icon in the Control Panel.

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.

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.

Considerations for NT and 2000 TSM Client Services

The following TSM services can be installed during installation or by using the TSM Client Service Configuration Utility:

For more information about using the TSM Client Service Configuration Utility to install the Client Acceptor Service and Remote Client Agent Service, see Appendix B, "Using the Scheduler Service Configuration Utility for Windows NT, 2000".

To install and configure TSM services on the system using the TSM Client Services Installation Utility, you must belong to a local administrator account or a domain administrator account. To back up files, you must also have access rights on the local drive or directory containing those files.

By default TSM client services are installed to run under the local system account. Since the service uses logon properties such as persistent drive mappings, and local search path and environment variables of the account into which they are logged, it may be desirable to have the services logged on by a domain account.

Also, since local accounts do not have domain credentials, domain resources, such as network drives, can only be accessed by services configured to run under a domain authorized account using dsmcutil or the Service Control Panel Application. Any non-system account (local or domain) must possess the following rights:

Without these rights, users can only backup files they own, but not files owned by other users or the system registry.

These are local user rights and must be set using the local User Manager application, and domain accounts may not automatically be enabled for them. Domain accounts may be granted local rights by the local User Manager.

The account must also have the following permissions to the HKEY_LOCAL_MACHINE, HKEY_KEY_USERS, and HKEY_CURRENT_USER registry hives:

The local system account and local Administrator group possess these permissions by default. Other accounts/groups (including domain Administrators) must be granted these permissions either explicitly via the registry editor security dialog (regedt32), or implicitly by adding the account/group to the local Administrators group via the local User Manager (recommended).

Starting the Client Scheduler

To start the TSM Scheduler, use one of the following methods:

When you start the client scheduler, it runs continuously until you close the window, shut down your system, or log out of your system.

You can also start multiple client scheduler services on your system to back up different file systems under different node names.

Starting TSM: Advanced Considerations

You can include TSM options on the command line, or by modifying the settings for the TSM icon. For example, you can modify the format used to display dates, times, and numbers, or you can include your password so that TSM does not prompt for it. (However, if you include the password option, your password can be seen by someone who sees you enter the command or who looks in your icon settings).

For example, you might have two machines that back up files to a TSM server under separate node names. If you want to recover a file from one machine (JONES1) while at the other machine (JONES2), you can start TSM using the nodename option specifying JONES1:

   start dsm -nodename=jones1

Attention: For Windows 95 and Windows 98, be careful if you use TSM in this way. Do not attempt to do an incremental backup from the JONES2 machine while connected to TSM as JONES1. If the drive labels are the same on the JONES1 and JONES2 machines, the incremental backup will expire any files that are not on the JONES2 machine, even if they still exist on JONES1. You could lose valuable backup generations.

For information about getting started with the TSM Windows graphical user interface, see TSM for Windows Using the Backup-Archive Clients, order number SH26-4117.


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, you can specify the URL of 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. From the TSM GUI, select the Utilities menu> Setup Wizard item.
  2. Select the Help me configure the TSM Web Client checkbox.
  3. Follow the instructions on the screen to configure and use the TSM Web client.

To install and configure the Web client from the command line, perform the following steps:

  1. If you do not already have password files generated for TSM clients, specify passwordaccess generate in the dsm.opt 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. Start the TSM Client Acceptor service:
    For Windows 95 and 98: Enter the dsmcad command.
    For Windows NT: Select the Start button> Settings> Control Panel> Services. In the Services window select TSM Client Acceptor and press the Start button.
    For Windows 2000: Select the Start button> Administrative Tools> Computer Management.
    Expand the System Tools sub-tree, and select Services. In the Services window, select TSM Client Acceptor.
    Click the right mouse button, and select Properties.
    Click the Start button.

    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 8, "Setting Processing Options" for more information.

  4. 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.
  5. 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.

Note:To back up the entire system registry, you must belong to a Windows NT group possessing the following rights:

  • Backup files and directories
  • Restore files and directories
  • Manage auditing and security logs
Users without these rights can only back up files they own, and not files owned by other users or the system registry. See "Considerations for NT and 2000 TSM Client Services" for more information.

If you want to use the Web client with secure socket layer (SSL) communications, which is supported on Windows NT 4.0, Windows 95, and Windows 98, see Appendix C, "TSM Web Client Secure Socket Layer" for more information.


Backing Up Network Resources on Windows NT

To backup network resources, perform the following steps:

  1. Change the startup options for the TSM Client Acceptor and the TSM Remote Client Agent services so that they log on using a user ID with the authority to access the network drives to be backed up.
  2. Log onto the user ID used in the previous step, and issue a net use command with the /persistent:yes option on all the drives that you want to back up, so that the drives are automatically mapped when the service starts up and logs on as that user ID.

If you have any locally defined shares, they will also show up as network drives.


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