Symantec NetBackup™ Device Configuration Guide

UNIX, Windows, Linux

Release 7.0

20654101

Symantec NetBackup™ Device Configuration Guide
The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: PN:

Technical Support
Symantec Technical Support maintains support centers globally. Technical Support’s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec’s support offerings include the following:
■

A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services

■

■ ■

■

For information about Symantec’s support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.

Contacting Technical Support
Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:
■

Product release level

local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals
. such as address or name changes General product information (features.■ ■ ■ ■ ■ ■ ■
Hardware information Available memory. gateway.com/business/support/
Customer service
Customer service information is available at the following URL: www.symantec. such as the following types of issues:
■ ■ ■ ■ ■ ■ ■ ■ ■
Questions regarding product licensing or serialization Product registration updates. access our technical support Web page at the following URL: www. and NIC information Operating system Version and patch level Network topology Router. language availability.symantec. disk space. and IP address information Problem description:
■ ■ ■
Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes
Licensing and registration
If your Symantec product requires registration or a license key.com/business/support/ Customer Service is available to assist with non-technical questions.

com semea@symantec. and Africa North America and Latin America customercare_apac@symantec. Middle-East.com
.com supportsolutions@symantec.Support agreement resources
If you want to contact Symantec regarding an existing support agreement. please contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan Europe.

Also use this guide for help with storage devices. see the following:
.Chapter
1
Introducing device configuration
This chapter includes the following topics:
■ ■ ■ ■ ■
Using this guide General device configuration sequence Use the support Web site About optical device support in NetBackup 7. Information about robotic storage devices. To determine if your hardware configuration is supported.0 Read the NetBackup Release Notes
Using this guide
Use this guide to help set up and configure the operating systems of the hosts you use for NetBackup servers .
Portions of this guide apply only to a specific NetBackup server type (for example. This guide is organized as follows:
■ ■
Information about operating systems. These sections provide any important platform-specific instructions or may contain specific instructions or limitations for server types. it does not replace the vendor documentation. Such topics are identified. Read the "Before you start" sections (if applicable) of the chapters in this guide. NetBackup Enterprise Server). This guide provides guidance about NetBackup requirements.

Volume I or the NetBackup Administration Console help. The NetBackup release notes. other configuration settings may also work. You may have to configure the server operating system to allow device discovery.
■
■
. For SCSI controlled libraries. Volume I or the NetBackup Administration Console help. The NetBackup_DeviceConfig_Guide. The format of this text file is similar to the printed version of the guide. you can cut and paste configuration details from a text file of the operating system chapters of this configuration guide.14
Introducing device configuration General device configuration sequence
■
The NetBackup support Web site. Add the storage devices to NetBackup and configure them. To minimize configuration errors. For more information. see "To administer devices on other servers" in the NetBackup Administrator’s Guide. Explicit configuration of device files is required on some UNIX servers to make full use of NetBackup features. See “Use the support Web site” on page 15.txt file is installed with NetBackup server software in the following paths:
■ ■
/usr/openv/volmgr (UNIX) install_path\Veritas\Volmgr (Windows)
General device configuration sequence
Use the following general sequence when you configure devices:
■
Physically connect the storage devices to the media server. Perform any hardware configuration steps that the device vendor or the operating system vendor specifies. see the NetBackup Administrator’s Guide. For instructions. SCSI commands allow NetBackup to discover and configure devices automatically.
■
Symantec tested the configuration file options in this guide. See “Read the NetBackup Release Notes” on page 16. NetBackup issues SCSI commands to the robotic devices. Device files are created automatically on Windows and on some UNIX platforms. You can configure devices in NetBackup from the master server or the media server to which the devices are attached (the device host). Create any required system device files for the drives and robotic control. Be sure to review the differences as explained at the beginning of the text file.

NetBackup media servers do not support optical drives or libraries. you can use optical devices on NetBackup 6. NetBackup uses SCSI reservation to avoid tape drive usage conflicts and possible data loss problems. Volume I.
■
Symantec does not recommend or support the use of single-ended to differential SCSI converters on NetBackup controlled devices.x media servers. SCSI reservation operates at the SCSI target level. For information about the NetBackup use of SCSI reservation. you can use SCSI persistent reserve or disable SCSI reservation entirely. see the Compatibility List for NetBackup Server or NetBackup Enterprise Server. The following is the address for the site: http://entsupport.
. By default. Alternatively.Introducing device configuration Use the support Web site
15
Configuration cautions
Observe the following cautions:
■
In multiple-initiator (multiple host bus adapter) environments. However. Robot and drive types.0
Beginning with the 7. the Shared Storage Option for Tape). see the following:
■ ■
"Enable SCSI reserve" in the NetBackup Administrator’s Guide. the hardware that bridges Fibre Channel to SCSI must work correctly.
Use the support Web site
The Symantec Enterprise Support Web site contains device and library compatibility information for NetBackup.0 release. NetBackup uses SPC-2 SCSI reserve and release. NetBackup licensed optional software (for example. It also contains supported platform information for the following:
■ ■
NetBackup Enterprise Server and NetBackup Server.com
About optical device support in NetBackup 7.symantec. "How NetBackup reserves drives" in the NetBackup Administrator’s Guide. You may encounter problems if you use these converters. Server platform.
■ ■
For the compatibility information. Volume II.

x release.16
Introducing device configuration Read the NetBackup Release Notes
For information about how to use optical devices. see the documentation for your NetBackup 6.
.
Read the NetBackup Release Notes
To determine the server platforms that NetBackup supports. see the NetBackup Release Notes.

The Symantec support Web site contains server platform compatibility information. The following is the URL:
http://entsupport.com
. see the Compatibility List for NetBackup Server or NetBackup Enterprise Server.symantec. For the compatibility information.Chapter
2
AIX
This chapter includes the following topics:
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Before you begin on AIX RS/6000 AIX adapter number conventions About the SCSI pass-through driver ovpass Installing the ovpass driver Ensuring that the ovpass driver device files are accessible Upgrading the ovpass driver Removing the ovpass driver Configuring robotic control device files Configuring tape drive device files in AIX About Sony AIT drives AIX command summary
Before you begin on AIX
Observe the following points when you configure the operating system:
■
Verify that NetBackup supports your server platform and devices.

See “Configuring tape drive device files in AIX” on page 38. If the card is in an I/O expansion drawer. NetBackup uses the Symantec ovpass pass-through driver.
. 0 corresponds to the standard I/O bus and 1 corresponds to the optional I/O bus.
■
■
To verify that the devices are configured correctly. To discover and communicate with SCSI connected devices. To obtain error and debug information about devices and robotic software daemons. use smit and /usr/sbin/lsdev command. as follows:
■
■
The first digit identifies the I/O bus. this digit is 0. as follows:
■
AA identifies the location code of the drawer that contains the adapter card. as follows
■
If AA is 00. NetBackup issues SCSI commands to the robotic devices.20
AIX RS/6000 AIX adapter number conventions
■
Attach all peripherals and reboot the system before you configure devices. you can use the smit System Management Interface Tool. the adapter card is located in the CPU drawer or system unit. If AA is not 00. For SCSI controlled libraries. 0 represents the standard I/O bus and 1 represents the optional I/O bus. add the robots and the drives to NetBackup. ensure that the operating system detects the devices on the SAN before you install and configure the option.
■ ■
BB identifies the I/O bus and the slot that contains the card. For many configuration steps. the card is located in an I/O expansion drawer. For the shared storage options. See syslogd(1) for more information. See “Configuring robotic control device files” on page 23.
■
After you configure the hardware. The second digit identifies the slot on the I/O bus. the syslogd daemon must be active. see the smit(1) man page. depending on the type of system. For more information. It is included with NetBackup. as follows:
■
The first digit of BB identifies the I/O bus that contains the adapter card. as follows:
■
If the card is in the CPU drawer or system unit. You must configure the ovpass driver and create the device files.
RS/6000 AIX adapter number conventions
The location code for an adapter consists of two pairs of digits with the format AA-BB.

depending on the type of system. The board is in either the CPU drawer or the system unit. NetBackup and its processes use the pass-through driver as follows:
■ ■ ■ ■ ■ ■ ■ ■ ■
To scan drives For SCSI reservations For SCSI locate-block operations For SAN error recovery For Quantum SDLT performance optimization To collect robot and drive information To collect TapeAlert information from tape drives For WORM tape support For future features and enhancements
The ovpass driver is not required if the only device you use is the IBM 3590 B11 tape stacker.
The following are examples of adapter numbers:
■ ■
00-00 identifies the Standard I/O Planar.
■
■
About the SCSI pass-through driver ovpass
For SCSI-controlled robotic peripherals. performance suffers. The drawer is connected to the asynchronous expansion adapter that is located in slot 8 of the optional I/O bus in the CPU drawer.AIX About the SCSI pass-through driver ovpass
21
■
The second digit identifies the slot number on the I/O bus (or slot number in the I/O expansion drawer) that contains the card. NetBackup requires the ovpass pass-through driver and SCSI pass-through device paths. NetBackup uses the ovpass driver for SCSI and FCP robot control. See “Installing the ovpass driver” on page 22.
. 00-05 indicates an adapter card that is in slot 5 of the standard I/O board. If you do not use the SCSI pass-through driver. 00-12 indicates an adapter card that is in slot 2 of the optional I/O bus in the CPU drawer. Symantec provides the ovpass pass-through driver. 18-05 indicates an adapter card that is located in slot 5 of an I/O expansion drawer. For full feature support.

Warning: This procedure removes any device files (/dev/ovpassn). If an error occurs when you create a Fibre Channel Protocol device file.
Installing the ovpass driver
Use the following procedure to install the ovpass driver. The following upgrade procedure is required only if you an error occurs when you create a Fibre Channel SCSI device file. To install the ovpass driver
◆
Enter the following command: /usr/openv/volmgr/bin/driver/install_ovpass
Ensuring that the ovpass driver device files are accessible
Use the following procedure to ensure that the ovpass driver device files are accessible after a computer reboot. To ensure that the driver device files are accessible after a system boot
◆
Add the following command to the system startup script: /usr/openv/volmgr/bin/driver/mkdev_ovpass
Upgrading the ovpass driver
Some versions of NetBackup earlier than release 4. If the device files are required. you may need to upgrade the NetBackup ovpass pass-through driver.
. you must recreate them.22
AIX Installing the ovpass driver
Note: You cannot use the System Manager Interface Tool (SMIT) to configure ovpass device files.5 used a version of the ovpass pass-through driver that did not support Fibre Channel protocol SCSI controllers.

To remove the ovpass driver
◆
Enter the following command: /usr/openv/volmgr/bin/driver/remove_ovpass
Configuring robotic control device files
NetBackup supports SCSI control and API control of robotic devices. See “Example 4 — IBM 3570 B-series robotic library” on page 35. See “Configuring SCSI or FCP robotic controls” on page 24.
. See “Example 1 — robotic device at LUN 0” on page 33.
■
Examples of how to create device files are available. A robotic device in a library moves the media between storage slots and the drives in the library. Examples are available. See the "Sun StorageTek ACSLS robots" chapter of this guide. All examples assume that the ovpass driver is installed and that the robotic devices are in the Available state. See “Example 3 — robotic device at LUN 6” on page 34. API control over a LAN. See “Example 2 — robotic device at LUN 1” on page 34. SCSI control includes Fibre Channel Protocol (FCP). You must configure the method of robotic control. See the "IBM Automated Tape Library (ATL)" chapter of this guide. as follows:
■
SCSI or Fibre Channel Protocol control. See the "ADIC Automated Media Library (AML)" chapter of this guide. which is SCSI over Fibre Channel.AIX Removing the ovpass driver
23
To upgrade to the latest pass-through driver
1
Remove the old ovpass driver:
/usr/openv/volmgr/bin/driver/remove_ovpass
2
Install the new ovpass driver:
/usr/openv/volmgr/bin/driver/install_ovpass
Removing the ovpass driver
Use the following procedure to remove the ovpass driver.

Each robotic device requires a device file. Examples of how to configure robotic control are available. Therefore. NetBackup discovers the robotic control device files (and hence the devices) automatically. A library may have more than one robotic device. The device file is the interface between AIX and the device. the NetBackup SCSI pass-through driver ovpass must be installed. Before you configure the robotic controls. If you use device discovery in NetBackup. See “About the SCSI pass-through driver ovpass” on page 21. you must enter the pathname to the device file. NetBackup uses the device files to configure robotic control. To create the device file. The device files require the controller name and SCSI address. The device file is derived from the NetBackup ovpass pass-through driver. you must specify the controller name and the SCSI address of the device. See “Determining if the device file exists” on page 24. Help to determine if the device files exist is available. See “SCSI robotic control configuration examples” on page 33. If the ovpass device file already exists. See “Determining the controller name” on page 25.
Configuring SCSI or FCP robotic controls
To configure SCSI or Fibre Channel Protocol robotic control.
Determining if the device file exists
If the ovpass device file already exists for the device. For usage information for the AIX commands. See “Determining the SCSI address” on page 26.
. See “Creating the device file” on page 31. you must create a device file in AIX for the robotic device. robotic control exists. An ovpass device file would exist if one was configured already for NetBackup. you do not have to configure the robotic controls. you do not have to configure the robotic controls. If you add a robot manually in NetBackup. see their man pages.24
AIX Configuring robotic control device files
See “Example 5 — Fibre Channel attached library” on page 36.

correlate the ovpass device file location to the locations of the controllers.0 Veritas Media Changer
2
If an ovpassx device file exists. they appear in the lsdev output as ovpass0. See “Determining the SCSI address” on page 26. and so on. For Fibre Channel Protocol device files. use the following procedure. For SCSI device files. use the -s scsi option and argument. In the following example. ovpass0 is a SCSI robotic device file for NetBackup:
ovpass0 Available 00-01-5. you must know the controller name. See “Determining the controller name” on page 25.AIX Configuring robotic control device files
25
To determine if the device files exist
1
Display the current device files by using the AIX lsdev command. See “Alternative methods to determine the SCSI ID” on page 29. ovpass1. To determine the controller name. see their man pages. use the -s fcp option and argument. The following are examples of the two options:
/usr/sbin/lsdev -C -s scsi /usr/sbin/lsdev -C -s fcp
If the device files exist.
3
If an ovpassx device file does not exist. See “Creating the device file” on page 31. To do so.
Determining the controller name
To create a device file. For usage information for the AIX commands. you can determine which robotic device it is for.
. use the following procedures to create one:
a b c d See “Determining the controller name” on page 25.

26
AIX Configuring robotic control device files
To determine the controller name
1
Display the I/O controllers in the system by using the following AIX command:
/usr/sbin/lsdev -C | grep I/O
The output shows the name. the SCSI ID identifies the library. AIX commands do not reveal the SCSI addresses of robotic devices that do not have device files. which is a SCSI ID and a logical unit number (LUN).0 Available 10-68-01 Other SCSI Tape Drive Other FC SCSI Tape Drive
3
Correlate the location of the drives with the names of the controllers. A library may have more than one tape drive and more than one robotic control device. For example.
. for Fibre Channel Protocol devices. the location. Usually. each ID corresponds to a physical connection (port) on the library. However. The following example shows both a SCSI controller (scsi0) and a Fibre Channel SCSI controller (fscsi0) :
scsi0 Available 00-01 SCSI I/O Controller fscsi0 Available 10-68-01 FC SCSI I/O Controller Protocol Device
If you have more than one SCSI controller. the status. use fcp for the type.
/usr/sbin/lsdev -C -s type
The following are examples of SCSI drive and Fibre Channel SCSI drive output:
rmt0 rmt1 Available 00-01-00-3. and the description. identify the appropriate controller by correlating the tape drive locations to the controllers.
2
Display the devices that are connected to the SCSI controllers by using the following lsdev command.0 is attached to the controller at 00-01. So the controller name is scsi0. use scsi for the type.
Determining the SCSI address
To create a device file. For SCSI devices. continue with the following steps. The LUNs then identify the tape drives and the robotic devices in each partition of the library. a Fibre Channel attached library may have more than one SCSI ID. the SCSI tape drive at location 00-01-00-3. and the LUNs identify the tape drives and the robotic control devices in the library. To do so. you must know the SCSI address.

LUN 0 may be the robotic device and LUN 1 and higher may be the tape drives. use the tape drive addresses to infer the SCSI ID of the robotic device.
■
■
For usage information for the AIX commands. For example. To determine the SCSI ID. See “Determining IBM library SCSI address” on page 29. see their man pages. For the libraries that have more than one robotic device. AIX may create device files automatically for some SCSI attached IBM libraries. you must first determine the SCSI addresses of the tape drives. more information is available. The library may include the management software that assigns LUNs when you configure it. For those libraries. Then.AIX Configuring robotic control device files
27
The following information can help you determine the SCSI ID and LUN of a robotic device:
■
To determine the SCSI ID.
. The software also may let you determine the LUNs for the drives and robotic devices. you must determine the SCSI ID and LUN for each robotic device. refer to the vendor documentation. use the procedure later in this subsection. How the library assigns LUNs to its devices depends on the library:
■
■
The library may use a specific LUN for the robotic control device. To determine the LUN. The library may use physical switches (such as DIP switches) that let you specify the LUNs for the drives and robotic devices.

CuAt: name = "rmt0" attribute = "scsi_id" value = "0x1009ef" type = "R" generic = "DU" rep = "s" nls_index = 6
For a Fibre Channel Protocol controlled device.
. as follows:
■
If all tape drives in the library have the same SCSI ID and one robotic device exists. Use the odmget command as in the following example (rmtX is the name of the tape device):
/usr/bin/odmget -q "name=rmtX" CuAt
The following example output shows that rmt0 is at SCSI ID 0x1009ef.
/usr/sbin/lsdev -C -s type
The following are examples of a SCSI drive and a Fibre Channel SCSI drive:
rmt0 rmt1 Available 00-01-00-3. Use the same SCSI ID for each device file. If all tape drives in the library have the same SCSI ID and more than one robotic device exists: Create a device file for each robotic device. the SCSI ID is the ID of the N_Port on the robotic device (the destination ID (D_ID)).
■
■
To determine the LUN of each robotic device. use fcp for the type.
3
Determine the SCSI ID to use for each device file. For SCSI devices. Create a device file for each SCSI ID. consult the vendor documentation. a robotic device likely exists for each SCSI ID. inspect the ODM database for the SCSI ID of the tape drive. use scsi for the type. If the tape drives have more than one SCSI ID. for Fibre Channel Protocol devices.28
AIX Configuring robotic control device files
To determine the SCSI ID for a robotic device
1
Display the SCSI and Fibre Channel devices in the system by using the following lsdev command. use that SCSI ID.0 Available 10-68-01 Other SCSI Tape Drive Other FC SCSI Tape Drive
2
For each tape drive in the library.

inspect the name server for the switch (if available).
■
See “Determining IBM library SCSI address” on page 29. For example. Each vendor uses a unique method to show address information. inspect the bridge for mapping information (if available).
. Consult the documentation for the switch vendor.AIX Configuring robotic control device files
29
Alternative methods to determine the SCSI ID
Several alternative methods exist to determine the SCSI ID of a robotic device. you can use AIX commands to determine the SCSI address. In a Fibre Channel bridge environment. Each vendor uses a unique method to show address information. the following command shows the attributes of tape device rmt0:
/usr/sbin/lsattr -l rmt0 -E -H
■
In a Fibre Channel switch environment.
Determining IBM library SCSI address
AIX may create device files automatically for some IBM libraries that use the IBM Atape driver. If so. as follows:
■
Use the lsattr command rather than the odmget command. Consult the documentation for the bridge vendor.

If an smc device file exists for an IBM library. use the following procedure to create it. NetBackup uses the device file to configure robotic control. For instructions.
. Examples of how to create SCSI and Fibre Channel device files are available.AIX Configuring robotic control device files
31
2
Inspect the ODM database for the attributes of the medium changer device file. you must enter the pathname to the device file. NetBackup discovers the robotic control device file (and hence the device) automatically. If you add the robot manually. remove the smcx device file. If you use device discovery in NetBackup. the SCSI ID is the ID of the N_Port on the robotic device (the destination ID (D_ID)). See “SCSI robotic control configuration examples” on page 33. The device files reside in the /dev directory. For a Fibre Channel Protocol controlled device. Use the controller name and SCSI address you determined for the robotic control device.
Creating the device file
If the ovpass device file does not exist. Use the odmget command as in the following example:
/usr/bin/odmget -q "name=smc1" CuAt
The following example output shows that smc1 is at SCSI ID 0x111ca and the LUN is 1. see the IBM AIX documentation.
CuAt: name = "smc1" attribute = "scsi_id" value = "0x111ca" type = "R" generic = "DU" rep = "s" nls_index = 25 CuAt: name = "smc1" attribute = "lun_id" value = "0x1000000000000" type = "R" generic = "DU" rep = "s" nls_index = 26
Before you create the ovpass device file. remove the smc device file before you configure the ovpass device file. The LUN is derived from the LUN ID by moving it 48 bits to the right.

lun
The following are the arguments for the command:
■
-s type is scsi for a SCSI attached robot or fcp for a Fibre Channel
attached robot. To create a robotic control device file
1
Create the device file by using the AIX mkdev command.0 400 MB SCSI Disk Drive 400 MB SCSI Disk Drive Other SCSI Tape Drive Veritas Media Changer
. or vscsi1. use scsi for the type. The following is the command syntax:
mkdev -c media_changer -s type -t ovpass -p controller -w scsi_id. ovpass0 is a SCSI robotic control device file:
hdisk0 hdisk1 rmt0 ovpass0 Available Available Available Available 00-01-00-0.0 00-01-00-1.
/usr/sbin/lsdev -C -s type
In the following example output. fscsi0.1
2
To verify.
■
lun (the second argument to the -w option) is the logical unit number of the robotic connection. use fcp for the type.
The following is an example:
mkdev -c media_changer -s fcp -t ovpass -p fscsi0 -w 0x111ca.
■
-w scsi_id is the SCSI ID of the robotic connection. for Fibre Channel Protocol devices.32
AIX Configuring robotic control device files
If an error occurs when you configure a Fibre Channel Protocol device file. upgrade the SCSI pass-through driver. See “Upgrading the ovpass driver” on page 22. For SCSI devices.0 00-01-00-3. the SCSI ID is the ID of the N_Port on the robotic device (the destination ID (D_ID)).
■
-p controller is the logical identifier of the drive’s SCSI adaptor. display the device files by using the lsdev command.0 00-01-5. such
as scsi0. For a Fibre Channel
Protocol controlled device. The error may be a mkdev command error code 0514-0520.

0 400 MB SCSI Disk Drive Available 00-01-00-3.0 hdisk1 Available 00-01-00-1.
hdisk0 rmt0 Available 00-01-00-0. assume that the robot is a LUN 0 controlled robot.AIX Configuring robotic control device files
33
SCSI robotic control configuration examples
For examples of how to create device files. a device file does not exist for the controller scsi0 and SCSI ID 5.
/usr/sbin/lsdev -C -s scsi
The output shows the device files exist for tape and disk. However.0 Other SCSI Tape Drive
3
Create the device file by using the following command:
mkdev -c media_changer -t ovpass -s scsi -p scsi0 -w 5.0 ovpass0 Available 00-01-5. see the following subsections.
Example 1 — robotic device at LUN 0
For this example.
scsi0 Available 00-01 SCSI I/O Controller
2
Check if the ovpass device file exists at SCSI ID 5.0 rmt0 Available 00-01-00-3.0
400 MB SCSI Disk Drive 400 MB SCSI Disk Drive Other SCSI Tape Drive Veritas Media Changer
5
To configure the robotic control manually in NetBackup. The SCSI controller is controller 1 (00-01) at SCSI ID 5. To configure robot control at LUN 0
1
Determine the logical identifier for the SCSI controller as follows:
/usr/sbin/lsdev -C -c adapter | grep SCSI
The following output shows that scsi0 is the logical name for SCSI controller 1.0
4
Display the device files by using the following command:
/usr/sbin/lsdev -C -s scsi hdisk0 Available 00-01-00-0. All examples assume that the ovpassdriver is installed and that the robotic devices are in the Availablestate. use the following device file pathname:
/dev/ovpass0
.

.0 Other SCSI Tape Drive
3
Create the device file by using the following command:
mkdev -c media_changer -t ovpass -s scsi -p scsi0 -w 3. assume that the robot is a LUN 1 controlled robot. SCSI ID 3.0 hdisk1 Available 00-01-00-1. use the following device file pathname:
/dev/ovpass0
Example 3 — robotic device at LUN 6
Assume the robot and the drives are connected to an SCSI adapter.0 rmt0 Available 00-01-00-3. Assume that the drives are at SCSI IDs 4 and 5 and the robotic device is at SCSI ID 6. a device file does not exist for the controller scsi0.1
4
Display the device files by using the following command:
/usr/sbin/lsdev -C -s scsi hdisk0 Available 00-01-00-0.34
AIX Configuring robotic control device files
Example 2 — robotic device at LUN 1
For this example. However.0 ovpass0 Available 00-01-3. To configure robot control at LUN 1
1
Determine the logical identifier for the SCSI controller:
/usr/sbin/lsdev -C -c adapter | grep -i SCSI
The following output shows that scsi0 is the logical name for SCSI controller 1:
scsi0 Available 00-01 SCSI I/O Controller
2
Check if the device file exists for ovpass at SCSI ID 5. The SCSI controller is controller 1 (00-01) at SCSI ID 3.1
400 MB SCSI Disk Drive 400 MB SCSI Disk Drive Other SCSI Tape Drive Veritas Media Changer
5
To configure the robotic control manually in NetBackup. as follows:
/usr/sbin/lsdev -C -s scsi
The following output shows that the device files exist for tape and disk. and LUN 1:
hdisk0 rmt0 Available 00-01-00-0.0 400 MB SCSI Disk Drive Available 00-01-00-3.

0 Other SCSI Tape Drive
If drive 1 is SCSI ID 5.0 Other SCSI Tape Drive
The drives are on controller 00-04-01 (vscsi1). Assume a configuration as follows:
lsdev -C -c tape rmt0 Available 00-02-01-5.
3
Use vscsi1 as the controller name when you create the ovpass device file:
mkdev -c media_changer -t ovpass -s scsi -p vscsi1 -w 6. See the library’s operator guide for information on setting library mode and configuration.1
SCSI I/O Controller Wide SCSI I/O Controller Adapter SCSI I/O Controller Protocol SCSI I/O Controller Protocol
2
Display the tape drives:
lsdev -C -c tape rmt2 Available 00-04-01-4. the robotic control is LUN 1 of the drive's SCSI ID.0
Example 4 — IBM 3570 B-series robotic library
If the robotic library contains one drive. If it contains two drives. use the following command to create the device file:
. You can view or set the SCSI IDs by using the front panel on the robot. Also.0 Other SCSI Tape Drive rmt3 Available 00-04-01-5. they may be connected to different host systems. In this example. The robotic control for the IBM 3570 B01/B02 is NetBackup type TLD. the robotic control for the robotic library is LUN 1 of this SCSI ID.0 Available 00-04-0. if two drives exist. If vscsi1 is the correct adapter. the library should be in RANDOM mode and BASE configuration.0 Other SCSI Tape Drive rmt1 Available 00-02-01-6. the robotic control is LUN 1 of the drive 1 SCSI ID. the drive 1 host system provides the robotic control.AIX Configuring robotic control device files
35
To configure robot control at LUN 6
1
Display the SCSI controllers:
lsdev -C scsi0 ascsi0 vscsi0 Device vscsi1 Device | grep scsi Available 00-02 Available 00-04 Available 00-04-0.

use the following device file pathnames when you configure devices in NetBackup:
/dev/ovpass0 /dev/ovpass1
Configuring tape drive device files in AIX
The following subsections provide information about configuring tape drive device files on AIX systems.38
AIX Configuring tape drive device files in AIX
5
Display the Fibre Channel protocol devices by using the following command:
/usr/sbin/lsdev -C -s fcp ovpass0 Available 10-68-01 ovpass1 Available 10-68-01 rmt0 Available 10-68-01 rmt1 Available 10-68-01 rmt2 Available 10-68-01 rmt3 Available 10-68-01 rmt4 Available 10-68-01 rmt5 Available 10-68-01
Veritas Media Veritas Media Other FC SCSI Other FC SCSI Other FC SCSI Other FC SCSI Other FC SCSI Other FC SCSI
Changer Changer Tape Drive Tape Drive Tape Drive Tape Drive Tape Drive Tape Drive
6
To configure the robotic control manually in NetBackup.
Which tape driver to use
If you use IBM tape drives.
About non-QIC tape drives
Variable length block and fixed length block refer to how the operating system reads from and writes to a tape. see the IBM documentation. The smit application is the most convenient way to change from fixed to variable-length-block devices manually. Variable-mode devices allow more flexibility to read previously written tapes.
. For information about the driver. Symantec recommends that you install the IBM AIX Atape driver. If you use other tape drives. Symantec recommends that you use the IBM AIX ost (other SCSI tape) driver. For more information. Many tape devices can be accessed in either mode. For information about the driver. NetBackup assumes variable length for non-quarter inch cartridge (QIC) drives. see the chdev(1) and smit(1) man pages and the system management guide. see the IBM documentation.

About fast-tape positioning (locate-block) on AIX
Applies to AIT. When you add a non-QIC tape drive to NetBackup.
About extended-file marks for drives
If a tape drive supports extended file marks. NetBackup may not be able to use those drives. For reference. the following is the command that NetBackup uses:
/usr/sbin/chdev -l Dev -a extfm=yes
Replace Dev with the logical identifier for the drive (such as rmt0 or rmt1) Therefore. Otherwise NetBackup can write data but may not be able to read it correctly. For reference. NetBackup supports the SCSI locate-block command. NetBackup uses the locate-block command by default. you do not have to configure the drive manually for extended file marks. you may see a not in tar format error. When you add a tape drive to NetBackup. Therefore. the following is the command that NetBackup uses to configure a drive for variable mode:
/usr/sbin/chdev -l Dev -a block_size=0
Dev represents the logical identifier for the drive (for example: rmt0 or rmt1). To position a tape to a specific block. you do not have to configure the drive manually for variable mode. During a read. see the AIX chdev(1) and smit(1) man pages. DLT. you must configure it to use them (for example. you must configure non-QIC tape drives as variable-length-block devices. Otherwise. NetBackup issues the chdev command to configure the drive to use extended file marks. Symantec recommends that you do not disable locate-block positioning. Exabyte. execute the following command:
touch /usr/openv/volmgr/database/NO_LOCATEBLOCK
. NetBackup issues the chdev command to configure the drive as a variable length block device. If you need to disable it. 8-mm drives). For information. and half-inch cartridge tape drives.AIX Configuring tape drive device files in AIX
39
Warning: For NetBackup.

For SCSI devices. such as scsi0.
■ ■
For example.
/usr/sbin/lsdev -C -s type
The following example shows two disk drives and a tape drive:
hdisk0 hdisk1 rmt0 Available 00-01-00-0.0 400 MB SCSI Disk Drive Available 00-01-00-1. rmt1. use fcp for the type.0 400 MB SCSI Disk Drive Available 00-01-00-3.
3
If a device file does not exist for the wanted tape drive. To check for and create a no rewind device file
1
Display the I/O controllers in the system by using the following command:
/usr/sbin/lsdev -C | grep I/O
The following sample output shows that SCSI controller 1 (00-01) has been assigned the logical identifier scsi0. fscsi0.
Creating no rewind device files for tape drives
Use the following procedure to check for and create a no rewind device file. The previous example output shows rmt0. or vscsi1. use scsi for the type. NetBackup uses the forward-space-file/record method. create it by using the following command:
/usr/sbin/mkdev -c tape -s scsi -t ost -p controller -w id.
scsi0 Available 00-01 SCSI I/O Controller
2
Display the SCSI and Fibre Channel devices in the system by using the following command.0 Other SCSI Tape Drive
If the device files for the tape drives exist. for Fibre Channel Protocol devices. lun is the logical unit number of the drive connection. they appear in the output as rmt0. the following command creates a device file for a non-IBM 8-mm drive connected to controller scsi0 at SCSI address 5. and so on.lun
The following are the arguments for the command:
■
controller is the logical identifier of the drive’s SCSI adaptor.40
AIX Configuring tape drive device files in AIX
With locate-block positioning disabled. scsi_id is the SCSI ID of the drive connection.0:
.

0 00-01-00-5.
/usr/sbin/chdev -l dev -a block_size=0 /usr/sbin/chdev -l dev -a extfm=yes
7
To configure the drive manually in NetBackup.0 00-01-00-3. NetBackup uses the ovpass driver for medium changers.0
4
To verify. as follows:
/usr/sbin/lsdev -C -s scsi hdisk0 hdisk1 rmt0 rmt1 Available Available Available Available 00-01-00-0. enter the following device file pathname:
/dev/rmt1. Use the chdev command.
. display the SCSI device files by using the lsdev command. so you can disregard the message. use the following command to create them:
/usr/sbin/cfgmgr -l device
device is the controller number from step 1.0 400 MB SCSI Disk Drive 400 MB SCSI Disk Drive Other SCSI Tape Drive Other SCSI Tape Drive
The output shows that the rmt1 device file was created. rmt1)). SCSI ID 5) do not exist.AIX Configuring tape drive device files in AIX
41
mkdev -c tape -s scsi -t ost -p scsi0 -w 5.
6
Ensure that the device is configured for variable-mode and extended file marks.
5
If the device files do not exist on an FCP controller.0 00-01-00-1. You may receive a message that a device package is required for an FCP changer. as follows (dev is the logical identifier for the drive (for example.1
No rewind device file example
Assume the device files for the wanted SCSI 8-mm tape drive (controller 1.

The NetBackup Shared Storage Option provides shared drive functionality in NetBackup. you can use the System Manager Interface Tool (SMIT). use the following no rewind on close device file when you configure the device in NetBackup:
/dev/rmt*. Exabyte 8500C is an example of a tape drive for which you can use different densities. Zero (0) selects the default density for the tape drive.1
To use density setting 2.AIX Configuring tape drive device files in AIX
43
Using multiple tape densities
After you create the device files for your tape drives. Alternatively. which is usually the drive's high density setting. you can configure densities on the drives that support multiple densities. which means maximum density. Permitted values and their meanings vary with different types of tape drives.5
About SPC-2 SCSI reserve on AIX
By default. Alternatively. To modify the density settings
◆
The following commands modify both of the tape drive device files:
chdev -l tapedev -a density_set_1=density chdev -l tapedev -a density_set_2=density
The following describe the arguments to the command options:
■ ■
tapedev is the logical identifier for the drive. The following procedure is an example of using the chdev command to modify the density settings. such as rmt0 or rmt1. density is a decimal number from 0 to 255 that represents the wanted density. use the following no rewind on close device file when you configure the device in NetBackup:
/dev/rmt*. AIX supports two configuration settings for density.
To use density setting 1. The default density for both density setting 1 and density setting 2 is 0. NetBackup uses SPC-2 SCSI reserve and release for tape drive reservations in shared drive environments. as follows:
. although not all tape drives support multiple densities. you can use SCSI persistent reserve for shared tape drive reservations in NetBackup.

For the tape drives that do not support CRH. see the following:
■
The description of the Enable SCSI Reserve Media host property in the following:
■ ■
The NetBackup Administrator’s Guide for UNIX and Linux. Volume II
Disabling SPC-2 SCSI reserve in AIX
To disable SPC-2 SCSI reserve. you can use persistent reserve by enabling it in NetBackup. If the drive does not support CRH and you do not disable SPC-2 SCSI reserve. do not use SCSI persistent reserve with the drives that do not support CRH. you must disable SPC-2 SCSI reserve in AIX for those drives. To disable SPC-2 SCSI reserve in AIX
◆
Invoked the following command:
chdev -l name -a res_support=no
Replace name with the name of the device file. After you disable SPC-2 SCSI reserve. For information about the chdev command. Volume I The NetBackup Administrator’s Guide for Windows.44
AIX Configuring tape drive device files in AIX
■
For the tape drives that support SPC-3 Compatible Reservation Handling (CRH). The sctape driver is an example of a tape driver that lets you disable SPC-2 SCSI reserve. such as rmt0.
■
For more information about NetBackup and SCSI reservations. See “Disabling SPC-2 SCSI reserve in AIX” on page 44. use the AIX chdev command to change the reserve attribute for the device file for the tape drive. access attempts to the drive fail.
. No special configuration in AIX is required. Warning: If the tape driver does not let you disable SPC-2 SCSI reserve. Volume I
■
The "How NetBackup reserves drives" topic in the following:
■ ■
The NetBackup Administrator’s Guide for UNIX and Linux. Volume II The NetBackup Administrator’s Guide for Windows. see the AIX chdev man page. you can use SCSI persistent reserve by enabling it in NetBackup.

AIX About Sony AIT drives

45

About Sony AIT drives
Sony S-AIT drives have DIP switches (SWA and SWB) located on the bottom of the drive. For the NetBackup Shared Storage Option, you must set the SWA-1 (No Reply Unit Attention After Process Login) switch correctly. Its factory setting depends on the serial number of the drive. If the drive has an early serial number, switch SWA-1 may be OFF. If so, change the switch to ON. Drives with newer serial numbers have SWA-1 set to ON as the default. These newer serial numbers are as follows:
■ ■

SDZ-130 :01442007 and later SDZ-130/L :01200696 and later

Also, for the drives that have a date of May 17, 2004 and later, the DIP switch is set to ON. Table 2-1 shows the dip switch settings for the newer serial number drives. Table 2-1 Switch
SWA-1 SWA-2 SWA-3 SWA-4 SWA-5 SWA-6 SWA-7 SWA-8

Creates the device files for the robotic control SCSI ID. controller is the logical identifier of the drive SCSI adaptor (such as scsi0 or scsi1). id is the SCSI ID of the robotic connection. lun is the logical unit number of the robotic connection.
■

mkdev -c media_changer -s fcp -t ovpass -p controller -w scsi_id,lun

Creates the device files for the robotic control Fibre Channel SCSI ID. controller is the logical identifier of the drive SCSI adaptor (such as scsi0 or scsi1). scsi_id is the Fibre Channel SCSI ID of the robotic connection. lun is the logical unit number of the robotic connection.
■

mkdev -c tape -s scsi -t ost -p controller -w id,lun

Creates the device files for tapes. controller is the logical identifier of the drive SCSI adaptor (such as scsi0 or scsi1). id is the SCSI ID of the robotic connection. lun is the logical unit number of the robotic connection.
■

Configures the drive with logical identifier specified by dev (for example: rmt0) for extended file marks. Where ovpass_id is the logical identifier assigned to the device.
■

/etc/lsattr -l dev -E -H

AIX AIX command summary

47

Displays the device information, where dev is the name of the device (for example, rmt1).
■

/usr/sbin/cfgmgr -l device

Creates the device files on a Fibre Channel Protocol controller, where device is the controller number (for example, fscsi0).
■

/usr/bin/odmget -q "name=rmtX" CuAt

Displays the device attributes for the device (rmtX). This command can be used to determine SCSI target and LUN pairs when you configure Fibre Channel devices. Where rmtX is the name of the tape device (for example: rmt0 or rmt1).

48

AIX AIX command summary

The Symantec support Web site contains server platform compatibility information.Chapter
3
HP-UX
This chapter includes the following topics:
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Before you begin on HP-UX About robotic control on HP-UX About HP-UX device addressing schemes About tape drive device file requirements About device drivers and files for persistent DSFs Configuring persistent DSFs About HP-UX legacy device drivers and files Configuring legacy device files About SPC-2 SCSI reserve on HP-UX Disabling SPC-2 SCSI reserve in HP-UX Disable the HP-UX EMS Tape Device Monitor for a SAN About SAN clients on HP-UX Errors when more than 10 NetBackup jobs are active HP-UX command summary
Before you begin on HP-UX
Observe the following points when you configure the operating system:
■
Verify that NetBackup supports your server platform and devices.
.

as follows:
■
SCSI or Fibre Channel Protocol control. The following is the URL: http://entsupport. A robotic device in a library moves the media between storage slots and the drives in the library. To verify that the devices are configured correctly. See “About device drivers and files for persistent DSFs” on page 52.Symantec. See the "ADIC Automated Media Library (AML)" chapter of this guide. you still must configure tape drive device file access in HP-UX.
■
■
After you configure the hardware. therefore.
. see the Compatibility List for NetBackup Server or NetBackup Enterprise Server. NetBackup issues SCSI commands to the robotic devices. add the robots and the drives to NetBackup. Agile addressing uses persistent device special files (DSFs) for devices. See “Configuring persistent DSFs” on page 54. NetBackup device discovery finds persistent DSFs only. which is SCSI over Fibre Channel.com
■
For SCSI controlled libraries. For NetBackup to function correctly.50
HP-UX About robotic control on HP-UX
For the compatibility information. See the "Sun StorageTek ACSLS robots" chapter of this guide. which was introduced in HP-UX 11i v3. If you use API control. For the NetBackup Shared Storage Option.
About robotic control on HP-UX
Several options exist for robotic control. See “About HP-UX device addressing schemes” on page 50. the properly named device files must exit. Some HP SCSI adapters do not support SCSI pass through.
■
About HP-UX device addressing schemes
NetBackup supports the following two HP-UX device addressing schemes for mass storage devices:
■
Agile addressing. ensure that the operating system detects the devices on the SAN. SCSI control includes Fibre Channel Protocol (FCP). use the HP-UX sam utility and the ioscan -f command. devices on such adapters are not discovered automatically. API control over a LAN. See the "IBM Automated Tape Library (ATL)" chapter of this guide. Symantec recommends that you use persistent DSFs. Therefore.

See “About SAN clients on HP-UX” on page 68. If you use the legacy model. See “About tape drive device file requirements” on page 51. The letter b in the file name indicates Berkeley-style close device files.) To establish the correct position for the next tape operation. See “Disable the HP-UX EMS Tape Device Monitor for a SAN” on page 67. You may be required to perform other HP-UX configuration. Both types of DSFs can coexist and may be used simultaneously to access mass storage devices. You cannot use NetBackup device discovery and automatic configuration.
When HP-UX 11i v3 is installed. NetBackup assumes Berkeley-style close on HP-UX systems. (Conversely. In Berkeley-style close. you must configure devices manually in NetBackup. both legacy and persistent DSFs are created on the system. in AT&T-style close.
About tape drive device file requirements
Table 3-1 describes the requirements for tape drive device files.
. the tape position remains unchanged by a device close operation. NetBackup requires specific device file capabilities for tape drives. See “About HP-UX legacy device drivers and files” on page 56. See “Disabling SPC-2 SCSI reserve in HP-UX” on page 67. the drive advances the tape to just after the next end-of-file (EOF) marker.HP-UX About tape drive device file requirements
51
■
The legacy naming model. applications must assume the tape's position after a close. See “About SPC-2 SCSI reserve on HP-UX” on page 66. See “Configuring legacy device files” on page 58. See “Errors when more than 10 NetBackup jobs are active” on page 68. Legacy device files are supported in HP-UX 11i v3 and earlier. Table 3-1 Requirement
Berkeley-style close
Tape drive device file requirements Description
NetBackup requires Berkeley-style close for tape drive device files.

NetBackup uses the locate-block command by default if a pass-through path is configured.
About device drivers for persistent DSFs
The following are the device drivers required to use persistent DSFs:
■ ■
The eschgr driver for robotic control. Persistent DSFs are a component of a new storage stack addressing model HP calls agile addressing. if you do not use persistent DSFs. The letter n in the file name indicates no rewind device files.
About device drivers and files for persistent DSFs
NetBackup supports persistent device special files (DSFs) for robotic tape libraries and tape drives. You can use persistent DSFs on some HP-UX servers and legacy device files on others.
. To disable locate-block positioning. When HP-UX 11i v3 is installed. Symantec recommends that you use persistent DSFs. For a list of drive types that NetBackup supports. The device file name of the logical unit is independent of the paths that lead to the LUN. However. Note: NetBackup device discovery finds persistent DSFs only. both persistent DSFs and legacy device files are created on the system. you must configure devices manually in NetBackup. The device World Wide Identifier (WWID) identifies a device.52
HP-UX About device drivers and files for persistent DSFs
Table 3-1 Requirement
Fast-tape positioning (locate-block)
Tape drive device file requirements (continued) Description
HP-UX supports locate-block for most drive types for Fast Wide GSC SCSI adapters. NetBackup uses the forward-space-file/record method. execute the following command: touch /usr/openv/volmgr/database/NO_LOCATEBLOCK When locate-block positioning is disabled. The estape driver for tape drives. a device path does not identify a device.
No rewind on close NetBackup requires no rewind on close for tape devices. see the Symantec support Web site. Therefore.

NetBackup creates the paths during device discovery or when you run the /usr/openv/volmgr/bin/scan command. NetBackup uses pass-through device files for drive access. if HP-UX discovers two robotic devices (auto-changers) and assigns them instance numbers 0 and 1 respectively.HP-UX About device drivers and files for persistent DSFs
53
■
For IBM tape drives.
About persistent DSF pass-through paths
Although NetBackup requires the /dev/rtape DSFs to configure tape drives. BEST indicates the highest density.Symantec.com/docs/284599 Also see the NetBackup OS compatibility list for the minimum OS patch level that is required to run on HP-UX: http://entsupport. n indicates no rewind on close. NetBackup creates pass-through paths for all valid /dev/rtape paths.Symantec. http://entsupport. HP-UX automatically creates the following device files:
/dev/rchgr/autoch0 /dev/rchgr/autoch1
About persistent DSFs for tape drive access
The following is the persistent DSF name format for tape drive read and write access:
/dev/rtape/tape#_BESTnb
The following describe the DSF name format:
■ ■ ■ ■
The # represents the instance number. The following is the file name format:
/dev/pt/pt_tape#
.com/docs/278064
About persistent DSFs for robotic control
The following is the persistent DSF name format for robotic control:
/dev/rchgr/autoch#
The # represents the instance number. For example. NetBackup requires a minimum atdd driver level. Please see the NetBackup hardware compatibility list for more IBM atdd driver levels that are supported and atdd configuration information. the atdd driver. b indicates Berkeley-style close.

see the man page. However. enter insf –d atdd To refresh the device path for all devices that use a driver. Although NetBackup uses the pass-through device files during tape drive operations. See “Creating HP-UX persistent DSFs” on page 54. NetBackup then uses the appropriate pass-through device files. For the estape tape driver.54
HP-UX Configuring persistent DSFs
The # represents the instance number that matches the number in the /dev/rtape/tape#_BESTnb device file or that is retrieved from the ioscan output. See “Creating HP-UX persistent DSFs” on page 54. To create the persistent DSFs automatically
◆
Depending on the driver. enter the following command as root: For the eschgr autochanger driver. For more information about using the HP-UX insf command. enter insf –d eschgr.
Configuring persistent DSFs
Configure persistent DSFs for the following:
■
Robotic control. For the IBM atdd tape driver. See “Creating persistent DSF pass-through paths” on page 55. you can reinstall or create the persistent DSFs. you specify the /dev/rtape device files if you configure the drives manually in NetBackup. See “Creating persistent DSF pass-through paths” on page 55. create persistent DSFs on every server on which you want to use the new persistent DSFs.
■
Creating HP-UX persistent DSFs
By default. new installations of HP-UX 11i v3 and later create both persistent DSFs and legacy device files for the eschgr and estape drivers. See “Upgrading NetBackup to use HP-UX persistent DSFs” on page 55.
. adding the –e option to the command line. enter insf –d estape. Then. First connect the devices to the system. Tape drive read and write accesss.

the legacy paths remain configured as alternate paths. The following example shows how to create a pass-through device file for a persistent DSF.
2
After adding the entry to the vm. However.conf file. ltid scans for device paths. If you run the NetBackup Device Configuration Wizard before you perform this change.HP-UX Configuring persistent DSFs
55
Upgrading NetBackup to use HP-UX persistent DSFs
Use the following procedures to configure an existing NetBackup environment to use persistent DSFs after you upgrade a media server to HP-UX 11i v3. you can create them manually.conf file and with no current jobs running on the media server.
4
After the services are started and device paths updated. NetBackup creates the paths during device discovery or when you run the /usr/openv/volmgr/bin/scan command. After ltid starts. The following procedure also removes the legacy paths from the NetBackup device configuration. adds the new DSFs.
. you can use the NetBackup tpconfig utility to disable the old paths but retain them in the device configuration.conf file (the syntax must be as specified in all capital letters):
AUTO_PATH_CORRECTION=YES
The AUTO_PATH_CORRECTION entry directs NetBackup to scan for device paths when the ltid device daemon starts. only the new persistent DSF paths should be configured in NetBackup. NetBackup adds the new DSF paths to the device configuration. run the following command:
/usr/openv/volmgr/bin/stopltid
3
Wait a few minutes for the service to stop.
Creating persistent DSF pass-through paths
NetBackup creates pass-through paths for all valid /dev/rtape paths. However. you can (but do not have to) remove the AUTO_PATH_CORRECTION=YES entry from the vm. To change a NetBackup media server to use the new DSFs
1
Add the following entry to the /usr/openv/volmgr/vm. then restart ltid by running the following command:
/usr/openv/volmgr/bin/ltid
Upon start-up. and then purges the legacy DSFs from your NetBackup configuration for the media server. To save the legacy paths.

symantec.56
HP-UX About HP-UX legacy device drivers and files
To create a pass-through path for a tape drive
◆
Enter the following command (# is the instance number of the device from the ioscan output):
mksf –P –C tape –I #
For more information about using the HP-UX mksf command. TARGET is the SCSI ID of the robotic control. The stape driver for tape drives. NetBackup can use the /dev/sctl device files. the atdd driver. NetBackup does not discover legacy device files.
.symantec. NetBackup requires a minimum atdd driver level.com/docs/284599
Also see the NetBackup OS compatibility list for the minimum OS patch level that is required to run on HP-UX:
http://entsupport.
http://entsupport.
About HP-UX legacy device drivers and files
Legacy device files are the old style device files that are not part of the HP-UX agile addressing scheme. see the man page. If you use legacy device files. The device file names have the following format:
/dev/sctl/cCARDtTARGETlLUN c Major 0xIITL00
Where:
■ ■
CARD is the card instance number of the adapter. For IBM tape drives. See the NetBackup hardware compatibility list for the atdd driver versions that are supported and for atdd configuration information: NetBackup also supports the use of the IBM atdd tape driver on HP-UX 11i v3.com/docs/278064
About legacy robotic control device files
For SCSI robotic control. you must configure devices manually in NetBackup.
About device drivers for legacy device files
The following are the drivers supported:
■ ■ ■
The sctl driver for robotic control.

Each robotic device requires a device file. L is a hexadecimal digit that represents the SCSI LUN of the robotic control. See “Creating legacy SCSI and FCP robotic controls on HP-UX” on page 58. d# is the device LUN.
The following are examples of tape drive device files:
/dev/rmt/c7t0d0BESTnb /dev/rmt/c7t1d0BESTnb /dev/rmt/c7t4d0BESTnb /dev/rmt/c7t5d0BESTnb
See “Creating legacy tape drive device files” on page 64.
About legacy tape drive device files
NetBackup can use the /dev/rmt device files to configure tape drives.
. Major is the character major number (from the lsdev command). II are two hexadecimal digits that represent the card instance number. NetBackup uses pass-through device files for drive access.
A library may have more than one robotic device.
About legacy pass-through paths for tape drives
Although NetBackup requires the /dev/rmt device files to configure tape drives. The device file names have the following format:
/dev/rmt/c#t#d#BESTnb
The following describe the device file names:
■ ■ ■ ■
c# is the card instance number. BEST indicates the highest density format and data compression the device
supports. t# is the SCSI ID.
■ ■
n indicates no rewind on close. b indicates Berkeley-style close. T is a hexadecimal digit that represents the SCSI ID of robotic control.HP-UX About HP-UX legacy device drivers and files
57
■ ■ ■ ■ ■
LUN is the SCSI logical unit number (LUN) of the robot.

Wide SCSI or HP 28655A . NetBackup does not modify or delete any existing pass-through paths. they are not created automatically when the system boots. NetBackup creates the pass-through device files in the /dev/sctl directory. NetBackup then uses the appropriate pass-through device files. However.58
HP-UX Configuring legacy device files
NetBackup automatically creates pass-through device files if the appropriate/dev/rmt tape drive device files exist. Tape drive read and write access. you do not have to create pass-through paths for drives. which is SCSI over Fibre Channel. Therefore. instructions to do so are provided for reference. SCSI control includes Fibre Channel Protocol (FCP). NetBackup does not detect the type of adapter cards that are installed in the system.
■
Creating legacy SCSI and FCP robotic controls on HP-UX
You must create the robotic control device files for the sctl driver manually. Before you create the device files. See “Creating tape drive pass-through device files” on page 64. you must do the following:
■
Install and configure the sctl driver. These pass-through paths do not cause problems. NetBackup creates pass-through paths for tape drives connected to the adapter cards that do not support pass through. Usually. See “Creating legacy SCSI and FCP robotic controls on HP-UX” on page 58. A robotic device in a library moves the media between storage slots and the drives in the library.
. See “Creating legacy tape drive device files” on page 64. For more information.
Configuring legacy device files
You can use legacy device files for the following:
■
Robotic control using SCSI or Fibre Channel Protocol control. Although NetBackup uses the pass-through device files during tape drive operations. see the HP-UX scsi_ctl(7) man page. See “Creating tape drive pass-through device files” on page 64. Note: Pass-through paths are not supported on HP-PB adapters such asHP28696A .SE SCSI. you specify the /dev/rmt device files when you configure the drives in NetBackup.

The H/W Path column of the changer output (schgr) includes the SCSI ID and LUN. you do not have to configure the kernel to use the sctl pass-through driver. If so. See “Example of how to create sctl device files for FCP (Itanium)” on page 62. TARGET is the SCSI ID of the robotic control. See “Example of how to create sctl device files for FCP (Itanium)” on page 62.HP-UX Configuring legacy device files
59
The sctl driver may be the default pass-through driver on your system. Major is the character major number (from the lsdev command). Attach the devices. LUN is the SCSI logical unit number (LUN) of the robot. see the HP-UX autochanger(7) man page.
■
Examples of how to create the device files are available. as follows:
■ ■
The instance number of the card is in the I column of the output.
4
Use the following commands to create the device file for the SCSI robotic control:
mkdir /dev/sctl cd /dev/sctl /usr/sbin/mknod cCARDtTARGETlLUN c Major 0xIITL00
Where:
■ ■ ■ ■
CARD is the card instance number of the adapter. Use the card's H/W Path value to filter the changer's H/W Path entry.
3
Determine the character major number of the sctl driver by using the following command:
lsdev -d sctl
Examine the output for an entry that shows sctl in the Driver column. For more information.
■
Install and configure the schgr device driver. the SCSI ID and the LUN remain.
. To create sctl device files
1 2
Invoke the ioscan -f command to obtain SCSI bus and robotic control information. Examine the output for the card instance number and the SCSI ID and LUN of the robotic device. See “Example of how to create a sctl device file for SCSI (PA-RISC)” on page 60.

For the ADIC robot.
cd /dev/sctl /usr/sbin/mknod c7t2l0 c 203 0x072000 /usr/sbin/mknod c7t3l0 c 203 0x073000
If you add the robots to NetBackup manually.
. With Fibre Channel. and the LUN is 0. the card instance number is 7. and the LUN is 0. For the IBM robot. the hardware paths are longer than with SCSI. the SCSI ID is 3. you specify the following for ADIC robotic control and IBM robotic control respectively:
/dev/sctl/c7t2l0 /dev/sctl/c7t3l0
Example of how to create a sctl device file for FCP (PA-RISC)
In the following example. the card instance number is 7. the target is 2.
4
The commands to create the device files follow. an STK 9740 robot contains one drive.HP-UX Configuring legacy device files
61
3
Determine the character major number of the sctl driver by using the following command:
lsdev -d sctl Character Block 203 -1
Driver sctl
Class ctl
The output from this command shows that the character major number for the sctl driver is 203.

1. as follows:
Class I H/W Path Driver S/W State H/W Type Description ================================================================== ext_bus 3 0/0/0. The card instance number is 3.0).0 stape CLAIMED DEVICE QUANTUM DLT7000 target 1 0/0/0.0.0 fcpmux CLAIMED INTERFACE HP A3308 FCP-SCSI MUX Interface target 0 0/0/0.0.0.8. as follows:
lsdev -d sctl Character Block 203 -1
Driver sctl
Class ctl
The output from this command shows that the character major number for the sctl driver is 203.0.0.0.0.0.8.0. LUN 0.8.1 tgt CLAIMED DEVICE autoch 0 0/0/0. and the LUN is 0. If you use the card's H/W Path value as a mask (0/0/0.8.0.0 sctl CLAIMED DEVICE Initiator
2
Examine the output for the card instance number and the SCSI ID and LUN of the robotic device.0. An STK 9740 robot is at SCSI ID 1.0.0.
cd /dev/sctl /usr/sbin/mknod c3t1l0 c 203 0x031000
If you add the robot to NetBackup manually.8.62
HP-UX Configuring legacy device files
To create an FCP robotic device file for HP-UX PA-RISC
1
ioscan -f
Invoke the ioscan -f command.8.0.0.0.
3
Determine the character major number of the sctl driver by using the lsdev command.0.0.
4
The commands to create the device file for the STK 9740 robotic control are as follows.0.0.7 tgt CLAIMED DEVICE ctl 3 0/0/0.8.0 schgr CLAIMED DEVICE STK9740 target 2 0/0/0.
.0.7. you specify the following pathname for robotic control:
/dev/sctl/c3t1l0
Example of how to create sctl device files for FCP (Itanium)
With Fibre Channel.0 tgt CLAIMED DEVICE tape 0 0/0/0. as in the following example: The interface card instance number (I column) is 3.0.0. LUN 0. the hardware paths are longer than with SCSI. a DLT 7000 drive is at SCSI ID 0.8. the target is 1.

Alternatively. and the devices must be attached and operational.64
HP-UX Configuring legacy device files
■
The robotic controls for the HP VLS 6000 robot partitions are through card instance 13. Robotic control for the other partition is at SCSI ID 0 and LUN 4. use either the HP-UX System Administration Manager (SAM) utility or the insf(1M) command. the tape driver must be installed and configured.
/dev/sctl/c12t0l0 /dev/sctl/c13t0l0 /dev/sctl/c13t0l4
Creating legacy tape drive device files
By default.
Creating tape drive pass-through device files
Usually.
4
The commands to create the devices file for the robotic controls are as follows:
cd /dev/sctl /usr/sbin/mknod c12t0l0 c 203 0x0c0000 /usr/sbin/mknod c13t0l0 c 203 0x0d0000 /usr/sbin/mknod c13t0l4 c 203 0x0d0400
If you add the robots to NetBackup manually. HP-UX creates tape drive device files when the system is booted. you can create them manually. The following example shows how to create the pass-through device files. To do so. NetBackup creates pass-through paths for tape drives automatically. you can create tape drive device files manually.
. However. The second and third device files are for the VLS 6000 robot (two robotic devices). For information. see the HP-UX documentation. The first device file is for the HP EML E-Series robot.
3
Determine the character major number of the sctl driver by using the following command:
lsdev -d sctl Character Block 203 -1
Driver sctl
Class ctl
The output from this command shows that the character major number for the sctl driver is 203. you specify the following pathnames for robotic control. However. Robotic control for one partition is at SCSI ID 0 and LUN 0.

HP-UX Configuring legacy device files

65

To create pass-through tape drive device files

1

Determine the devices that are attached to the SCSI bus by using the HP-UX ioscan -f command:

The robotic control for an ADIC Scalar 100 library is on a SCSI bus with an instance number of 7. The SCSI ID is 2, and the LUN is 0. The robotic control for an IBM ULT3583-TL library is on the same SCSI bus at SCSI ID 3 and LUN 0. The ADIC library contains two Quantum Super DLT drives. One has a SCSI ID of 0 and a LUN of 0. The other has a SCSI ID of 1 and a LUN of 0. The IBM library contains two IBM Ultrium LTO drives. One has a SCSI ID of 4 and a LUN of 0. The other has a SCSI ID of 5 and a LUN of 0. Use the IBM atdd driver when you configure IBM tape drives on HP-UX. Configure atdd and BEST device paths according to the IBM driver documentation. Do not configure atdd for robotic control of IBM robots.

■

■

66

HP-UX About SPC-2 SCSI reserve on HP-UX

For the latest recommended atdd driver version from IBM, check the Symantec support Web site.

When you use the HP-UX mknod command for tape drives, the target is the SCSI ID of the tape drive. It is not the SCSI ID of the robotic control. The previous commands create the following pass-through device files.
/dev/sctl/c7t0l0 /dev/sctl/c7t1l0 /dev/sctl/c7t4l0 /dev/sctl/c7t5l0

Although the pass-through device files for tape drives are used during NetBackup operation, they are not used during NetBackup configuration. During NetBackup tape drive configuration, use the following device files to configure the tape drives.
/dev/rmt/c7t0d0BESTnb /dev/rmt/c7t1d0BESTnb /dev/rmt/c7t4d0BESTnb /dev/rmt/c7t5d0BESTnb

About SPC-2 SCSI reserve on HP-UX
By default, NetBackup uses SPC-2 SCSI reserve and release for tape drive reservations in shared drive environments. However, you must disable SPC-2 SCSI reserve and release in HP-UX. If you do not, conflicts occur between the operating system and NetBackup. The NetBackup Shared Storage Option provides shared drive functionality in NetBackup. Symantec recommends that you use the SAM utility to disable SPC-2 SCSI reserve and release. As an alternative to SCSI reserve and release, you can use SCSI persistent reserve in NetBackup for shared tape drive reservations. If you use SCSI persistent reserve, you still must disable SPC-2 SCSI reserve and release in HP-UX.

HP-UX Disabling SPC-2 SCSI reserve in HP-UX

67

For more information about NetBackup and SCSI reservations, see the following:
■

The description of the Enable SCSI Reserve Media host property in the following:
■ ■

The NetBackup Administrator’s Guide for UNIX and Linux, Volume I The NetBackup Administrator’s Guide for Windows, Volume I

Disabling SPC-2 SCSI reserve in HP-UX
Use the following procedure to disable SPC-2 SCSI reserve in HP-UX. To disable SPC-2 SCSI reserve in HP-UX

1 2

Set the st_ats_enabled kernel parameter to 0 (zero) . Reboot the system.

Disable the HP-UX EMS Tape Device Monitor for a SAN
This topic is a NetBackup Enterprise Server topic. You should configure the Tape Device Monitor (dm_stape) so it does not run on HP-UX hosts in a SAN configuration. The Tape Device Monitor is a component of the Event Monitoring System (EMS). The EMS service periodically polls the tape devices to monitor their conditions. When a server polls the devices while another server uses a tape device, backup operations may time out and fail. You can avoid the situation as follows:
■

To disable EMS completely, run the HP-UX Hardware Monitoring Request Manager and select (K) kill (disable) Monitoring. Invoke the Hardware Monitoring Request Manager by using the /etc/opt/resmon/lbin/monconfig command. To configure EMS so it does not log any events or poll devices, set the POLL_INTERVAL value to 0 (zero). The POLL_INTERVAL parameter is in the following HP-UX configuration file:
/var/stm/config/tools/monitor/dm_stape.cfg

■

EMS runs but does not send any SCSI commands.

68

HP-UX About SAN clients on HP-UX

About SAN clients on HP-UX
NetBackup SAN clients use tape drivers and SCSI pass-through methods for Fibre Transport traffic to NetBackup FT media servers. On HP-UX systems, NetBackup SAN clients require the sctl pass-through driver and pass-through tape drive device files. If the sctl driver is not the default pass-through driver on your system, install and configure the sctl driver. See “Creating legacy SCSI and FCP robotic controls on HP-UX” on page 58. If the sctl driver is installed, by default HP-UX creates the /dev/rmt tape drive device files when the system is booted. (The NetBackup FT media server must be active and the SAN must be zoned correctly.) NetBackup automatically creates the required /dev/sctl pass-through device files from the /dev/rmt tape drive device files. The media server FT devices appear as ARCHIVE Python tape devices during SCSI inquiry from the SAN client. However, they are not tape devices and do not appear as tape devices in NetBackup device discovery.

Errors when more than 10 NetBackup jobs are active
Applies to HP PA-RISC systems only. If a NetBackup master server resides on an HP-UX PA-RISC host and more than 10 NetBackup jobs are active, additional jobs may fail. The NetBackup status code is 81 (the NetBackup volume manager daemon (vmd) is not active). This error indicates an operating system problem, not a NetBackup problem. The number of pending undo operations on a semaphore exceed the operating system limit. These errors continue to occur until fewer than 10 jobs are active. To resolve this OS limitation, Symantec recommends that you modify the HP-UX kernel semmnu parameter. Increase the value by at least the number of jobs greater than 10 that you want active concurrently. Symantec recommends at least 50 for the value. (The default value for semmnu is 30.) Symantec recommends that you use the HP System Management (SMH) utility to change the value of semmnu to 50. A reboot is necessary for the changes to take effect. For information about the SMH utility, see the HP-UX documentation. (The HP-UX System Administration Manager (SAM) utility is deprecated in HP-UX 11i V3 release.)

For usage examples.
lsdev -d driver
Displays the information about the SCSI robotic control drivers. class is the type of interface.HP-UX HP-UX command summary
69
HP-UX command summary
The following is a summary of commands that may be useful when you configure and verify devices. II are two hexadecimal digits that represent the card instance number.
. as follows:
■ ■ ■
tape specifies tape drives. The following describe the device file names:
■ ■ ■ ■ ■ ■ ■ ■
CARD is the card instance number of the adapter. Numeric information is displayed in decimal. ext_bus specifies SCSI controllers.
■
ioscan -C class -f
Shows the information about the physical interfaces.
mknod /dev/spt/cCARDtTARGETlLUN c Major 0xIITL00
Creates the device files for SCSI robotic or tape drive controls. as specified by the ioscan command. LUN is the SCSI logical unit number (LUN) of the robot. T is a hexadecimal digit that represents the SCSI ID of robotic control.
■
mksf -C tape -H hw-path -b BEST -u -n
Creates the device files for tape drives. TARGET is the SCSI ID of the robotic control. L is a hexadecimal digit that represents the SCSI LUN of the robotic control. The hw-path is the hardware path of the tape drive. see the procedures in this chapter. Major is the character major number (from the lsdev command).

70
HP-UX HP-UX command summary
.

see the Compatibility List for NetBackup Server or NetBackup Enterprise Server. NetBackup issues SCSI commands to the robotic devices. For NetBackup to function correctly. For the compatibility information. The Symantec support Web site contains server platform compatibility information. The following is the URL:
http://entsupport.Chapter
4
Linux
This chapter includes the following topics:
■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Before you begin on Linux About the required Linux SCSI drivers Verifying the Linux drivers Configuring robot and drive control for the Linux 2.
. Information about how to configure device files is available. the properly named device files must exits.symantec.6 kernel Verifying the device configuration About SAN clients on Linux About SCSI persistent bindings About Emulex HBAs Utilities to test SCSI devices Linux command summary
Before you begin on Linux
Observe the following important points when you configure the operating system:
■
Verify that NetBackup supports your server platform and devices.com
■
For SCSI controlled libraries.

6 kernel” on page 74. If you do not use a pass-through driver.
■
Multipath configurations (multiple paths to robots and drives) are supported only with the following configurations:
■ ■
Native path (/dev/nstx.
About the required Linux SCSI drivers
To use SCSI tape drives and robotic libraries. performance suffers. Enable multi-LUN support for the kernel according to the Linux documentation. as follows:
■
Follow the HBA vendor's installation guide to install or load the driver in the kernel.72
Linux About the required Linux SCSI drivers
See “Configuring robot and drive control for the Linux 2. This driver allows pass-through commands to SCSI tape drives and control of robotic devices. NetBackup and its processes use the pass-through driver as follows:
■ ■ ■ ■ ■ ■ ■ ■
To scan drives For SCSI reservations For SCSI locate-block operations For SAN error recovery For Quantum SDLT performance optimization To collect robot and drive information To collect Tape Alert information from tape drives For WORM tape support
. refer to your HBA vendor documentation.
■ ■
■
For more information. add the robots and the drives to NetBackup. the following drivers must be configured in the kernel or loaded as modules:
■
Linux SCSI generic (sg) driver.
■
Verify that a SCSI low-level driver is installed for each HBA in your system. Probe all LUNs on each SCSI device and enable the SCSI low-level driver for the HBA. Configure the kernel for SCSI tape support and SCSI generic support. /dev/sgx) The sysfs file system that is mounted on /sys
After you configure the hardware.

6.h ST_NBR_MODE_BITS values
Number of tape drives to support
64 128
Use this value for ST_NBR_MODE_BITS
1 0
About st buffer size and performance
Internal st tape driver buffers have a default size of 32K. the first is on a RedHat Linux system and the second is on a SUSE Linux system:
/usr/src/redhat/BUILD/kernel-2.60-0. use a value from the table. Modify the ST_BUFFER_BLOCKS parameter in the st_options.21/drivers/scsi
Table 4-1
st. This driver allows the use of SCSI tape drives.Linux About the required Linux SCSI drivers
73
■ ■ ■ ■
For future features and enhancements
SCSI tape (st) driver.h file.h file resides in the /drivers/scsi directory.18/linux-2. In the following two example paths.18.6. Because NetBackup uses only one minor number. you can modify the driver to support up to the following:
■ ■
64 tape devices (with four minor device numbers) 128 tape devices (with two minor device numbers)
Table 4-1 shows the ST_NBR_MODE_BITS parameter values.h file.
st driver support for additional tape devices
The st tape driver supports up to 32 tape devices in its default configuration.x86_64/drivers/scsi /usr/src/linux-2.
. The st. The default block size for bptm is 64K. Modify the ST_NBR_MODE_BITS parameter in the st.16. This configuration provides eight minor device numbers. The path to the /drivers/scsi directory depends on the Linux version and build. set the value to 64. You may improve performance if you set those buffers to match the default block size that the NetBackup bptm process uses. Standard SCSI driver.6. SCSI-adaptor driver.

you also may need to reduce the number of buffers to allow. To incorporate these source changes into your system. The default value is 4.74
Linux Verifying the Linux drivers
Depending on the available system memory. You can use the /sbin/lsmod command to verify that the st and the sg drivers are loaded in the kernel. Verify that the drivers are installed and loaded in the kernel. follow the operating system guidelines. including robotic devices. modify the ST_MAX_BUFFERS parameter in the st_options.6 kernel
NetBackup supports SCSI control and API control of robotic devices. NetBackup uses device files to configure control for SCSI tape devices. see the Linux documentation.
Verifying the Linux drivers
NetBackup requires specific Linux drivers. (A robotic device in a library moves the media between storage slots and the drives in the library.h file. Example output is as follows:
Module sg st Size 14844 24556 Used by 0 0
The standard Enterprise Linux releases have the sg and the st modules available for loading. The modules are loaded as needed.)
. Also. which is SCSI over Fibre Channel. as follows:
■
SCSI or Fibre Channel Protocol control. For details. To do so. See “About the required Linux SCSI drivers” on page 72. you can load these modules if they are not in the kernel.
About the st driver debug mode
You can enable debug mode for the st tape driver. Debug mode echoes each command and its result to the system log. Use the following commands:
/sbin/modprobe st /sbin/modprobe sg
Configuring robot and drive control for the Linux 2. You must configure the control method. SCSI control includes Fibre Channel Protocol (FCP).

6 kernel tape drive device files” on page 75. NetBackup discovers the device files (and hence the devices) automatically. If you use device discovery in NetBackup. If you use device discovery. if you add a robot manually in NetBackup. If you change the default mode.Linux Verifying the device configuration
75
See “About the Linux 2. which results in data loss. Alternatively.
About the Linux 2. see the Linux documentation for information about how to create them. run the following command from a terminal window to view this file:
cat /proc/scsi/scsi
The output that is displayed should be similar to the following:
.6 kernel robotic control device files ” on page 75. NetBackup looks for /dev/sgx robotic control device files. See “About the Linux 2. you must enter the pathname to the device file for that drive. Linux should create the device files automatically. you must enter the pathname to the device file for that robotic device. See the "IBM Automated Tape Library (ATL)" chapter of this guide. If the device files do not exist. The Linux driver should create the device files automatically.
About the Linux 2. See the "Sun StorageTek ACSLS robots" chapter of this guide.
■
API control over a LAN. where x is a decimal number from 0 to 255. NetBackup discovers the robotic control device files (and hence the devices) automatically. if you add a drive manually in NetBackup. See the "ADIC Automated Media Library (AML)" chapter of this guide. To verify that the operating system can see the devices.6 kernel robotic control device files
For robotic devices. NetBackup uses the /dev/nstx files (n indicates the no rewind device file). NetBackup may not read and write tapes correctly.6 kernel tape drive device files
For tape drive device files. NetBackup looks for /dev/nstx device files. NetBackup uses the /dev/sgx device files. see the Linux documentation for information about how to create them. If the device files do not exist.
Verifying the device configuration
The /proc/scsi/scsi file shows all of the devices that the SCSI driver detects. The NetBackup avrd daemon establishes a default tape driver operating mode. Alternatively.

The robtest utility resides in /usr/openv/volmgr/bin. You can use theNetBackup robtest utility to test robots. see the mt(1) man page.
■
/usr/sbin/reboot
Stops and restarts the system. For more information. x is a decimal number from 0 to 255.
■
/sbin/modprobe
Installs loadable kernel modules.
■
/bin/mknod /dev/sgx c 21 N
Creates SCSI generic device files.78
Linux Utilities to test SCSI devices
Utilities to test SCSI devices
You can manipulate tape devices with the operating system mt command.
.
Linux command summary
The following is a summary of commands that were used in this chapter:
■
/sbin/lsmod
Lists the modules that are loaded. A set of SCSI utilities are available from the Linux SCSI Generic (sg) driver home page.

symantec.Chapter
5
Solaris
This chapter includes the following topics:
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Before you begin on Solaris About the NetBackup sg driver Installing the NetBackup sg driver Uninstalling the sg driver Special configuration for the Sun StorEdge Network Foundation HBA driver Binding Fibre Channel HBA drivers Configuring the sg and the st drivers Preventing driver unloading About Solaris robotic controls About Solaris tape drive device files Configuring SAN clients to recognize FT media servers Solaris command summary
Before you begin on Solaris
Observe the following points when you configure the operating system:
■
Verify that NetBackup supports your server platform and devices.com
. For the compatibility information. see the Compatibility List for NetBackup Server or NetBackup Enterprise Server. The following is the URL:
http://entsupport. The Symantec support Web site contains server platform compatibility information.

Therefore. ensure that the SAN and storage devices are configured correctly.
. those HBAs do not support WORM media. If you remove or replace adapter cards.
■ ■ ■
Verify that the Solaris st driver is installed.
The Solaris tape and disk driver interfaces also create a device file for each tape drive device. For NetBackup to function correctly. This driver is called the SCSA (generic SCSI pass-through driver). See “About Solaris robotic controls” on page 89. the SCSI generic sg driver. If you use the Automated Cartridge System (ACS) robotic software. you must ensure that the SunOS BSD Source Compatibility Package is installed. remove all device files that are associated with that adapter card. create a touch file as follows:
touch /usr/openv/volmgr/database/SIXTEEN_BYTE_CDB
■
■
■
■
After you configure the hardware. To override this limitation. you should attach all peripherals and reboot the system with the reconfigure option (boot -r or reboot -. These device files must exist for all read or write I/O capability. You must configure this driver properly to create device files for any device NetBackup uses. Verify that the devices are configured correctly. For the NetBackup shared storage options. NetBackup issues SCSI commands to the robotic devices. also referred to as the sg driver. Sun systems with parallel SCSI host bus adapters do not support 16-byte SCSI commands on any devices that are attached to these HBAs. The package is required so that the ACS software can use the shared libraries in /usr/ucblib. as follows:
■
NetBackup installs its own pass-through driver.-r). use the Solaris mt command and the NetBackup /usr/openv/volmgr/bin/sgscan utility. To do so. add the robots and the drives to NetBackup. the properly named device files must exits.
About the NetBackup sg driver
NetBackup provides its own SCSI pass-through driver to communicate with SCSI-controlled robotic peripherals. When you configure devices.80
Solaris About the NetBackup sg driver
■
For SCSI controlled libraries.

Solaris Installing the NetBackup sg driver
81
For full feature support. See “About the NetBackup sg driver” on page 80. To determine if the sg driver is loaded
◆
Invoke the following command:
/usr/sbin/modinfo | grep sg
If the driver is loaded. to install the driver. To collect Tape Alert information from tape devices allowing support of functions such as tape drive cleaning. More information about the driver is available. NetBackup requires the sg driver and SCSI pass-through device paths. By NetBackup to position tapes by using the locate-block method. By NetBackup for SCSI reservations. or to reinstall the driver. performance suffers. If you do not use a pass-through driver. By NetBackup device configuration to collect robot and drive information. NetBackup does not support the Solaris sgen SCSI pass-through driver. Future NetBackup features and enhancements
■ ■
Note: Because NetBackup uses its own pass-through driver. By NetBackup for SAN error recovery.5e)
. output includes a line similar to the following:
141 fc580000 2d8c 116 1 sg (SCSA Generic Revision: 3. NetBackup uses the pass-through driver for the following:
■ ■ ■ ■ ■ ■ ■
By avrd and robotic processes to scan drives. For WORM tape support.
Installing the NetBackup sg driver
Use the following procedures to determine if the sg driver is loaded. By NetBackup for Quantum SDLT performance optimization.

install
After you install the driver.install
Uninstalling the sg driver
You can uninstall the sg driver. it binds the StorEdge Network Foundation host bus adapter World Wide Port Names for use by the sg driver.conf
2
Install the sg driver. To determine if a host contains a StorEdge Network Foundation HBA. as follows:
/usr/openv/volmgr/bin/driver/sg.install command during or after each system boot. To reinstall the sg driver
1
Remove the sg.82
Solaris Uninstalling the sg driver
To install the sg driver
◆
Invoke the following command:
/usr/openv/volmgr/bin/driver/sg. See “Configuring the sg and the st drivers” on page 83. you do not have to reboot the system or run the sg. Ensure that the luxadm command is installed and in the shell path. as follows:
/usr/bin/rm -f /kernel/drv/sg. NetBackup performance suffers. you can run the following command:
/usr/openv/volmgr/bin/sgscan
If the script detects a StorEdge Network Foundation HBA. If you do. To uninstall the sg driver
◆
Invoke the following command:
/usr/sbin/rem_drv sg
Special configuration for the Sun StorEdge Network Foundation HBA driver
When you configure the sg driver. The configuration process uses the Solaris luxadm command to probe for HBAs that are installed in the system. it produces output similar to the following example:
.conf file.

When you bind devices to targets.Solaris Binding Fibre Channel HBA drivers
83
#WARNING: detected StorEdge Network Foundation connected devices not in sg configuration file: # # Device World Wide Port Name 21000090a50001c8 # # See /usr/openv/volmgr/NetBackup_DeviceConfig_Guide.
. If you change the ID. In some instances. Each time you add or remove a device. Symantec products are configured to use a specific target ID. you must bind the devices to specific target IDs on the NetBackup host. For information about how to modify the HBA configuration files to bind devices to targets.
Configuring the sg and the st drivers
You must configure the NetBackup sg driver and the Sun st driver on each Solaris NetBackup media server that hosts tape devices. continue with the Solaris configuration in the same manner as for parallel SCSI installations. See “Configuring the sg and the st drivers” on page 83.build and # sg.
Binding Fibre Channel HBA drivers
For Fibre Channel HBAs other than Sun StorEdge Network Foundation. The binding may be based on the following:
■ ■ ■
Fibre Channel World Wide Port Name (WWPN) World Wide Node Name (WWNN) The destination target ID and LUN
After you bind the devices to target IDs. see the documentation for the HBA. the products fail until you configure the ID correctly. the target ID does not change after a system reboot or a Fibre Channel configuration change.install to configure these devices
Each time you add or remove a device.txt topic # "Special configuration for Sun StorEdge Network Foundation # HBA/Driver" for information on how to use sg. you should configure the sg and the st drivers again. How you bind devices to targets is vendor and product specific. you must update the bindings and then configure the sg and the st drivers again.

conf file:
name="st" name="st" name="st" name="st" name="st" name="st" name="st" class="scsi" class="scsi" class="scsi" class="scsi" class="scsi" class="scsi" class="scsi" target=0 target=1 target=2 target=3 target=4 target=5 target=6 lun=0.84
Solaris Configuring the sg and the st drivers
Each time you add or remove a device. lun=0.conf file with all of the entries from the /usr/openv/volmgr/bin/driver/st.conf
See “st. lun=0. To configure the sg and the st drivers
1
Invoke the following two commands to run the NetBackup sg.
■
/usr/openv/volmgr/bin/driver/sg.
You should make a backup copy of the /kernel/drv/st.build all -mt target -ml lun
The following describes the options:
■
The all option creates the following files and populates them with the appropriate entries:
■
/usr/openv/volmgr/bin/driver/st. lun=0.
.links file example” on page 87.conf
See “sg. Before you configure the sg and the st drivers.
■
The -mt target option and argument specify the maximum target ID that is in use on the SCSI bus (or bound to an FCP HBA).conf file example” on page 85.build script:
cd /usr/openv/volmgr/bin/driver /usr/openv/volmgr/bin/sg.links
See “sg. By default. the SCSI initiator target ID of the adapter is 7. lun=0. The -ml lun option and argument specify the maximum number of LUNs that are in use on the SCSI bus (or by an FCP HBA).conf file example” on page 86. lun=0. The maximum value is 126. you should configure the sg and the st drivers again.
■
/usr/openv/volmgr/bin/driver/sg.conf file before you modify it. The maximum value is 255.
■
2
Replace the following seven entries in the /kernel/drv/st. lun=0. ensure that all devices are turned on and connected to the HBA. so the script does not create entries for target ID 7.

lun=1. lun=2.tab file.links file to the /etc/devlink. lun=0. the system probes all targets in the st.
st.conf file example shows targets 0-15 and LUNs 0-7. During the boot process.
4
Verify that the system created the device nodes for all the tape devices by using the following command:
ls -l /dev/rmt/*cbn
5
Install the new sg driver configuration by invoking the following two commands:
/usr/bin/rm -f /kernel/drv/sg.conf.-r).conf file example
The following /usr/openv/volmgr/bin/driver/st.
name="st" class="scsi" target=0 name="st" class="scsi" target=0 name="st" class="scsi" target=0 name="st" class="scsi" target=0 name="st" class="scsi" target=0 name="st" class="scsi" target=0 name="st" class="scsi" target=0 name="st" class="scsi" target=0 name="st" class="scsi" target=1 name="st" class="scsi" target=1 name="st" class="scsi" target=1 .conf /usr/openv/volmgr/bin/driver/sg. Creates the /dev/sg directory and nodes.install script does the following:
■ ■
Installs and loads the sg driver.
.
■ ■
6
Verify that the sg driver finds all of the robots and tape drives.conf file to /kernel/drv/sg. lun=5.conf file for devices.Solaris Configuring the sg and the st drivers
85
3
Reboot the system with the reconfigure option (boot -r or reboot -.install
The NetBackup sg. lun=6. Appends the /usr/openv/volmgr/bin/driver/sg. lun=3. <entries omitted for brevity> . lun=7. Copies the /usr/openv/volmgr/bin/driver/sg. lun=0. lun=2. lun=4. It should create device files for all devices it discovers. lun=1.

addr=w500104f0008d53c3.name=sg.addr=w500104f0008d53c3.name=sg.name=sg.addr=w500104f0008d53b9.addr=w500104f0008d53c9. type=ddi_pseudo. type=ddi_pseudo.addr=w500104f0008d53b9. and Fibre Channel drivers.name=sg. The drivers are the st driver (from Sun).addr=w500104f0008d53c9. When the driver loads and unloads occur may cause problems. These problems can range from a SCSI bus not able to detect a device to system panics. Symantec recommends that you prevent Solaris from unloading the st and the sg drivers from memory.1.0.name=sg.0. type=ddi_pseudo.name=sg.1. The following is an example for a JNI driver:
forceload: drv/fcaw
.addr=w500104f0008d53c6.88
Solaris Preventing driver unloading
type=ddi_pseudo.0.1.addr=w500104f0008d53b9. type=ddi_pseudo. To prevent Solaris from unloading the st and the sg drivers from memory
◆
Add the following forceload statements to the /etc/system file:
forceload: drv/st forceload: drv/sg
To prevent Solaris from unloading the Fibre Channel drivers from memory
◆
Add an appropriate forceload statement to the /etc/system file: Which driver you force to load depends on your Fibre Channel adaptor.name=sg. type=ddi_pseudo.name=sg.name=sg.1.0.name=sg. Solaris unloads unused drivers from memory and reloads drivers as needed.name=sg.name=sg. type=ddi_pseudo.1.1.addr=w500104f0008d53c6.0.1.name=sg.addr=w500104f0008d53b9.name=sg. type=ddi_pseudo. the sg driver (from Symantec).addr=w500104f0008d53cc.addr=w500104f0008d53cc. type=ddi_pseudo.addr=w500104f0008d53cc. type=ddi_pseudo.name=sg. type=ddi_pseudo. Tape drivers are often unloaded because they are used less often than disk drivers.1. type=ddi_pseudo.0.addr=w500104f0008d53cc. type=ddi_pseudo.addr=w500104f0008d53c9. # end SCSA devlinks
sg/c\N0t\A1l1 sg/c\N0t\A1l0 sg/c\N0t\A1l1 sg/c\N0t\A1l0 sg/c\N0t\A1l1 sg/c\N0t\A1l0 sg/c\N0t\A1l1 sg/c\N0t\A1l0 sg/c\N0t\A1l1 sg/c\N0t\A1l0 sg/c\N0t\A1l1 sg/c\N0t\A1l0 sg/c\N0t\A1l1 sg/c\N0t\A1l0 sg/c\N0t\A1l1
Preventing driver unloading
When system memory is limited. type=ddi_pseudo.0. type=ddi_pseudo.

a NetBackup script creates the device files for the attached robotic devices. If you add a robot manually in NetBackup.Solaris About Solaris robotic controls
89
About Solaris robotic controls
NetBackup supports SCSI control and API control of robotic devices. See “About the NetBackup sg driver” on page 80. See the "Sun StorageTek ACSLS robots" chapter of this guide. See the "ADIC Automated Media Library (AML)" chapter of this guide.
Examples of SCSI and FCP robotic control device files
The following is an example of sgscan all output from a host. use the NetBackup sgscan command with the all parameter. Robotic control varies. NetBackup discovers the robotic control device files in the /dev/sg directory (and hence the devices) automatically. API control over a LAN. as follows:
■
SCSI or Fibre Channel Protocol control. See “Examples of SCSI and FCP robotic control device files” on page 89. A robotic device in a library moves the media between the storage slots and the drives in the library.
■
About SCSI and FCP robotic controls on Solaris
When you configure the NetBackup sg driver. to which the examples refer:
# /usr/openv/volmgr/bin/sgscan all /dev/sg/c0t6l0: Cdrom: "TOSHIBA XM-5401TASUN4XCD" /dev/sg/c1tw500104f0008d53b9l0: Changer: "STK SL500" /dev/sg/c1tw500104f0008d53c3l0: Tape (/dev/rmt/0): "HP /dev/sg/c1tw500104f0008d53c6l0: Tape (/dev/rmt/1): "HP /dev/sg/c1tw500104f0008d53c9l0: Tape (/dev/rmt/2): "IBM /dev/sg/c1tw500104f0008d53ccl0: Tape (/dev/rmt/3): "IBM
Ultrium 3-SCSI" Ultrium 3-SCSI" ULTRIUM-TD3" ULTRIUM-TD3"
. See “About SCSI and FCP robotic controls on Solaris” on page 89. Examples are available. See the "IBM Automated Tape Library (ATL)" chapter of this guide. you must enter the pathname to the device file. To display the device files that the sg driver can use. The word "Changer" in the sgscan output identifies robotic control device files. If you use device discovery in NetBackup.

the following is the device file pathname:
/dev/sg/c1tw500104f0008d53b9l0
Example 2 — STK SL500
For the SCSI robotic control for an STK SL500 is SCSI ID 1 of adapter 2. the following is the device file pathname:
/dev/sg/c2t1l0
About Solaris tape drive device files
NetBackup uses the tape drive device files that support compression. b indicates Berkeley-style close.90
Solaris About Solaris tape drive device files
/dev/sg/c2t1l0: /dev/sg/c2t2l0: /dev/sg/c2t3l0: /dev/sg/c2tal0: /dev/sg/c2tbl0: /dev/sg/c3t0l0: /dev/sg/c3t3l0:
Changer: "STK SL500" Tape (/dev/rmt/22): "HP Ultrium 3-SCSI" Tape (/dev/rmt/10): "HP Ultrium 3-SCSI" Tape (/dev/rmt/18): "IBM ULTRIUM-TD3" Tape (/dev/rmt/19): "IBM ULTRIUM-TD3" Disk (/dev/rdsk/c1t0d0): "FUJITSU MAV2073RCSUN72G" Disk (/dev/rdsk/c1t3d0): "FUJITSU MAV2073RCSUN72G"
You can filter the sgscan output for device types by using other sgscan options. Solaris creates the device files for the attached tape devices See “Configuring the sg and the st drivers” on page 83. and Berkeley style close. Therefore.
. The following is the sgscan usage statement:
sgscan [all|basic|changer|disk|tape] [conf] [-v]
Example 1 — StorEdge Network Foundation HBA
The robotic control for a Sun StorEdge Network Foundation HBA attached library is LUN 0 of World Wide Node Name (WWNN) 500104f0008d53b9. and they have the following format:
/dev/rmt/IDcbn
The following describe the device file names:
■ ■ ■
ID is the logical drive number as shown by the NetBackup sgscan command. no rewind on close. When you configure the Solaris st driver. c indicates compression. The device files are in the /dev/rmt directory.

In Berkeley-style close. the tape position remains unchanged by a device close operation. The letter b in the file name indicates Berkeley-style close device files. The output can help you associate tape devices with other SCSI devices that may be configured on the same adapter.) To establish the correct position for the next tape operation. the device file pathname is:
/dev/rmt/22cbn
You can show all device types by using the all option. use the sgscan command with the tape parameter. as follows:
# /usr/openv/volmgr/bin/sgscan tape /dev/sg/c1tw500104f0008d53c3l0: Tape (/dev/rmt/0): "HP Ultrium 3-SCSI" /dev/sg/c1tw500104f0008d53c6l0: Tape (/dev/rmt/1): "HP Ultrium 3-SCSI" /dev/sg/c1tw500104f0008d53c9l0: Tape (/dev/rmt/2): "IBM ULTRIUM-TD3" /dev/sg/c1tw500104f0008d53ccl0: Tape (/dev/rmt/3): "IBM ULTRIUM-TD3" /dev/sg/c2t2l0: Tape (/dev/rmt/22): "HP Ultrium 3-SCSI" /dev/sg/c2t3l0: Tape (/dev/rmt/10): "HP Ultrium 3-SCSI" /dev/sg/c2tal0: Tape (/dev/rmt/18): "IBM ULTRIUM-TD3" /dev/sg/c2tbl0: Tape (/dev/rmt/19): "IBM ULTRIUM-TD3"
The following are examples of no-rewind. compression. in AT&T-style close. no rewind on close. NetBackup assumes Berkeley-style close on HP-UX systems.Solaris About Solaris tape drive device files
91
■
n indicates no rewind on close. NetBackup discovers the device files and hence the devices.
If you use device discovery in NetBackup. the drive advances the tape to just after the next end-of-file (EOF) marker. NetBackup requires compression. To display the tape device files that are configured on your system. the device file pathname is:
/dev/rmt/0cbn
■
For the HP Ultrium3 SCSI drive at SCSI ID 2 of adapter 2. and Berkeley-style close device files. Berkeley-style close device files from the preceding sgscan example output:
■
For the Ultrium3 SCSI drive at LUN 0 of World Wide Node Name (WWNN) 500104f0008d53c3. you must specify the pathname to the device file. (Conversely.
. The following is the sgscan usage statement:
sgscan [all|basic|changer|disk|tape] [conf] [-v]
About Berkeley-style close
NetBackup requires Berkeley-style close for tape drive device files. applications must assume the tape's position after a close. If you add a tape drive to a NetBackup configuration manually.

After you disable SPC-2 SCSI reserve. If the drive does not support CRH and you do not disable SPC-2 SCSI reserve. DTF. execute the following command:
touch /usr/openv/volmgr/database/NO_LOCATEBLOCK
If locate-block positioning is disabled. as follows:
■
For the tape drives that support SPC-3 Compatible Reservation Handling (CRH). Alternatively. The NetBackup Shared Storage Option provides shared drive functionality in NetBackup. the tape is not rewound after a close operation. access attempts to the drive fail. see the following:
. and half-inch tape drives.
About SPC-2 SCSI reserve on Solaris
By default. It remains in position for the next write operation. NetBackup uses the forward-space-file/record method. To position a tape to a specific block. you must disable SPC-2 SCSI reserve in Solaris for those drives. If you need to disable it.92
Solaris About Solaris tape drive device files
About no rewind device files on Solaris
NetBackup requires no rewind on close device files for tape drives. The letter n in the device file names in the /dev/rmt directory specifies no rewind on close. NetBackup supports the SCSI locate-block command. It requires the NetBackup sg driver. Symantec recommends that you do not disable locate-block positioning. Exabyte.
■
For more information about NetBackup and SCSI reservations. DLT. See “Disabling SPC-2 SCSI reserve on Solaris” on page 93. you can use SCSI persistent reserve for shared tape drive reservations in NetBackup. NetBackup uses SPC-2 SCSI reserve and release for tape drive reservations in shared drive environments. No special configuration in Solaris is required. With no rewind on close. For the tape drives that do not support CRH. NetBackup uses the locate-block command by default.
About fast-tape positioning (locate-block) on Solaris
Applies to AIT. you can use persistent reserve by enabling it in NetBackup. you can use SCSI persistent reserve by enabling it in NetBackup.

In the tape-config-list section of the st. Volume II The NetBackup Administrator’s Guide for Windows. Also see the Solaris devices and file systems documentation.0. To receive the most current support for devices.0x20000.
About nonstandard tape drives
Solaris includes the device drivers that support most standard devices. However.4.conf file. Volume I
■
The "How NetBackup reserves drives" topic in the following:
■ ■
The NetBackup Administrator’s Guide for UNIX and Linux. the device vendor should contact Sun Microsystems to add support for the device to Solaris.conf file on the NetBackup media server. the device manufacturer should provide the software to install and administer the device properly. See “About SPC-2 SCSI reserve on Solaris” on page 92. In addition.
For more information about the st. the following entry disables SCSI reserve and release for all tape drives that use the DLT7k-data configuration values:
DLT7k-data = 1. you should install the latest Solaris patch for the st driver.0x82.2. contact the device vendor.
.0x85.0x84. see the Solaris st(7D) man page.Solaris About Solaris tape drive device files
93
■
The description of the Enable SCSI Reserve Media host property in the following:
■ ■
The NetBackup Administrator’s Guide for UNIX and Linux. More information about reservations is available. set the ST_NO_RESERVE_RELEASE configuration value (0x20000) in the appropriate data-property-name entry. For more information about what you need for unsupported devices. Volume I The NetBackup Administrator’s Guide for Windows.conf file.0x38. if you have a device that Solaris does not support. Volume II
Disabling SPC-2 SCSI reserve on Solaris
Use the following procedure to disable SPC-2 SCSI reserve. For example. To disable SPC-2 SCSI reserve
◆
Modify the Solaris st.0x83.

Examine the tape-config-list= section for a line that begins with ARCHIVE Python and contains ARCH_04106. Delete the comment character (#) from the beginning of the line. Therefore. The media server FT devices appear as ARCHIVE Python tape devices during SCSI inquiry on the SAN client.conf file. Use the following procedures to configure the Solaris operating system so that it recognizes the FT devices on the NetBackup media servers. 0x00. 0. 0x8C. st. 0x8c. 0x8C. "FT Pipe". 3. 0x2C. they are not tape devices and do not appear as tape devices in NetBackup device discovery.
. If such a line exists. ensure that it begins with a comment character (#). However. To add the FT device entry to the st. The following is an example of the line:
ARCH_04106 = 1. 4.conf file
1 2
In the /kernel/drv/st. 0x09639.conf file changes to ARCHIVE Python do not affect an existing tape drive product. copy it.94
Solaris Configuring SAN clients to recognize FT media servers
Configuring SAN clients to recognize FT media servers
NetBackup SAN clients use tape drivers and SCSI pass-through methods for Fibre Transport traffic to NetBackup FT media servers. Symantec owns the ARCHIVE brand name and Python product name.
3
4
Find the line that begins with ARCH_04106. Add the following line to the tape-config-list= section:
"ARCHIVE Python". find the tape-config-list= section or create it if it does not exist. and paste it after the tape-config-list= line. "ARCH_04106".

conf.conf. and generates SCSI Target IDs with multiple LUNs. and sg.-r
Reboot the system with the reconfigure option (-r). The kernel’s SCSI disk (sd) driver then recognizes the drive as a disk drive during system initialization.96
Solaris Solaris command summary
Updates st.
■
boot -r or reboot -.
. Also checks for the devices that are connected to the Sun StorEdge Network Foundation HBA that are not configured for use by Symantec products.links. See the procedures in this chapter for examples of their usage.
■
/usr/openv/volmgr/bin/sgscan all
Scans all connected devices with an SCSI inquiry and provides correlation between physical and the logical devices that use all device files in /dev/sg. sg.

Make sure that Windows detects the devices on the SAN before you configure the NetBackup Shared Storage Option. NetBackup issues SCSI pass-through commands to the devices in a configuration. The following is the URL: http://entsupport. Verify that your server platform is supported before configuring devices. This will normally be the device with the lowest-ordered LUN.Chapter
6
Windows
This chapter includes the following topics:
■ ■ ■
Before you begin on Windows About tape device drivers on Windows Attaching devices to a Windows system
Before you begin on Windows
Observe the following points when performing the configurations described in this chapter:
■
The Symantec support web site contains server platform compatibility information for a number of vendors and products (see the NetBackup Product > Compatibility area of the site).
■
■
■
. If you have multiple devices connected to a fibre bridge.com For NetBackup to recognize and communicate with connected devices and for device discovery to discover devices. A tape driver must exist for each tape device. The device applications available on your server may differ depending on your Windows operating system. Use the Microsoft Windows device applications to verify that the devices are configured correctly.symantec. Attached devices appear in the registry. Windows may only see one LUN.

Ensure that SCSI targets and termination settings are consistent with adapter card and peripheral vendor recommendations.
Attaching devices to a Windows system
The following steps describe a general method for attaching devices to a Windows computer. follow the vendor’s instructions for attaching the device. The Microsoft Windows device applications available on the server that you use in these steps may differ depending on your Windows operating system.98
Windows About tape device drivers on Windows
This limitation occurs because of the default install settings for the device driver for some fibre channel HBAs. If you add drives. To attach devices to a Windows system
1 2
Use the appropriate Windows application to obtain information on any currently attached SCSI devices.
After configuring the hardware. If you attach a new robotic library or drive to a NetBackup media server.
3
Reboot the server and answer the prompts for adapter card peripheral configuration options. See the "IBM Automated Tape Library (ATL)" chapter of this guide. See your vendor documentation to verify the settings.
4
. Watch the display to ensure that the adapter card recognizes the attached peripherals. If you require drivers.
■
Information about how to configure API robot control over a LAN is available See the "ADIC Automated Media Library (AML)" chapter of this guide.
About tape device drivers on Windows
Symantec does not provide device drivers for Windows hosts. install the tape drivers and use the appropriate Windows application to verify that the drive was recognized. add the drives and robots to NetBackup. See the "Sun StorageTek ACSLS robots" chapter of this guide. Shut down the server and physically attach the supported device. contact Microsoft or the tape drive vendor.

in terms of slot capacity or number of drives. NetBackup classifies robots according to one or more of the following characteristics:
■
The communication method the robotic control software uses.12 media slots). To determine which robot type applies to the model of robot that you use. NetBackup uses robotic control software to communicate with the robot firmware. see the Symantec support Web site at the following URL:
. The physical characteristics of the robot. The media type commonly used by that class of robots.
■
■
The following table lists the NetBackup robot types. Stacker usually refers to a robot with one drive and low media capacity (6 . SCSI and API are the two main methods. HCART (1/2-inch cartridge tape) and 8 mm are examples of media types.Chapter
7
Robot overview
This chapter includes the following topics:
■ ■ ■ ■ ■
About NetBackup robot types Robot attributes Table-driven robotics Robotic test utilities Robotic processes
About NetBackup robot types
A robot is a peripheral device that mounts and unmounts media in tape drives. with drive and slot limits for each type. Library usually refers to a larger robot.

Symantec does not provide support for robtest. You may be able to add support for new or upgraded devices without waiting for a maintenance patch from Symantec.
Robotic test utilities
You can use robotic test utilities for testing robots already configured in NetBackup. ADIC AML/S.
Media type support
Hosts supported Barcode support
Robot examples
ADIC AML/J. HCART. you can obtain a list of available test commands by entering a question mark (?). you can download an updated mapping file to obtain support for newly NetBackup-certified devices. Barcodes must be the same as the media ID (1 to 6 characters). The device mapping file includes the information that relates to the operation and control of libraries. and Linux Yes. DTF. 8MM.
.108
Robot overview Table-driven robotics
Table 7-7 Attribute
TLM robot attributes (continued) NetBackup Enterprise Server
4MM. HCART3. DLT. REWR_OPT (HP9000-800 only). UNIX. WORM_OPT (HP9000-800 only). Windows. 8MM3. Therefore.
Table-driven robotics
Table-driven robotics provides support for new robotic library devices without the need to modify any library control binary files. Note: The robtest utility is provided "as is" for customer convenience.exe (Windows)
From each test utility. HCART2. This feature uses a device mapping file for supported robots and drives. Depends on DAS/SDLC software to obtain the Media Manager media ID. Invoke the test utilities as follows:
■ ■
/usr/openv/volmgr/bin/robtest (UNIX and Linux) install_path\Veritas\Volmgr\bin\robtest. DLT3. and ADIC Scalar 10000. DLT2. 8MM2.

It mounts or unmounts tapes If the connection cannot be made or errors exist.Robot overview Robotic processes
109
The following point applies only to NetBackup Enterprise Server.
. When a connection is made to the appropriate robotic library. In addition. it starts the robotic processes and the robotic control processes for all of the configured robots on that host. You can also start and stop this daemon or service by using the Device Monitor Actions menu or the Media and Device Management Actions menu. When a robotic process or robotic control process is active. When the Device Manager stops. the robotic processes and the robotic control processes stop. and it returns to the UP state when the connection is made or problems no longer exist. the process changes to the DOWN state. the NetBackup Activity Monitor Processes tab shows it in the UP state or DOWN state. by the IBM device number For TLM robot types. by ACS. Use the drstat command to determine the drive addressing parameters for ACS. TLH. the NetBackup Commands guide describes commands to control the robotic processes that run on Windows media servers. Panel. (On UNIX. by the robot drive number
Robotic processes
A NetBackup robotic process and possibly a robotic control process exist on a NetBackup media server for each robot that you install. the corresponding process is in the UP state. LSM.) The Daemons (UNIX and Linux) tab or Services (Windows) tab of the NetBackup Activity Monitor has commands to start and stop this daemon or service. NetBackup addresses drives as follows:
■ ■ ■ ■
For ACS robot types. and TLM robot types. This command is available in the robotic test utilities for these robot types.
■
When the NetBackup Device Manager starts. and Drive number For TLH robot types. by the DAS/SDLC drive name For other robot types. Robotic control processes exist only for the robot types that support library sharing (or robot sharing). the name is Media Manager Device daemon. The robotic process receives requests from the NetBackup Device Manager (ltid) and sends necessary information directly to the robotics or to a robotic control process. In the DOWN state. the process still runs. as follows:
■
Every media server that has a drive in a robotic library has a robotic process for that robotic library.

Tape library 8MM (TL8)
tl8d
tl8cd
. It also requests inventories of the volumes that are under the control of ACS library software. The tape library DLT Control daemon tldcd communicates with the tape library DLT robotics through a SCSI interface.110
Robot overview Robotic processes
Processes by robot type
Table 7-8 describes the robotic processes and robotic control processes for each robot type. UNIX and Linux only. For library sharing. The tape library DLT daemon tldd runs on a NetBackup server that has a drive in the tape library DLT. tldcd. acsssi processes all RPC communications from acsd or from the ACS robotic test utility that are intended for the ACS library software. This process receives NetBackup Device Manager requests to mount and unmount volumes. tl8cd runs on the NetBackup server that has the robotic control. tldcd runs on the NetBackup server that has the robotic control. UNIX and Linux only. tl8cd. The NetBackup ACS storage server interface (SSI) event logger acssel logs events. The tape library 8MM Control daemon tl8cd communicates with the TL8 robotics through a SCSI interface.
Process
acsd
acssel
acsssi
Tape library DLT (TLD) tldd
tldcd
Tape library 4MM (TL4)
tl4d
The tape library 4MM daemon tl4d runs on the host that has a tape library 4MM. The NetBackup ACS storage server interface (SSI) acsssi communicates with the ACS library software host. and sends these requests to the robotic-control process. For library sharing. This process receives NetBackup Device Manager requests to mount and unmount volumes and communicates these requests to the robotics through a SCSI interface. Table 7-8 Robot type
Automated Cartridge System (ACS)
Robotic processes and robotic control processes Description
The NetBackup ACS daemon acsd provides robotic control to mount and dismount volumes. and sends these requests to the robotic-control process. The tape library 8MM daemon tl8d runs on a NetBackup server that has a drive in the tape library 8MM. This process receives NetBackup Device Manager requests to mount and unmount volumes.

Figure 7-1 shows the processes and where they run for a TLD robot.
. However.Robot overview Robotic processes
111
Table 7-8 Robot type Process
Robotic processes and robotic control processes (continued) Description
The tape library Half-inch daemon tlhd runs on each NetBackup server that has a drive in the tape library Half-inch. the tldd process on the host to which the drive is attached sends control information to the tldcd process on the robotic control host. and the tldcd robotic control process runs on that host only. and a tldd process runs on each host. To mount a tape.
Tape library Half-inch tlhd (TLH)
tlhcd
Tape library Multimedia (TLM)
tlmd
Robotic process example
Each drive in a tape library DLT (TLD) robot can be attached to a different host. only one host controls the robotics. The tape library half-inch control daemon tlhcd runs on the NetBackup server that has the robotic control. This process receives NetBackup Device Manager requests to mount and unmount volumes and sends these requests to the robotic-control process. It communicates with the TLH robotics through a SCSI interface tlmd runs on the NetBackup server and communicates mount and unmount requests to the host that controls the TLM robotics.

The NetBackup Device Manager services on host A and B start tldd.
. The tldd process on host A also starts tldcd.Robot overview Robotic processes
113
■
The robotic control and therefore the robotic control process. Requests to mount tapes from host B go to tldd on host B. tldcd. is on host A. which then sends the robotic command to tldcd on host A.

116
ADIC Automated Media Library (AML) Sample TLM configuration
■
Scalar Distributed Library Controller (DLC)
TLM robots are API robots (a NetBackup robot category in which the robot manages its own media). See Figure 8-1 on page 117. This chapter provides an overview of those differences. See Table 8-1 on page 117.
Sample TLM configuration
The sample TLM configuration includes the following:
■
A configuration that uses Distributed AML Server software. Support for these devices is different than for other types of robots.
■
. An explanation of the major components in the sample configuration.

A PC that runs an IBM OS/2 or Windows operating system. it allows NetBackup to start sending data to the drive. It also processes return status. tlmd uses the ADIC
■
client software to pass the request to the DAS or Scalar DLC server software that resides in the Archive Management Unit.
■
The DAS or Scalar DLC server locates the media and directs the robotics to mount the media in the drive.
Media requests for a TLM robot
The following is the sequence of events for a media request for a TLM robot:
■
The Media Manager device daemon (UNIX) or NetBackup Device Manager service (Windows) ltid receives the request from bptm.
■
Configuring TLM robotic control
Before you add a robot to NetBackup.
. ensure that the ADIC Automated Media Library has been physically connected and configured. They provide shared access to the Automated Media Libraries (AML). usually located in or near the AML cabinet. When the NetBackup media server receives a successful response from the server. The DAS or Scalar DLC server runs on the AMU. see the ADIC installation and administration guides. tlmd also receives and processes robot inventory requests.118
ADIC Automated Media Library (AML) Media requests for a TLM robot
Table 8-1 Component
ADIC configuration component description (continued) Description
This NetBackup daemon or service uses the ADIC client software to pass mount and dismount requests to the DAS or Scalar DLC server.
TLM daemon or service (tlmd)
Archive Management Unit (AMU)
Distributed AML Server (DAS) Scalar Distributed Library Controller (DLC) Automated Media Library (AML)
An ADIC multimedia robotic library.
ltid sends a mount request to the TLM daemon tlmd. For information about how to configure the ADIC components of the Automated Media Library. These are two ADIC client and server software products that reside in the Archive Management Unit.

Configuring TLM drives on the host
Before you configure the drives in NetBackup. see the Compatibility List for NetBackup Enterprise Server.ADIC Automated Media Library (AML) Configuring TLM drives on the host
119
For information on platform support for TLM robotic control. Allocate the drives on the DAS or Scalar DLC server so they are available to that NetBackup media server. see the ADIC documentation.
. Configure environment variables on that NetBackup media server.com Ensure that your ADIC client software is compatible with your version of NetBackup. see the NetBackup Release Notes.
■ ■
For more information about how to configure the DAS or Scalar DLC server and client. That media server is the DAS or Scalar DLC client. the ADIC library is named libaci.sl.so) in the operating system folder /usr/lib.
2
Set the following system environment variables and values:
DAS_CLIENT DAS_SERVER name_of_NetBackup_media_server name_of_DAS_server
3
Set any other environment variables ADIC requires. The libraries provide the client functionality in the ADIC client and server architecture.
Installing ADIC client software on UNIX
For NetBackup compatibility information for the ADIC client software. Use the following procedure to install the ADIC client software on a UNIX NetBackup media server: To install and configure ADIC software
1
Install the ADIC library (libaci.symantec. you must do the following:
■
Install the appropriate ADIC library files on the NetBackup media server that functions as the device host. You can download the Compatibility List from the following Web site: http://entsupport. On HP-UX systems.

aci. see the Compatibility List for NetBackup Enterprise Server.exe This command installs the NobleNet Portmapper for TCP service. the NetBackup server uses as its DAS or Scalar DLC client name the host name that NetBackup obtains from the gethostname() system call.symantec. Also refer to the ADIC users guide for Windows DAS clients. You can download the Compatibility List from the following Web site: http://entsupport.
. and it must be a valid client name. Use the following procedure to install ADIC software on a Windows NetBackup media server. Set this service to start automatically when the server is started.
Configuring the DAS or Scalar DLC client name
The DAS or Scalar DLC client name is required for the NetBackup media server.dll winrpc32. This name must be the same name for the server that NetBackup uses.120
ADIC Automated Media Library (AML) Configuring TLM drives on the host
Installing ADIC client software on Windows
For NetBackup compatibility information for the ADIC client software. To install and configure ADIC software
1
Set the following system environment variables and values:
DAS_CLIENT DAS_SERVER name_of_NetBackup_media_server name_of_DAS_server
2 3
Set any other environment variables ADIC requires. By default.dll
4
Run portinst.dll ezrpcw32. the client name is stored in the configuration file on the DAS or Scalar DLC server. This name is usually the one that you use for the client name in the configuration file on the DAS or Scalar DLC server. NobleNet Portmapper is provided with the Windows DAS client. Copy the following DLLs to windows\system32 (or install_path\Volmgr\bin).com Ensure that your ADIC client software is compatible with your version of NetBackup.

2
On the NetBackup media server.30C1 does not allow hyphens in client names. To resolve client name problems
1
In the configuration file on the DAS or Scalar DLC server. allocate the drives to the NetBackup media server. see the ADIC documentation.conf file. Add the new client name by using a DAS_CLIENT entry in the /usr/openv/volmgr/vm. Windows. How to do so depends on the operating system type. change the client name. you must use another name.
Allocating TLM drives on a DAS server
After you install the ADIC client software and configure client names. For instructions to change a client name. These entries are of the form: DAS_CLIENT = DASclientname Where DASclientname is the name that you want the NetBackup media server to use as its DAS or Scalar DLC client name. as follows:
■
UNIX.
. To do so. if this name is invalid for DAS or Scalar DLC clients. change the name of the client system that is the NetBackup media server. A similar problem exists if a NetBackup server's short host name is used as the client name but gethostname() returns the long host name.
■
3 4
Stop and start the ltid daemon (UNIX) or service (Windows) to enable the TLM daemon to use the new client name.ADIC Automated Media Library (AML) Configuring TLM drives on the host
121
However. use the DASADMIN administrative command on the DAS server. DAS 1. restart the DAS or Scalar DLC server and then allocate the drives to the NetBackup media server. It must be the same as the client name in the configuration file on the DAS or Scalar DLC server. For example. When the client names are correct. Set the DAS_CLIENT environment variable to the new client name.

For guidance about the NetBackup requirements.
. Enter the client name for the value of Name. the following shows two drives and the clients to which they are allocated.
Configuring TLM drives in NetBackup
A TLM robot can have several different types of drives (UNIX) or half-inch cartridge tape drives (Windows). configure the operating system tape drivers and device files for those drives. and grouse and mouse are the clients (grouse is a NetBackup media server).
. see the information about the host operating system in this guide. For information about how to do so./dasadmin allocd DN2 DOWN mouse . For example. the following two commands deallocate drive DN2 from client mouse and allocate it to client grouse (the NetBackup media server):
./dasadmin allocd DN2 UP grouse
Allocating TLM drives on a Scalar DLC server
Use the following procedure to allocate the drives for the NetBackup media server./dasadmin listd ==>listd for client: successful drive: DN1 amu drive: 01 st: UP type: N sysid: client: grouse volser: cleaning 0 clean_count: 17 drive: DN2 amu drive: 02 st: UP type: N sysid: client: mouse volser: cleaning 0 clean_count: 4
2
Use the dasadmin allocd command to allocate the drive. refer to the operating system documentation. DN1 and DN2 are the drives. usually with a SCSI interface.122
ADIC Automated Media Library (AML) Configuring TLM drives in NetBackup
To allocate a TLM drive
1
Use the dasadmin listd command to list the clients and drives available. For example. To allocate TLM drives
1
Start the Scalar DLC console and choose Configuration > Clients.
2
Select the Drive Reservation tab on the client and choose UP for the drives that you want to allocate to this client. Enter the network host name for the value of Client Host Name. Before you configure drives in NetBackup.

Therefore. amu_name = 01. The following example uses tlmtest:
tlmtest -r dasos2box
The following is the output from this utility (the user entered the drstat command on the third line). type = N. state = UP. state = UP.ADIC Automated Media Library (AML) Configuring TLM drives in NetBackup
123
Use the same methods to create device files or add tape drivers for these drives as for other drives. client = grouse. volser = . cleaning = NO. Volume I.
Current client name is 'grouse'. tape mounts or backups may fail. type = E. Warning: When you add drives to NetBackup. volser = . Symantec recommends that you use the NetBackup Device Configuration Wizard to configure robots and drives in NetBackup. amu_name = 04. cleaning = NO. Volume I or NetBackup Administrator’s Guide for Windows. client = grouse. the drives share the same SCSI ID. type = E. clean_count = 378 DRIVE STATUS complete
. volser = .
Determining drive designations
You may need to add drives to your configuration manually for the following:
■ ■
Older drives The DAS or Scalar DLC servers that do not support serialization
You must determine the drive designations so you know which drives to add to NetBackup. you must specify the logical unit number (LUN) for each drive. see the NetBackup Administrator’s Guide for UNIX and Linux. amu_name = 03. ensure that you assign the correct DAS or Scalar DLC drive name to each drive. If the drives are SCSI and connect to the robot through a control unit. clean_count = 480 Drive 3: name = DE4. client = grouse. state = UP. Use the NetBackup TLM test utility to determine the DAS or Scalar DLC drive designations. To add the drives to NetBackup. cleaning = NO. Enter tlm commands (? returns help information) drstat Drive 1: name = DN1. If the drive name is incorrect. clean_count = 17 Drive 2: name = DE3.

client client_name = NetBackupShared # ip address = 000. To configure the DAS server
1
Modify the DAS server’s \ETC\CONFIG file to create a shared client entry.124
ADIC Automated Media Library (AML) Configuring shared TLM drives
This output shows that you should use DAS or Scalar DLC drive names DN1.100. you must configure the ADIC DAS server to allow simultaneously drive allocation to all NetBackup media servers that share the drives. choose UP for the drives that you want to allocate to the shared client (NetBackupShared from the example in step 1). DE3.000.102 server_2
3
In the DASADMIN interface.
Configuring shared TLM drives
To share TLM drives. For the ADIC software. the following adds two servers:
192.000.000 hostname = any
2
Place the IP addresses of all NetBackup media servers that use the shared client entry in the \MPTN\ETC\HOSTS file on the DAS server. The NetBackup Shared Storage Option allows shared drives. and DE4 should be used.
. For example.
Configuring the ADIC DAS server
DAS server software version 3.100. the NetBackup media servers are considered clients.168. It also shows that you should use grouse as the client name of the NetBackup media server.01. For example. Use one of the following procedures depending on which ADIC robotic control software you use.4 or later is required.100 server_1 192. the following creates a client entry named NetBackupShared.168.

3 or later is required. such as the following: DAS_CLIENT = NetBackupShared Windows. the following adds NetBackupShared as a DAS client:
DAS_CLIENT = NetBackupShared
5
Test the DAS configuration by using the NetBackup robtest and tlmtest utilities:
■
For example. shared client by using the following values:
Name Client Host Name name_of_client (such as NetBackupShared) any
2 3 4
In the Scalar DLC console. For example. set the client name (use client NetBackupshared in tlmtest) and run the drive status command drstat. Choose UP for the drives that you want to allocate to the shared client. On Windows media servers.conf file with the shared client name. create a new. the client name is obtained from the DAS_CLIENT environment variable so the client command is not needed in tlmtest. Set the DAS_CLIENT Windows operating system environment variable to the shared client name. create an entry in the vm.ADIC Automated Media Library (AML) Configuring shared TLM drives
125
4
On each of the NetBackup media servers that share the drives. To configure the Scalar DLC server
1
In the Scalar DLC console.
■
5
Test the Scalar DLC configuration using robtest and tlmtest:
■
For example. such as NetBackupShared. Configure the shared client name on the NetBackup media servers that share the drives.
■
Configuring the ADIC Scalar DLC server
Scalar DLC software version 2. Create an entry in the vm.
. set the client name (use client NetBackupshared in tlmtest) and run the drive status command drstat. select the Drive Reservation tab for the shared client (NetBackupShared). as follows:
■
UNIX.conf file with the shared DAS client name.

see "Correlating device files to physical drives" in the NetBackup Administrator’s Guide. For example.
. Volume I. For this process to work correctly. the following must be true:
■
The wizard discovered the devices and their serial numbers successfully the first time. Allow the drives to be added as stand-alone drives. Make each drive robotic. Also. the wizard also discovers the positions of the drives within the library. With shared drives. you can define the tape drive configuration manually by using the NetBackup Administration Console or NetBackup commands. Take care to avoid any errors. The wizard discovers the tape drives that are available. for 20 drives that 30 hosts share. Scan all hosts that have TLM drives in the library. To configure shared drives in a nonserialized configuration
1
Run the NetBackup Device Configuration wizard on one of the hosts to which drives in an TLM-controlled library are attached. If errors occur. For the robot types that support serialization. Usually. the client name is obtained from the DAS_CLIENT environment variable so the client command is not needed in tlmtest. If the DAS or Scalar DLC server does not support serialization. the NetBackup Shared Storage Option (SSO) for Tape requires shared drives. use the following procedure to configure shared drives. To determine the correct drive addresses and verify the drive paths.126
ADIC Automated Media Library (AML) Configuring shared TLM drives
■
On Windows media servers. A SAN (including switches rather than direct connection) can increase the possibility of errors. ensure that the drives are defined correctly to avoid errors. these configuration steps require that you configure only 20 device paths rather than 600 device paths. This procedure can significantly reduce the amount of manual configuration that is required in an SSO environment. the device paths must be correct for each server. The wizard adds the TLM robot definition and the drives to the other hosts and uses the correct device paths.
2
3
After you verify the drive paths on one host. Add the TLM robot definition and update each drive to indicate its appropriate position in the robot. run the Device Configuration wizard again.
Configuring the drives in NetBackup
Use the NetBackup Device Configuration wizard to configure shared drives in NetBackup.

If any of the reports differ.
■ ■
Define the media in NetBackup by using the DAS or Scalar DLC volser as media IDs. see the NetBackup Administrator’s Guide for UNIX and Linux.
Providing common access to volumes
All NetBackup media servers use the same database. You can obtain the insert area name from the DAS configuration file. and tracks storage cell locations for the media. The AMU Archive Management Software then reads the bar codes. For procedures. Do one of the following to empty the media access port:
■
■
In the NetBackup Administration Console. Issue the DAS insert directive from a DAS administrative interface. NetBackup still moves them to stand-alone. inventory the robot from each NetBackup media server and compare the results. NetBackup operational problems may occur. Add new volumes. Volume I or NetBackup Administrator’s Guide for Windows. perform a shutdown and restart of the DAS or Scalar DLC server.
Adding tapes to a TLM robot
The following is an overview of how to add tapes to a TLM robot and then add those tapes to NetBackup:
■
Add barcode labels to the media and insert the media into the robot by using the media access port (insert area). You can obtain the insert area name from the DAS configuration file. if you update the NetBackup volume configuration from one of the servers. classifies the media by media type. NetBackup moves to stand-alone the volumes that are not configured for that server. Then. Although the volumes are configured correctly for a different server. For example.ADIC Automated Media Library (AML) Providing common access to volumes
127
■
You configured the drive paths correctly on the first host. To define the media. If they do not have access to the same volsers. select the robot inventory update inventory function and select Empty media access port prior to update.
■
Issue the DAS insert directive from the NetBackup tlmtest utility.
■
. Volume I. Therefore. correct the DAS or Scalar DLC configuration. As a test. all media servers that share drives must have access to the same sets of volumes (volsers) in the DAS or Scalar DLC configuration. do one of the following:
■
Update the volume configuration by using the robot inventory function.

Because the DAS or Scalar DLC volser and bar codes are the same. Note that you do not enter slot locations. update the volume location to stand alone in NetBackup. use Show Contents and Compare Contents with Volume Configuration from the Robot Inventory dialog box in NetBackup.
■
■ ■
2
If you use a DAS or Scalar DLC administrative interface or the NetBackup tlhtest utility. To do so.
■
. Volume I or NetBackup Administrator’s Guide for Windows. Volume I. see the NetBackup Administrator’s Guide for UNIX and Linux. For procedures. Volume I. For procedures. see the NetBackup Commands guide. use these options to update the NetBackup volume configuration when media has moved. see the NetBackup Administrator’s Guide for UNIX and Linux. A DAS or Scalar DLC administrative interface. The configuration update maintains consistency between the DAS or Scalar DLC database and the NetBackup EMM database. Move the volumes. Volume I.
Removing tapes from a TLM robot
You can remove tapes by using a DAS or Scalar DLC administrative interface or by using NetBackup. For usage. The eject command in the NetBackup tlmtest utility. the ADIC software manages them.
■
To verify your configuration. The NetBackup vmchange command. do one of the following:
■
Update the volume configuration by using the robot inventory function. see the NetBackup Administrator’s Guide for UNIX and Linux. To remove media
1
Physically remove the media from the library by using one of the following:
■
Actions > Eject Volumes From Robot in the NetBackup Administration Console.128
ADIC Automated Media Library (AML) Removing tapes from a TLM robot
For procedures. NetBackup has a record of the bar codes for the media. Volume I or NetBackup Administrator’s Guide for Windows. Also. Volume I or NetBackup Administrator’s Guide for Windows.

NetBackup then displays a list of the volumes and their media types according to the DAS or Scalar DLC server. If the operation does not require updating the volume configuration. NetBackup uses the media type defaults for TLM robots when it creates an inventory report. In the previous table. NetBackup filters out the volumes that are not occupied in their home cell locations or in drives. The following occurs when you inventory a TLM robot in NetBackup:
■
NetBackup requests volume information from the DAS server or SDLC server through a DAS or Scalar DLC application library call. The server responds by providing a list of volume IDs and associated information from its database. The result is an error such as Misplaced Tape. volser A00250 becomes media ID A00250. Volume I. Volume I or the NetBackup Administrator’s Guide for Windows. See the NetBackup Administrator’s Guide for UNIX and Linux. NetBackup maps the TLM media types to the default NetBackup media types Information about the default media type mappings and how to change them is available.
■
■
. The following are examples of the type of information received.ADIC Automated Media Library (AML) Robot inventory operations on TLM robots
129
If you do not update the EMM database. NetBackup does not know the new location of the media and may issue mount requests for it. TLM volume ID
A00250 J03123 DLT001 MM1200 NN0402 002455
■
TLM media type
3480 3590 DECDLT 8MM 4MM UNKNOWN
■
NetBackup translates the volsers directly into media IDs and barcodes. If the operation requires a volume configuration update.
Robot inventory operations on TLM robots
In NetBackup. and the barcode for that media ID is also A00250. a TLM robot type supports barcodes.

as follows:
■
The robotic control host communicates directly to robot See Figure 9-1 on page 133.132
IBM Automated Tape Library (AML) Sample TLH configurations
Sample TLH configurations
The following sections show example ATL configurations and explain their major components. Robotic control and robot connection on separate hosts. See Figure 9-2 on page 134. See Table 9-1 on page 135.
■
■
An explanation of the major components in those configurations.
.
UNIX system example configurations
The UNIX TLH examples include the following:
■
Two possible ATL configurations.

■
■
An explanation of the major components in those configurations. The NetBackup Media Manager device daemon. It passes mount and dismount requests to the tape library half-inch control daemon (tlhcd) on the robotic control host. The Library Manager is a PC that usually is located within the robot cabinet. Communication occurs by using the IBM Library Device Driver interface (on AIX) or IBM Tape Library system calls (other UNIX systems). This daemon receives mount or dismount requests from tlhd or robot inventory requests through an external socket interface. See Figure 9-4 on page 137. See Table 9-2 on page 138. Robotic control and robot connection on separate hosts. Tape Library Half-inch daemon (tlhd) This daemon resides on a NetBackup media serve. as follows:
■
Robotic control on host with ATL drives. ltid.
. See Figure 9-3 on page 136. tlhcd must reside on the same system that communicates with lmcpd.IBM Automated Tape Library (AML) Sample TLH configurations
135
Table 9-1 Component
UNIX TLH configuration component description Description
NetBackup media server A host that has NetBackup media server software and is a client to the ATL through the Library Manager Control Point daemon (lmcpd). This software handles all Point daemon (lmcpd) communications with the Library Manager and must run on any system from which the Automatic Tape Library is directly controlled. An IBM physical library under automated robotic control. forwards mount and dismount requests to the Tape Library Half-inch daemon (tlhd). Library manager A component of IBM ATL support that provides control of the robotics and the robotic library.
IBM Automated Tape Library (ATL)
Windows system example configurations
The Windows TLH examples include the following:
■
Two possible ATL configurations.
TapE Library Half-inch control daemon (tlhcd)
Library Manager Control A component of IBM ATL support.

138
IBM Automated Tape Library (AML) Media requests for a TLH robot
Table 9-2 Component
Windows TLH configuration component description Description
NetBackup media server A host that has NetBackup media server software and is a client to the Automated Tape Library through the IBM ATL service. The NetBackup Device Manager service (ltid) forwards mount and dismount requests to the Tape Library Half-inch service (tlhd). The control daemon communicates with the Library Manager Control Point daemon lmcpd by using the Library Device Driver interface.
Tape Library Half-inch control process (tlhcd)
IBM Automated Tape Library service
Library Manager
IBM Automated Tape Library (ATL)
Media requests for a TLH robot
The following is the sequence of events for a media request for a TLH robot:
■
The Media Manager device daemon (UNIX) or NetBackup Device Manager service (Windows) ltid receives the request from the NetBackup bptm process. A component of IBM ATL support. tlhd passes the request to the NetBackup TLH control daemon tlhcd. ltid sends a mount request to the NetBackup TLH daemon tlhd. This host can be the same host on which tlhd is running or another host. tlhcd resides on the host to which the Automatic Tape Library is connected. tlhcd communicates with the robotic library as follows:
■
■ ■
■
AIX. It passes mount and dismount requests to the Tape Library Half-inch control process (tlhcd) on the robotic control host. A component of IBM ATL support that provides control of the robotics and the robotic library.
. This process receives mount or dismount requests from tlhd or robot inventory requests through an external socket interface. This software handles all communications with the Library Manager and must be running on any system from which the Automatic Tape Library is directly controlled. The Library Manager is a PC that is usually located within the robot cabinet. An IBM physical library under automated robotic control. tlhcd must reside on the same system that communicates with the IBM ATL service. Tape Library Half-inch process (tlhd) This process resides on a NetBackup media server.

For information about how to configure the IBM components of the Automated Tape Library.com You use a recommended version of the Automated Tape Library. To locate the recommended levels. The control process communicates with the IBM ATL service through Tape Library system calls from an application library interface. The following example uses the lsdev command:
/etc/lsdev -C | grep "Library Management"
. see the Symantec support Web site. ensure the following:
■
The IBM Automated Tape Library is physically connected and configured correctly. When the NetBackup media server receives a successful response from the Library Manager. Windows.Symantec.IBM Automated Tape Library (AML) Configuring robotic control
139
■
UNIX. The control daemon communicates with the Library Manager Control Point daemon lmcpd through Tape Library system calls from an application library interface. Medium Changer.
■
Robotic control on an AIX system
The following subsections explain how to configure robotic control when the NetBackup media server is installed on an AIX system.
■
Configuring robotic control
When you add a TLH robot to NetBackup. The Library Manager then locates the media and directs the TLH robotics to mount the media in the drive.
Determine the path to the LMCP device file
Use the Library Manager Control Point (LMCP) device file as the robotic device file in NetBackup. and Library Device Drivers Installation and User's Guide (or any related publications). This file is set up when the Automated Tape Library is first configured. it allows NetBackup to start sending data to the drive. Use the lsdev command (or smit) to determine the LMCP device file. see the NetBackup release notes and the Symantec support Web site: http://entsupport.
■
■
lmcpd (UNIX) or the IBM ATL service (Windows) passes the information to the Library Manager. The documentation includes SCSI Tape Drive. see the IBM documentation. For information on platform support for TLH robotic control.

.. the following command verifies communication with the library:
/usr/bin/mtlib -l /dev/lmcp0 -qL
The following is the output from this command:
Library Data: state....... Primary hard drive available....
................01 accessor status.........Accessor available Gripper 1 available Gripper 2 available Vision system operational comp avail status.......ALL input stations empty ALL output stations empty machine type....3494 sequence number.........11398 number of cells.. Convenience input station available...........140
IBM Automated Tape Library (AML) Configuring robotic control
The following is the output from this command:
lmcp0 Available LAN/TTY Library Management Control Point
Verify library communications on an AIX computer
After you determine the path to the LMCP device file.30 accessor config..... specify the Library Manager Control Point device file with the mtlib command. verify library communications through the IBM-provided mtlib interface............... Automated Operational State Dual Write Disabled input stations...Primary library manager installed.......... Convenience output station installed. if the LMCP device path is /dev/lmcp0...1 output stations......129 subsystems.. Primary hard drive installed............. To verify communications with a specific library..............1 input/output status.....2 convenience capacity......141 available cells.... Primary library manager available. Convenience input station installed.. For example......... Convenience output station available.... Resolve all errors before attempting to configure IBM 3494 support in Media Manager...

92
Configure the robotic device file on AIX
Configure the robotic path.1 DOWN 31 Drive1 hcart TLH(8) 003590B1A00 /dev/rmt12.IBM Automated Tape Library (AML) Configuring robotic control
141
avail 3490 cleaner cycles.0 avail 3590 cleaner cycles. note the following lines:
TLH(8) LMCP device path = /dev/lmcp0 EMM Server = maui
Where /dev/lmcp0 is the path to the robotic device file and maui is the EMM server for this robot.
# /usr/openv/volmgr/bin/tpconfig -d Id DriveName Type Residence Drive Path Status ******************************************************************* 5 Drive0 hcart TLH(8) 003590B1A00 /dev/rmt4. The drive with drive index 31 is under TLH robotic control and the drive with drive index 78 is under TL4 control. The following example uses tpconfig -d to view the robotic device information. For procedures..
Robotic control on a UNIX system
The following subsections explain the steps for configuring robotic control when the NetBackup media server is a UNIX system other than AIX. Volume I. the first two drives are stand-alone drives.1 UP Currently defined robotics are: TL4(77) robotic path = /dev/ovpass0 TLH(8) LMCP device path = /dev/lmcp0 EMM Server = maui
In this example.1 DOWN 78 Drive1 4mm TL4(77) DRIVE=1 /dev/rmt11. Volume I or NetBackup Administrator’s Guide for Windows. you can view the robotic device information.. When the configuration is complete. In this example. see the NetBackup Administrator’s Guide for UNIX and Linux.
.1 DOWN 13 Drive2 hcart TLH(8) 003590B1A00 /dev/rmt8.

2
....3494 sequence number.154..... This name is set up when the Automated Tape Library is first configured (see your IBM system documentation).. The library name is configured in the /etc/ibmatl...... The following is an example entry in that file:
3494AH 176...... verify library communications through the IBM-provided mtlib interface......11398 number of cells...141 available cells........1 input/output status.......... Resolve all errors before attempting to configure IBM 3494 (TLH) support in NetBackup....ALL input stations empty ALL output stations empty machine type..... 176... specify the library name with the mtlib command...141 is the IP address of the PC workstation that is running the Library Manager software...... ibmpc1 is the host name of the PC workstation that is running the Library Manager software........
■
Verify library communications on a UNIX computer
After you determine the library name.. For example...1 output stations......142
IBM Automated Tape Library (AML) Configuring robotic control
Determine the ATL library name on UNIX
Use the library name instead of the robotic device file when you configure the storage device in NetBackup...........123..141 ibmpc1
The following describes the example entry:
■ ■
3494AH is the library name. if the library name is 3494AH..conf file....Automated Operational State Dual Write Disabled input stations... determine the library name by viewing the contents of the file.........129 subsystems..154....123... the following command verifies communications with the library:
/usr/bin/mtlib -l 3494AH -qL
The following is the output from this command:
Library Data: state............ To verify communications with a specific library.

......144
IBM Automated Tape Library (AML) Configuring robotic control
Where 3494AH is the library name and glozer is the EMM server for this robot. specify the library name with the mtlib command...1
. The library name is configured in the C:\winnt\ibmatl..141 ibmpc1
The following describes the example entry:
■ ■
3494AH is the library name... For example....141 is the IP address of the PC workstation that is running the Library Manager software.... Resolve all errors before attempting to configure IBM 3494 (TLH) support in NetBackup..123.conf file. verify library communications through the IBM-provided mtlib interface. ibmpc1 is the host name of the PC workstation that is running the Library Manager software..
Determine the ATL name on Windows
Use the library name when you configure the robot in NetBackup..... To verify communications with a specific library...1 output stations. This name is set up when the Automated Tape Library is first configured (see the IBM system documentation).....
Robotic control on a Windows system
The following subsections explain how to configure robotic control when the NetBackup media server is on a Windows system. 176..000 input stations..Automated Operational State Dual Write Disabled functional state.123......154.... The following is an example entry in that file:
3494AH 176.. the following command verifies communications with the library:
mtlib -l 3494AH -qL
The following is the output from this command:
Library Data: operational state. determine the library name by viewing the contents of the file. if the library name is 3494AH.154...
■
Verify library communications on a Windows computer
After you determine the library name.

The following example uses tlhtest and shows the drives in the robot that NetBackup controls:
■ ■
UNIX: /usr/openv/volmgr/bin/tlhtest -r /dev/lmcp0 Windows: tlhtest -r 3494AH
If the robotic control is configured on a UNIX server other than AIX. For information about how to do so. Warning: When you add drives to NetBackup. see the information about the host operating system in this guide.1. and glozer is the EMM server for this robot.1. ensure that you assign the correct IBM device number to each drive.
Configuring TLH drives
TLH robots have half-inch cartridge tape drives.0> Currently defined robotics are: TLH(0) library name = 3494AH TLD(5) SCSI port=3.0> DRIVE1 dlt TLD(5) DRIVE=1 <3. use the library name as configured in /etc/ibmatl. Use the NetBackup TLH test utility (tlhtest) to determine the TLH drive designations. If the IBM device number is incorrect.
. create or identify device files for these drives. tape mounts or backups may fail. refer to the operating system documentation. Use the same methods to create or identify device files for these drives as for other drives. as follow:
■
On UNIX systems. How you configure the drives depends on the operating system. On Windows systems. bus=1. lun=0 EMM Server = glozer 1
UP
In this example.146
IBM Automated Tape Library (AML) Configuring TLH drives
<1.1. configure the operating system tape drivers and device files for those drives. you must install a system tape driver according to the appropriate system and vendor documentation. Do not use the LMCP device path on the call to tlhtest.conf. For guidance about the NetBackup requirements.0. note the following lines:
TLH(0) library name = 3494AH EMM Server = glozer
3494AH is the library name.
■
Before you configure drives in NetBackup. target=6.

QUERY DEVICE DATA complete
Cleaning drives
The IBM ATL interface does not allow applications to request or configure drive cleaning. You must configure drive cleaning by using an IBM administrative interface.3590 device category: 0x0000 mounted volser: <none> mounted category: 0x0000 device states: Device installed in ATL. Drive information: device name: 003590B1A01 device number: 0x156600 device class: 0x10 .3590 device category: 0x0000 mounted volser: <none> mounted category: 0x0000 device states: Device installed in ATL.
Opening /dev/lmcp0 (UNIX) Opening 3494AH (Windows) Enter tlh commands (? returns help information) drstat Drive information: device name: 003590B1A00 device number: 0x156700 device class: 0x10 . ACL is installed. You would use 156700 and 156600 when you add these drives to NetBackup. ACL is installed. Dev is available to ATL. Dev is available to ATL.
.
Adding tapes to TLH robots
The following table is an overview of how to add tapes to a TLH robot and then add those tapes to NetBackup. you cannot assign cleaning tapes to a TLH robot in the NetBackup. Therefore.IBM Automated Tape Library (AML) Cleaning drives
147
The following is the output from tlhtest (the user entered the drstat command on the third line).

See the NetBackup Administrator’s Guide for UNIX and Linux. Volume I or NetBackup Administrator’s Guide for Windows Volume I. The Automated Tape Library finds the media when NetBackup requests it.
Define the media in To define the media. Volume I or NetBackup Administrator’s Guide for Windows Volume I. The eject command in the NetBackup tlhtest utility. Some volume categories restrict application access to certain volumes. Verify the volume configuration Use Show Contents and Compare Contents with Volume Configuration from the Robot Inventory dialog. A category is assigned to each volume.
■
■
.
Add barcode labels to the media and insert the media into the robot by using the media access port.148
IBM Automated Tape Library (AML) Removing tapes from TLH robots
Table 9-3 Task
Adding tapes process Description
The Library Manager reads the bar codes and classifies the media by media type. You can move media from one location to another within the robot. NetBackup has a record of the barcodes for the media. see the NetBackup Commands guide. See the NetBackup Administrator’s Guide for UNIX and Linux. The NetBackup vmchange command. do one of the following: NetBackup by using the ATL ■ Add new volumes by using the Configure Volumes volume IDs as media IDs Wizard. Note that you do not enter slot locations because the ACS library software manages them. Because the ATL volume IDs and barcodes are the same. The Library Manager tracks volume locations.
Removing tapes from TLH robots
Use the following procedure to remove tapes. To remove volumes
1
Physically remove the media from the library by using one of the following:
■
Actions > Eject Volumes From Robot in the NetBackup Administration Console. ■ Update the volume configuration by using the NetBackup robot inventory function. For usage.

Volume I or NetBackup Administrator’s Guide for Windows Volume I. For procedures.
Robot inventory operations on TLH robots
In NetBackup. The media type is based on the attributes that were returned. see the NetBackup Administrator’s Guide for UNIX and Linux. NetBackup filters out the volume categories that cannot be used. To do so. The Library Manager responds by providing a list of volume IDs and volume attributes from its database.
■
If you do not update the volume location. The following table shows an example of the types of information that NetBackup receives: TLH volume ID
PFE011 303123 CB5062 DP2000
■
TLH media type
3480 3490E 3590J 3590K
. see the NetBackup Administrator’s Guide for UNIX and Linux. NetBackup displays a list of the volumes and a translated version of the volume’s media type.IBM Automated Tape Library (AML) Robot inventory operations on TLH robots
149
■
An IBM Library Manager interface. The result is an error such as Misplaced Tape. update the volume location to stand alone in NetBackup. The following sequence of events occurs when you inventory a TLH robot in NetBackup:
■
NetBackup requests volume information from the Library Manager through the Library Manager Control Point daemon. do one of the following:
■
Update the volume configuration by using the robot inventory function. Volume I or NetBackup Administrator’s Guide for Windows Volume I. NetBackup does not know the new location of the media and may issue mount requests for it.
2
If you use the IBM Library Manager interface or the NetBackup tlhtest utility. Move the volumes. For procedures. the TLH robot type supports barcodes.

add an INVENTORY_FILTER entry in the vm. value2 is a second filter value (up to 10 filter values are allowed). The following is the usage statement:
INVENTORY_FILTER = TLH robot_number BY_CATEGORY value1 [value2 . If the operation requires a volume configuration update. NetBackup uses the media type defaults for TLH robots when it creates the inventory report.. volume ID PFE011 becomes media ID PFE011. including pools by application.
The following is an example:
INVENTORY_FILTER = TLH 0 BY_CATEGORY 0xcdb0
. value1 is a filter value of type IBM category (if filter_type = BY_CATEGORY).. and the barcode for that media ID is also PFE011. On the NetBackup media server from which you invoke the inventory operation. In the previous table. NetBackup maps the TLH media types to the default NetBackup media types Information about the default media type mappings and how to change them is available. Volume I or NetBackup Administrator’s Guide for Windows Volume I.conf file.150
IBM Automated Tape Library (AML) Robot inventory operations on TLH robots
■
NetBackup translates the volume IDs into media IDs and barcodes. The IBM Library Manager maintains the concept of a volume category. you can filter the volume information from the library.. which can be used to classify volumes into pools.]
The following describes the filter:
■ ■ ■
robot_number is the number of the robot in NetBackup. If the operation does not require updating the volume configuration. See the NetBackup Administrator’s Guide for UNIX and Linux.
■
■
Robot inventory filtering on TLH robots
If you want NetBackup to use only a subset of the volumes under library control.

Note: The access control feature of Sun StorageTek ACSLS controlled robots is not compatible with media sharing. Media sharing restricts volume access by the requesting hosts IP address. Use caution when you implement media sharing in an ACSLS environment. Sun StorageTek Automated Cartridge System Library Software controlled robots are NetBackup robot type ACS. ACS robots are API robots (a NetBackup robot category in which the robot manages its own media). Unlike other robot types, NetBackup does not track slot locations for the media in ACS robots. The Automated Cartridge System Library Software tracks slot locations and reports them to NetBackup. The term automated cartridge system (ACS) can refer to any of the following:
■ ■ ■

A type of NetBackup robotic control. The Sun StorageTek system for robotic control. The highest-level component of the Sun StorageTek ACSLS. It refers to one robotic library or to multiple libraries that are connected with a media pass-through mechanism.

The ACS library software component can be either of the following Sun StorageTek products:
■ ■

A typical UNIX ACSLS configuration. See Figure 10-1 on page 153. A typical Windows ACSLS configuration. See Figure 10-2 on page 154. The major components in typical configurations. See Table 10-1 on page 155.

■

■

Sun StorageTek ACSLS robots Sample ACSLS configurations

153

Figure 10-1

Typical ACSLS configuration on UNIX
ACSLS Administrative Utility

NetBackup media server

ascd

IPC acsssi acsssi

Robotic requests using RPC ACS Library Software

Device Drivers SCSI SCSI

Database

Library Management Unit (LMU)

Robotics

Data

Drive

Driv e

C AP

Control Unit (CU)

Drive

Library Storage Module (LSM)

154

Sun StorageTek ACSLS robots Sample ACSLS configurations

Figure 10-2

Typical ACSLS configuration on Windows
ACSLS Administrative Utility

NetBackup media server

acsd

IPC

Sun StorageTek LibAttach Service

Robotic requests using RPC

ACS Library Software

Device Drivers SCSI SCSI

Database

Library Management Unit (LMU)

Robotics

Data

Drive

Table 10-1 describes the components of the ACSLS configuration.

Driv e

C AP

Control Unit (CU)

Drive

Library Storage Module (LSM)

Sun StorageTek ACSLS robots Sample ACSLS configurations

155

Table 10-1 Component
NetBackup media server

ACSLS configuration component description

Description
A host that has NetBackup media server software and is a client to the ACS library software host. The NetBackup ACS robotic daemon (acsd) formulates requests for mounts, unmounts, and inventories. An API then uses IPC communication to routes these requests to: (UNIX) The NetBackup ACS storage server interface (acsssi). The requests are converted into RPC-based communications and sent to the ACS library software. ■ (Windows) the Sun StorageTek LibAttach service. This service sends the requests to the ACS library software.
■

Sun StorageTek LibAttach Library Attach for Windows is an ACS library software client application that enables Service Windows servers to use the StorageTek Nearline enterprise storage libraries. Windows computers only LibAttach provides the connection between Windows and ACS library software through a TCP/IP network. Obtain the appropriate LibAttach software from Sun. See the Symantec support Web site for the latest compatibility information. The following ACS library Receives the robotic requests from NetBackup and uses the Library Management Unit software: to find and mount or unmount the correct cartridge on media management requests. Automated Cartridge On compatible host platforms, you may be able to configure ACS library software and System Library NetBackup media server software on the same host. Software (ACSLS) ■ Sun StorageTek Library Station
■

Library Management Unit Provides the interface between the ACS library software and the robot. A single LMU (LMU) can control multiple ACSLS robots. Library Storage Module (LSM) Control Unit (CU) Contains the robot, drives, or media.

The NetBackup media server connects to the drives through device drivers and a control unit (tape controller). The control unit may have an interface to multiple drives. Some control units also allow multiple hosts to share these drives. Most drives do not require a separate control unit. In these cases, the media server connects directly to the drives.

CAP

Cartridge Access Port.

156

Sun StorageTek ACSLS robots Media requests for an ACS robot

Media requests for an ACS robot
The following is the sequence of events for a media request for an ACS robot:
■

An API then uses Internal Process Communications (IPC) to send the request on the following systems:
■

UNIX. The NetBackup ACS storage server interface acsssi. The request is then converted into RPC-based communications and sent to the ACS library software. Windows. The Sun StorageTek LibAttach service. This service sends the request to the ACS library software.

■

■

If the Library Storage Module (LSM) in which the media resides is offline, the ACS library software reports this offline status to NetBackup. NetBackup assigns the request a pending status. NetBackup retries the request hourly until the LSM is online and the ACS library software can satisfy the media request. The ACS library software locates the media and sends the necessary information to the Library Management Unit (LMU). The LMU directs the robotics to mount the media in the drive. When the LibAttach service (Windows) or acsssi (UNIX) receives a successful response from the ACS library software, it returns the status to acsd. The acsd child process (that is associated with the mount request) scans the drive. When the drive is ready, acsd sends a message to ltid that completes the mount request. NetBackup then begins to send data to or read data from the drive.

■

■

■

Configuring ACS drives
An ACS robot supports DLT or 1/2-inch cartridge tape drives. If an ACS robot contains more than one type of DLT or 1/2-inch cartridge tape drive, you can configure an alternate drive type. Therefore, there can be up to three different DLT and three different 1/2-inch cartridge drive types in the same robot. If you use alternate drive types, configure the volumes by using the same alternate media type. Six drive types are possible: DLT, DLT2, DLT3, HCART, HCART2, and HCART3.

Sun StorageTek ACSLS robots Configuring ACS drives

157

Before you configure drives in NetBackup, configure the operating system tape drivers and device files for those drives. For information about how to do so, refer to the operating system documentation. For guidance about the NetBackup requirements, see the information about the host operating system in this guide Use the same methods to create or identify device files for these drives as for other drives. If the drives are SCSI and connect to the robot through a shared control unit, the drives share the same SCSI ID. Therefore, you must specify the same logical unit number (LUN) for each drive. When you configure ACS drives as robotic in NetBackup, you must include the ACS drive coordinate information. Table 10-2 shows the ACS drive coordinates. Table 10-2 ACS drive coordinates Description
The index, in ACS library software terms, that identifies the robot that has this drive. The Library Storage Module that has this drive. The panel where the drive is located. The physical number of the drive in ACS library software terms.

ACS drive coordinate
ACS number

LSM number Panel number Drive number

Figure 10-3 shows the location of this information in a typical ACS robot.

158

Sun StorageTek ACSLS robots Configuring shared ACS drives

Figure 10-3

ACSLS robot and drive configuration information

ACS Library Software Host

ACS Library Software

ACS number (0-126) Library Management Unit (LMU) LSM number (0-23)

Robotics
D ri ve

SCSI ID

Control Unit (CU)

Drive Drive

SC

Panel number (0-19)

SI

ID

Library Storage Module (LSM)

SCSI ID Drive

Drive number (0-19)

Configuring shared ACS drives
If the ACSLS server does not support serialization, use the following procedure to configure shared drives. Shared drives require the NetBackup Shared Storage Option license. (Sun StorageTek ACSLS versions before 6.1 do not support serialization.) If the server supports serialization, use the NetBackup Device Configuration Wizard to configure shared drives. This procedure can significantly reduce the amount of manual configuration that is required in an SSO environment. For example, for 20 drives that 30 hosts share,

Sun StorageTek ACSLS robots Configuring shared ACS drives

159

these configuration steps require that you configure only 20 device paths rather than 600 device paths. During the setup phase, the NetBackup Device Configuration Wizard tries to discover the tape drives available. The wizard also tries to discover the positions of the drives within the library (if the robot supports serialization). A SAN (including switches rather than direct connection) can increase the possibility of errors. If errors occur, you can define the tape drive configuration manually by using the NetBackup Administration Console or NetBackup commands. Take care to avoid any errors. With shared drives, the device paths must be correct for each server. Also, ensure that the drives are defined correctly to avoid errors. (A common error is to define a drive as ACS index number 9 rather than ACS index 0.) To configure shared drives in a nonserialized configuration

1

Run the NetBackup Device Configuration Wizard on one of the hosts to which drives in an ACS-controlled library are attached. Allow the drives to be added as stand-alone drives. Add the ACS robot definition and update each drive to indicate its position in the robot. Make each drive robotic and add the ACS, LSM, Panel, and Drive information. Information about how to determine the correct drive addresses and how to verify the drive paths is available. See "Correlating device files to physical drives" in the NetBackup Administrator’s Guide for UNIX and Linux, Volume I or NetBackup Administrator’s Guide for Windows, Volume I.

2

3

After you verify the drive paths on one host, run the Device Configuration Wizard again. Scan all hosts that have ACS drives in the library. The wizard adds the ACS robot definition and the drives to the other hosts and uses the correct device paths. For this process to work correctly, the following must be true:
■

The wizard discovered the devices and their serial numbers successfully the first time. You configured the drive paths correctly on the first host.

■

Verify the volume configuration Use Show Contents and Compare Contents with Volume Configuration from the Robot Inventory dialog. Because the ACS volume IDs and bar codes are the same. For procedures. see the NetBackup Administrator’s Guide for UNIX and Linux. do not use any of the following characters when you configure ACS volumes:
■ ■ ■ ■
Dollar sign ($) Pound sign (#) The yen symbol Leading and trailing spaces
The following tables is an overview of how to add tapes to an ACS robot and then add those tapes to NetBackup. Note that you do not enter slot locations because the ACS library software manages slot locations. Therefore.
Define the media in To define the media. inventory function. A category is assigned to each volume. Table 10-3 Task
Add barcode labels to the media and insert the media into the robot by using the media access port. The Library Manager tracks volume locations. NetBackup has a record of the bar codes for the media. ■ Add new volumes by using the Volume Configuration Wizard. Volume I. see the NetBackup Administrator’s Guide for UNIX and Linux. For procedures.
Adding tapes process Description
The Library Manager reads the bar codes and classifies the media by media type. Volume I or NetBackup Administrator’s Guide for Windows. Some volume categories restrict application access to certain volumes. Volume I or NetBackup Administrator’s Guide for Windows. do one of the following: NetBackup by using the ACS ■ Update the volume configuration by using the robot volume IDs as media IDs. Volume I.
. (Volume ID is the ACS term for media ID).160
Sun StorageTek ACSLS robots Adding tapes to ACS robots
Adding tapes to ACS robots
ACS robotic control software supports the following characters in a volume ID that are not valid NetBackup media ID characters.

do one of the following:
■
Update the volume configuration by using the NetBackup robot inventory function. Volume I or NetBackup Administrator’s Guide for Windows Volume I.
.
Removing tapes using NetBackup
You can remove tapes by using one of the following methods:
■
Actions > Eject Volumes From Robot in the NetBackup Administration Console.
■
Both of these methods performs the logical move and the physical move. you can move media from one location to another within the robot. Use the NetBackup vmchange command.
■
If you do not move media logically. which causes a misplaced tape error.conf file. do one of the following:
■
Add new volumes by using the Configure Volumes Wizard.Sun StorageTek ACSLS robots Removing tapes from ACS robots
161
Removing tapes from ACS robots
You can remove tapes by using the Sun StorageTek utility or by using NetBackup. The ACS library software finds the requested media if its database is current. To do so. Volume I or NetBackup Administrator’s Guide for Windows Volume I. Old versions of Library Station do not support queries of all volumes in an ACS robot. See the NetBackup Administrator’s Guide for UNIX and Linux. Move the volumes. you must move the media logically to stand alone in NetBackup. See the NetBackup Administrator’s Guide for UNIX and Linux. See the NetBackup Commands guide.
Robot inventory operations on ACS robots
If the ACS library software host is a Sun StorageTek Library Station. an Inventory Robot Filter (INVENTORY_FILTER) entry may be required in the vm. To define the media. NetBackup may issue mount requests for it. However. NetBackup does not know that the media were moved.
Removing tapes using the ACSLS utility
If you remove media from an ACS robot.

Sun StorageTek ACSLS robots Robot inventory operations on ACS robots
163
Table 10-4 ACS volume ID
900100 900200
ACS drive coordinates (continued) ACS media type
EECART UNKNOWN
ACS
0 0
LSM
0 0
Robot inventory filtering on ACSs robots
If you want NetBackup to use only a subset of the volumes under ACS library control. A partial inventory also includes those volumes that NetBackup can validate exist in the robotic library.conf file. the library reports the complete list of volumes that exist in the robotic library. A NetBackup robot inventory includes the volumes that exist in the ACS scratch pool. Assign ID 4 and 0 to 500 as the range for the number of volumes. To do so.. as follows:
ACSSA> define pool 0 500 4
2
Use the ACSLS administrative interface (ACSSA) command to define the volumes in scratch pool 4:
ACSSA> set scratch 4 600000-999999
3
On the NetBackup media server from which you invoke the inventory operation. To prevent losing track of previously mounted volumes.]
The following define the options and arguments:
. The following is the usage statement:
INVENTORY_FILTER = ACS robot_number BY_ACS_POOL acs_scratch_pool1 [acs_scratch_pool2 . Then you configure NetBackup to use only the volumes in those scratch pools. The following is an example of how to configure an inventory filter. The ACS library software moves each volume from the scratch pool after it is mounted. you use the ACSLS administrative interface to assign the volumes you want to use to a scratch pool or pools.. To configure an inventory filter (example)
1
Use the ACSLS administrative interface (ACSSA) command to create a scratch pool. you can filter the volume information from the library. add an INVENTORY_FILTER entry to the vm. including volumes not in the ACS scratch pool.

How NetBackup uses robotic control.164
Sun StorageTek ACSLS robots Robotic control. This request process accommodates the configurations that have SCSI multiplexors. and logging
■ ■
robot_number is the number of the robot in NetBackup. It also requests inventories of the volumes that are under the control of ACS library software.
INVENTORY_FILTER = ACS 0 BY_ACS_POOL 4 5
Robotic control.
Windows systems
The NetBackup acsd process provides robotic control to mount and dismount volumes. acs_scratch_pool2 is a second scratch pool ID (up to 10 scratch pools are allowed). The NetBackup Device Manager service ltid starts the acsd process and communicates with it.
NetBackup ACS daemon (acsd)
The NetBackup ACS daemon acsd provides robotic control to mount and dismount volumes. communication. the following entry forces ACS robot number 0 to query scratch volumes from Sun StorageTek pool IDs 4 and 5. several NetBackup daemons and processes provide robotic control. See “UNIX systems” on page 164. and logging during tape operations depends on the operating system type. the Media Manager device daemon ltid starts the acsd
. and logging. See “Windows systems” on page 164. communication. communication.
UNIX systems
On UNIX systems.
■
For example. It also requests inventories of the volumes that are under the control of ACS library software. acs_scratch_pool1 is the scratch pool ID as configured in the ACS library software. and logging
NetBackup Enterprise Server only. Loaded tapes are not ejected forcibly when a dismount operation occurs. communication. The acsd process requests SCSI tape unloads through the device host’s tape driver before it uses the ACS API to request that tape dismounts.

exe program stops the acssel process. it first starts the NetBackup acssel process and then starts the acsssi process. NetBackup cannot process requests immediately. On Windows systems. its functional model differs from other NetBackup robotic controls. On UNIX systems. The acsd daemon requests SCSI tape unloads through the device host’s tape driver before it uses the ACS API to request that tape dismounts. and logging
165
daemon and communicates with it. If acsssi cannot connect to acssel. communication. The full path to the event logger is /usr/openv/volmgr/bin/acssel. When acsd starts.Sun StorageTek ACSLS robots Robotic control. If multiple media servers share drives in an ACS robot. Therefore.
NetBackup ACS SSI event logger (acssel)
The NetBackup ACS storage server interface (SSI) event logger acssel is modeled after the Sun StorageTek mini_el event logger. The usage format is as follows:
acssel [-d] -s socket_name
The following describes the options:
■ ■
-d displays debug messages (by default. acsssi must be active on each media server. Loaded tapes are not ejected forcibly when a dismount operation occurs. only the kill command stops acssel. acsd passes the ACS library software host name to acsssi.kill_all utility (UNIX ) stops the acssel process. When it starts acsssi. You also can start it manually. you can start acsd manually. socket_name is the socket name (or IP port) to listen on for messages. If ltid is active already. Event messages are logged to the following file:
/usr/openv/volmgr/debug/acsssi/event. retry and error recovery situations can occur. This control process accommodates the configurations that have SCSI multiplexors. Therefore.
. debug messages are disabled). the bpdown. The NetBackup bp. The NetBackup acsd daemon starts acssel automatically.log
Note: Symantec recommends that acssel run continuously because it tries to connect on the event logger's socket for its message logging. One copy of acsssi starts for each ACS library software host that appears in the NetBackup device configuration for the media server.

(This script stops all NetBackup processes.conf file and add an ACS_SEL_SOCKET entry.conf ACS_SEL_SOCKET entry can change the default). acsssi.)
/usr/openv/NetBackup/bin/bp.conf file does not contain an ACS_SEL_SOCKET entry.)
/usr/openv/NetBackup/bin/bp.conf configuration file
1
Edit the vm. acssel listens on socket name 13740 by default. (The vm. However. To change the default by modifying the vm. Add environment variables. setting an environment variable is preferred.kill_all
2
Set the wanted socket name in an environment variable and export it. and acssel processes by invoking the following script. This method assumes that one ACS robot is configured and that the SSI default socket name has not been changed. The following is an example:
ACS_SEL_SOCKET = 13799 export ACS_SEL_SOCKET
3
Start the event logger in the background. (This script stops all NetBackup processes. and acssel processes by invoking the following script.166
Sun StorageTek ACSLS robots Robotic control.conf configuration file.start_all
To change the default by adding environment variables
1
Stop the acsd. You can change this default by using one of the following methods:
■ ■
Modify the vm. and logging
Using acssel with a different socket name
If the vm.
acssel also has a command line option to specify the socket name. communication.kill_all
3
Restart the NetBackup daemons and processes by invoking the following script:
/usr/openv/NetBackup/bin/bp.
/usr/openv/volmgr/bin/acssel &
. The following is an example:
ACS_SEL_SOCKET = 13799
2
Stop the acsd. acsssi.
because acsssi needs to know the event logger socket name.

NetBackup ACS storage server interface (acsssi)
The NetBackup ACS storage server interface (SSI) acsssi communicates with the ACS library software host. You can specify the socket name (IP port) used by acsssi in any of the following ways:
■
On the command line when you start acsssi. acsssi processes all RPC communications from acsd or from the ACS robotic test utility that are intended for the ACS library software.
CSI_HOSTNAME = einstein export CSI_HOSTNAME
5
Start acsssi as follows:
/usr/openv/volmgr/bin/acsssi 13741 &
6
Optionally.Sun StorageTek ACSLS robots Robotic control. and logging
167
4
Set the ACS library software host name for acsssi in an environment variable. start acstest by using the robtest utility or by using the following command:
/usr/openv/volmgr/bin/acstest -r einstein -s 13741
If you request SCSI unloads. acsd tries to start copies of acsssi for each host. the new acsssi processes for that host fails during initialization.
/usr/openv/volmgr/bin/ltid
During initialization. it has to use (listen on) the same SSI socket that acsd uses to send data. acsd obtains the SSI Event Logger socket name from vm. The robtest utility specifies drive paths automatically if ACS drives have been configured.
. acsssi runs in the background and sends log messages to acssel. if an acsssi process for a specific ACS library software host exists already. See “ACS robotic test utility” on page 169. which starts acsd. However. communication. You can use the -v option for verbose message output. If acsssi is started manually. One copy of acsssi must run for each unique ACS library software host that is configured on a NetBackup media server.
7
Start ltid as follows. In normal operations. you also must specify drive paths on the acstest command line.conf and sets ACS_SEL_SOCKET in the environment before it starts acssel.

the socket names begin at 13741. Start acsssi. it
supports environment variables to control most aspects of operational behavior. and logging
■ ■
By using an environment variable (ACS_SSI_SOCKET). Use the following format:
ACS_SSI_SOCKET = ACS_library_software_hostname socket_name
The following is an example entry (do not use the IP address of the ACS library host for this parameter):
ACS_SSI_SOCKET = einstein 13750
Starting acsssi manually
This method is not the recommended method to start acsssi. To specify socket names on an ACS library software host basis. Normally. The ACS library software host name is passed to acsssi by using the CSI_HOSTNAME environment variable. communication. The following is a Bourne shell example:
CSI_HOSTNAME=einstein export CSI_HOSTNAME /usr/openv/volmgr/bin/acsssi 13741 &
To start acsssi
1 2
Start the event logger. you must configure the CSI_HOSTNAME environment variable.
Using the ACS_SSI_SOCKET configuration option
By default.
If you configure acsssi to use a nondefault socket name.conf file. you can add a configuration entry in the NetBackup vm. See “Optional environment variables” on page 169. you also must configure the ACS daemon and ACS test utility to use the same socket name. acsd starts acsssi. Through the default value. acsssi listens on unique. The format is acsssi socket_name.168
Sun StorageTek ACSLS robots Robotic control. Therefore.
. Before you can start ascssi manually. consecutive socket names.
acsssi is based on the Sun StorageTek storage server interface. acssel.

The default is 172800 seconds. the local host name is used. you can set environment variables before the acsssi processes are started. The acstest utility lets you verify ACS communications and provides a remote system administrative interface to an ACS robot.. Communication problems may occur if acsd and acstest process ACS requests at the same time. unload. You can verify that this service is started by using the Services tool available in administrative tools in the Windows control panel. The default is five retries..Sun StorageTek ACSLS robots ACS robotic test utility
169
Optional environment variables
If you want individual acsssi processes to operate differently. panel. Set this variable to a small positive integer. By default. Set this variable to a small positive integer. enter. eject. and populate ACS library software scratch pools. It can also be used to query. While acsd services requests. acstest lets you define. The default is 2 seconds. do not use acstest. In addition. LSM. and dismount volumes. [-C sub_cmd]
The following example assumes that the LibAttach service started:
install_path\Volmgr\bin\acstest -r einstein -d Tape0 0. delete. acstest attempts to communicate with ACS library software by using the LibAttach service.0. The following are the optional environment variables:
SSI_HOSTNAME Specifies the name of the host where ACS library software RPC return packets are routed for ACS network communications.2. drive] .
acstest on Windows systems
acstest depends on the Sun StorageTek LibAttach service being started
successfully.1
. The usage format follows:
acstest -r ACS_library_software_hostname [-d device_name ACS. mount. Set this variable to a value between 600 seconds and 31536000 seconds.
CSI_RETRY_TIMEOUT
CSI_RETRY_TRIES
CSI_CONNECT_AGETIME
ACS robotic test utility
NetBackup Enterprise Server only.

Restart the NetBackup daemons and processes by invoking the following script:
/usr/openv/NetBackup/bin/bp. [-C sub_cmd]
The following example assumes that the acsssi process has been started by using socket 13741:
/usr/openv/volmgr/bin/acstest -r einstein -s 13741
Changing your ACS robotic configuration
UNIX and Linux systems only. You can pass the socket name on the command line. To update NetBackup after you change your configuration
1 2 3
Make your configuration changes.kill_all to stop all running processes. for the acstest utility to function.. Any acsssi processes must be canceled after your changes are made and before the Media Manager device daemon ltid is restarted. Use /usr/openv/NetBackup/bin/bp.170
Sun StorageTek ACSLS robots Changing your ACS robotic configuration
acstest on UNIX systems
acstest depends on acsssi being started successfully. drive] . acstest
attempts to communicate with ACS library software using acsssi and connects on an existing socket. acsssi for the selected robot must be running. Otherwise. the default socket name (13741) is used. and ACS library software. NetBackup Enterprise Server only.start_all
ACS configurations supported
UNIX and Linux systems only.
. Also. The usage format follows. If you change your ACS robot configuration.. acstest.
acstest -r ACS_library_software_hostname [-s socket_name] [-d drive_path ACS. panel. NetBackup Enterprise Server only. You can use the UNIX netstat -a command to verify that a process listens on the SSI socket. LSM. you should update NetBackup so that acsssi can successfully communicate with acsd.

.0. the configuration is invalid. panel.1 in the NetBackup device configuration Is under control of robot number 10 (ACS(10)). 1. drive) of 0. The robots are controlled from a single ACS library software host.Sun StorageTek ACSLS robots ACS configurations supported
171
NetBackup supports the following ACS configurations:
■ ■
Multiple robots that are controlled from a single ACS host Multiple robots that are controlled from multiple ACS hosts
Multiple ACS robots with one ACS library software host
NetBackup supports the following configuration:
■ ■
A NetBackup server is connected to drives in multiple ACS robots.1.
■
If any other robot ACS(10) drives have a different ACS drive address (for example.
See Figure 10-4 on page 171.1.0). Figure 10-4 Multiple ACS robots. LSM. one ACS library software host
Robot 1 Sun StorageTe k ACS 0 ACS Library Software Host Robot 2 Sun StorageTek ACS 1
NetBackup Server ACS(10) controls drive 1 ACS(20) controls drive 2
Network Communications (RPC)
Inventory requests include: the volumes that are configured on the ACS library software host that resides on the ACS robot that is designated in the drive address. NetBackup supports configurations of multiple LSMs in a single ACS robot if a pass-through port exists.0. assume the following about drive 1:
■
Has an ACS drive address (ACS. In this example.

Ensures that the ACSLS server does not query the portmapper on the client platform. Volume II or the NetBackup Administrator’s Guide for Windows.
Set to FALSE .
Set to TRUE .Firewall-secure ACSLS runs across TCP..
■
The port that the user chooses. you would change the following settings as shown:
■
Changes to alter use of TCP protocol.. The 30031 default value is used most often. For example. in a typical ACSLS firewall configuration. Set to TRUE .conf file.conf entries is available.Allows specification of a single port for the ACSLS server. use the following NetBackup vm.
..conf file configuration entries to designate TCP port connections:
■ ■ ■
ACS_CSI_HOSTPORT ACS_SSI_INET_PORT ACS_TCP_RPCSERVICE
More information about vm..
■
Changes to alter use of the portmapper....Firewall-secure ACSLS runs across TCP.conf file..
■
Changes to alter use of UDP protocol.
Set to NEVER . For complete information about setting up a firewall-secure ACSLS server.. refer to your vendor documentation.Sun StorageTek ACSLS robots Sun StorageTek ACSLS firewall configuration
173
To configure an ACS robot in an Sun StorageTek ACSLS firewall environment.. Volume II.
Port number used by the CSI. The Sun StorageTek ACSLS server configuration options must match the entries in the vm.
■
Enable CSI to be used behind a firewall. This port number must match the port number that you specify in the NetBackup vm. See the NetBackup Administrator’s Guide for UNIX and Linux.

Chapter
11
Device configuration examples
This chapter includes the following topics:
■ ■ ■ ■ ■ ■ ■
A robot on a server example Stand-alone drives on a server example A robot and multiple servers example An ACS robot on a Windows server example An ACS robot on a UNIX server example A TLH robot on a UNIX server example A TLM robot on a UNIX server example
A robot on a server example
Figure 11-1 shows a simple configuration.
.

Device configuration examples A robot and multiple servers example
183
Figure 11-3
Multiple servers and one robot configuration example
ACS Library Software Host
ACS Library Software
ACS number (0-126) Library Management Unit (LMU) LSM number (0-23)
Robotics
D ri ve
SCSI ID
Control Unit (CU)
Drive Drive
SC
Panel number (0-19)
SI
ID
Library Storage Module (LSM)
SCSI ID Drive
Drive number (0-19)
This example is a more complex configuration than the previous examples because of the following:
■ ■
The robotic control is on one NetBackup media server server Two other media servers use the drives. robotic control is on host eel. The Robot Number is 0 in all three cases because the three servers refer to the same physical robot.
Following are some things to note when you review this example:
■
Media for all devices is configured in an EMM server.
■
. which is located on server eel. In this case.

This software must be installed on each Windows server that has the ACS drives attached to it. you can run NetBackup media server software and ACS library software on the same server. where the ACS library software resides. These numbers can be different. and DRIVE numbers are part of the ACS library software configuration and must be obtained from the administrator of that host. LSM.188
Device configuration examples An ACS robot on a Windows server example
The following are items to note when you review this example:
■
The Sun StorageTek ACSLS host (in the Add Robot dialog) is host whale. although they both default to zero. If you connnect the drives through an independent control unit. Table 11-19 Dialog box field
Device Host Robot Type Robot Number Robot control is handled by a remote host ACSLS Host
Add Robot dialog entries (remote host) Value
shark ACS (Automated Cartridge System) 0 Set (cannot be changed for this robot type) whale
Table 11-20 shows the drive 0 attributes. The Add Robot dialog entries include an ACSLS Host entry so that the ACS library software host communicates by using STK LibAttach software. Automated Cartridge System Library Software (ACSLS) is installed as the ACS library software. PANEL. you must use the correct Logical Unit Numbers (LUNs) so that the correct tape name is used. Robot number is the robot identifier used in NetBackup. Robot number and ACS number are different terms. you need only one server. Therefore.
■
■
■
■
Table 11-19 shows the robot attributes for the remote host shark. On some server platforms. The ACS. ACS number is the robot identifier in ACS library software. In this example. Table 11-20 Dialog box field
Device Host Drive Type Drive Name
Add Drive dialog entries (drive 0) Value
shark 1/2" Cartridge (hcart) shark_drive_0
.

These numbers can be different. If you connnect the drives through an independent control unit. LSM. where the ACS library software resides. although they both default to zero. you can run NetBackup media server software and ACS library software on the same server. Robot number is the robot identifier used in NetBackup. Host shark can be a UNIX NetBackup master server or media server. and DRIVE numbers are part of the ACS library software configuration and must be obtained from that system.
■
■
■
. Automated Cartridge System Library Software (ACSLS) is installed as the ACS library software. On some server platforms. In this example. Therefore. PANEL. ACS number is the robot identifier in ACS library software. Robot number and ACS number are different terms. The ACS.190
Device configuration examples An ACS robot on a UNIX server example
Figure 11-5
Host A
UNIX server and ACS robot configuration example
Device Manager Host B tldd Tape Library DLT (TLD)
tldcd
Device Manager
Robotics SCSI
tldd
Drive 1
Drive 2
SCSI
This configuration uses an Automated Cartridge System (ACS) robot for storage. you need only one server. The following are some items to note when you review this example:
■
The ACSLS Host (in the Add Robot dialog) is server whale. you must use the correct Logical Unit Numbers (LUNs) so that the correct tape name is used.

If shark was a UNIX server that was not AIX or a Windows server. The robotic control (tlhcd) also can exist on a different server. The main difference between TLH robot configuration and other robot types is the robotic device file. so the LMCP file is specified for the robotic device file. Linux. You cannot assign a cleaning frequency in NetBackup. The drive configuration uses the IBM device number. The server shark can be a UNIX (AIX. Solaris SPARC.Device configuration examples A TLH robot on a UNIX server example
193
Figure 11-6
UNIX Server shark
UNIX server and TLH robot configuration example
LMCP
Library Manager
PC Device Files for the physical drives TLH Robot IBM Automated Tape Library (ATL) SCSI
003590B1A00
003590B1A01
TLH_rob_drv1
TLH_rob_drv2
This configuration adds a TLH robot to the configuration. The following are some things to note when you review this example:
■
The robot control host is the server shark.
■
■
. HP-UX). or Windows server. In this example. you would specify the library name (for example 3494AH). The robotic device file is the Library Manager Control Point (LMCP) file on AIX systems and is the library name on non-AIX systems. shark is a AIX server. and can be a NetBackup master server or media server.