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 TSM Web site at http://www.tivoli.com/storage. |
You can install TSM directly from the server CD-ROM. However, you must have Create access to the directory where TSM components will be 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 were 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 to.
After the installation program ends, 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 9, 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 4 shows an example of a NetWare dsm.opt client options file that is using TCP/IP communication:
Figure 4. 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 ADSM\SYS: ADSM\DATA: DOMain ADSM/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 |
The include-exclude list in your client options file contains statements that identify any files you want to include or exclude from backup services. 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.
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.
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 5 shows a sample include-exclude list.
Figure 5. 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 adsm\directory net_directory |
For information that can help you decide whether to create an include-exclude list, see Chapter 8, "Creating an Include-Exclude List". For more information about management classes, see "Using Management Classes with Include".
To create an include-exclude list, perform these steps:
Note: | The order of the include and exclude statements is very important. For more information, see Chapter 8, Creating an Include-Exclude List. |
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, 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.)
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, simply point your Web browser at 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:
load dsmc query session
and, when prompted, enter your password to access the TSM server.
load dsmc query tsa
and, when prompted, enter your NetWare user ID and password.
load dsmc query tsa nds
and, when prompted, enter your NetWare user ID and password.
The only options you can use with the dsmcad command are optfile and httpport.
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.
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 Version 3.12, 4.11, 3.20, 4.20, and 5.x NetWare servers, you must:
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.