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/storage. |
See Appendix C, "Customizing the Installation for Windows" for information on customizing the TSM clients installation and performing a silent installation.
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 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. |
For Intel: type x:\tsmcli\win32\intel\setup where x is your CD-ROM drive. Click OK.
For Alpha: type x:\tsmcli\decalpha\setup where x is your CD-ROM drive. Click OK.
In the Select Components window, highlight the Client Files item and click the Change button to select the clients you want to install.
Notes:
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.
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 NT Administrator's Guide, GC35-0292.
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.
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 TSM:
uninstal /silentall
Attention: This feature automatically stops all running TSM services, and removes all previously installed versions of TSM located in the registry. Uninstalling commences immediately upon execution; there are no confirmation prompts.
No change of the environment variables is necessary, except for the following conditions:
If one of these conditions exist, then you need to set the following environment variables:
Note: | Keep the client options file in a common location if both the backup-archive and administrative clients use it. |
Ensure 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
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:
The preferences editor updates the client configuration file, dsm.opt, if any options change.
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 NT Quick Start.
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.
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 then TSM uses the machine name. For more information about registration requirements, see Registering Your Workstation with the Server (Required).
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 8, Creating an Include-Exclude List.
If you did not create an include-exclude list after installation, you can use one of the following methods:
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:
copy a.opt dsm.opt dsm
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 will have to 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
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.
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:
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.
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.
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 D, "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).
To start the TSM Scheduler, use one of the following methods:
Notes:
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.
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 some 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-4101.
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:
You can also use the Web client by performing 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, 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.
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 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:
|
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 E, "TSM Web Client Secure Socket Layer" for more information.
To backup network resources, perform the following steps:
If you have any locally defined shares, they will also show up as network drives.