This chapter provides installation instructions for Windows 98, Me, NT, or 2000 client workstations. There are three basic steps to a successful installation and setup:
After you complete the install process, please follow the steps in "Getting Started and Initial Configuration".
Attention |
---|
Before you begin installing, please refer to the README file that is shipped on the product installation media. Also, for the most current product information, such as the list of supported platforms and updated documentation, refer to the Web site: http://www.tivoli.com/support/storage_mgr/tivolimain.html |
Follow these steps to install the software on your Windows 98, Me, NT, or 2000 workstation.
x:\tsmcli\win32\baclient\setup where x is your CD-ROM drive and click OK.
Notes:
Notes:
For more information on using the ODBC driver and the Administrative client, see Tivoli Storage Manager for Windows Administrator's Guide, GC35-0410.
If you are doing a large number of installs, you might want to perform an unattended or silent install. You can use the following command to silently install the backup archive client from the command line. By placing an appropriate version of this command in a batch script, you can easily perform an identical installation on multiple Windows client workstations. You must enter the command on one line.
msiexec /i "Z:\tsm_images\TSM_BA_Client\baclient\Tivoli Storage Manager Client.msi" RebootYesNo="No" REBOOT="Suppress" ALLUSERS=1 INSTALLDIR="d:\program files\tivoli\tsm" ADDLOCAL="BackupArchiveGUI,BackupArchiveWeb,ApiRuntime, AdministrativeCmd,Online_Client_Readmes" TRANSFORMS=1033.mst /qn /l*v "c:\log.txt"
The command and its parameters are as follows:
Client Features | Feature Description |
---|---|
BackupArchiveGUI BA | Graphical User Interface |
BackupArchiveWeb | Backup-archive Web client |
ApiRuntime | API Runtimes |
ApiSdk | API SDK |
AdministrativeCmd | Administrative Command Line |
Online_Client_Readmes | Client Readmes and HTMLHelp Book |
BooksPdf | PDF Book |
BackupArchiveGuiChs | Simplified Chinese GUI support |
BackupArchiveWebChs | Simplified Chinese Web support |
BackupArchiveGuiCht | Traditional Chinese GUI support |
BackupArchiveWebCht | Traditional Chinese Web support |
BackupArchiveGuiDeu | German GUI support |
BackupArchiveWebDeu | German Web support |
BackupArchiveGuiEsp | Spanish GUI support |
BackupArchiveWebEsp | Spanish Web support |
BackupArchiveGuiFra | French GUI support |
BackupArchiveWebFra | French Web support |
BackupArchiveGuiIta | Italian GUI support |
BackupArchiveWebIta | Italian Web support |
BackupArchiveGuiJpn | Japanese GUI support |
BackupArchiveWebJpn | Japanese Web support |
BackupArchiveGuiKor | Korean GUI support |
BackupArchiveWebKor | Korean Web support |
BackupArchiveGuiPtb | Portugese GUI support |
BackupArchiveWebPtb | Portugese Web support |
Transform | Language |
---|---|
1028.mst | CHT Traditional Chinese |
1031.mst | DEU German |
1033.mst | ENG English |
1034.mst | ESP Spanish |
1036.mst | FRA French |
1040.mst | ITA Italian |
1041.mst | JPN Japanese |
1042.mst | KOR Korean |
1046.mst | PTB Portuguese |
2052.mst | CHS Simplified Chinese |
The installation process creates a program group containing all of the client components that you selected. To run any of these components, go to the Windows task bar and click Start> Programs> Tivoli Storage Manager.
If you have multiple client installations on the same system, be careful when changing from one client to another. Environment variables such as DSM_DIR may be shared by more than one installed client.
Back up any files you want to retain before you reinstall the client.
The reinstall will replace any previous version it finds in the installation directory. If you want to save files from the previous version, you can copy them to another directory. However, the reinstall will not replace an existing dsm.opt file. Instead, the newly reinstalled client will use the existing dsm.opt file.
If you want to install the client files in a directory other than the one where you previously installed them, you should uninstall the previous version before installing the new version. To do this:
Attention |
---|
For current installation and configuration information, refer to the README file that is shipped on the product installation media. For current information concerning supported platforms and for the latest documentation, refer to the Tivoli Storage Web site: http://www.tivoli.com/support/storage_mgr/tivolimain.html. |
After installation, required setup tasks include:
Attention: Although creating an include-exclude list is optional, if you do not perform this task, every file on your workstation will be available for backup and your workstation will be associated with the default management class. Additionally, Windows 2000 implicitly excludes from backup any files described in the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ BackupRestore\FilesNotToBackup
This section provides instructions for required setup tasks of creating a client options file and registering your workstation with a backup server.
A client options file contains most of the necessary settings for performing backup and archive operations. These settings include the communication protocol you are using and the name of the backup server that you will connect to. When you run the program, if it does not detect an options file, it will automatically launch the configuration wizard to help you create one. If you want to manually start the wizard later, perhaps to modify your options file, follow these steps:
You can also modify your options file manually. The install process creates a sample client options file called dsm.smp. If you accepted the default installation path, this file is in the Program Files\Tivoli\TSM\config directory. The dsm.smp file is a generic configuration file that contains communication parameters that are normally used in a Windows environment. You can use this file as a template when customizing your own options file. First, copy the dsm.smp file to your Program Files\Tivoli\TSM\baclient directory and rename it dsm.opt. Open it in Notepad or your favorite plain text editor and use the following guidelines to customize it for your environment.
One of the options file's most important purposes is to define the communication protocol used between your workstation and the backup server. Use the commmethod option to specify a communication protocol. For example, to use the TCP/IP communication protocol, enter:
COMMmethod TCPIP
You must also specify the TCP/IP server address of the backup server you will connect to using the tcpserveraddress option. For example, you can enter the following:
TCPServeraddress dsmchost.endicott.ibm.com
You may also specify what you want to call your workstation by using the nodename option. When you register with the backup server during setup, this is the name the server will use for your workstation. If you do not specify a node name, the server will identify your workstation by its host name. You can type hostname at a DOS command prompt to see your workstation's host name. For more information about registration requirements, see Registering Your Workstation with a Server (Required).
You can also use the options file to specify authorization, backup and archive processing, and scheduling options. The options specified in your options file are in effect every time you start Tivoli Storage Manager from either the GUI or the command line. However, you can override options temporarily by using the command line.
Your backup server can override your options by using server defined and enforced client option sets. See Chapter 8, "Setting Processing Options" for more information about option processing.
Notes:
Once you have created an options file, you can use one of the following methods to edit your options file from the GUI:
While it is optional, we recommend that you set the DSM_CONFIG environment variable to the location of your client options file. See "Setting Environment Variables" for more information about setting environment variables.
The whole point of using backup or archive is to keep a copy of your important files in a separate location. This means thatyour workstation needs to be able to send those files to another machine somewhere in your network. Therefore, before you can perform backup or archive operations, you need to connect your machine to the server that will keep track of your stored files. This process is called registration.
There are two types of registration: open and closed. Your administrator chooses the type of registration for your site. If the administrator sets the authentication option to off, you will not need a password.
With closed registration, an administrator must register your workstation as a client node with the server for you. If your enterprise uses closed registration, you need to provide the following information to your administrator:
Your administrator needs this infomration to register your workstation with the server. In addition, your administrator defines:
With open registration, you can register your workstation as a client node with the server by yourself. You do not need to go through your administrator.
The first time you start a session, a dialog will prompt you for the information necessary to register your workstation with the server identified in your options file. If your administrator has set authentication to on, you will also need to supply a password.
By default when you use open registration:
If necessary, your administrator can change these defaults later.
This section section provides instructions for optional setup tasks. Performing these optional tasks will help you to fine-tune your installation.
This is an optional task but an important one. If you do not create an include-exclude list, every file on your workstation will be eligible for backup and archive services. Also, the server will associate your workstation with the default management class.
An include-exclude list contains statements that identify any specific files you want to include or exclude from backup or archive operations. This list is in the dsm.opt file. This list can also contain include-exclude statements obtained from separate include-exclude files which you specify with the inclexcl option.
For example, you might want to exclude all swap files, easily reproducible files (such as object files), and operating system files. See "Excluding System Files" for a minimum include-exclude list that you should include in your dsm.opt file.
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 dsm.smp sample file created during installation contains a sample include-exclude list.
For detailed information about creating an include-exclude list or specifying an include-exclude file in your client options file, see Chapter 7, "Creating an Include-Exclude List".
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. The server uses its default management class for any files which you do not explicitly assign to a management class. For more information about management classes refer to "Using Management Classes with Include".
Generally, setting the environment variables is an optional task. Setting them will make it more convenient for you to use the command line. However, you must set the environment variables if you need to run in either of the following environments:
You need to set three environment variables:
Ensure that the environment variables meet the following guidelines:
SET PATH=c:\"program files"\tivoli\tsm\baclient;%PATH%
SET DSM_CONFIG=c:\"program files"\tivoli\tsm\baclient\dsm.opt
SET DSM_DIR=c:\"program files"\tivoli\tsm\baclient
A server administrator can generate client options files in a shared directory on a Windows NT or Windows 2000 server. Windows 98, Me, NT, and 2000 clients can access the shared directory and use the files there to create their own client options file. For more information see Tivoli Storage Manager for Windows Quick Start, GC35-0409.
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 backup or archive tasks.
Suppose you want to back up your files to one server (server a), and archive files to another (server b). Instead of editing the dsm.opt file each time you want to connect to a different server, create 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:
copy a.opt dsm.opt dsm
dsm -optfile=b.opt
SET DSM_CONFIG=c:\program files\tivoli\tsm\baclient\b.opt
You can also override the server specified in dsm.opt by using command line options. For example:
dsm -TCPS=myserver -NODE=mynode -TCPPORT=1599
To start the TSM Backup-Archive client:
To start the TSM Administrator client:
When using the Administrative client command line or the client command line, you must start the TSM client from the directory where it is installed or include that directory in the issued command. If you find yourself using the command line often, you can avoid having to type the path to the commands every time by updating your environment as described in Setting Environment Variables.
When the backup-archive 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 clicking Utilities and then Setup Wizard from the GUI.
Your administrator can require you to use a password to connect to the server. You will be prompted for the password if it is required. Contact your administrator if you do not know your password.
You can install the following services during installation or by using the Client Service Configuration Utility. For more information about using the Client Service Configuration Utility to install these services, see Appendix C, "Using the TSM Client Service Configuration Utility for Windows NT, 2000":
To install and configure services on the system using the Client Service Configuration 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, Windows installs these client services to run under the local system account. Since the service uses the logon properties (such as persistent drive mappings and local search path and environment variables) of the logon account, you may want to change from the local system to a domain logon 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 back up files they own, but not files owned by other users or the system registry.
These are local user rights and, since domain accounts may not be automatically enabled for them,you must set them using the local User Manager application.
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. You must grant these permissions to other accounts/groups (including domain Administrators) 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).
To start the Scheduler, use one of the following methods:
Notes:
When you start the client scheduler from the desktop or Start menu, it runs continuously until you close the window, shut down your system, or log out of your system. If the scheduler is run as a service, it runs until the system is shutdown (or the service is stopped via the services control panel).
You can also start multiple client scheduler services on your system to back up different file systems under different node names.
The Client Acceptor service can manage the client scheduler, reducing the number of background processes on your workstation. This also resolves memory retention problems that may occur when using traditional methods of running the scheduler. It is strongly recommended that you use the Client Acceptor service to manage the client scheduler.
Use the managedservices option in your client options file to specify whether the Client Acceptor service manages the client scheduler. See Managedservices for more information.
To set up the CAD to manage the client schedule, perform the following steps:
If the journal engine service is installed and running, then by default the incremental command performs a journal-based incremental backup on any journaled file systems. TSM does not use the journaling facility inherent in Windows NTFS 5 file systems or any other journaled file system.
The journal engine service records changes to an object or its attributes in a journal database. During a journal-based backup, TSM obtains a list of files that are eligible for backup from the journal database.
Journal-based backup can increase backup performance. With journal-based backup, the client does not scan the local file system or obtain information from the server to determine which files to process. Journal-based backup also reduces network traffic between the client and server.
To support journal-based backup, you must install the journaling engine service background process as a service on Windows NT and 2000. Install this service by using the dsmcutil command or the TSM GUI Setup Wizard. See "Using the Dsmcutil Command" for more information about installing this service using the dsmcutil command.
To install and configure this service using the TSM GUI setup wizard, perform the following steps:
The journal service uses the configuration file tsmjbbd.ini located in the TSM installation directory. An initial configuration file is created during installation, but it is necessary to use the TSM Setup Wizard to customize the settings in this file to your environment. The TSM Setup Wizard will automatically start the journal service after it is installed, and will configure the journal service so that it is automatically started when your machine is rebooted. If you modify the journal service settings using the Update feature of the journal setup wizard, you must restart the journal service before the changes will take effect.
The TSM Journal error log, jbberror.log, is in the TSM installation directory. The journal service configuration file contains some settings which you cannot modify by using the setup wizard. These settings include a list of Windows system directories to exclude from journaling and a filter indicating what changes to journal. While it is possible to manually edit the tsmjbbd.ini file, we do not recommend it.
See Appendix D, "Journal Service Configuration" for more information about the configuration file tsmjbbd.ini.
The incrthreshold option, which you can set via the preferences editor, also affects the behavior of journal-based backup. See Incrthreshold for more information.
Attention: If you are using Norton AntiVirus, there are limitations to journal-based backup. Refer to the README file that is shipped on the product installation media for more information.
You can use the Web client to perform backup, archive, restore, and retrieve operations from any workstation 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 the Web client, specify the URL of the client workstation running the Web client in your Web browser; you will also need to specify the localhost port number. The Web client is only supported on a server that is Version 3 or higher.
To use the Web client, perform the following steps:
To install and configure the Web client from the command line, perform the following steps:
dsmc query session
and, when prompted, enter your user ID and password.
The TSM Web client agent service automatically starts when needed.
The only options you can use with the dsmcad command are optfile, httpport, httpsport, and webports.
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 specified by the errorlogname option. The dsmwebcl.log and dsmerror.log files are in the directory specified by the DSM_LOG environment variable or in the current working directory. See Chapter 8, "Setting Processing Options" for more information.
http://your_workstation_name:1581
where your_workstation_name is the hostname of the workstation running the TSM Web client.
Port 1581 is the default port number. You can set a different port number using the httpport option. See Httpport for more information about the httpport option.
You can access the Web client workstation through the system administrative GUI.
Notes:
To back up network resources using the Web client, perform the following steps:
If you have any locally defined shares, they will also show up as network drives.