This chapter provides instructions to install and set up TSM on a NetWare server.
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 Web site at: http://www.tivoli.com/support/storage_mgr/tivolimain.html. |
After initial installation completes, see "Setting Up, Configuring, and Starting TSM" for additional required and optional tasks to perform before using TSM.
You can install TSM directly from the server CD-ROM. However, you must have Create access to the directory where TSM components are installed.
Notes:
To Install the TSM NetWare API:Install following files in a different directory than the backup-archive client:
The API client sample files are also in {CD-ROM}:\TSMCLI\NTW\API\SAMPLE
To install the Web backup-archive client: The TSM native backup-archive client (DSMC) must be installed before installing the Web client. To install the Web client, copy the following files from directory {CD-ROM}:\TSMCLI\NTW and subdirectories into the directory containing the native backup-archive client:
Directory TSMCLI\NTW\COMMON\WEB_HELP contains subdirectories which must be copied into the current directory where the TSM files reside, as follows:
xcopy x:tsmcli\ntw\common\web_help\* n:tivoli\tsm\client\ /s/e/v
where x is the CDROM drive and n is the NetWare volume where the TSM files are copied.
To install the Tivoli Storage Manager for NetWare Using the Backup-Archive Client manual: Directory {CDROM}:\TSMCLI\NTW\COMMON\BOOKS contains files and subdirectories which must be copied into the current directory where the TSM files reside, as follows:
xcopy x:\tsmcli\ntw\common\books\*.* n:\tivoli\tsm\client\ books\ /s/v
where x is the CDROM drive and n is the NetWare volume (drive) where the TSM files are copied.
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. |
After installation, required setup tasks include the
following:
Optional setup tasks include the following:
Task | Page |
---|---|
Creating an Include-Exclude List (Optional) | "Creating an Include-Exclude List (Optional)" |
Accessing Remote NetWare Servers | "Accessing Remote NetWare Servers" |
After the installation program completes, use a text editor to add the following entry to your NetWare server's autoexec.ncf file:
search add VOLUME:INSTALL_DIRECTORY
where VOLUME:INSTALL_DIRECTORY is the destination you specified for the installation files.
You can also add the following command to the end of your autoexec.ncf file:
load dsmc sched
This command starts the client scheduler at each server startup. Be sure to load all communication programs before loading the scheduler.
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, backup and archive processing options, and scheduling options. You can override certain options when using TSM commands by including the options with the commands. For information about the options file, see Chapter 8, Setting Processing Options.
When you install TSM on your NetWare server, the sample client options file dsm.smp is stored in SYS:\tivoli\tsm\client\ba by default or in another location selected at installation time. To view its contents, use a text editor. The NetWare LOAD EDIT command starts the NetWare text editor.
Attention: When editing is required, use the NetWare LOAD EDIT command with caution because loss of data can occur. This text editor is normally used to modify small text files. Do not edit large files with this utility.
To create a client options file:
copy dsm.smp dsm.opt
The following communication options must be defined in the dsm.opt client options file to enable communications between NetWare and TSM servers:
See "Client Options Reference" for more information about these options.
Use the commmethod option to specify a communication protocol. For example,
COMMmethod TCPip
See "Communication Options" for communication protocols that are supported for the NetWare client.
Figure 3 shows an example of a NetWare dsm.opt client options file that is using TCP/IP communication:
Figure 3. Example of NetWare Client Options File
NODename ABNERYOUNG COMMmethod TCPIP TCPPort 1520 TCPServeraddress node.domain.company.com DOMain SERVA\SYS: SERVA/BINDERY DOMain SERVB\SYS: SERVB/BINDERY DOMain TSM\SYS: TSM\DATA: DOMain TSM/DIRECTORY: COMPression ON TCPBuffsize 31 TCPWindowsize 32 MAXCMDRetries 2 RETRYPeriod 20 SCHEDLOGname SYS:logs\dsmsched.log QUERYSCHedperiod 12 SCHEDMODe POlling TCPCLIENTAddress node.domain.company.com TCPCLIENTPort 1501 ERRORLOGname SYS:logs\dsmerror.log EXclude SERVA\SYS:...\*.obj EXclude SERVB\SYS:...\*.obj REPlace YES NWWaitonerror YES SCROLLPrompt YES SCROLLLines 20 PASSWORDAccess generate |
The include-exclude list contains statements that identify any files you want to include or exclude from backup services. This list is contained in the dsm.opt client options file. This list can also contain include-exclude statements obtained from include-exclude files which you specify with the inclexcl option.
For example, you might want to exclude all empty directories and files, all files that contain compiled object code that are easily reproducible by other methods, and operating system files. You can also enter broad statements that exclude entire groups of files. Then, you can enter include statements to make exceptions to those broad statements.
If an include-exclude list or include-exclude file specified with the inclexcl option do not exist in the client options file, TSM considers all files for backup services and uses the default management class for backup and archive services.
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. TSM uses a default management class for any files to which you do not explicitly assign a specific management class. For more information about management classes, see "Using Management Classes with Include".
The sample client options file contains a specific list of files that are to be excluded from backup. If you do not create an include-exclude list, TSM considers all files for backup services and uses the default management class.
Figure 4 shows a sample include-exclude list.
Figure 4. Sample Include-Exclude List
exclude K9\SYS:user\empty.txt include K2\SYS:bob\* personal_files include KY\SYS:home\ramke\...\* include K0\SYS:home\ramke\...\*source_code exclude KC\SYS:home\time.log include tsm\directory net_directory
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 Client Owner authority.
Before you can begin requesting services from a TSM server, you must register your NetWare server client node with a TSM server. After registration, you can begin using TSM to back up, archive, restore, and retrieve files.
Depending on the registration procedures determined by your TSM administrator, you can use either Closed or Open registration.
With closed registration, the TSM administrator must register your NetWare server as a client node with the TSM server. If your enterprise uses closed registration, you need to provide the following information to your TSM administrator:
The TSM administrator determines the following for you:
With open registration, you can register your NetWare server as a client node with the TSM server.
The first time you start a session using the load dsmc or load dsmc loop command, TSM prompts you for your password and contact information before a session is established with the TSM server.
To register your NetWare server with additional TSM servers, edit the dsm.opt file and change the communication options. Then, when you start a session, your NetWare server is registered.
When you use open registration:
If necessary, your TSM administrator can change these defaults later.
To start TSM, enter the following command:
load dsmc
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.
You can include TSM options on the load dsmc command. 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.)
To start the client scheduler on your client node and connect to the server schedule, change to the TSM directory and enter the following command:
load dsmc schedule
When you start the client scheduler, it runs continuously until you end the process, log off your system, or enter this command at the NetWare console prompt:
unload dsmc
You can also include the schedule command in your autoexec.ncf file so that every time you start NetWare, the client scheduler starts.
Tape prompting does not occur during a scheduled event regardless of the tapeprompt option setting in your options file.
It is strongly recommended that you use the Client Acceptor daemon to manage the TSM Client Scheduler. Do not use the Client Acceptor daemon while the schedule command is in use. See "Managing the Client Scheduler Using the TSM Client Acceptor Service" for more information.
The TSM Client Acceptor daemon can manage the TSM 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 daemon to manage the TSM Client Scheduler.
Use the managedservices option in your client options file to specify whether the TSM Client Acceptor daemon manages the TSM Scheduler. See Managedservices for more information.
To setup the CAD to manage the client schedule, perform the following steps:
managedservices schedule webclient
If you do not want to run the Web client specify:
managedservices schedule
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 default number should be 1581. The Web client is only supported on a server that is Version 3 or higher.
To use the Web client perform, the following steps:
load dsmc query session
when prompted, enter your TSM node name and password to authenticate with the TSM server.
load dsmc query tsa
when prompted, enter your NetWare user ID and password to authenticate with the NetWare server.
load dsmc query tsa nds
when prompted, enter your NetWare user ID and password to authenticate with the NetWare tree under which the NetWare server belongs.
The only options you can use with the dsmcad command are optfile, httpport, 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 located 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
To access the Web client from a network that is not DNS enabled, enter the following URL from any supported browser:
http://your_machine_IP_address:1581
where your_machine_name and your_machine_IP_address is the hostname and the IP address, respectively, of the machine running the 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.
The Web client workstation can also be accessed through the Web administrative GUI.
You can access other NetWare servers with TSM if you have one of the following:
To back up, restore, archive, and retrieve files on remote 5.x NetWare servers, you must have:
When requesting TSM services, specify the remote NetWare server name and volume at the beginning of any directory, file, or path name you want to operate on. When you try to contact a remote NetWare server, you are prompted for an ID and a password if one of the following occurs:
For details about the nwuser option, see Nwuser.