To configure the TSM tape library in the Solaris 10 system

Given its powerful capabilities and good user interface, TSM has won the favor of many customers. But TSM is more for IBM Aix, http://www.aliyun.com/zixun/aggregation/11208.html ">microsoft Windows, Linux, HP-UX, and other operating systems, at Sun There are relatively few uses on the Solaris platform. Most of the Sun Solaris platforms currently use Symantec Veritas Backup management software for data backup and recovery. Compared to other Unix operating systems, Solaris is relatively troublesome in device management, mainly in the context of the need to modify device configuration files, bind to Lun-target, and so on.

Also, different versions of the Solaris operating system differ in how they are configured for the same device. In addition, the installation configuration of TSM on the Sun Solaris platform requires modifications to the configuration file and, on this basis, to build the device files that TSM itself can use, with the exception of the regular driver installation. Therefore, the configuration of TSM has caused a lot of inconvenience, but also to the installer put forward a better request.

Lan-free Installation Instance

The following is a lan-free example to illustrate the process of TSM configuration on the Solaris 10 platform. The key to installing TSM under the Solaris platform is to correctly build the device files required for TSM, so this article focuses on generating the device files that TSM requires, and not describing the specific installation steps for TSM.

Environment Description:

TSM Server: Sunfire v490

OS Level:solaris 10

TSM server:5.3.3

Tape Library: STK l700e, the picker is connected to the TSM server through SCSI, and the drive is connected to the TSM server and eight backup clients (Sun servers) via a fibre switch

Configuration step: Confirm HBA Card Type

1, confirm the Host Bus adapter card (hereinafter referred to as the HBA card) type

There are currently two main HBA cards available on the Sun host, one is the QLogic company's HBA card and the other is Sun's own HBA card. However, Sun's own HBAs are OEM QLogic companies, although both types of HBA cards are from QLogic, but their kernel are different and the configuration file modification method is not the same. Therefore, to configure a tape device under the Sun platform, you first need to confirm the type of HBA card.

Sun supplies the QLogic HBA uses the/KERNEL/DRV/QLC kernel module, its configuration file is/kernel/drv/qlc.conf, and the HBA card supplied by QLogic itself uses Qla kernel module, for example, for sun The OEM's Fc-hba has the following information:

By viewing the card's "Subsytem-id" information to confirm its type,

"0x10a" means that the Fc-hba card is QLogic brand, but using Sun's driver and FCode, which indicates that the HBA card is a Sun OEM QLogic company, the FCode version information can be obtained by the following command:

Configuration step: Displaying recognized tape devices