VERITAS NetBackup™ 6.
Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix What Is In This Guide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix How To Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Third-Party Fibre Channel HBA Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Configuring Robotic Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Configuring SCSI Robotic Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Examples of SCSI Robotic Control Device Files . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Configuring Tape Drives . . . . . . . . . . . . . . . . . . . . .
Configuring SCSI Robotic Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Examples of SCSI Robotic Control Device Files . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Configuring IBM 3590 Stacker Robotic Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configuring Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configuring Non-QIC Tape Drives . . . . . . . . . . . . .
Configuring Device Files for the spt Passthru Driver . . . . . . . . . . . . . . . . . . . . . 60 Configuring Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Using Berkeley Style Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Using the Passthru Driver for Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Automatic Configuration . . . . . . . . . . . . .
Device-Specific Entry for HP Ultrium 460 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Device-Specific Entry for HP Ultrium 230e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Device-Specific Entry for Seagate Viper 200 - LTO . . . . . . . . . . . . . . . . . . . . . . . . 79 Device-Specific Entry for STK 9840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Tape Device Drivers on 64 Bit Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This guide contains configuration information for adding storage peripherals (devices) to NetBackup media servers or SAN media servers controlled by Media Manager (NetBackup master servers can also be media servers). NetBackup (includes Media Manager) can be installed on UNIX or Windows servers. See the NetBackup release notes for information on the supported UNIX and Windows server platforms.
How To Use This Guide How To Use This Guide Keep the following points in mind when using this guide. ◆ Each server platform that is supported by NetBackup as a media server or SAN media servers is described in a separate chapter in this guide. You should only have to use the chapters for the platforms on which you are configuring devices. ◆ This guide is intended for use with NetBackup Server and NetBackup Enterprise Server.
Getting Help Accessing the VERITAS Technical Support Web Site The address for the VERITAS Technical Support Web site is http://support.veritas.com.
Accessibility Features a. From the main http://support.veritas.com page, click the E-mail Support icon. A wizard guides you to do the following: ◆ Select a language of your preference ◆ Select a product and a platform ◆ Provide additional contact and product information, and your message ◆ Associate your message to an existing technical support case b. After providing the required information, click Send Message.
Comment on the Documentation Comment on the Documentation Let us know what you like and dislike about the documentation. Were you able to find the information you needed quickly? Was the information clearly presented? You can report errors and omissions or tell us what you would find useful in future versions of our manuals and online help.
Comment on the Documentation xiv NetBackup Media Manager Device Configuration Guide for UNIX, Windows, and Linux
1 Using This Guide Before You Start Configuring Devices Observe the following important points before using this guide to configure media servers or SAN media servers, and devices. Considerations When Using This Guide ◆ “How To Use This Guide” on page x provides additional instructions for using this guide that you should review. ◆ This guide is intended for use with NetBackup Server and NetBackup Enterprise Server.
Before You Start Configuring Devices ◆ To minimize configuration errors, you can cut/paste configuration details from the text version of this configuration guide. The formatting of this text file is similar, but is not identical to the printed version of the guide. Be sure to review the differences as explained at the beginning of the text file. This file is installed with NetBackup Media Manager software in the following UNIX path: /usr/openv/volmgr/MediaMgr_DeviceConfig_Guide.txt.
General Device Configuration Sequence General Device Configuration Sequence Use the following general sequence when configuring your devices. 1. Physically connect the storage devices to the media server and perform any hardware configuration steps specified by the device or operating system vendor. See the appropriate chapter of this guide for your media server or SAN media server platform. 2.
General Device Configuration Sequence 4 NetBackup Media Manager Device Configuration Guide for UNIX, Windows, and Linux
2 Sun Solaris This chapter explains how to configure storage devices for use with Media Manager running on a Solaris platform.
Before You Start Before You Start Observe the following points when performing the configurations described in this chapter: ◆ The VERITAS support web site (http://www.support.veritas.com) contains server platform compatibility information for a number of vendors and products (see the NetBackup Product > Compatibility area of the site). Verify that your server platform is supported before configuring devices.
Preventing Possible System Problems Preventing Possible System Problems When system memory is limited, Solaris unloads unused drivers from memory and reloads drivers as needed. Tape drivers are a frequent candidate for unloading, since they tend to be less heavily used than disk drivers. Depending on the timing of these unload and load events for the st (Sun), sg (VERITAS), and fibre channel drivers, various problems may result.
Understanding the SCSI Passthru Drivers ▼ ◆ To collect TapeAlert information from tape devices allowing support of functions such as tape drive cleaning. ◆ For WORM tape support. ◆ Future NetBackup features and enhancements To manipulate the sg driver Perform the following steps as the root user. 1. Determine if an sg driver is loaded by using the following command: /usr/sbin/modinfo | grep sg 141 fc580000 153 fc7fa000 2d8c 116 1684 49 1 1 sg (SCSA Generic Revision: 3.
Configuring SG and ST Drivers Configuring SG and ST Drivers This procedure contains instructions for configuring the sg driver for SCSI targets 0 thru 6 and 8 thru 15 for fast or wide adapter cards. In this procedure, you execute sg.build to add these targets to the st.conf, sg.conf and sg.links files. Adjust the -mt and -ml parameters to create the range of targets and LUNs required by your configuration. See the following command summary or the more detailed explanation which follows.
Configuring SG and ST Drivers a. Make a copy of the /kernel/drv/st.conf file. b. Edit the /kernel/drv/st.conf file. Place a # in column one of each line of the seven default entries. The temporary file ./st.conf contains the entries that you need to insert into /kernel/drv/st.conf. c. Reboot the system with the reconfigure option (boot -r or reboot -- -r). d. Verify that the system created device nodes for all the tape devices using the following command: ls -l /dev/rmt/*cbn 3.
Configuring SG and ST Drivers 4. The following is an example of the /usr/openv/volmgr/bin/driver/sg.
Configuring the Sun StorEdge Network Foundation HBA Driver Configuring the Sun StorEdge Network Foundation HBA Driver The StorEdge Network Foundation HBA requires special configuration to bind device World Wide port names for use by the VERITAS sg driver. The script /usr/openv/volmgr/bin/sg.build adds the proper entries to the sg.links and sg.conf files. Before running the script, make sure that all devices are powered on and connected to the HBA.
Configuring Robotic Controls The binding process is vendor and product unique. Please refer to the documentation available for your specific HBA. The binding may be based on the fibre channel World Wide name of the port (WWPN) or the node (WWNN), or the destination ID (AL-PA or fabric assigned). Once the selected binding is in place, the configuration proceeds in the same manner as for parallel SCSI installations (see “Configuring SG and ST Drivers” on page 9).
Configuring Robotic Controls /dev/sg/c2t2l0: /dev/sg/c2t5l0: /dev/sg/c3t0l0: /dev/sg/c3t3l0: /dev/sg/c4t4l0: /dev/sg/c4t5l0: /dev/sg/c5t0l0: /dev/sg/c5t1l0: /dev/sg/c5t2l0: /dev/sg/c5t6l0: /dev/sg/c6t3l0: /dev/sg/c6t5l0: /dev/sg/c7t0l0: /dev/sg/c7t3l0: /dev/sg/c7t4l0: /dev/sg/c8t2l0: /dev/sg/c8t3l0: /dev/sg/c8t4l0: /dev/sg/c8t6l0: /dev/sg/c9t0l0: /dev/sg/c9t1l0: Tape (/dev/rmt/10): "Quantum DLT4000" Tape (/dev/rmt/11): "QUANTUM DLT7000" Disk (/dev/rdsk/c1t0d0): "FUJITSU M2952ESP SUN2.
Configuring Robotic Controls Example 3 Using the previous sgscan output, if the SCSI robotic control for an STK 9710 is SCSI ID 6 of adapter 8 and you want to use TLD robotics, use the following path: /dev/sg/c8t6l0 Example 4 If the SCSI robotic control for a DLT2700, DLT4700, or HP C1560B was SCSI ID 5 of adapter 0, use the following path: /dev/sg/c0t5l1 Note that logical unit number 1 is used for those devices. The sg driver configuration can be modified so sgscan lists LUN 1 devices.
Configuring Tape Drives Example 7 (Fujitsu M8100 Stackers) The robotic control for the Fujitsu M8100 stacker is TSH. The unit must be set up to run in SYSTEM Mode and 2LUN Mode. See the M8100 Cartridge Tape Drive product guide supplied with the unit for information on setting the library modes. The robotic control is LUN 1 of the drive's SCSI ID. The SCSI ID's are viewed and configured by using the front panel on the stacker.
Configuring Tape Drives Enabling locate-block NetBackup and Storage Migrator use the locate-block command by default if you did not uninstall the sg passthru driver. This uninstall procedure is explained in “Understanding the SCSI Passthru Drivers” on page 7. The driver is automatically installed with Media Manager. Disabling locate-block VERITAS recommends that you do not disable locate-block positioning.
Configuring Tape Drives No rewind on close device files are in the /dev/rmt directory, and have the following format: /dev/rmt/LOGICAL_DRIVE cbn Where: ◆ LOGICAL_DRIVE is the logical drive id, as shown by the sgscan command. ◆ c indicates compression. ◆ b indicates Berkeley-style close. ◆ n indicates no rewind on close.
Configuring Tape Drives Solaris Patches Some drives (for example, Quantum SDLT600) require Solaris patches for support. In these cases VERITAS lists the required patches for the drive on the VERITAS support web site (http://www.support.veritas.com). Device and library compatibility information for a number of vendors and products is available (see the NetBackup Product > Compatibility area of the site).
Configuring Tape Drives If you were to omit four of the spaces in the vendor name as shown in the following example, the drive would not be recognized correctly. The incorrect vendor name used would be HP + 2 spaces + C153. "HP ◆ C1533A", The best way to ensure that your entries are accurate is to copy them from the MediaMgr_DeviceConfig_Guide.txt file into the st.conf file. See “Considerations When Using This Guide” on page 1.
Configuring Tape Drives "IBM ULT3580-TD2", "IBM 3580 Ultrium-2", "CLASS_LTO2", "IBM Ultrium-TD2", "IBM Ultrium-2", "CLASS_LTO2", "SEAGATE ULTRIUM06242-XXX","Seagate LTO","SEAGATE_LTO", "SONY GY-2120", "Sony DTF Drive", "gy20-data", "SONY GY-8240", "DTF2", "gy2120-data", "SONY SDX-300C", "SONY 8mm AIT", "SONY_AIT", "SONY SDX-400C", "SONY 8mm AIT", "SONY_AIT", "SONY SDX-500C", "SONY 8mm AIT2", "SONY_AIT", "SONY SDX-700C", "Sony AIT3 8mm", "SONY_AIT3", "SONY SDZ-100", "SONY S-AIT", "SONY_SAIT", "SONY SDZ-130"
Configuring Tape Drives BM-DLT = 1,0x38,0,0x18639,4,0x40,0x40,0x40,0x40,3; CLASS_3580 = 1,0x24,0,0x45863d,2,0x00,0x01,0; CLASS_3590 = 1,0x24,0,0x1c63d,4,0x0,0x0,0x0,0x0,3; CLASS_3592 = 1,0x24,0,0x45D639,2,0x00,0x51,0; CLASS_LTO2 = 1,0x24,0,0x45863d,2,0x00,0x01,0; CLASS_STK = 1,0x36,0,0x1d639,1,0x00,0; DEC-DLT = 1,0x36,0,0x9639,4,0x0,0x0,0x0,0x0,3; DLT8k-data = 1,0x38,0,0x19639,4,0x1a,0x1b,0x41,0x41,3; EXB-8500C = 1,0x35,0,0x9639,4,0x14,0x15,0x8C,0x00,3; EXB-8505 = 1,0x35,0,0x9639,4,0x14,0x15,0x8C,0x00,3; E
Configuring Optical Disk Drives Adding Logical Unit Number Entries If the devices you are adding utilize the logical unit number (LUN) concept, (such as many fibre channel SAN configurations) you may also have to add entries to the following files: ◆ st.conf ◆ sg.conf ◆ sg.links See the “Configuring SG and ST Drivers” on page 9 for information on sg.build, a script that is used to create these files, and examples of the proper syntax to use.
Configuring Optical Disk Drives To display the disk device files that are configured on your system, use the sgscan command with the disk parameter: # /usr/openv/volmgr/bin/sgscan disk /dev/sg/c0t0l0: /dev/sg/c0t1l0: /dev/sg/c0t2l0: /dev/sg/c0t5l0: /dev/sg/c1t0l0: /dev/sg/c1t1l0: /dev/sg/c1t2l0: (/dev/rdsk/c0t0d0): (/dev/rdsk/c0t1d0): (/dev/rdsk/c0t2d0): (/dev/rdsk/c0t5d0): (/dev/rdsk/c1t0d0): (/dev/rdsk/c1t1d0): (/dev/rdsk/c1t2d0): "IBM "HP "HP "HP "SONY "SONY "SEAGATE DCAS32160SUN2.
Configuring Optical Disk Drives Example 2 Using the previous sample sgscan output, if the desired optical disk drive connects to SCSI ID 0 of S bus 1 adapter card 1, you would use the following device paths: Volume header device: /dev/rdsk/c1t0d0s0 Character device: /dev/rdsk/c1t0d0s6 Setting the HP Optical Drive Type in Nonvolatile Memory To use HP optical disk drives, the system must recognize the optical drives as disk drives at system boot time. If you are adding HP 1.
Command Summary Command Summary The following is a summary of commands that may be useful when configuring and verifying devices. See the procedures in this chapter for examples of their usage. /usr/sbin/modinfo | grep sg Displays whether or not the sg driver is installed. /usr/openv/volmgr/bin/driver/sg.install Installs or updates the sg driver. /usr/sbin/rem_drv sg Uninstalls the sg driver. This command is usually not necessary, since sg.install does this before performing a driver update.
3 IBM AIX This chapter explains how to configure storage devices for use with Media Manager running on an IBM AIX system.
Before You Start Before You Start Observe the following points when performing the configurations described in this chapter: ◆ The VERITAS support web site (http://www.support.veritas.com) contains server platform compatibility information for a number of vendors and products (see the NetBackup Product > Compatibility area of the site). Verify that your server platform is supported before configuring devices. ◆ Attach all peripherals and reboot the system before configuring devices.
RS6000 AIX Adapter Number Conventions The first digit of BB identifies the I/O bus containing the adapter card. If the card is in the CPU drawer or system unit, this digit will be 0 for the standard I/O bus or 1 for the optional I/O bus. If the card is in an I/O expansion drawer, this digit is 0. The second digit identifies the slot number on the indicated I/O bus (or slot number in the I/O expansion drawer) that contains the card. A location code of 00-00 is used to identify the Standard I/O Planar.
The SCSI Passthru Driver (ovpass) The SCSI Passthru Driver (ovpass) Read this topic if you plan to use SCSI-controlled robotic peripherals or HP 1.2 gigabyte or equivalent model magneto-optical disk drives. If you are using an API robot, such as an IBM Automatic Tape Library (ATL), refer to the NetBackup Media Manager Administration guide for information on configuring the robotic peripheral.
Configuring Robotic Controls ▼ To ensure 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 ▼ To remove the ovpass driver ❖ Enter: /usr/openv/volmgr/bin/driver/remove_ovpass Upgrading The SCSI Passthru Driver Note The following upgrade procedure is required only if you get an error while trying to configure a FCP SCSI device. See step 5 on page 33 for details.
Configuring Robotic Controls Configuring SCSI Robotic Controls Read this topic if you plan to use a robotic storage device that is controlled through a SCSI robotic connection. Information on supported SCSI robots (vendor models) can be found on the VERITAS support web site (see the NetBackup Product > Compatibility area of the site). ▼ To check for and create the necessary device files 1. Install the SCSI passthru driver as explained in “The SCSI Passthru Driver (ovpass)” on page 30. 2.
Configuring Robotic Controls 4. Display the FCP SCSI device files that have already been created by using the following command: /usr/sbin/lsdev -C -s fcp 5. If device files for the desired robotic control SCSI ID do not exist, create the files using the following commands. Note If you get an error (mkdev error code 0514-0520) while trying to configure a FCP SCSI device, review the topic “Upgrading The SCSI Passthru Driver” on page 31.
Configuring Robotic Controls ◆ Inspect the odm database for any tape devices in the robot using the following command: /usr/bin/odmget -q "name=rmtX" CuAt Where rmtX is the name of the tape device (for example: rmt0 or rmt1).
Configuring Robotic Controls Note Note that the smc device file only exists for IBM robots using the Atape driver. If smc0 device files exist for SCSI-connected IBM silos, remove the smc0 device files to allow for the use of ovpass0 files. See the VERITAS support site for a tech note with instructions for removing the smc0 files. The headline of the tech note is “Install_ovpass script does not appear to work upon AIX reboot”. 6.
Configuring Robotic Controls The output shows that the device files exist for tape and disk, but not for the SCSI robotic control at controller 1 (scsi0) and SCSI ID 5 (5,0). hdisk0 rmt0 Available 00-01-00-0,0 400 MB SCSI Disk Drive Available 00-01-00-3,0 Other SCSI Tape Drive 3. Create the device files by using the following command: mkdev -c media_changer -t ovpass -s scsi -p scsi0 -w 5,0 4.
Configuring Robotic Controls 4. Display the device files by issuing the lsdev command.
Configuring Tape Drives If this is the case, the host system which is connected to Drive 1 must also have the robotic control. Also, the library should be in RANDOM mode and BASE configuration. See the operator's guide supplied with the unit for information on setting library mode and configuration.
Configuring Tape Drives Configuring Non-QIC Tape Drives The terms variable length block or fixed length block refer to the behavior of reads and writes and the way the kernel packs physical tape records into logical tape records for an application. Variable-mode devices allow more flexibility in reading previously written tapes. Many tape devices can be accessed in either mode. NetBackup assumes variable length for non-QIC drives. For more information, see chdev(1), smit(1) and the system management guide.
Configuring Tape Drives Automatic Configuration When a tape drive is configured using NetBackup, NetBackup will automatically issue the chdev command to configure the drive to use extended file marks. It is normally not necessary to manually run the chdev command, but the details of the command issued by NetBackup are provided (see “Using the chdev Command” on page 40).
Configuring Tape Drives This sample output shows that SCSI controller 1 (00-01) has been assigned the logical identifier scsi0. scsi0 Available 00-01 SCSI I/O Controller 2.
Configuring Tape Drives You can display the newly created logical identifier for the device by using the lsdev command. /usr/sbin/lsdev -C -s scsi hdisk0 hdisk1 rmt0 rmt1 ovpass0 Available Available Available Available Available 00-01-00-0,0 00-01-00-1,0 00-01-00-3,0 00-01-00-5,0 00-01-6,0 400 MB SCSI Disk Drive 400 MB SCSI Disk Drive Other SCSI Tape Drive Other SCSI Tape Drive VERITAS Media Changer The rmt1 device file has been created. 4.
Configuring Tape Drives 3. Create the desired device files by using the following command: mkdev -c tape -t ost -s scsi -p scsi0 -w 5,0 4. Display the device files by issuing the following lsdev command: /usr/sbin/lsdev -C -s scsi hdisk0 hdisk1 rmt0 rmt1 Available Available Available Available 00-01-00-0,0 00-01-00-1,0 00-01-00-3,0 00-01-00-5,0 400 MB SCSI Disk Drive 400 MB SCSI Disk Drive Other SCSI Tape Drive Other SCSI Tape Drive 5.
Configuring Tape Drives To use density setting 1, use the following no rewind on close device file: /dev/rmt*.1 To use density setting 2, use the following no rewind on close device file: /dev/rmt*.5 Adding Sony AIT Drives Sony S-AIT drives have dip switches (SWA and SWB) located on the bottom of the drive. It is important that these switches are set correctly for use in an SSO configuration.
Configuring Optical Disk Drives Configuring Optical Disk Drives When adding optical disk drives to a Media Manager configuration, you specify only a character device path. Optical disk character device files are located in the /dev directory and have the following format, where ID is the logical identifier assigned to the device by the system. /dev/rhdiskID Note To use HP optical disk drives, the system must recognize the optical drives as disk drives at system boot time. If you are adding HP 1.
Configuring Optical Disk Drives If the device files for the SCSI optical disk drives exist, they show up in the output as hdisk0, hdisk1, and so on. hdisk0 hdisk1 rmt0 Available 00-01-00-0,0 400 MB SCSI Disk Drive Available 00-01-00-1,0 400 MB SCSI Disk Drive Available 00-01-00-3,0 Other SCSI Tape Drive For hdisk0, you would use the following device path: /dev/rhdisk0 3.
Configuring Optical Disk Drives Examples of Optical Disk Device Files Assume the device files for the desired optical disk drive (controller 1, SCSI ID 5) do not yet exist. 1. Determine the logical identifier for the SCSI controller as follows: /usr/sbin/lsdev -C -c adapter | grep SCSI The output shows that scsi0 is the logical name for SCSI controller 1. scsi0 Available 00-01 SCSI I/O Controller 2. Check to see if the device files exist for ovpass at SCSI ID 5.
Configuring Optical Disk Drives Setting the HP Optical Drive Type in Nonvolatile Memory To use HP optical disk drives, the system must recognize the optical drives as disk drives at system boot time. If you are adding HP 1.2 gigabyte or equivalent model magneto-optical disk drives to an AIX system, the system may not recognize them as disk drives and cannot use them. ▼ To detect whether the system recognizes the optical drives 1. Execute the following command after system boot.
Configuring Optical Disk Drives The following example output shows that a disk drive, a tape drive, an optical drive, and SCSI robotic control are configured: ◆ hdisk0 is a disk drive at controller 1 (00) and SCSI ID 0 (0,0) ◆ rmt0 is a tape drive at controller 1 (00) and SCSI ID 3 (3,0) ◆ omd0 is an optical drive at controller 1 (00) and SCSI ID 6 (6,0) ◆ ovpass0 refers to the SCSI robotic control for controller 1 (00) and SCSI ID 2 (2,0) hdisk0 rmt0 omd0 Available 00-00-0S-0,0 2.
Configuring Optical Disk Drives 3. Use the following command to change the device type (stored in the drive’s nonvolatile memory) from optical memory to disk. The format of the command is as follows, where ovpass_id is the logical identifier assigned to the device. /usr/openv/volmgr/bin/scsi_command -d /dev/ovpass_id -disk For example: /usr/openv/volmgr/bin/scsi_command -d /dev/ovpass1 -disk 4.
Command Summary Command Summary The following is a summary of commands that may be useful when configuring devices. See the procedures in this chapter for examples of their usage. /usr/openv/volmgr/bin/driver/install_ovpass Installs the ovpass driver for the first time. /usr/openv/volmgr/bin/driver/remove_ovpass Removes the ovpass driver.
Command Summary mkdev -c tape -s scsi -t ost -p controller -w id,lun Creates device files for tapes. Where controller is the logical identifier of the drive SCSI adaptor (such as scsi0 or scsi1), id is the SCSI ID of the robotic connection, and lun is the logical unit number of the robotic connection. /usr/sbin/chdev -l dev -a block_size=0 Configures the drive with logical identifier specified by dev (for example: rmt0) to variable mode.
4 Hewlett-Packard HP-UX This chapter explains how to configure storage devices for use with Media Manager running on an HP-UX system.
Before You Start Before You Start Observe the following points when performing the configurations described in this chapter: ◆ The VERITAS support web site (http://www.support.veritas.com) contains server platform compatibility information for a number of vendors and products (see the NetBackup Product > Compatibility area of the site). Verify that your server platform is supported before configuring devices.
Configuring Robotic Controls Configuring Robotic Controls Robots are controlled through a SCSI or a network connection. Robot control configuration can be found as follows: ◆ SCSI control is covered in the following sections. ◆ Configuration of network controlled robotic libraries (for example, ACS robots) is discussed in the appendices of the VERITAS NetBackup Media Manager System Administrator’s Guide for UNIX and Linux or the VERITAS NetBackup Media Manager System Administrator’s Guide for Windows.
Configuring Robotic Controls Example 1: Built-in SCSI interface (sctl driver) ioscan -f Class I H/W Path Driver S/W State H/W Type Description ==================================================================== ext_bus 2 10/12/5 c700 CLAIMED INTERFACE Built-in SCSI target 11 10/12/5.0 tgt CLAIMED DEVICE tape 0 10/12/5.0.0 stape CLAIMED DEVICE HP C1533A target 12 10/12/5.2 tgt CLAIMED DEVICE disk 6 10/12/5.2.0 sdisk CLAIMED DEVICE TOSHIBA CD-ROM In this case, the ext_bus entry specifies a c700 driver.
Configuring Robotic Controls If the devices do not exist, you can create device files by using the mknod command as follows. See the scsi_ctl(7) man page. mkdir /dev/sctl cd /dev/sctl /usr/sbin/mknod cCONTROLLERtTARGETlLUN c 203 0xIITL00 Where: ◆ CONTROLLER is the Instance number of the controlling bus. The Instance value is displayed in ioscan -f output under column I of the controller entry (ext_bus in the Class column). ◆ TARGET is the SCSI ID of the robotic control.
Configuring Robotic Controls Examples of Creating Device Files Example 1 In this example the robotic control for a ADIC Scalar 100 library is on a SCSI bus with a instance number of 7 (ext_bus entry, I column), SCSI ID 2 and LUN 0. The robotic control for an IBM ULT3583-TL library is on the same SCSI bus at SCSI ID 3 and LUN 0. Use the following procedure to create the robotic device files: 1. Use the ioscan -f command to get information on the SCSI bus and the robotic control.
Configuring Robotic Controls Example 2 Assume the robotic control for an Exabyte 10i tape stacker (TS8) is on a built-in SCSI bus at SCSI ID 3, LUN 0. Also assume that an ioscan -f verifies that the SCSI ID is 3 and shows that the Instance number for the robot’s SCSI bus is 1. The commands to create the device file are cd /dev/sctl /usr/sbin/mknod c1t3l0 c 203 0x013000 This creates the following device file, which you specify to Media Manager: /dev/sctl/c1t3l0 Example 3 1.
Configuring Robotic Controls 3. The commands to create the passthru device file for the tape drive follow. See the “Command Summary” on page 70 for the mknod command format or see the scsi_ctl(7) man page. cd /dev/sctl /usr/sbin/mknod c3t0l0 c 203 0x030000 These commands create the following passthru device file. /dev/sctl/c3t0l0 Although the passthru device file is used during NetBackup operation, it is not specified during configuration.
Configuring Robotic Controls 3. Use the following commands to create the device file for the SCSI robotic control: mkdir /dev/spt mknod /dev/spt/Name c Major 0xIITL00 Where: ◆ Name is the device name as defined in the format: cCONTROLLERtTARGETlUNIT ◆ Major is the character major number (from the lsdev command). ◆ II is two hexadecimal digits identifying the controlling bus interface card by its Instance number. ◆ T is one hexadecimal digit representing the SCSI ID of robotic control.
Configuring Tape Drives 4. Create the device file as follows: mknod /dev/spt/c1t3l0 c 137 0x013000 This command creates the /dev/spt/c1t3l0 device file. Specify this file as the robot control path when configuring your device under Media Manager. Configuring Tape Drives Read the following topics if you plan to use tape drives: Using Berkeley Style Close The examples in this section show Berkeley-style close for tape drives as indicated by the letter b after the compression specification.
Configuring Tape Drives ◆ To collect TapeAlert information from tape devices allowing support of functions such as tape drive cleaning. ◆ For WORM tape support. ◆ Future NetBackup features and enhancements Note Passthru paths are not supported on HP-PB adapters such as HP 28696A - Wide SCSI or HP 28655A - SE SCSI.
Configuring Tape Drives The IBM library contains 2 IBM Ultrium LTO drives, one with SCSI ID 4, SCSI LUN 0 and the other with SCSI ID 5, SCSI LUN 0. Use the following procedure to create the robotic control device files and the passthru driver tape drive device files: 1.
Configuring Tape Drives 3. The commands to create the passthru device files for the tape drives are as follows: cd /dev/sctl /usr/sbin/mknod /usr/sbin/mknod /usr/sbin/mknod /usr/sbin/mknod c7t0l0 c7t1l0 c7t4l0 c7t5l0 c c c c 203 203 203 203 0x070000 0x071000 0x074000 0x075000 These commands create the following passthru device files. Although the passthru device files for tape drives are used during NetBackup operation, they are not specified during configuration.
Configuring Tape Drives Enabling SCSI Reserve/Release This is a NetBackup Enterprise Server topic. The VERITAS implementation of SCSI reserve/release protects data on a tape from corruption by other applications in a shared drive (SSO) configuration. ▼ To enable SCSI reserve/release 1. Set the kernel parameter st_ats_enabled to zero. Using the SAM utility is the easiest way to set this parameter.
Configuring Tape Drives No Rewind Device Files When adding tape drives to the Media Manager configuration, you need only specify a no rewind on close device file path. These device files are found in the /dev/rmt directory and have the following format: /dev/rmt/cCONTROLLERtTARGETdUNITBESTnb Where: ◆ CONTROLLER is the Instance number of the controlling bus. The Instance value is displayed in ioscan -f output under the column I of the controllers entry (ext_bus in the Class column).
Configuring Optical Disk Drives Configuring Optical Disk Drives When adding optical disk drives to the Media Manager configuration, you need only specify a character device path. Optical disk character device files are found in the /dev/rdsk directory and have the following format: /dev/rdsk/cBItTARGETd0 Where: ◆ BI is the bus Instance number of the controlling bus. The Instance value is displayed in ioscan output under the column I of the ext_bus entries. ◆ TARGET is the SCSI ID of the drive.
Handling Errors when More Than 10 NetBackup Jobs are Active Using the Configure Storage Devices Wizard with Optical Disk Drives The Media Manager device configuration wizard can discover and automatically configure optical disk drives that have a /dev/sctl SCSI passthru device file. Note Optical disk drives are not supported in an SSO configuration. ▼ To use the device configuration wizard 1. Create the passthru device files.
Command Summary ▼ To modify the kernel The following procedure uses the /usr/sbin/sam utility to change the value of semmnu to 50. A reboot is necessary for the changes to take effect. See the appropriate HP-UX documentation for information on using this utility. 1. Select SAM Kernel Configuration. 2. Select SAM Configurable Parameters. 3. Select semmnu. 4. Select Actions from the menu bar. 5. Select Modify Configurable Parameter from the menu. 6. Select Formula/Value and enter 50. 7.
Command Summary mknod /dev/spt/Name c Major 0xIITL00 Creates device files for SCSI robotic or tape drive controls. Name is the device name as defined in the format: cCONTROLLERtTARGETlUNIT Major is the character major number (from the lsdev command). II are the two hexadecimal digits identifying the controlling bus interface card by its Instance number. The Instance value is displayed in the ioscan output under the I column of the proper ext_bus entry.
Command Summary 72 NetBackup Media Manager Device Configuration Guide for UNIX, Windows, and Linux
5 Hewlett-Packard Tru64 This chapter explains how to configure storage devices for use with Media Manager running on an HP Alpha system.
Before You Start Before You Start Observe the following points when performing the configurations described in this chapter: ◆ The VERITAS support web site (http://www.support.veritas.com) contains server platform compatibility information for a number of vendors and products (see the NetBackup Product > Compatibility area of the site). Verify that your server platform is supported before configuring devices.
Configuring Tape Drives Creating SCSI Robotic Control Device Files Media Manager requires that device files from the /dev/changer directory are used to configure SCSI robotic control. These files are created by the operating system at boot time. To display devices that are available on the system, use the following command: # hwmgr -view devices HWID: Device Name Mfg Model Location -------------------------------------------------------------3: /dev/kevm 34: /dev/disk/floppy0c 3.
Configuring Tape Drives Adding Standard Tape Drives Media Manager requires that no rewind on close device files are used to configure tape drives. These files are created by the operating system at boot time. The device files are located in the /dev/ntape directory and have the following format: /dev/ntape/tapeID_dDENSITY Where: ◆ ID is the identification number of the tape device. ◆ Values for DENSITY can be 0 - 7. Typically, 1 (for high density) is used.
Configuring Tape Drives Adding Nonstandard Tape Drives This topic applies to the following drive types: ◆ HP LTO ◆ Seagate LTO ◆ STK 9840 Some types of tape drives require changes to the kernel before you can use them on Tru64. ▼ To change the kernel Refer to the following man pages for more information on Dynamic Device Recognition (DDR): ◆ ddr.dbase(4) ◆ ddr_config(8) 1. Add the appropriate device-specific entries to the /etc/ddr.
Configuring Tape Drives DensityCode = Blocking = CompressionCode = Buffered = Speed = # # Ultrium mode select # MODESELECT: ModeSelectNumber = SavePage = PageFormat = BlockDescriptor = TransferLength = Hdr.Tape.BufferMode = Hdr.MediumType = Data.UBYTE[0] = Data.UBYTE[1] = Data.UBYTE[2] = Data.
Configuring Tape Drives DENSITY: DensityNumber = 1 OneFileMarkOnClose = yes DensityCode = 0x00 Blocking = 0 CompressionCode = 0x1 Buffered = 0x1 Device-Specific Entry for Seagate Viper 200 - LTO SCSIDEVICE Type = tape Name = "SEAGATE" "ULTRIUM" PARAMETERS: TypeSubClass TagQueueDepth MaxTransferSize ReadyTimeSeconds CMD_PreventAllow CMD_ExtReserveRelease BlockSize PwrMgmt_Capable = = = = = = = = tk 0 0x0ffffff # (16MB - 1) 180 # seconds supported supported 0 false DENSITY: DensityNumber DensityCode Comp
Configuring Tape Drives Device-Specific Entry for STK 9840 SCSIDEVICE Type = tape Stype = 2 Name = "STK" "9840" PARAMETERS: TypeSubClass BlockSize MaxTransferSize SyncTransfers WideTransfers Disconnects CmdReordering TaggedQueuing TagQueueDepth WCE_Capable PwrMgmt_Capable LongTimeoutRetry ReadyTimeSeconds DisperseQueue CMD_PreventAllow CMD_ExtReserveRelease = = = = = = = = = = = = = = = = 3480 0 0x40000 enabled enabled enabled disabled disabled 0 false false disabled 240 false supported supported # 256k
Command Summary DENSITY: # # /dev/tape/tapeX_d2, _d6 # DensityNumber = 2,6 DensityCode = 0x43 CompressionCode = 0 Buffered = 0x1 Command Summary The following is a summary of commands that may be useful when configuring and verifying devices. See the procedures in this chapter for usage examples. hwmgr -view devices Displays all devices on the system.
Command Summary 82 NetBackup Media Manager Device Configuration Guide for UNIX, Windows, and Linux
6 Enterprise Linux This chapter explains how to configure devices for use with Media Manager on an Intel host platform running Linux. After configuring the hardware, use one of the available Media Manager configuration interfaces to add the drives and robots to your Media Manager configuration.
Before You Start Before You Start Observe the following important points when performing the tasks described in this chapter: ◆ The VERITAS support web site (http://www.support.veritas.com) contains server platform compatibility information for a number of vendors and products (see the NetBackup Product > Compatibility area of the site). Verify that your server platform is supported before configuring devices.
Using the Passthru Driver ◆ Establishes a default tape driver operating mode. If the operator changes the default mode, NetBackup may be unable to correctly read and write tape media, resulting in data loss. In particular, never set MT_ST_ASYNC_WRITES, or MT_ST_SYSV to the value one. Never set MTSETBLK to a non-zero value. Do not interfere with the execution of make_scsi_dev at system boot (it is called by the S77netbackup startup script). See “Configuring SCSI Robotic Control Device Paths (2.
Configuring Robotic Controls ◆ By NetBackup and Storage Migrator for SAN error recovery. ◆ By NetBackup and Storage Migrator for Quantum SDLT performance optimization. ◆ By NetBackup and Storage Migrator for SCSI reserve/release. ◆ By the NetBackup device configuration GUIs to collect robot and drive information. ◆ To collect TapeAlert information from tape devices allowing support of functions such as tape drive cleaning. ◆ For WORM tape support.
Configuring Robotic Controls Configuring SCSI Robotic Control Device Paths (2.4 kernel) The binary /usr/openv/volmgr/bin/make_scsi_dev creates device files in the /dev/sg directory. The names of these files in this directory have the following format: hHOSTcCHANNELtTARGETlLUN Where: ◆ HOST is the host bus adaptor. ◆ CHANNEL is channel. ◆ TARGET is the target ID. ◆ LUN is the logical unit number.
Configuring Tape Drives Configuring Tape Drives To use SCSI tape drives, the following drivers must be configured in the kernel or loaded as modules: ▼ ◆ Standard SCSI driver ◆ SCSI-adaptor driver ◆ SCSI tape (st) driver ◆ Linux SCSI generic (sg) driver To create device entries (2.4 kernel) 1. Run mknod /dev/sgN c 21 N. N is a decimal number from 0 to 255. 2. Run make_scsi_dev. Adding Standard Tape Drives (2.4 kernel) make_scsi_dev creates device files in the /dev/st directory.
Verifying The Device Configuration Adding Standard Tape Drives (2.6 kernel) Tape devices have multiple device files. However, NetBackup uses only the /dev/nstX file where X is a decimal number from 0 to 127. Verifying The Device Configuration The file /proc/scsi/scsi shows all devices recognized by the SCSI driver.
Other Considerations (Advanced Topics) Since NetBackup uses only one minor number, you can modify the driver and support up to 128 tape devices. The st.
Utilities to Test SCSI Devices Set lpfc_check_cond_err to a value of zero. NetBackup is unable to mount tapes if this variable is left at a value of one. The use of the touch file /usr/openv/volmgr/AVRD_DEBUG on a system with the Emulex HBA driver may cause the system log (syslog) to contain many entries that look like the following. You can ignore these messages.
Command Summary Command Summary The following is a summary of commands that may be useful when configuring devices. See the appropriate sections of this chapter for examples of their usage. /sbin/lsmod List loaded modules. /sbin/modprobe Install loadable kernel modules. /usr/sbin/reboot Stop and restart the system. /bin/mknod /dev/sgN c 21 N Create SCSI generic device files. Where N is a decimal number from 0 to 255.
7 Microsoft Windows 2000, 2003 This chapter explains how to configure storage devices and install tape device drivers for use with Media Manager on a platform running Microsoft Windows.
Before You Start Before You Start Observe the following points when performing the configurations described in this chapter: ◆ The VERITAS support web site (http://www.support.veritas.com) contains server platform compatibility information for a number of vendors and products (see the NetBackup Product > Compatibility area of the site). Verify that your server platform is supported before configuring devices.
Installing Tape Device Drivers on 32 Bit Servers ▼ To use the Device Driver Installer wizard This wizard (located on the NetBackup CD) guides you through the installation of the latest device drivers. 1. Log in as Administrator on the server where you installed NetBackup. 2. Insert the NetBackup CD-ROM in the drive. On Windows systems with AutoPlay enabled for CD-ROM drives, the NetBackup installation browser starts automatically.
Installing Tape Device Drivers on 64 Bit Servers ▼ To obtain the latest tape device drivers Visit the VERITAS support web site. http://www.support.veritas.com Installing Tape Device Drivers on 64 Bit Servers VERITAS does not provide device drivers for 64 bit servers. Contact Microsoft or the tape drive vendor to obtain these drivers.
Index A E accessibility features xii ACS (see Automated Cartridge System) AIX (see RS6000) AL-PA destination ID, Sun4/SPARC 13 AT&T style close 16, 62 atdd driver, HP9000 64 Automated Cartridge System, Sun4/SPARC 6 editing the st.
optical disk HP9000 68 on RS6000 45 Sun4/SPARC 23 ovpass driver 30 I IBM RS6000 (see RS6000) install_ovpass script 30, 51 installing 32 bit tape device drivers, Windows 94 installing 64 bit tape device drivers, Windows 96 ioscan command, HP9000 70 K kernel changes HP Alpha 77 HP9000 66 P passthru driver (see SCSI) plug and play drivers, Windows 95 R rem_drv command, Sun4/SPARC 26 remove_ovpass command 31, 51 robotic controls SCSI on RS6000 32, 38 SCSI, HP Alpha 74 SCSI, HP9000 55 SCSI, Linux (2.
remove_ovpass 31 sg.install, Sun4/SPARC 8 sgscan 13, 17, 26 SCSI logical unit numbers, Sun4/SPARC 23 passthru driver on RS6000 30 Sun4/SPARC 7 robotic control HP Alpha 74 HP9000 55 Linux (2.4 kernel) 87 Linux (2.6 kernel) 87 on RS6000 32, 38 spt (SCSI passthru) driver, HP9000 60 SCSI reserve/release data integrity 3 disabling 3 enabling 66 scsi_command on RS6000 52 Sun4/SPARC 25, 26 sd driver, Sun4/SPARC 25 Seagate LTO, HP Alpha 77 semmnu 69 sg driver Linux 84 Sun4/SPARC 13 sg.
