Implementing IBM Tape in Linux and Windows

Transcription

1 Front cover Implementing IBM Tape in Linux and Windows How to set up tape drives and libraries New: Ultrium3 and WORM features Integration with popular backup products Charlotte Brooks Alv Jon Hovda Reena Master Abbe Woodcock ibm.com/redbooks

2

3 International Technical Support Organization Implementing IBM Tape in Linux and Windows October 2005 SG

4 Note: Before using this information and the product it supports, read the information in Notices on page xix. Fourth Edition (October 2005) This edition applies to IBM TotalStorage 3580 Tape Drive, IBM TotalStorage 3581 Tape Autoloader, IBM TotalStorage 3581 Tape Autoloader, IBM TotalStorage 3582 Tape Library, IBM TotalStorage 3583 Tape Library, IBM TotalStorage 3584 Tape Library, and IBM TotalStorage 3592 Tape Drive. Copyright International Business Machines Corporation 2002, 2003, 2004, All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ix Tables xvii Notices xix Trademarks xx Preface xxi The team that wrote this redbook xxi Become a published author xxiii Comments welcome xxiii Summary of changes xxv October 2005, Fourth Edition xxv July 2004, Third Edition xxv Part 1. Setting up IBM tape in Linux and Windows Chapter 1. Introduction to LTO on Linux and Windows LTO overview LTO Ultrium models IBM TotalStorage 3580 Tape Drive IBM TotalStorage 3581 Tape Autoloader IBM TotalStorage U Tape Autoloader IBM TotalStorage 3582 Tape Library IBM TotalStorage 3583 Tape Library IBM TotalStorage 3584 Tape Library Hardware and operating system platforms Hardware server platforms ISV storage management software Windows 2000/2003 connectivity Windows 2000/2003 SCSI direct attach Windows 2000/2003 Fibre Channel attachment Intel Linux connectivity Linux SCSI direct attach Determining the number of drives on a SCSI bus Host Bus Adapters and device drivers LVD or HVD LVD and HVD Why this is important? SCSI HD68 and VHDCI cable connectors Chapter 2. IBM LTO Tape Library sharing and partitioning Definitions Library sharing Homogenous drive sharing What should I use? Partitioning multi-path tape libraries Partitioning the IBM Partitioning the IBM Copyright IBM Corp. 2002, 2003, 2002, 2003, 2004, All rights reserved. iii

6 2.2.3 Partitioning the IBM 3584 (ALMS not enabled) Partitioning the IBM 3584 using the wizard (ALMS not enabled) Partitioning the IBM 3584 with the Operator panel (ALMS not enabled) ALMS Functional description Configuring ALMS Using ALMS Chapter 3. Basic IBM tape setup for Windows IBM tape installation overview Determine requirements Installing IBM tape device drivers for Windows Installing the medium changer device driver Installing the tape drive device driver Installing IBM tape device drivers for Windows Installing the medium changer device driver Installing the tape drive device driver Control Path Failover CPF driver installation using install.exe CPF driver installation using the CPF_install.doc Configuring control path failover in the library Verifying the IBM tape device installation Testing the library with NTUTIL Creating a library device table Testing the library with NTBACKUP Configuring tape and medium changer devices Deleting LTO devices Windows 200x SCSI adapter installation Windows 200x Fibre Channel HBA driver installation QLogic QLAxxxx HBA driver installation QLogic QLAxxxx HBA driver configuration Emulex LPxxxxx HBA driver installation Emulex HBA driver configuration Emulex LPxxxxx HBA driver removal IBM Tape Library Specialists IBM U Tape Library Specialist IBM 3582 Tape Library Specialist IBM 3583 Tape Library Specialist IBM 3584 Tape Library Specialist Updating library, drive, and RMU firmware Keeping up-to-date with drivers and firmware using My Support Check the installed firmware Upgrading RMU firmware using the IBM Tape Library Specialist Upgrading drive firmware using the IBM Tape Library Specialist Upgrading the drive firmware using LTO-TDX Chapter 4. Basic IBM tape setup for Linux Hardware and software requirements Installing library and tape device drivers Using native Linux device driver to configure IBM tape Identifying and activating the SCSI controller Kernel compilation and installation checklist Identifying and accessing the LTO device iv Implementing IBM Tape in Linux and Windows

7 4.3.4 The mtx utilities Identification and correct implementation of mt Module and kernel parameters for the Linux tape driver Working with user-defined block sizes Controlling hardware compression Alternative device file names in Linux Using IBM Tape Device Driver Installing the IBM tape device driver and utilities Creating a library device table Uninstalling the Ultrium device drivers and utilities Setting up control path failover on Linux Setting up data path failover on Linux Intel Linux Fibre Channel HBA installation QLogic Using IBM tape driver in Linux on zseries Use /etc/zfcp.conf file Modify the /etc/modules.conf file Dynamically attaching a tape device Chapter 5. SAN considerations SAN design considerations for IBM tape libraries What bandwidth do we need for FC tape? Multiple paths to tape drives Tape and disk on the same HBA Different SAN fabrics for disk and tape Zoning Some basic information about zoning Types of zoning Suggestion on zoning for tapes World Wide Names of FC Host Bus Adapter Persistent binding Persistent binding with a QLogic HBA Persistent binding with an Emulex HBA Connection type of IBM tapes Part 2. LTO libraries and backup software Chapter 6. Configuring RSM Removable Storage Manager RSM benefits Software support RSM implementation Enabling RSM Attaching the IBM RSM with a SAN Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux IBM Tivoli Storage Manager overview Tivoli Storage Manager commonly used terms Tivoli Storage Manager and tape library sharing Non-shared tape device with Tivoli Storage Manager for Windows Installing Tivoli Storage Manager Defining the library and drives using the Configuration Wizard Defining the library and drives using the command line Contents v

8 7.2.4 Defining the device class using the Configuration Wizard Defining the device class using the command line Defining the storage pool using the Configuration Wizard Defining the storage pool using the command line Inserting data and cleaning cartridges Non-shared tape device with Tivoli Storage Manager for Linux Performance hints for Tivoli Storage Manager, LTO, and LTO WORM (Write Once Read Many) Various IBM 3592 media types and Tivoli Storage Manager Sharing LTO libraries with Tivoli Storage Manager Configuring the Library Manager to share libraries Configuring the library client Define library and drives for library client Administering shared libraries LAN-free backup with Tivoli Storage Manager LAN-free configuration setup Define path considerations NDMP backup with Tivoli Storage Manager Network Attached Storage Overview of Tivoli Storage Manager NDMP backup Tivoli Storage Manager NDMP backup configurations Tivoli Storage Manager and redundant library control paths Tivoli Storage Manager and data path failover Tape alert support Device migration and coexistence Scenarios Tivoli Storage Manager V5.2 SAN device mapping SAN device mapping functions Chapter 8. Configuring EMC Legato NetWorker on Windows EMC Legato NetWorker overview EMC Legato NetWorker and IBM LTO interoperability NetWorker installation on Windows Installation preparation Software installation NetWorker library configuration NetWorker 6.1 library configuration of IBM NetWorker 7 library configuration of IBM Labeling cartridges Inventory Some additional settings NetWorker client backup Chapter 9. Configuring BakBone NetVault on Windows and Linux NetVault by BakBone Installing NetVault on Windows Installation preparation Installing NetVault Installing NetVault on Linux Installation preparation Installing NetVault Configuring NetVault Configuring the IBM vi Implementing IBM Tape in Linux and Windows

9 9.5 NetVault NDMP plug-in Installation of NDMP Client Chapter 10. Configuring Arkeia on Linux Arkeia from Knox Software Installing Arkeia Installation preparation Package installation Configuring the LTO library Part 3. Appendixes Appendix A. IBM SAN Data Gateway Connecting tape drives to a SDG WWN of SDG Getting the WWN of the SDG SAN Data Gateway setup Basic setup Install and use the SDG Specialist SDG LUN mapping Access control by channel zoning Access control by Virtual Private SAN (VPS) Appendix B. SNMP setup Simple Network Management Protocol (SNMP) alerts Configuring SNMP for the IBM Configuring SNMP for the IBM Configuring SNMP for the IBM Enable SNMP traps using the Operator panel Enable SNMP traps using Tape Library Specialist Enabling or disabling SNMP requests Appendix C. Additional information Rules for booting SAN Data Gateway and FC hosts Performance considerations Linux Windows Tivoli Storage Manager tape and tape library commands EMC Legato NetWorker autochanger maintenance commands Verifying device attachment with tapeutil or ntutil Linux tape and medium changer device attachment test Windows tape and medium changer device attachment test Using tapeutil element inventory (Linux) Using NTUTIL element inventory (Windows) Troubleshooting Collect real-time failure information Hints Related publications IBM Redbooks Other publications Online resources How to get IBM Redbooks Help from IBM Contents vii

10 Index viii Implementing IBM Tape in Linux and Windows

11 Figures 1-1 LTO Ultrium road map Ultrium generation media compatibility The LTO Ultrium product family IBM TotalStorage 3580 Tape Drive L1x, H1X, L23, and H IBM TotalStorage 3580 Tape Drive L33/L3H IBM TotalStorage 3581 Tape Autoloader IBM TotalStorage U Tape Autoloader IBM TotalStorage 3582 Tape Library IBM TotalStorage 3583 Tape Library IBM TotalStorage 3584 Tape Library Example of a 16-frame IBM Supported HBA and microcode (excerpt) Device data flow SCSI connectors IBM 3494 tape library sharing IBM multipath architecture and logical partitioning Tivoli Storage Manager library sharing LAN-free backup Library sharing done by TSM IBM 3582 partitioning IBM IBM 3583 Tape Library Specialist Operator panel IBM 3583 setting up partitioning IBM 3583 setting up partitioning IBM 3583 setting up partitioning IBM 3583 setting up partitioning IBM 3584 partitioning example IBM 3584 Specialist main screen IBM 3854 Tape Library Specialist Logical Libraries entry window IBM 3854 Tape Library Specialist configuration wizard Current physical configuration IBM 3584 Tape Library Specialist Logical Libraries IBM 3854 Tape Library Specialist drives and slots Rename logical library IBM 3584 Operator panel: Main Menu IBM 3584 Operator panel: configuration IBM 3584 configuration display IBM 3584 Operator panel: Set Logical Libraries IBM 3584 Operator panel: Set Storage Slots IBM 3584 Operator panel: Set Drives IBM 3584 Operator panel: Configuration Summary IBM 3584 with ALMS Welcome screen before enabling ALMS Enable ALMS Create Logical Library Create Logical Library Added new Logical Library Cartridge assignment policy main screen Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. ix

12 2-35 Cartridge Assignment Policy assignments Assign Data Cartridge menu Assign cartridge to a logical library Cartridge list Drive Assignment Drive with control path Drive details Display drive element number Drive gap warning Change maximum number of cartridges Logical Library details Detailed info before ALMS is enabled Detail Info after ALMS enabled Inventory before move medium Inventory after moving cartridge Performing a hardware scan Extracted device driver package contents Device Manager window: pre-configured The driver tab of the medium changer s properties box Device Driver Wizard install options Device driver location search options Specify a location Search results Device Driver Wizard completion Pre-configured tape drives in Device Manager The driver tab of the unconfigured tape drive s properties box Device Driver Wizard install options Device driver location search options Specify a location Search results Device Driver Wizard completion To install the version for RSM, select the check box Install one of the other drivers Choose the driver from the list Device Driver Wizard completion for clients that use RSM Performing a hardware scan Extracted device driver package contents Device Manager window: pre-configured The driver tab of the medium changer s properties box Device Driver Wizard install options Device Driver Wizard Install Search and Installation Options: search for driver Device Driver Wizard: no driver found Device Driver Wizard Install Search and Installation Options: choose driver Device Driver Wizard: specify location Device Driver Wizard: select driver Device Driver Wizard: warning Device Driver Wizard: upgrade complete Pre-configured tape drives in Device Manager The driver tab of the unconfigured tape drive s properties box Device Driver Wizard: install options Device Driver Wizard Install Search and Installation Options: search for driver Device Driver Wizard: select a driver Device Driver Wizard: warning Device Driver Wizard completion x Implementing IBM Tape in Linux and Windows

13 3-39 To install the version for RSM select the second driver listed Device manager with library installed Hardware scan install.exe in driver install directory Changer Bus Enumerator installation warning Driver installation certification warning Welcome window Add/Remove window Searching Wizard window Is hardware connected window Installed hardware window Hardware location window Hardware classes window System devices window Location of the inf file Changer Bus Enumerator found Verifying the install WHQL warning window Completing the Wizard window Device manager IBM 3582: Enable control paths IBM 3583: Enable control path IBM 3584: Enabling additional control paths without ALMS IBM 3584: Enabling additional control paths with ALMS enabled High availability control path configuration on an IBM Viewing IBM tape device in Device Manager Driver details Driver tab Driver File details Import media present message The NTBACKUP Backup tab The NTBACKUP Restore tab Disabling an IBM tape device The Services window Disabling RSM Accessing the Device Uninstall option Uninst.exe in extracted driver directory Executing uninst.exe Uninst.exe completed successfully Windows SCSI attached configuration System settings change Accessing SCSI controller properties Adaptec properties: Driver tab Upgrade Device Driver Wizard Device driver search options Device driver search location Device driver copy location Device driver search results Driver file search results Digital signature warning SANSurfer main window SANBlade Manager with HBA Configuring SAN devices Figures xi

14 3-92 Configured devices SAN device details SANSurfer Settings tab SANSurfer Advanced Adapter Settings Recommended MaximumSGList value Emulex Configuration Tool Disabling the Emulex HBA Configuration menu s NET PARAMETER command IBM 3581 Tape Library Login screen IBM U operation screen IBM U firmware update screen Operator panel: Configuring RMU IP address IBM 3582 Specialist welcome screen IBM 3582 Specialist: Configuration panel IBM 3582 Specialist: Diagnostics file panel IBM 3582 Specialist: Operator panel IBM 3583 Operator panel: Configuring RMU IBM 3583 Specialist: Welcome screen IBM 3583 Specialist: Configuration panel IBM 3583 Specialist: Diagnostics file panel IBM 3583 Specialist: Operator panel Change Ethernet parameters on IBM 3854 Specialist: Welcome page Specialist: Physical Library Summary panel IBM 3584 Specialist: Cartridges IBM 3584 Specialist: drive summary IBM 3584 Specialist: ID change warning IBM 3584 Specialist: Drive Assignment Filter IBM 3584 Specialist: Drive Assignment IBM 3584 Specialist: Assignment Change warning Change Password screen IBM 3584 Specialist: Check drive firmware version Tape Library Specialist: Updating RMU firmware LTO-TDX selection screen LTO-TDX selection screen LTO-TDX Selection screen LTO-TDX selection screen LTO-TDX selection screen Linux SCSI lab environment Kernel configuration main window Configuration for SCSI disk, tape, generic device support Kernel configuration for the Adaptec SCSI controller Typical zseries SAN SAN Bandwidth for tape Switch Management window Port performance Our lab configuration Device Manager Tape and disk on the same HBA SAN example for backup Zoning Zone to restrict the tapes to one HBA only IBM 3584 with 8 FC LTO Drives, 1 server with 2 HBA, 2 zones xii Implementing IBM Tape in Linux and Windows

15 5-11 WWN with QLogic SANSurfer SANSurfer Fibre Channel Port Configuration Set visible All devices visible Configuring LUN mapping Select target ID N-Port login SCSI lab environment Windows 2000 system services RSM Services properties Removable Storage administration RSM library RSM drives Preparing tapes Allocated media Registry changer key Tivoli Storage Manager supported platforms Tivoli Storage Manager library sharing overview Tivoli Storage Manager LAN-free data transfer overview Initializing the Tivoli Storage Manager server Initial configuration task list Tivoli Storage Manager Management Console Service Information Device Driver options Device Configuration Wizard Tivoli Storage Manager Device Driver start prompt Tivoli Storage Manager device selection Tivoli Storage Manager devices selected Choose recording format SCSI Element number of tape drives in the IBM SCSI Element number of tape drives in the IBM Checking the Tivoli Storage Manager device name in the Management Console Selection for Media Labeling Wizard Media Labeling Wizard Device selection for labeling Volume selection for labeling Media Labeling Monitor: volume selection for labeling Tivoli Storage Manager media check-in Media check-in issued How each of the SCALECAPACITY parameters initialize 3592 JA cartridges Library connected to NAS system Library on Tivoli Storage Manager server: drives on NAS system How version control works for NDMP backups IBM 3584 with multiple control paths enabled drive with multiple data paths configured Migration scenario Migrating to LTO as sequential primary copy Migrating to LTO through disk primary copy SCSI attach configuration NetWorker installation start window Install from the current location Select the NetWorker client and server software for installation Selection of additional servers is not required Figures xiii

16 8-6 Library view Display hidden attributes Set max parallelism Device View: Edit dummy device Edit Device: Disable dummy drive Device view with disabled dummy devices Device configuration Labeling cartridges Labeling in progress Display of cartridges after labeling Autochanger edit menu: Adjust the timer values Backup main window NetWorker client window with file selections for backup NetWorker Client during backup operation Windows 2000 direct SCSI configuration Windows 2000 SAN configuration Initial NetVault installation window License agreement Destination folder Database location Setup type Enter machine name NetVault password Linux lab environment NetVault Configurator Update/plug-in installation program Enter install file name Software identification window Primary NetVault interface (NetVault GUI) Device Management Select library server Selecting the library device Displaying library device Selecting library devices Selecting first device Identifying the tape device Selecting another drive bay Verify library and tape selections Completion of library addition Library status SAN lab environment Client Management Client Properties NetVault Backup Display backup properties Configuring NDMP server NetVault NDMP client NDMP backup request Linux Arkeia environment Server authentication Server administration window Server license Tape library license xiv Implementing IBM Tape in Linux and Windows

17 10-6 Adding a new library Library added Drives management Drive type selection Rewind device name Drive added Library drive associations Library drives Attaching drive Drive selection Library drive association A-1 Example of a connection with SDG A-2 WWN of the SDG A-3 Connected to the SDG A-4 Install of the SDG StorWatch Specialist A-5 SDG StorWatch connect to server A-6 SDG StorWatch logon A-7 Connect to SDG A-8 Install firmware on the SDG A-9 Select the SCSI option A-10 SCSI Channel parameters A-11 Select the Fibre Channel options A-12 Fibre Channel parameters A-13 Basic SCSI connection to a system A-14 SDG attached through Fibre Channel - Host view A-15 Select Device Mapping A-16 Device Mapping A-17 Select Channel Zoning A-18 Channel Zoning Settings B-1 IBM 3582 Tape Library Specialist: SNMP MIB download B-2 IBM 3582 Ultrium Tape Library Specialist: Configuring SNMP B-3 IBM 3583 Ultrium Tape Library Specialist: SNMP MIB download B-4 IBM 3583 Ultrium Tape Library Specialist: Configuring SNMP B-5 Tivoli NetView SNMP monitoring B Operator panel: Enable/disable SNMP Traps B Operator panel: V1/V2 traps B-8 IBM 3584 Operator panel: Destination IP address B-9 IBM 3584 Operator panel: Set destination IP address B-10 IBM 3584 Operator panel: Set community name B-11 IBM 3584 Specialist: Enabling SNMP B-12 IBM 3584 Specialist: SNMP destinations B-13 Tivoli NetView: Create new object B-14 NetView: Create new object B-15 NetView: Browse network segment B-16 NetView: SNMP traps B-17 NetView: Detail description of 3584 SNMP trap B-18 Enable SNMP request with IBM 3584 Specialist B-19 SNMP Request: Drive status B-20 SNMP request: Number of all physical cartridges B-21 SNMP request: List of all physical media C-1 IBM 3582 Ultrium Tape Library Specialist: Download logs C-2 IBM 3584 Ultrium Tape Library Specialist: Download logs Figures xv

18 xvi Implementing IBM Tape in Linux and Windows

19 Tables 1-1 IBM 3583 model capacities with Ultrium 2 tape drives IBM 3583 model capacities with Ultrium 3 tape drives IBM 3583-L18 and L36 library capacity with feature # IBM 3583-L72 library capacity IBM 3584 frame capacity with Ultrium 2 drives IBM 3584 frame capacity with Ultrium 3 drives LTO Windows 2000/2003 attachment summary Linux attachment HVD and LVD characteristics Library device table Types of password protection Firmware upload times via different methods Special device file names used with Linux Library device table How many tape drives can run concurrently on HBA or ISL PCI buses Library device table Configuring LAN-free backups LTO migration and coexistence examples A-1 Target ID and device mapping - Native SCSI A-2 Device map from host perspective with SDG C-1 Commonly used Tivoli Storage Manager tape commands C-2 NetWorker autochangers maintenance commands C-3 Library device table Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. xvii

20 xviii Implementing IBM Tape in Linux and Windows

21 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. xix

22 Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX AS/400 Eserver Eserver FICON IBM iseries Magstar Netfinity NetView OS/390 OS/400 pseries Redbooks Redbooks (logo) RS/6000 SANergy Tivoli TotalStorage xseries z/os zseries The following terms are trademarks of other companies: IPX, Java, RSM, Solaris, Sun, Ultra, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows server, Windows NT, Windows, Win32, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Itanium, Pentium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. xx Implementing IBM Tape in Linux and Windows

23 Preface This IBM Redbook follows IBM TotalStorage Tape Libraries Guide for Open Systems, SG , and will help you plan, install, and configure IBM Ultrium LTO tape drives, as well as the IBM 3592 tape drive and libraries with servers running Linux and Windows 2000/2003. This redbook focuses on the setup and customization of these drives and libraries in both direct-attached SCSI and SAN configurations. Part 1, Setting up IBM tape in Linux and Windows on page 1, describes how to attach and configure the drives and libraries, and covers basic installation and administration. It also covers the sharing and partitioning of libraries and explains the concept and usage of the Advanced Library Management System (ALMS) and virtual I/O with the IBM TotalStorage 3584 Tape Library. Part 2, LTO libraries and backup software on page 243, documents how to use these products with popular data backup applications, including IBM Tivoli Storage Manager, BakBone NetVault, Arkeia, and EMC Legato NetWorker. This redbook will help IBM personnel, Business Partners, and clients to better understand and implement the IBM Ultrium LTO product line and also the IBM 3592 tape drive in Windows and Linux environments. We assume that the reader is familiar with tape drives and libraries, and understands basic SAN concepts and technologies. The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center. Charlotte Brooks is a Certified IT Specialist and Project Leader for IBM TotalStorage solutions at the International Technical Support Organization, San Jose Center. She has 15 years of experience with IBM in the fields of IBM TotalStorage hardware and software and IBM ^ servers. She has written 12 Redbooks, and has developed and taught IBM classes in all areas of storage and storage management. Before joining the ITSO in 2000, she was the Technical Support Manager for Tivoli Storage Manager in the Asia Pacific Region. Alv Jon Hovda is a Senior IT Specialist with IBM Global Services in Norway. He has 35 years of experience with IBM, the last nine years working with Tivoli Storage Manager. He holds a Masters degree in Engineering Physics. He is Tivoli Storage Manager certified, and his areas of expertise include Tivoli Storage Manager and AIX. He has the author of two previous redbooks on Tivoli Storage Manager and IBM tape. Reena Master is a Field Technical Support Specialist in Atlanta, Georgia, supporting the storage sales team in the Southeast for the past four years. She has extensive experience in both high-end mainframe and open systems tape. Her daily support activities include pre- and post-sales support, including developing and presenting technical solutions and proposals and positioning IBM capabilities versus competitive offerings. She holds a Bachelor's degree in Civil Engineering and a Master's degree in Industrial Engineering. Abbe Woodcock is a Consulting IT Specialist with the Advanced Technical Support (ATS) tape team in the Americas. She joined IBM in 1974 as a Program Support Representative for DOS/VS systems, then moved to a CICS/VS Level 2 Support position. After positions in SPD Development and Field Engineering Service Planning, she was a Large Systems System Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. xxi

24 Engineer. She became a Certified IT Architect while working in IBM Global Services. Since joining the ATS, she has supported z/os tape products and now supports LTO tape products. Figure 1 The team: Alv Jon, Charlotte, Abbe, Reena Thanks to the following people for their contributions to this project: The authors of the previous editions of this book: Bertrand Dufrasne, Thomas Gaines, Carsten Krax, Michael Lohr, Takashi Makino, Tony Rynan, Josef Weingand, and Erwin Zwemmer. xxii Implementing IBM Tape in Linux and Windows

25 Wade Wallace and Emma Jacobs International Technical Support Organization Jennifer Bappert, Bill Baxter, Janet Bolton, Craig Bell, Kevin Cummings, Tommy De Jesus, Brett Dennis, Glen Jaquette, Lee Jesionowski, Yun Mou, Khanh Ngo, Anh Nguyen, Diem Nguyen, Steve Nunn, Debra Parker, Carla Ruhl, Ann Sargent, James Thompson, Dan Watanabe IBM tape development and marketing, Tucson Jeff Ziehm IBM Dallas Tony Abete IBM Chicago Become a published author Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners, and clients. Your efforts will help increase product acceptance and client satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability. Obtain more information about the residency program, browse the residency index, and apply online at: ibm.com/redbooks/residencies.html Comments welcome Your comments are important to us! We want our Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an Internet note to: [email protected] Mail your comments to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California Preface xxiii

26 xxiv Implementing IBM Tape in Linux and Windows

27 Summary of changes This section describes the technical changes made in this edition of the book and in previous editions. This edition may also include minor corrections and editorial changes that are not identified. Summary of Changes for SG for Implementing IBM Tape in Linux and Windows as created or updated on October 12, October 2005, Fourth Edition This revision reflects the addition, deletion, or modification of new and changed information described below. New information WORM media for Ultrium 3 drives Ultrium 3 drives and libraries Virtual I/O for IBM TotalStorage 3584 Tape Library July 2004, Third Edition This revision reflects the addition, deletion, or modification of new and changed information described below. New information New models, IBM TotalStorage U Tape Autoloader L28 and F28 New frames and features for the IBM TotalStorage 3584 Tape Library, including support for IBM TotalStorage 3592 Tape Drive with WORM media Setup and implementation information for the IBM TotalStorage 3592 Tape Drive Advanced Library Management System (ALMS) for the IBM 3584 Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. xxv

28 xxvi Implementing IBM Tape in Linux and Windows

29 Part 1 Part 1 Setting up IBM tape in Linux and Windows In this part, we introduce the IBM TotalStorage tape products (LTO Ultrium products and 3592 Enterprise Tape Drive) and describe how to set them up in Windows 2000 and Linux environments. Both native SCSI and SAN (Fibre Channel) attachments are presented. We also show how to use the administration tools, such as the IBM TotalStorage Tape Library Specialist. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 1

30 2 Implementing IBM Tape in Linux and Windows

31 1 Chapter 1. Introduction to LTO on Linux and Windows This chapter provides an overview of the Linear Tape-Open (LTO) initiative and the corresponding IBM TotalStorage LTO Ultrium product line, including the IBM TotalStorage 3592 Tape Drive. This includes: An overview of the IBM LTO models available: IBM TotalStorage 3580 Tape Drive IBM TotalStorage 3581 Tape Autoloader IBM TotalStorage U Tape Autoloader IBM TotalStorage 3582 Tape Library IBM TotalStorage 3583 Tape Library IBM TotalStorage 3584 Tape Library Server and operating system platforms, and storage management software Connectivity examples, such as: Direct SCSI attachment SCSI bus performance HBAs and drivers discussion LVD versus HVD discussion HD68 versus VHDCI discussion Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 3

32 1.1 LTO overview The Linear Tape-Open (LTO) program is a joint initiative of Hewlett-Packard, IBM, and Seagate Technology. In 1997, the three companies set out to enable the development of best-of-breed tape storage products by consolidating state-of-the-art technologies from numerous sources. The three companies also took steps to protect client investment by providing a four-generation road map and establishing an infrastructure to enable compatibility between competitive products. The LTO technology objective was to establish new open-format specifications for high capacity, high performance tape storage products for use in the midrange and network server computing environments, and to enable superior tape product options. LTO program cooperation goes beyond the initial three companies. LTO format specifications have been made available to all who want to participate through standard licensing provisions. LTO program technology has already attracted a number of other industry leaders, so that LTO-specified products (tape drives and tape storage cartridges) will reach the market from multiple manufacturers, not just the Technology Provider Companies. This is critical to meeting an open market objective, and is accomplished through open licensing of the technology. Cooperation is also evident in the LTO program requirement that all products produced by licensees be technically certified annually. The primary objective of this certification is to help determine whether LTO format cartridges will be exchangeable across drives produced by different Ultrium manufacturers. In other words, LTO compliant media from any vendor can be read and written in LTO compliant drives from any vendor. All three consortium members (IBM, HP, and Seagate) are now shipping LTO Ultrium products, and numerous other licensees are shipping hardware and media. The Linear Tape-Open organization home page is: For more information about LTO technology, see IBM TotalStorage Tape Libraries Guide for Open Systems, SG The IBM LTO home page is: The LTO Ultrium road map (Figure 1-1 on page 5) shows the evolution of LTO technology. At the time of writing, IBM Ultrium generation 2 and 3 products are offered; however, there are many existing installations of now-withdrawn Ultrium 1 products, so we also include them for your reference. The information in the road map is given as an indication of future developments by the three consortium members, and is subject to change. Important: Hewlett-Packard, IBM, and Seagate reserve the right to change the information in this migration path without notice. 4 Implementing IBM Tape in Linux and Windows

33 LTO Ultrium Road Map Generation 1 Generation 2 Generation 3 Generation 4 Generation 5 Generation 6 Capacity (Native) 100GB 200GB 400GB 800GB 1.6 TB 3.2 TB Transfer Rate (Native) Up to 20MB/s Up to 40MB/s Up to 80MB/s Up to 120MB/s Up to 180MB/s Up to 270MB/s WORM No No Yes Yes Yes Yes Figure 1-1 LTO Ultrium road map LTO Ultrium models The IBM TotalStorage LTO Ultrium family consists of: IBM TotalStorage 3580 Tape Drive IBM TotalStorage 3581 Tape Autoloader IBM TotalStorage U Tape Autoloader IBM TotalStorage 3582 Tape Library IBM TotalStorage 3583 Tape Library IBM TotalStorage 3584 Tape Library These are shown in Figure 1-3 on page 7. Some existing models have three drive options: Ultrium 1, Ultrium 2, and Ultrium 3. More recent models are available with Ultrium 2 and Ultrium 3 drives only. IBM Ultrium 1 drives were withdrawn from marketing in October Ultrium 1 was the first generation of the LTO Ultrium technology with a tape capacity of 100 GB per cartridge in a native format, and capacity of 200 GB using 2:1 compression. Ultrium 2 is the second generation of the LTO Ultrium technology with a tape capacity of 200 GB per cartridge in native format, and capacity of 400 GB using 2:1 compression. Ultrium 3 is the third generation of the LTO Ultrium technology with a tape capacity of 400 GB per cartridge in native format, and capacity of 800 GB using 2:1 compression. A WORM (write-once, read-many) version of the Ultrium 3 cartridge is also available. Chapter 1. Introduction to LTO on Linux and Windows 5

34 Media compatibility Figure 1-2 depicts the media compatibility characteristics for the three generations of Ultrium tape. IBM Ultrium 1,2, 3 and 3 WORM Compatibility Ultrium 1 Cartridge Up to 15 MB/s, 100 GB* IBM Ultrium 1 Tape Drive 20 MB/s, 100 GB* xxxxxxl1 Read/write Ultrium 1 format up to 20 MB/s, 100 GB* Ultrium 2 Cartridge Up to 35 MB/s, 200 GB* IBM Ultrium 2 Tape Drive Up to 35 MB/s, 200 GB* xxxxxxl2 Ultrium 3 Cartridge xxxxxxl3 -OR- Ultrium 3 WORM Cartridge xxxxxxlt Read Ultrium 1 format Up to 80 MB/s, 400 GB* Read/write Ultrium 2 format Silver-grey bottom Ultrium 2 Logo IBM Ultrium 3 Tape Drive in 3580, 3581, 3582, 3583, 3584 Ultrium 3 Logo * Native sustained data rate, native physical capacity Figure 1-2 Ultrium generation media compatibility Ultrium 1 The Ultrium 1 Tape Drive is not compatible with (cannot read or write) the cartridges of its successors, the Ultrium 2 and Ultrium 3 Tape Drive. Cartridge compatibility for the Ultrium 1 Tape Drive is as follows: Reads and writes Ultrium 1 format on Ultrium 1 cartridges Ultrium 2 The Ultrium 2 Tape Drive is compatible with the cartridges of its predecessor, the Ultrium 1 Tape Drive. Cartridge compatibility for the Ultrium 2 Tape Drive is as follows: Reads and writes Ultrium 2 format on Ultrium 2 cartridges Reads and writes Ultrium 1 format on Ultrium 1 cartridges Does not write Ultrium 2 format on Ultrium 1 cartridges Does not write Ultrium 1 format on Ultrium 2 cartridges Ultrium 3 The Ultrium 3 Tape Drive is compatible with the cartridges of its predecessors, the Ultrium 2 and Ultrium 1 Tape Drive. Cartridge compatibility for the Ultrium 3 Tape Drive is as follows: Reads and writes Ultrium 3 format on Ultrium 3 cartridges Reads and writes Ultrium 2 format on Ultrium 2 cartridges Reads Ultrium 1 format on Ultrium 1 cartridges Does not write Ultrium 3 format on Ultrium 2 cartridges Does not write Ultrium 2 format on Ultrium 3 cartridges 6 Implementing IBM Tape in Linux and Windows

35 WORM tape format Beginning with LTO Ultrium 3, Write Once Read Many (WORM) functionality provides for non-erasable, non-rewritable operation with tape media and is designed for long term tamper resistant record retention The LTO Ultrium 3 specification for WORM includes the use of low level encoding in the Cartridge Memory (CM), which is also mastered into the servo pattern as part of the manufacturing process. This encoding is designed to prevent tampering. Data can be appended at the end of a WORM cartridge to which data was previously written, allowing the full use of the high capacity tape media. LTO Ultrium 3 WORM cartridges can be used with any LTO Ultrium 3 tape drive with the appropriate microcode and firmware. LTO Ultrium 3 non-worm enabled and WORM enabled drives can coexist in the same library. Figure 1-3 The LTO Ultrium product family IBM TotalStorage 3580 Tape Drive The IBM TotalStorage 3580 Tape Drive (abbreviated to IBM 3580) is an external, stand-alone, SCSI-attached tape drive that attaches to a variety of server and operating system platforms (see 1.2.1, Hardware server platforms on page 28). The IBM 3580 can also connect to Fibre Channel server Host Bus Adapters through the IBM SAN Data Gateway Routers models 2108-R03 or 2108-G07. Chapter 1. Introduction to LTO on Linux and Windows 7

36 Note: The IBM SAN Data Gateway Router models 2108-R03 and 2108-G07 were withdrawn from marketing in December The IBM 3580 is available as four separate model types, depending on the Ultrium format and SCSI interface. IBM 3580-L23 has an Ultrium 2 drive and a Low-Voltage Differential (LVD) Ultra2 SCSI attachment that connects to LVD fast/wide adapters. IBM 3580-H23 has an Ultrium 2 drive and a High-Voltage Differential (HVD) Ultra SCSI attachment that connects to HVD fast/wide adapters. IBM 3580-L33 and IBM 3580-L3H have an Ultrium 3 drive and a Low-Voltage Differential (LVD) Ultra SCSI attachment that connects to LVD fast/wide adapters. The IBM 3580-L33 and IBM 3580-L3H are functionally identical; the only difference is the IBM 3580-L3H is an Express Model, which is part of the On-Demand Express Portfolio. The four previously available model types are: IBM 3580-L11 and IBM 3580-L13 have an Ultrium 1 drive and a Low-Voltage Differential (LVD) Ultra2 SCSI attachment that connects to LVD fast/wide adapters. IBM 3580-H11 and IBM 3580-H13 have an Ultrium 1 drive and a High-Voltage Differential (HVD) Ultra SCSI attachment that connects to HVD fast/wide adapters. The IBM 3580-L11 and IBM 3580-L13 are functionally identical; the only difference is that the IBM 3580-L13 has a three-year Customer Element Exchange warranty. The IBM 3580-H11 and IBM 3580-H13 are functionally identical; the only difference is that the IBM 3580-H13 has a three year Customer Element Exchange warranty. Note: The IBM 3580-L11 and IBM 3580-L13 were withdrawn from marketing in July 2004 and the replacement products are the IBM 3580-L23, IBM 3580-L33, and IBM 3580-L3H. The IBM 3580-H11 and IBM 3580-H13 were withdrawn from marketing in January 2005, and the replacement products are the IBM 3580-H23, IBM 3580-L33, and IBM 3580-L3H. Figure 1-4 shows the IBM 3580-L1x, H1X, L23, and H23, and Figure 1-5 on page 9 shows the IBM 3580-L33/L3H. Figure 1-4 IBM TotalStorage 3580 Tape Drive L1x, H1X, L23, and H23 8 Implementing IBM Tape in Linux and Windows

37 Figure 1-5 IBM TotalStorage 3580 Tape Drive L33/L3H IBM TotalStorage 3581 Tape Autoloader Note: All models of the IBM TotalStorage 3581 Tape Autoloader (IBM 3581-L17/H17, IBM 3581-L13/H13, and IBM 3581-L23/H23) were withdrawn from marketing in October The replacement is the IBM TotalStorage U Tape Autoloader Model L28; see 1.1.4, IBM TotalStorage U Tape Autoloader on page 10. The IBM TotalStorage 3581 Tape Autoloader (abbreviated to IBM 3581) is an external, stand-alone or rack-mounted autoloader that can incorporate an IBM Ultrium 1 or Ultrium 2 tape drive. It attaches to a variety of server and operating system platforms (See 1.2.1, Hardware server platforms on page 28). The IBM 3581 capacity with Ultrium 1 drives is seven tape cartridges, providing a media capacity of up to 700 GB (1.4 TB with 2:1 compression) data storage per library, and a sustained data rate of up to 15 MB per second (uncompressed). The IBM 3581 capacity with Ultrium 2 drives is seven tape cartridges, providing a media capacity of up to 1.4 TB (2.8 TB with 2:1 compression) data storage per library, and a sustained data rate of up to 35 MB per second (uncompressed). The six model types are: IBM 3581-L17 has an Ultrium 1 drive and a LVD Ultra2 SCSI attachment. IBM 3581-L13 has an Ultrium 1 drive and a LVD Ultra2 SCSI attachment and comes with a three-year Customer Element Warranty. IBM 3581-L23 has an Ultrium 2 drive and LVD Ultra2 SCSI attachment and comes with a three-year Customer Element Warranty. IBM 3581 H-17 has an Ultrium 1 drive and a HVD Ultra SCSI attachment. IBM 3581 H-13 has an Ultrium 1 drive and a HVD Ultra SCSI attachment and comes with a three-year Customer Element Warranty. IBM 3581 H-23 has an Ultrium 2 drive and a HVD Ultra SCSI attachment and comes with a three-year Customer Element Warranty. Figure 1-6 on page 10 shows the IBM Chapter 1. Introduction to LTO on Linux and Windows 9

38 Figure 1-6 IBM TotalStorage 3581 Tape Autoloader IBM TotalStorage U Tape Autoloader The IBM TotalStorage U Tape Autoloader (abbreviated to IBM U) is a desktop or rack-mountable unit (requiring two rack units, thus 2U ) that operates in automatic, sequential, or random mode and comes equipped with a robotic interface that moves tape cartridges to and from the drive and cartridge carousel. The IBM TotalStorage U Tape Autoloader attaches to a variety of server and operating system platforms (See 1.2.1, Hardware server platforms on page 28). The IBM U uses the IBM Ultrium 2 and Ultrium 3 drives for fast data transfer and reliability in automated library services. The Ultrium 2 cartridge has a native capacity of 200 GB. The Ultrium 3 cartridge has a native capacity of 400 GB. The IBM U has an eight-cartridge capacity. With an IBM Ultrium 2 drive, the native media capacity is 1.6 TB (3.2 TB with 2:1 compression) with a sustained data rate up to 35 MB/sec (uncompressed). With an IBM Ultrium 3 drive, the native media capacity is 3.2 TB (6.4 TB with 2:1 compression) with a sustained data rate up to 80 MB/sec (uncompressed) with Ultrium 3 media. The IBM U s robotic system includes an I/O door, a cartridge carousel with eight cartridge slots, and a cartridge loader. The I/O door allows the importing or exporting of a single cartridge to or from the Autoloader. The cartridge carousel encircles the Ultrium 2 or 3 drive and positions the specified cartridge slot in front of the tape drive. A robotic cartridge loader moves the cartridges between the cartridge slots and the tape drive. The four models of the IBM U are: The IBM TotalStorage U Tape Autoloader Model L28 The IBM 3581-L28 has an Ultrium 2 drive and a Low-Voltage Differential (LVD) Ultra 160 SCSI attachment that connects to LVD fast/wide adapters. Using the optional High-Voltage Differential (HVD) converter (feature #3104), a SCSI LVD to HVD converter/expander converts the Autoloader s low voltage differential (LVD) to wide high voltage differential (HVD). 10 Implementing IBM Tape in Linux and Windows

39 The IBM TotalStorage U Tape Autoloader Model F28 The IBM 3581-F28 has an Ultrium 2 drive and a 2 Gbps native switched fabric Fibre Channel attachment. The IBM TotalStorage U Tape Autoloader Model L38/L3H The IBM 3581-L38 has an Ultrium 3 drive and a Low-Voltage Differential (LVD) Ultra 160 SCSI attachment that connects to LVD fast/wide adapters. The IBM TotalStorage U Tape Autoloader Model F38/F3H The IBM 3581-F38 has an Ultrium 3 drive and a 2 Gbps Native Switched Fabric Fibre Channel attachment. The IBM 3581-L38 and IBM 3581-L3H are functionally identical. The IBM 3581-F38 and IBM 3581-F3H are functionally identical.the only difference is the IBM 3580-L3H and IBM 3581-F3H are Express Models and are part of the On-Demand Express Portfolio. Remote Management Unit Available as an optional feature, a Remote Management Unit (RMU) provides an Ethernet port, so that the library can be configured as a TCP/IP device in the network. Library status can be sent to the network as Simple Network Management Protocol (SNMP) traps. The IBM Ultrium Tape Library Specialist enables network access (via Web browser) to the library for more detailed status and for updating the firmware of the library. All library Operator panel functions can be accessed using the IBM Ultrium Tape Library Specialist. Figure 1-7 shows the IBM U. Figure 1-7 IBM TotalStorage U Tape Autoloader IBM TotalStorage 3582 Tape Library The IBM TotalStorage 3582 Tape Library (abbreviated to IBM 3582) is an entry-level tape library that can accommodate one or two Ultrium 2 or Ultrium 3 drives. Designed for tape automation, the IBM 3582 attaches to a variety of server and operating system platforms (See 1.2.1, Hardware server platforms on page 28). The IBM 3582 has one model, the 3582-L28. The IBM 3582 uses the IBM Ultrium 2 and Ultrium 3 tape drives for fast data transfer and reliability in automated library service. The Ultrium 2 cartridge has a native capacity of 200 GB. The Ultrium 3 cartridge has a native capacity of 400 GB. Each aspect of the library subsystem has been designed for repeated, reliable unattended tape handling. The tape handling mechanism is designed to reliably move cartridges to IBM Chapter 1. Introduction to LTO on Linux and Windows 11

40 Ultrium Tape Drives within the library. The IBM Ultrium tape cartridges have been refined using the many years of IBM tape experience to provide a tape cartridge that provides fast data transfer, but stands up to the rigors of automated handling. The IBM 3582 is designed for easy expansion. It has a one-cartridge Import/Export station and 22 data cartridge slots. With Ultrium 2 drives and media, the IBM 3582 provides a media capacity of up to 4.8 TB (9.6 TB with 2:1 compression) and a sustained data rate of up to 35 MB per second (uncompressed). With Ultrium 3 drives and media, the IBM 3582 provides a media capacity of up to 9.6 TB (19.2 TB with 2:1 compression) and a sustained data rate of up to 80 MB per second (uncompressed). The IBM 3582 comes standard with multi-path architecture, which allows the sharing of the library robotics. This allows the IBM 3582 to be partitioned into one to two logical libraries, providing each library with its own control path, drives, and storage slots. The Import/Export station (slot) is shared among each logical library on a first come, first served basis. The cartridges under library control are not shared among the logical libraries. This feature will enable up to two heterogeneous applications to manage a single physical library. The tape library Import/Export (I/O) station allows cartridges to be inserted and removed without disrupting library operation. The are two I/O station options: A single import/export slot option to load or remove single tapes Two 7-slot magazines to perform bulk load and unloads A Bar Code Reader is standard for reading data cartridge labels, although the library can function with unlabeled cartridges. The IBM 3582 with Ultrium 2 and Ultrium 3 drives supports SCSI HVD, SCSI LVD and native Fibre Channel connected Ultrium 2 or Ultrium 3 drives. The direct attached SCSI drives may be any mixture of SCSI LVD, SCSI HVD, or Fibre Channel up to a total of two drives. Control path failover For enhanced availability you can use control path failover. This optional feature provides automatic control path failover to a preconfigured redundant control path in the event of a loss of a host adapter or control path drive, without aborting the current job in progress. Support is provided under AIX, Linux, HP-UX, Windows, and Solaris for both SCSI and Fibre Channel attachments when the IBM tape device drive is used. Data path failover and load balancing Data path failover and load balancing exclusively support native Fibre Channel Ultrium 2 and Ultrium 3 Tape Drives in a IBM 3582 library using the IBM tape device driver for AIX, Linux, and Solaris. Note: Load balancing is not supported on Solaris. Data path failover provides a failover mechanism in the IBM device driver, which enables you to configure multiple redundant paths in a SAN environment. In the event of a path or component failure, the failover mechanism is designed to automatically provide error recovery to retry the current operation using an alternate, preconfigured path without aborting the current job in progress. This allows you flexibility in SAN configuration, availability, and management. When accessing a tape drive device that has been configured with alternate pathing across multiple host ports, the IBM device driver automatically selects a path through the host bus adapter (HBA) that has the fewest open tape devices, and assigns that path to the application. This autonomic self-optimizing capability is called load balancing. The dynamic load balancing support is designed to optimize resources for devices that have physical connections to multiple HBAs in the same machine. The device driver is designed to dynamically track the usage on each HBA as applications open and close devices, and balance the number of applications using each HBA in the machine. This may help optimize 12 Implementing IBM Tape in Linux and Windows

41 HBA resources and improve overall performance. Further, data path failover provides autonomic self-healing capabilities similar to control path failover, with transparent failover to an alternate data path in the event of a failure in the primary host-side path. Data path failover and load balancing for Ultrium 3 Tape drives in all supported operating environments require an optional feature 1681 and the control path failover feature code Data path failover and load balancing for Ultrium 2 Tape drives in an AIX environment require the control path failover feature 1680 but do not require an optional feature; in non-aix environments, the control path failover feature 1680 and an RPQ are required. Remote Management Unit Available as an optional feature, a Remote Management Unit (RMU) provides an Ethernet port, so that the library can be configured as a TCP/IP device in the network. Library status can be sent to the network as Simple Network Management Protocol (SNMP) traps. The IBM Ultrium Tape Library Specialist enables network access (via Web browser) to the library for more detailed status and control. All library Operator panel functions can be accessed using the IBM Ultrium Tape Library Specialist. Note: The RMU is required when Fibre Channel drives are installed. Figure 1-8 shows the IBM Figure 1-8 IBM TotalStorage 3582 Tape Library IBM TotalStorage 3583 Tape Library The IBM TotalStorage 3583 Tape Library (abbreviated to IBM 3583) is a high-performance, reliable, and scalable tape subsystem. Designed for tape automation, the IBM 3583 attaches to a variety of server and operating system platforms (See 1.2.1, Hardware server platforms on page 28). The IBM 3583 can contain IBM Ultrium 1 (no longer available), Ultrium 2, or Ultrium 3 tape drives for fast data transfer and reliability in automated library service. The Ultrium 2 cartridge holds 200 GB. The Ultrium 3 cartridge holds 400 GB. Chapter 1. Introduction to LTO on Linux and Windows 13

42 With Ultrium 2 drives and media, the IBM 3583 library provides a sustained data rate of up to 35 MB per second (uncompressed). With Ultrium 3 drives and media, the IBM 3583 provides a sustained data rate of up to 80 MB per second (uncompressed). With Ultrium 1 drives and media, the IBM 3583 provides a sustained data rate of up to 20 MB per second (uncompressed). Each aspect of the library subsystem has been designed for repeated, reliable, and unattended tape handling. The tape handling mechanism is designed to reliably move cartridges to IBM Ultrium Tape Drives within the library. The IBM Ultrium tape cartridges have been refined using the many years of IBM tape experience to provide a tape cartridge that provides fast data transfer, but stands up to the rigors of automated handling. The tape library is designed for easy expansion. It can accommodate from one to six tape drives and from 18 to 72 cartridges. There are three Library Models: L18, L36, and L72. The cartridge capacities of the models are: IBM 3583-L18: 18 cartridges IBM 3583-L36: 36 cartridges IBM 3583-L72: 72 cartridges The IBM 3580-L18 and IBM 3580-L36 can be field upgraded to hold 72 cartridges. Cartridge expansion is in increments of 18 cartridges. One IBM Ultrium drive is required and five additional drives are available for factory or field installation. Upgrade features are modular units that are easy to install. Table 1-1 and Table 1-2 show the storage capacity of the IBM 3583 Library models with Ultrium 2 and Ultrium 3 tape drives. Table 1-1 IBM 3583 model capacities with Ultrium 2 tape drives Model Cartridge slots Data capacity (native) L18 L36 L72 18 a 36 b 72 c a. Plus one (1) I/O station slot b. Plus one (1) I/O station slot c. Including twelve (12) I/O Station slots Table 1-2 IBM 3583 model capacities with Ultrium 3 tape drives Model Cartridge slots Data capacity (native) L18 L36 L72 18 a 36 b 72 c a. Plus one (1) I/O station slot b. Plus one (1) I/O station slot c. Including twelve (12) I/O Station slots Data capacity (compressed) 3.6 TB 7.2 TB TB 12.8 TB TB 28.8 TB 1 6 Data capacity (compressed) 7.2 TB 14.4 TB TB 28.8 TB TB 57.6 TB 1-6 IBM Ultrium Tape Drives IBM Ultrium Tape Drives 14 Implementing IBM Tape in Linux and Windows

43 The tape library input/output (I/O) station enables cartridges to be inserted and removed without disrupting library operation. The IBM 3583 comes standard with a one-cartridge I/O station on the 3583-L18 and L36, or a 12-cartridge I/O station on the IBM 3583-L72. The IBM 3583-L18 and L36 can be upgraded to a 12-cartridge I/O station with an optional feature (#8012). The I/O station can be defined as I/O slots or data storage and the definition affects the number of cartridges available for data storage. Refer to Table 1-3 and Table 1-4 for the various combinations and resulting cartridge storage capacities. Table 1-3 IBM 3583-L18 and L36 library capacity with feature #8012 Model Slots without FC 8012 Slots w/ FC 8012 Defined as Storage Slots w/ FC 8012 Defined as I/O Slots L18 Storage: 18 I/O: 1 Storage: 36 I/O: 0 Storage: 24 I/O: 12 L18 with one FC 8007 (18-slot option) Storage: 36 I/O: 1 Storage: 54 I/O: 0 Storage: 42 I/O: 12 L18 with two FC 8007 (18-slot option) Storage: 54 I/O: 1 Storage: 72 I/O: 0 Storage: 60 I/O: 12 L36 Storage: 36 I/O: 1 Storage: 54 I/O: 0 Storage: 42 I/O: 12 L36 with one FC 8007 (18-slot option) Storage: 54 I/O: 1 Storage: 72 I/O: 0 Storage: 60 I/O: 12 Table 1-4 IBM 3583-L72 library capacity I/O door definition Slots L72 with I/O door defined as storage Storage: 72 I/O: 0 L72 with I/O door defined as I/O Storage: 60 I/O: 12 IBM 3583 with Ultrium 1 Note: LTO Ultrium 1 drives and the SAN Data Gateway Integrated Module were withdrawn from marketing in October Native Fibre Channel Ultrium 2 and Ultrium 3 drives are available. The IBM 3583 with Ultrium 1 drives allows a mixture of up to six direct attached SCSI LVD or HVD drives. If you are using the integrated SAN Data Gateway to enable FC connectivity, then up to six LVD or HVD drives can be installed. The SAN Data Gateway Integrated Module cannot support a mixture of HVD and LVD drives. The capacity of the IBM 3583 models with Ultrium 1 tape drives is one-half of the capacity with Ultrium 2 tape drives, as shown in Table 1-1 on page 14. The SAN Data Gateway Integrated Module is a chargeable library feature. The gateway provides the ability for SCSI devices in the library to connect into a SAN infrastructure. The gateway can run at either 1 Gbps or 2 Gbps port speeds, providing compatibility for older (1 Gbps) devices, as well as support for higher speed devices. Two Fibre Channel ports make multiple attachments easy and support failover redundancy. The Gateway has two Fibre Channel interfaces or ports and four SCSI interfaces or ports. The Fibre Channel ports are Chapter 1. Introduction to LTO on Linux and Windows 15

44 equipped with 2 Gigabit, SC-style shortwave multimode Gigabit Interface Converter (GBIC) modules. The Fibre Channel ports are capable of communicating reliably at distances of up to 300 m, over 50 µm multimode-optical fiber cables. The four SCSI ports are Ultra2, low voltage differential (LVD), with VHDCI-style connectors (Very High Density Cable Interconnect), so be sure to order the LVD version of the LTO drive. IBM 3583 with Ultrium 2 The IBM 3583 with Ultrium 2 drives supports SCSI HVD, SCSI LVD, and native FC connected Ultrium 2 drives. The drives may be any mixture of SCSI LVD, SCSI HVD, or FC up to a total of six drives. The FC drives are native switched fabric 2 Gbps Fibre Channel LTO Ultrium 2 Drives that can be directly attached to a host or a switch. IBM 3583 with Ultrium 3 The IBM 3583 with Ultrium 3 drives supports SCSI LVD and native FC connected Ultrium 3 drives. The drives may be any mixture of SCSI LVD or FC up to a total of six drives. The FC drives are native switched fabric 2 Gbps Fibre Channel LTO Ultrium 3 Drives that can be directly attached to a host or a switch. Multi-path support The patented multi-path support feature of the IBM 3583 supports sharing of the library robotics. This is accomplished by partitioning the library into up to three multiple logical libraries and providing each logical library its own separate and distinct drives, storage slots, and control paths. Note: An 18-slot storage column needs to be dedicated to each logical partition. I/O slots are shared on a first come, first served basis. This type of partitioning allows heterogeneous applications to share the library robotics independent of each other. Cartridges under library control are not shared between logical libraries nor allowed to be moved between logical libraries. An example of heterogeneous sharing is a Microsoft Windows 2000 application using the drive and storage slots of one logical library while a UNIX application uses the drive and slots of another logical library. Logical libraries can also be used for separating different generations of Ultrium Tape Drives and cartridges for applications that do not support mixing the drives in the same logical library. Support for multi-path architecture and partitioning may require an updated microcode level. Download the latest microcode from either of these Web sites: ftp://ftp.software.ibm.com/storage/358x/3583/ Control path failover For enhanced availability, you may use control path failover. This optional feature provides automatic control path failover to a preconfigured redundant control path in the event of a loss of a host adapter or control path drive, without aborting the current job in progress. Support is provided under AIX, Linux, HP-UX, Windows, and Solaris for both SCSI and Fibre Channel attachments when the IBM tape device driver is used. 16 Implementing IBM Tape in Linux and Windows

45 Data path failover and load balancing Data path failover exclusively supports native Fibre Channel Ultrium 3 or Ultrium 2 drives in the IBM 3583 using the IBM tape device driver for AIX, Linux, and Solaris. Load balancing exclusively supports native Fibre Channel Ultrium 3 or Ultrium 2 drives in the IBM 3583 using the IBM tape device driver for AIX and Linux (it is not supported for Solaris). Data path failover provides a failover mechanism in the IBM device driver, so that you can configure multiple redundant paths in a SAN environment. If a path or component fails, the failover mechanism is designed to automatically provide error recovery to retry the current operation using an alternate, preconfigured path without aborting the current job in progress. This allows you flexibility in SAN configuration, availability, and management. When accessing a tape drive device that has been configured with alternate pathing across multiple host ports, the IBM device driver automatically selects a path through the host bus adapter (HBA) that has the fewest open tape devices, and assigns that path to the application. This autonomic self-optimizing capability is called load balancing. The dynamic load balancing support is designed to optimize resources for devices that have physical connections to multiple HBAs in the same machine. The device driver is designed to dynamically track the usage on each HBA as applications open and close devices, and balance the number of applications using each HBA in the machine. This may help optimize HBA resources and improve overall performance. Further, data path failover provides autonomic self-healing capabilities similar to control path failover, with transparent failover to an alternate data path in the event of a failure in the primary host-side path. Data path failover and load balancing for Ultrium 3 drives in all supported operating environments requires optional feature code 1681 and the control path failover feature code Data path failover and load balancing for Ultrium 2 drives in an AIX environment requires the control path failover feature code 1680 but do not require the optional feature code 1681; in non-aix environments, the control path failover feature code 1680 and an RPQ are required. Remote Management Unit A Remote Management Unit (RMU) comes standard in every IBM The RMU provides an Ethernet port, so that the library can be configured as a TCP/IP device in the network. The library status can be sent to the network as Simple Network Management Protocol (SNMP) traps. The TotalStorage Ultrium Specialist enables network access (via Web browser) to the library for more detailed status and control. All library Operator panel functions can be accessed using the IBM Ultrium Tape Library Specialist. Figure 1-9 on page 18 shows the IBM Chapter 1. Introduction to LTO on Linux and Windows 17

46 Figure 1-9 IBM TotalStorage 3583 Tape Library IBM TotalStorage 3584 Tape Library The IBM TotalStorage 3584 Tape Library (abbreviated to IBM 3584), as shown in Figure 1-10 on page 19, is designed for the large, unattended storage requirements of today's mid-range systems up to the high-end systems. Each aspect of the subsystem is designed to optimize access to data and reliability. The IBM 3584 is designed to connect to host systems using any combination of Fibre Channel, Ultra2/Wide Low Voltage Differential (LVD) SCSI, or Ultra/Wide High Voltage Differential (HVD) SCSI interfaces. The IBM 3584 attaches to a variety of server and operating system platforms (See 1.2.1, Hardware server platforms on page 28). The IBM 3584 can contain IBM Ultrium 1 (no longer available), Ultrium 2, Ultrium 3, or 3592 tape drives. With Ultrium 3 drives and media, the IBM 3584 provides a sustained data rate of up to 80 MB per second (uncompressed). With Ultrium 2 drives and media, the IBM 3584 provides a sustained data rate of up to 35 MB per second (uncompressed). With 3592 drives and media, the IBM 3584 provides a sustained data rate of up to 40 MB per second (uncompressed). With Ultrium 1 drives and media, the IBM 3584 provides a sustained data rate of up to 20 MB per second (uncompressed). Figure 1-10 on page 19 shows the IBM Implementing IBM Tape in Linux and Windows

47 Figure 1-10 IBM TotalStorage 3584 Tape Library The IBM Tape Library Specialist is the primary hardware management tool that enables network access (via a Web browser) to the library for more detailed status and control. All library Operator panel functions can be accessed using the IBM Tape Library Specialist. We provide detailed information in 3.8.4, IBM 3584 Tape Library Specialist on page 161. IBM 3584-L52 base frame with IBM Ultrium 2 and Ultrium 3 The IBM 3584-L52 Base Frame is designed for IBM Ultrium 2 and Ultrium 3 drives, and IBM LTO Ultrium data cartridges. The initial capacity of an IBM 3584-L52 is enabled to use 64 cartridge slots for LTO Ultrium cartridges. If you add the Intermediate or Full Capacity on Demand features, you can enable storage elements in the IBM 3584 L52 to increase the available capacity to 129 cartridge slots, or 219 to 287 cartridge slots (depending on the features you order). The IBM 3584-L52 Base Frame has support for up to 12 tape drives with an incremental reduction of storage slots for more than four drives or with the additional I/O station installed. This model has a smaller footprint than the IBM 3584-L32. The IBM 3584-L52 is designed with an optimized gripper for use with IBM LTO or 3592 tape cartridges. Data capacity for the IBM 3584-L52 depends on the types of cartridges. Up to 12 logical libraries can be configured for each frame. Details of the capacity of the IBM 3584 with the various expansions options are in Table 1-5 on page 23 and Table 1-6 on page 24. Each IBM 3584-L52 library has a standard 16-slot cartridge I/O station for importing or exporting LTO tape cartridges from the library without requiring a re-inventory. An additional 16-slot cartridge I/O station is optionally available for either IBM LTO or 3592 data cartridges. Libraries containing a mixture of IBM LTO and 3592 drive technologies must have one LTO I/O station and one 3592 I/O station. For bulk loading of tape cartridges, the library door can be opened. Each time the library door is closed, a bar code reader mounted on the autochanger scans the cartridge labels, enabling a re-inventory of the cartridges in the library frame in typically less than 60 seconds. A door lock is included to restrict physical access to cartridges in the library. Chapter 1. Introduction to LTO on Linux and Windows 19

48 IBM 3584-D52 expansion frame with IBM Ultrium 2 and Ultrium 3 The IBM 3584-D52 Expansion Frame is designed for IBM Ultrium 2 and Ultrium 3 drives, and IBM LTO Ultrium data cartridges. Up to 15 IBM 3584-D52 Expansion Frames may be added to the IBM 3584-L22, L32, or L52 Base Frame to increase LTO cartridge storage or drive capacity. Each IBM 3584-D52 supports up to 440 LTO cartridge slots and up to 12 Ultrium 2 or Ultrium drives, with an incremental reduction of storage slots for each set of four tape drives installed. Each frame can have up to 12 logical libraries or 12 control paths. IBM 3584 high availability frame model HA1 The IBM 3584 High Availability Frame Model HA1 is designed to improve the performance and availability of the IBM The 3584-HA1, in conjunction with service bay features on the IBM 3584-D22 and D52, provides for the installation of a second library accessor that is designed to operate simultaneously with the first accessor and service mount requests in the IBM 3584 at the same time. It is designed to nondisruptively failover to a redundant accessor when any component of either accessor fails, which helps maintain availability and reliability. Additionally, this design includes the ability to add one or more IBM 3584-L52 or D22 Frames to a IBM 3584 that has an attached 3584-HA1 with minimal disruption. Dual active accessor support is provided in a mixed media library. This includes any combination of IBM 3592 and LTO Ultrium media types. Advanced Library Management Systems (ALMS) will be required for support of dual accessors and two or more IBM 3584 frames are required in a high availability configuration. A dual accessor library will have two garage areas called service bays. Service Bay A (the IBM 3584 High Availability Frame Model HA1) is to the left of and adjacent to the L-frame, when facing the front door. Service Bay B (a modified IBM 3584-D22 or D52) is to the right of the last active frame in the library. The service bays will be regular library frames, but they will not have any drives, power supplies, or node cards. Storage slots within the service bays will only be used to test service actions. The actual performance of the IBM 3584 is determined by a number of factors, such as accessor capacity, number of library frames, number of tape drives, location of tape drives and tape cartridges, and tape cartridge residency. IBM 3588 Tape Drive Model F3A The IBM TotalStorage 3588 Tape Drive Model F3A is designed for installation in an IBM 3584 to offer high capacity, performance, and technology designed for the midrange open systems environment. This model incorporates the Ultrium 3 drive, which more than doubles the maximum tape drive throughput data rate performance over the Ultrium 2 drive. It has a native data transfer of up to 80 MB/sec with Ultrium3 media. In addition, with the use of the Ultrium 400 GB Data Cartridge, the IBM 3588 doubles the tape cartridge capacity up to 400 GB native physical capacity (800 GB with 2:1 compression), as compared to the Ultrium 2 drives and cartridges. Ultrium 3 drives can read and write Ultrium 2 cartridges and read Ultrium 1 cartridges. The IBM 3588 comes with a 2 Gbps Fibre Channel interface for connection to a wide spectrum of open system servers. IBM 3584-L22 base frame with IBM 3592 The IBM 3584-L22 Base Frame is designed for 3592 Model J1A Tape Drives and 3592 data cartridges. The initial capacity of an IBM 3584-L22 is enabled to use 58 cartridge slots for 3592 cartridges. If you add the Intermediate or Full Capacity on Demand features, you can enable storage elements in the IBM 3584-L22 to increase the available capacity to 117 cartridge slots, or 199 to 260 cartridge slots (depending on the features you order). 20 Implementing IBM Tape in Linux and Windows

49 The IBM 3584-L22 Base Frame has support for up to 12 tape drives with an incremental reduction of storage slots for more than four drives or with the additional I/O station installed. This model has a smaller footprint than the IBM 3584-L32. The IBM 3584-L22 is designed with an optimized gripper for use with IBM Ultrium or IBM 3592 tape cartridges. Up to 12 logical libraries can be configured for each frame. Each IBM 3584-L22 has a standard 16-slot cartridge I/O station for importing or exporting 3592 tape cartridges from the library without requiring a re-inventory. An additional 16-slot cartridge I/O station is optionally available for either IBM Ultrium or IBM 3592 data cartridges. Libraries containing a mixture of IBM Ultrium and IBM 3592 drive technologies must have one LTO I/O station and one 3592 I/O station. For bulk loading of tape cartridges, the library door can be opened. Each time the library door is closed, a bar code reader mounted on the autochanger scans the cartridge labels, enabling a re-inventory of the cartridges in the library frame in typically less than 60 seconds. A door lock is included to restrict physical access to cartridges in the library. IBM 3584-D22 expansion frame with IBM 3592 The IBM 3584-D22 Expansion Frame is designed for the IBM 3592 Model J1A Tape Drives and 3592 data cartridges. Up to 15 Model D22 Expansion Frames may be added to an IBM 3584-L22, L32, or L52 Base Frame to increase the 3592 cartridge storage or drive capacity. Each Model D22 supports up to cartridge slots and up to drives, with an incremental reduction of storage slots for each set of four tape drives installed. Each frame can have up to 12 logical libraries or 12 control paths. Note: An IBM 3584 with IBM 3592 drives may be attached to zseries systems using the IBM TotalStorage 3953 Library Manager and Tape Frame. For more information about the IBM 3953, please refer to the IBM TotalStorage 3953 Tape Frame Model F05 and Library Manager Model L05 Introduction and Planning Guide, GA IBM TotalStorage 3592 Tape Drive Model J1A As indicated, the IBM 3584-L22 and D22 frames support the IBM TotalStorage 3592 Tape Drive Model J1A (IBM 3592). The IBM 3592 has a native data rate of up to 40 MB/sec. With the use of the IBM TotalStorage Enterprise Tape Cartridge 3592, it provides a native cartridge capacity of up to 300 GB (900 GB with 3:1 compression). It uses an optimal dynamic compression method called byte level compression scheme swapping, which is designed to achieve maximum data compression, and unlike other tape drive compression methods, is designed to prevent data expansion. The IBM 3592 has a dual-ported 2-Gbps native switched fabric Fibre Channel interface. The IBM 3592 also has additional characteristics that may help improve performance, capacity, and availability, including: Large 128 MB internal data buffer Digital speed matching to adjust the drive's native data rate to the net host data rate (after data compressibility has been factored out) throughput performance Channel calibration, which is designed to allow for customization of each read/write data channel for optimum performance High resolution tape directory plus enhanced search speed to improve nominal and average access times Streaming Lossless Data Compression (SLDC) algorithm, which is designed to offer an improvement over previous IBM lossless compression algorithms Chapter 1. Introduction to LTO on Linux and Windows 21

50 The IBM TotalStorage 3592 Tape Drive Model J1A supports Write Once, Read Many (WORM) data cartridges, and Economy (short-length 60 GB) rewritable or WORM data cartridges. The IBM 3592 WORM data cartridges are designed to provide non-alterable, non-rewritable tape media for long-term records retention. When the IBM 3592 detects a WORM cartridge, the tape drive prevents overwrite or changes to existing client data. New data can be appended to existing data until the cartridge capacity is reached. WORM cartridges are available in two sizes: 300 GB or 60 GB native capacity. These new media types are reported to the host by the IBM WORM and standard tape cartridges can be intermixed within the IBM TotalStorage 3584 Tape Library. IBM 3584 withdrawn features Attention: The IBM 3584-L32, IBM 3584-L32, and the Ultrium 1 drives were withdrawn from marketing in October IBM 3584-L32 base unit with Ultrium 1 or 2 The IBM 3584-L32 base library has 141 to 281 cartridge slots and support for up to twelve IBM LTO Ultrium 1 or Ultrium 2 tape drives with an incremental reduction of storage slots for more than four drives. Data capacity for the IBM 3584-L32 is 14 to 28 TB native and 28 to 56 TB using LTO-DC (LTO Data Compression) (2:1) compression. Up to twelve logical libraries and/or up to twelve control paths can be configured for each IBM 3584-L32 frame. Each IBM 3584-L32 library has a standard 10-slot cartridge input/output station for importing or exporting cartridges from the library without requiring a re-inventory. Alternatively, a 20 I/O station can be selected. For bulk-loading of IBM LTO Ultrium tape cartridges, the library door can be opened. Each time the library door is closed, a bar code reader mounted on the autochanger scans the cartridge labels enabling a re-inventory of the cartridges in the library frame in less than 60 seconds typically. A door lock is included to restrict physical access to cartridges in the library. Clients can expand library capacity and number of drives to meet their changing needs. The base IBM 3584-L32 can be expanded by adding up to fifteen additional D32 frames. IBM 3584-D32 expansion frame with Ultrium 1 or 2 Up to fifteen expansion frames, IBM 3584-D32, may be added to the base frame (IBM 3584-L32) to add storage or drive capacity. Each IBM 3584-D32 frame supports up to 440 storage slots and up to twelve drives, with incremental reduction of storage slots for each set of four of drives installed. A fully configured IBM 3584 with one IBM 3584-L32 frame and fifteen IBM 3584-D32 frames supports up to 192 drives with an aggregate data rate of 18 TB per hour (2:1 compression), or up to 6881 storage slots with a total capacity of 1376 TB native or 2752 TB with 2:1 compression. Each frame can have up to 12 logical libraries and 12 control paths due to the multi-path architecture of the IBM IBM 3584 capacity As mentioned, a fully configured IBM 3584 consists of a base frame with up to 15 expansion frames, making a total of 16 frames and 6887 slots, as shown in Figure 1-11 on page 23. You may mix and match the expansion frames and base frames as follows: An L32 frame may be expanded with any combination of D22, D32, and D52 expansion frames. An L52 frame may be expanded with any combination of D22, D32, and D52 expansion frames. 22 Implementing IBM Tape in Linux and Windows

51 16 Frames 192 LTO Drives L32/D Slots L52/D Slots Figure 1-11 Example of a 16-frame IBM 3584 Table 1-5 shows the different slot and drive capacities contained in the IBM 3584-L32 and D32 frames with Ultrium 2 drives and cartridges. Table 1-5 IBM 3584 frame capacity with Ultrium 2 drives Drives in L32 Frame Slots in 3584-L32 Frame (without Capacity Expansion Feature) Quantity Native Capacity (in TB) Comp. Capacity (in TB) Slots in 3584-L32 Frame (with Capacity Expansion Feature and 30 I/O slots) Quantity Native Capacity (in TB) Comp. Capacity (in TB) Slots in L32 Frame (with Capacity Expansion Feature and 10 I/O slots) Quantity Native Capacity (in TB) Comp. Capacity (in TB) Drives in D32 Frame Slots in 3584-D32 Frame Quantity Native Capacity (in TB) Compressed Capacity (in TB) Chapter 1. Introduction to LTO on Linux and Windows 23

52 Note: The quantity of slots depends on whether the Capacity Expansion Feature is installed, whether the upper and lower I/O stations are used, and the number of drives installed in a frame. The Capacity Expansion Feature of the IBM 3584 enables use of columns on the library door to provide extra cartridge storage slots. Table 1-6 shows the different slot and drive capacities contained in the IBM 3584-L52 and D52 frames and the native capacity with Ultrium 3 drives and cartridges. Table 1-6 IBM 3584 frame capacity with Ultrium 3 drives Type of Frame Type of Capacity on Demand Feature Quantity of Drives Quantity of I/O Slots Quantity of Storage Slots Ultrium 3 Native Capacity (in TB) L52 Entry L52 Intermediate L52 Full L52 Full L52 Full L52 Full L52 Full L52 Full D52 1 N/A 2 0 N/A D52 N/A 1-4 N/A D52 N/A 5-8 N/A D52 N/A 9-12 N/A Note: 1. If the L frame is not an IBM 3584-L32 or L52, then the first D frame of a mixed media library will have one less storage slot to accommodate a diagnostic cartridge. 2. N/A = not applicable. Note: The quantity of storage slots depends on the type of Capacity on Demand Expansion feature installed, whether the upper and lower I/O stations are used, and the quantity of drives in a frame. Multi-path support The multi-path architecture of the IBM 3584 provides the capability for sharing of the library robotics. This is accomplished by partitioning the library into up to 192 multiple logical libraries (up to the number of drives installed), and providing each logical library its own separate and distinct drive(s), storage slots, and control path(s). I/O slots are shared on a first come, first served basis. This type of partitioning allows heterogeneous applications to share the library robotics independent of each other. Cartridges under library control are not shared between logical libraries, nor allowed to be moved between logical libraries. An example of heterogeneous sharing is a Microsoft Windows 2000 application using the drive and storage 24 Implementing IBM Tape in Linux and Windows

53 slots of one logical library, while a UNIX application uses the drive and slots of another logical library. Logical libraries can also be used for separating different generations of IBM LTO drives and cartridges, or IBM 3592 drives and cartridges, for applications which do not support mixing the drives in the same logical library. Support for multi-path architecture and partitioning may require an updated microcode level. Download the latest microcode from either of these Web sites: ftp://ftp.software.ibm.com/storage/358x/3584/ Advanced Library Management System (ALMS) The Advanced Library Management System (ALMS) is the next generation of patented IBM Multi-Path Architecture. ALMS is designed to provide enhanced automation functionality, such as dynamic partitioning, including storage slot pooling and flexible drive assignment. Capacity On Demand (COD) level additions can also be selected and implemented through license key upgrades with the IBM 3584-L52 or L22, providing growth flexibility as required. The IBM 3584 continues to offer a SAN-ready multi-path architecture, and the ability to partition the library into 192 logical libraries. IBM Tivoli Storage Manager and other industry-leading compatible software offerings can provide storage and tape management for the IBM For implementation information for ALMS, see 2.3, ALMS on page 58. Control path failover This optional feature is designed to provide automatic control path failover to a pre-configured redundant control path in the event of a loss of a host adapter or control path drive, without aborting the current job in progress. Support is provided under AIX, Linux, Windows, HP-UX, and Solaris when the IBM device driver is used. Data path failover and load balancing Data path failover and load balancing exclusively support native Fibre Channel IBM LTO 2 and LTO 3 drives and IBM 3592 drives in the IBM 3584 using the IBM device driver for AIX, HP-UX, Windows, Linux, and Solaris. Data path failover provides a failover mechanism in the IBM device driver, so that you can configure multiple redundant paths in a SAN environment. If a path or component fails, the failover mechanism is designed to automatically provide error recovery to retry the current operation using an alternate, pre-configured path without aborting the current job in progress. This provides flexibility in SAN configuration, availability, and management. When accessing a tape drive device that has been configured with alternate pathing across multiple host ports, the IBM device driver automatically selects a path through the host bus adapter (HBA) that has the fewest open tape devices, and assigns that path to the application. This autonomic self-optimizing capability is called load balancing. The dynamic load balancing support is designed to optimize resources for devices that have physical connections to multiple HBAs in the same machine. The device driver is designed to dynamically track the usage on each HBA as applications open and close devices, and balance the number of applications using each HBA in the machine. This may help optimize HBA resources and improve overall performance. Further, data path failover provides autonomic self-healing capabilities similar to control path failover, with transparent failover to an alternate data path in the event of a failure in the primary host-side path. Data path failover and load balancing for Ultrium 3 drives in all supported operating environments requires optional feature code 1681 and the Control Path Failover feature code Data path failover and load balancing for Ultrium 2 drives in an AIX environment Chapter 1. Introduction to LTO on Linux and Windows 25

54 requires the Control Path Failover feature code 1680 but does not requires the optional feature code 1681; in non-aix environments, the Control Path Failover feature code 1680 and an RPQ are required. Virtual I/O slots The configuration of virtual I/O slots in the IBM 3584 makes it appear to the host application that the library has more physical I/O slots than actually exists. Note: If your library does not have the virtual I/O slot capability and you want to enable it, you must first install the license key for the Advanced Library Management System (ALMS). With the ALMS license key installed, you have the option to enable ALMS and the virtual I/O slot feature through the Tape Library Specialist Web interface. ALMS must be enabled and the I/O station must be empty before you can enable or disable virtual I/O slots. For information about enabling or disabling ALMS, see 2.3, ALMS on page 58. When the Advanced Library Management System (ALMS) is enabled, you can enable virtual I/O slots in the IBM 3584 so that the library automatically queues all cartridge moves between the I/O station and the storage slots. This makes the process of adding and removing cartridges easier and faster. The IBM 3584 has input/output (I/O) stations and I/O slots that allow you to import and export up to 32 cartridges at any given time. The I/O slots are also known as import/export elements (IEEs). Virtual I/O slots increase the quantity of available I/O slots by allowing storage slots to appear to the host as I/O slots. These storage slots are called virtual import/export elements (VIEEs). With virtual I/O slots, the library automatically moves cartridges from the I/O stations to the VIEEs. In this way, the library enhances its import and export capabilities. The goal of virtual I/O slots is to reduce the dependencies between the system administrator and library operator so that each performs their import and export tasks without needing the other to perform any actions: In a typical import scenario without virtual I/O slots, a library operator needs to stand at the physical library and fill the I/O station with cartridges; a system administrator must trigger the applications to send commands for moving cartridges out of the I/O station and into library storage slots. After the operator fills the I/O station with cartridges, he must wait for the I/O station to be cleared before he can insert additional cartridges, which means he is waiting on the system administrator to clear the I/O station of each set of inserted cartridges. If the library is enabled with virtual I/O slots, the operator can continuously insert cartridges into the I/O station and the administrator does not need to issue commands to move each new set of inserted cartridges. Instead, the library automatically moves the cartridges and places them into virtual I/O slots until they are ready to be processed later as one composite set of inserted cartridges. In a typical export scenario without virtual I/O slots, the system administrator may need to export a large number of cartridges from the library. However, after the I/O station is filled, he must wait for the operator to physically remove cartridges from the entire I/O station before he can issue another export command. This operation can be inconvenient. If the library is enabled with virtual I/O slots, the administrator does not have to wait to issue all export commands (up to 255 export commands can be issued at the same time for each logical library) and the operator can remove cartridges from the I/O stations as soon as the accessor automatically moves them from the storage slots. After enabling virtual I/O slots, the library can use the Cartridge Assignment Policy and Insert Notification features to determine the best storage slot location for each inserted cartridge. This determination is designed to optimize the mount throughput for the logical library to 26 Implementing IBM Tape in Linux and Windows

55 which the inserted cartridge is assigned. For more information, see Cartridge Assignment Policy and Virtual I/O on page 62. Using mtlib in the IBM 3584 The mtlib program facilitates communication between the IBM 3584 and the IBM 3494, as well as the IBM TotalStorage Virtual Tape Server (VTS). The mtlib program is a command-line interface designed originally to control the IBM It is shipped with the 3494 device driver, similar to the way the tapeutil utility comes with the SCSI tape device driver. The mtlib program provides an interface from the server to a 3494 Tape Library, and also to the virtual tape drives and cartridges within an attached VTS. The mtlib program has been enhanced to also work with SCSI tape libraries, such as the IBM Some clients have written mtlib scripts to work with the IBM If a client with an IBM 3494 decides to migrate to the IBM 3584, this mtlib enhancement will ease the migration. Existing client scripts that use mtlib require no changes or minor changes, depending on the functions of the IBM 3494 that are used. For example, there is no category concept in SCSI tape libraries, so that any mtlib command that references categories might need to be changed. For a complete description of the mtlib program and command syntax, see the IBM TotalStorage Tape Device Drivers Installation and User s Guide, GC SMI-S Support The SMI-S Agent for Tape is designed to be compliant with the Storage Management Initiative - Specification. The 3584 Tape Library can use the Storage Management Initiative - Specification (SMI-S) to communicate in a SAN environment. To communicate with storage devices in a SAN, management software uses other software known as the Storage Management Initiative - Specification (SMI-S) Agent for Tape. You must install the SMI-S Agent for Tape on an Intel machine that runs the SUSE Linux Enterprise Server 9 operating system. The SMI-S Agent for Tape communicates by using the Web-Based Enterprise Management (WBEM) protocol, which allows management software to communicate with the IBM The SMI-S Agent for Tape is designed to be compliant with the Storage Management Initiative - Specification. The SMI-S is a design specification of the Storage Management Initiative (SMI) that was launched by the Storage Networking Industry Association (SNIA). The SMI-S specifies a secure and reliable interface that allows storage management systems to identify, classify, monitor, and control physical and logical resources in a Storage Area Network (SAN). The interface is intended as a solution that integrates the various devices to be managed in a SAN and the tools used to manage them. The SMI-S was developed to address the problems that many vendors face in managing heterogeneous storage environments. It creates a management interface protocol for multivendor storage networking products. By enabling the integration of diverse multivendor storage networks, the initiative is able to expand the overall market for storage networking technology. For detailed information about SMI-S, see the IBM TotalStorage SMI-S Agent for Tape Installation Guide, GC Chapter 1. Introduction to LTO on Linux and Windows 27

56 1.2 Hardware and operating system platforms This section gives information about operating system support, SCSI and FC adapter vendors, and some applications that support the LTO family Hardware server platforms The LTO products are supported on the following operating systems and servers: IBM ^ iseries, AS/400 with OS/400 IBM System p5, RS/6000, and SP with AIX and Linux IBM ^ xseries and other Intel-based systems (Windows NT, 2000, and 2003) Sun SPARC with Solaris Hewlett-Packard with HP-UX Intel Linux (Red Hat and SLES) zseries Linux Tru64 (IBM 3584 only) Other open systems using SCSI attachment or Fibre Channel attachment Note that not all platforms and attachment methods are supported for all models for current details for operating system and attachment support for each Ultrium model, see the following Web sites: Note: Always check the Web site for the most current, detailed, and accurate information ISV storage management software Although operating systems provide utilities, such as dd, tar, and cpio, to perform basic read/write operations for tape drives, in most cases a storage management software package is used. These packages are designed to provide sophisticated capabilities that manage tape drives and libraries. They are available from companies known as Independent Software Vendors (ISVs). We discuss some of the most popular applications in Part 2, LTO libraries and backup software on page 243. IBM publishes information about ISV storage management applications that are certified with LTO Ultrium devices and on which operating system platforms. This is available at the Web site: You should also check with the ISV for detailed support information. 28 Implementing IBM Tape in Linux and Windows

57 1.3 Windows 2000/2003 connectivity In this section, we cover examples of connecting LTO models to Windows 2000/2003 using the IBM Windows 2000/2003 SCSI direct attach Table 1-7 is an extract from the IBM Web site that details server, operating system levels, Host Bus Adapters, and fabric support for the IBM 3584 in the Windows 2000/2003 environment (correct at the time of writing). We listed the URLs for each LTO model in 1.2.1, Hardware server platforms on page 28. Click the details button (on the Web site) to read the readme file. Table 1-7 LTO Windows 2000/2003 attachment summary SCSI LTO Ultrium 1 and Ultrium 2 Drive Features in L32 and D Frames Servers Operating system Host adapters Windows 2003 details Build 3790 or later Windows 2000 details Build 2195 or later HVD Adaptec 2944 Netfinity Adapter #59H3900 LVD Adaptec 29160, 29160LP, Adaptec 39320, 39320D-R, 39320D Adaptec 2940U2W LSI Logic Sym Netfinity Adapter #19K4646 Netfinity Adapter #33L5000 IBM #13N2249 Notes: 1. Certain restrictions may apply. See the details above for your operating system. 2. Control Path Failover supported for Ultrium 2 and 3592 drives with Windows. 3. Data Path Failover supported for Ultrium 2 and 3592 drives with Windows. From the table, we can see that in order to attach an IBM 3584 to a Windows 2000 Server, build 2195 or higher of the operating system is required, and for a Windows 2003 Server, build 3790 or higher is required. The matrix shows that there is a choice of thirteen SCSI adapters; some of these use the LVD interface and the other cards use the HVD interface. You need to choose an adapter with the correct SCSI interface for the tape drives installed in the library Windows 2000/2003 Fibre Channel attachment If you want to use a Fibre Channel attachment, you will use Fibre Channel Ultrium 2 or Ultrium 3 drives. We will now determine the supported adapters for the IBM Go to the following Web site and check off the Ultrium product and operating system of choice (for example, IBM 3584 with Ultrium 3 FCP drives and Windows 2000): Attention: This URL is case sensitive. The search results are returned, as shown in Figure 1-12 on page 30 (excerpt only). Chapter 1. Introduction to LTO on Linux and Windows 29

58 Figure 1-12 Supported HBA and microcode (excerpt) This excerpt from the output shows that with you can attach the Fibre Channel Ultrium 3 FCP drives with the IBM, QLogic, or Emulex adapters. If you click the View Details link for each HBA, this will take you to the vendor s Web site to download device drivers and microcode. We give more information about using SCSI and SAN HBAs to attach the LTO drives and libraries with Windows 2000 in Chapter 3, Basic IBM tape setup for Windows on page Intel Linux connectivity In this section, we show an example of a direct SCSI attachment of an Intel Linux server to the IBM Linux SCSI direct attach Table 1-8 on page 31 is an example of the IBM Web site that details server, operating system levels, and SCSI adapters for the IBM 3584 in the Red Hat Linux environment. The URLs for each LTO model are given in 1.2.1, Hardware server platforms on page Implementing IBM Tape in Linux and Windows

59 Table 1-8 Linux attachment SCSI LTO Ultrium 1 & Ultrium 2 Drive Features in L32 and D Frames Servers Operating systems Host Adapters Linux Servers Red Hat Advanced Server Enterprise Linux 3.0 details SUSE Linux Enterprise Server 8, 9 details HVD Adaptec 2944 LVD Adaptec Adaptec Adaptec ALP, Adaptec 2940 UBN #13N Certain restrictions may apply. See the details above for your operating system. 2. Control Path Failover supported for Ultrium 2 and 3592 drives with Linux. 3. Data Path Failover supported for Ultrium 2 and 3592 drives with Linux. In order to attach an IBM 3584 to a Linux server, you need to ensure that you are running the correct Linux operating system and kernel levels. The matrix shows that there is a choice of seven SCSI adapters. Some use the LVD interface and the others use the HVD interface. You need to choose an adapter with the correct SCSI interface for the tape drives installed in the library. 1.5 Determining the number of drives on a SCSI bus How do you determine how many SCSI drives to place on a host adapter? There are several factors to take into consideration, including: Tape drive speed capability Disk drive speed capability Application Application needs Application characteristics: Read/write mix, amount of data transferred, streaming or stop/start, and data block size Adapter slot availability and capability Cost of more adapters To ensure best performance, if possible, avoid daisy-chaining (connecting more than one drive to an adapter). If cost or slot availability considerations make daisy-chaining unavoidable, then connect no more than two drives per HVD (Ultrium 1 and 2), 2 4 drives per LVD adapter (Ultrium 1 and 2), or no more than two drives per LVD adapter for Ultrium 3. When daisy-chaining with Ultrium 3 drives, you must consider the data transfer rate of the drive and the capacity of the adapter. A single Ultrium 3 SCSI drive, which is capable of transferring over 200 MB/sec of compressible data, can saturate a SCSI-160 adapter. A SCSI-160 adapter can transfer 160 MB/sec, but that does not include SCSI overhead. With overhead, the available bandwidth is approximately MB/sec. Two Ultrium 3 drives cannot run at their native drive rate of 80 MB/sec on a single adapter. If performance is not a primary consideration, it may be possible to daisy-chain two Ultrium 3 drives on one adapter. The type of application is also significant. If you are mainly doing smaller volume reads or writes, then more drives can be attached without saturating the adapter. A more typical use of Chapter 1. Introduction to LTO on Linux and Windows 31

60 tape is in high-volume backup, usually writing large blocks of data (for example, backing up large database files). In this scenario, a single drive per adapter will give the best performance. Another situation where daisy-chaining may be required is when connecting a multi-drive library through a SAN Data Gateway (SDG) (withdrawn from marketing). The SDG has a total of four ports and one is recommended for the SCSI medium changer. Therefore, if more than three drives are installed in the library, daisy-chaining will be required. 1.6 Host Bus Adapters and device drivers This section will cover the following: What are HBAs? Why are they needed, and which one do you need? Are drivers needed for HBAs? Restriction: At this time, there are restrictions on attaching both disk and tape devices to the same HBA. See 5.1.3, Tape and disk on the same HBA on page 228 for more information. What are HBAs HBA stands for Host Bus Adapter. An HBA is an I/O adapter (or card) that sits between the host computer's bus and the SCSI or Fibre Channel fabric and manages the transfer of information between the two channels. To minimize the impact on host processor performance, the HBA performs many low-level interface functions automatically or with minimal processor involvement. Device drivers A device driver is a program that controls a device. Every device, whether it be a printer, disk drive, or keyboard, must have a driver program. Many drivers, such as the keyboard driver are included with the operating system. For other devices, you may need to load a new driver either from the operating system CD, or as provided by the manufacturer when you first install the device on your computer. A driver acts like a translator between the device and programs that use the device. Each device has its own set of specialized commands that only its driver knows. In contrast, most programs access devices by using generic commands, that is, Read, Write, Put, and Get. The driver, therefore, accepts generic commands from a program and then translates them into specialized commands for the device. Figure 1-13 is an example of the data flow between an application program and a LTO tape device. Note the different pieces of code or microcode are involved. The HBA Device Driver is not always a separate piece of installable software; sometimes it is included as part of the standard operating system. This is true for many common SCSI adapters with Linux. You should check the documentation provided with the card to see if this applies. For Fibre Channel HBAs, driver software will almost always need to be installed. Application Program (software) LTO device driver (software) HBA device driver (software) HBA device adapter (hardware) LTO tape device Figure 1-13 Device data flow 32 Implementing IBM Tape in Linux and Windows

61 Data flow The simplified list below reflects the components involved in the data path for moving data at a file level between disk storage devices and tape. Problem or performance analysis must be approached by determining which component of the data path impacts performance. Disk device SCSI Device Adapter Adapter device driver Disk device driver Logical Volume Manager File system Application program Atape Device Driver: Tape driver HBA Adapter Device Driver HBA (SCSI or FC-AL) Device Adapter Tape device IBM device driver overview The IBM Ultrium tape and medium changer device drivers are designed specifically to take advantage of the features provided by the IBM Ultrium tape drives and medium changer devices. The goal is to give applications access to the functions required for basic tape functions (such as backup and restore) and medium changer operations (such as cartridge mount and dismount), as well as to the advanced functions needed by full tape management systems. Whenever possible, the Ultrium driver will take advantage of the device features transparently to the application. 1.7 LVD or HVD This section discusses the different types of attachment interfaces found in SCSI devices and explains why selecting the right interface is important LVD and HVD LTO tape drives have two types of SCSI attachment interfaces: low voltage differential (LVD) and high voltage differential (HVD). LVD and HVD, as the names imply, use different voltage levels while sending the signal down the SCSI bus. LVD uses 3.3 volts DC and HVD uses 5 volts DC. LTO tape drives are either LVD or HVD, and cannot be upgraded or converted from one to the other. To change from LVD to HVD, a LVD drive would need to be replaced with a HVD drive. Therefore, when configuring an LTO product, consider carefully whether you should choose HVD or LVD drives. Note: Ultrium 3 drives attach only via SCSI LVD (or native Fibre Channel) interfaces Why this is important? Why choose one over the other and why should you care? The main reason is connectivity. If you to try to attach an HVD LTO drive to an LVD adapter, it will not work. Placing an LVD device on an HVD bus will cause the LVD device to shut down. Placing an HVD device on an LVD bus will cause the entire LVD bus to shut down. Therefore, check to see what type of adapter you have available in the hosts that will be attaching, and choose the correct model of drive accordingly. Chapter 1. Introduction to LTO on Linux and Windows 33

62 There are also differences in the speed characteristics of HVD versus LVD. LVD is available either as Ultra2 SCSI, which has an 80 MB/second speed or the new Ultra160 SCSI at 160 MB/second, while HVD is Ultra SCSI, which has a maximum speed of 40 MB/second. Does this mean that the LTO drive will run faster with LVD versus HVD? Not necessarily. The speed seen here is the SCSI bandwidth or bus speed. Ultrium 1 drives (whether LVD, HVD, or native Fibre Channel) have a nominal speed of 15 MB/second, while Ultrium 2 drives are rated at 35 MB/second. If the speed of the bus is the only limiting factor in your configuration, then yes, switching to a faster bus could improve your performance. Usually, the speed capability of the bus will determine the number of LTO drives that can be attached on the same bus. But again, this is not the only factor in the equation. In addition to the speed differences, there are connection restrictions associated with each. Both HVD and LVD can span 25 meters in a point-to-point configuration. In a multidrop (daisy-chain) configuration, HVD can span 25 meters, while LVD is limited to 12 meters. So, which should you choose? If you have a situation where the 12 meter multidrop limitation of LVD is not an issue, then you would purchase LVD, right? You would think so, but the correct answer is that it depends. It depends on the HBA that you have installed in your server. If you have an existing adapter and you do not want to change it, then whether the adapter is HVD or LVD will dictate which LTO drive you order and the configuration capabilities. What if you do not already have an adapter? Order LVD, right? Again, not necessarily. At this time, not all supported SCSI HBAs are available in both interface types. For example, iseries and AS/400 support only HVD drives when directly SCSI attached. Table 1-9 summarizes key HVD and LVD differences. Table 1-9 HVD and LVD characteristics HVD LVD Point-to-point 25 meters 25 meters Multidrop 25 meters 12 meters Speed 40 MB/second 80 or 160 MB/second 1.8 SCSI HD68 and VHDCI cable connectors There are three types of SCSI cables: HD68-HD68, HD68-VHDCI, and VHDCI-VHDCI. The HD68 connector is the normal 68-pin SCSI connector. The Very High Density Connector (VHDCI) is a mini SCSI connector that is about half the width of the HD68 connector. The server SCSI adapter can be either HD68 or VHDCI. For RS/6000, AS/400, and HP servers, LVD SCSI adapters are always VHDCI, and HVD adapters are always HD68. But Sun and Netfinity/Intel servers have some adapters that are reversed. The connector type for a given adapter can be found in either of two ways. You can look at the adapter and the plug will be either about 3 cm wide (VHDCI) or 6 cm wide (HD68). The other method is to look up the adapter characteristics to determine the plug type. One source of this information is the IBM Total Storage UltraScalable Tape Library 3584 Operator Guide, GA , available online at: Before June 12, 2001, all the LTO tape drives used HD68 connectors. The current IBM 3584 hot swappable canister LTO drive uses the VHDCI connectors. Check to make sure you order the correct cable with the right-end plug to attach to your HBA. 34 Implementing IBM Tape in Linux and Windows

63 Figure 1-14 shows the VHDCI and HD-68 connectors. VHDCI Figure 1-14 SCSI connectors HD68 Chapter 1. Introduction to LTO on Linux and Windows 35

64 36 Implementing IBM Tape in Linux and Windows

65 2 Chapter 2. IBM LTO Tape Library sharing and partitioning In this chapter, we describe the sharing and partitioning of the IBM TotalStorage 3582 Tape Library, IBM TotalStorage 3583 Tape Library, and IBM TotalStorage 3584 Tape Library. The topics are: Tape library sharing and partitioning definitions Sharing the IBM TotalStorage 3583 Tape Library Partitioning the IBM TotalStorage 3583 Tape Library using the Tape Library Specialist Sharing the IBM TotalStorage 3584 Tape Library Partitioning the IBM TotalStorage 3584 Tape Library using the Tape Library Specialist Partitioning the IBM TotalStorage 3584 Tape Library using the Operator panel Using and partitioning the IBM TotalStorage 3584 Tape Library with the Advanced Library Management System (ALMS) For additional discussions on Tape Library Sharing, refer to the redbook: Get More Out of Your SAN with IBM Tivoli Storage Manager, SG Details about the ALMS functionality and setup can be found in the 3584 manuals: IBM Total Storage UltraScalable Tape Library 3584 Operator Guide, GA IBM TotalStorage UltraScalable Tape Library 3584 Introduction and Planning Guide, GA Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 37

66 2.1 Definitions In general, the sharing of devices improves the utilization of the devices and can reduce the total cost of ownership. Sharing of disk devices is a common practice. Compared to disk devices, which allow random access from different clients, tape drives are sequential devices that do not allow access from different clients at the same time. Still, sharing can improve the utilization of the tape drive; indeed, a tape drive is normally not used 100% of the time by a single client (host), and there are different possible ways to share either a tape library or tape drives among multiple hosts. The most basic requirement in sharing any library between backup applications and servers is the ability to control the medium changer. The tape drives and media may or may not be shared, but the medium changer must be available to be manipulated by all of the backup applications and servers Library sharing We differentiate between outboard library management and the multipath approach. Outboard library management One approach is to share the library but not the tape drives. Multiple servers attached to a tape library can share the library robotic. Drives and cartridges are pooled, and such a drive and cartridge pool belong to one set of servers (one server or multiple servers) and cannot be shared with another set of servers. Some applications, like IBM Tivoli Storage Manager use the name library sharing if they share drives and library. We will explain drive sharing later. Some technique is needed to share the library robotic. The most common way is to use an outboard library manager that controls the library. The library manager receives the commands from the attached servers, controls the resources inside the library, and executes the commands received from the servers. The communication between the library manager and attached servers normally takes place over the LAN using a proprietary command set. The tape library manager controls access to and sequencing of the medium changer. The medium changer is physically available to all backup and application servers. The IBM 3494 tape library uses this type of library sharing. For communication with the IBM 3494, a command set called mtlib must be used (see Figure 2-1 on page 39). Other examples are STK with ACSLS or ADIC with Scalar DLC. 38 Implementing IBM Tape in Linux and Windows

67 Server Server Server mtlib mtlib mtlib Library Commands (LAN Attachment) Data Path SCSI/Fibre Channel Data Path SCSI/Fibre Channel Data Path SCSI/Fibre Channel Library Manager Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Cartridge Accessor Accessor Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Tape Drives Cartridges IBM 3494 Tape Library Figure 2-1 IBM 3494 tape library sharing The IBM 3494 tape library pools cartridges by using categories. Drives, on the other hand, are pooled by simply connecting them to one set of servers. Multi-path SCSI medium changer library The disadvantage of the outboard library management is that it introduces an additional software layer. The IBM patented multi-path architecture eliminates this disadvantage. Multi-path architecture is the capability of a tape library to provide multiple paths to the library robotics without needing a library manager. This capability allows the partitioning of the physical library into several logical libraries. A logical partition (logical library) contains tape drives and storage slots. The library robotic is shared among all logical partitions and the tape library controls access and sequencing to the medium changer. All IBM LTO tape libraries, including the high-end IBM TotalStorage 3584 Tape Library, offer this partitioning capability at no additional cost. Partitioning is available for SCSI and FC drives. Figure 2-2 shows the multipath design of an IBM LTO tape library. Every drive can have a path defined to the SCSI medium changer. The library in this example (Figure 2-2 on page 40) has been partitioned into three logical libraries. Each logical partition has two tape drives and a set of cartridge slots. All the servers share the library robotic, but not the drives or the cartridges. Chapter 2. IBM LTO Tape Library sharing and partitioning 39

68 FRAME CONTROLLER (SCSI Medium Changer) LUN1 Logical Library 1 DRIVE1 LUN0 DRIVE2 LUN0 to Host 1 iseries Logical Library 2 DRIVE3 LUN0 DRIVE4 LUN0 to Host 2 Windows Logical Library 3 DRIVE5 LUN0 DRIVE6 LUN0 to Host 3 pseries Multiple hosts 'owning' separate logical library inventories & drives Figure 2-2 IBM multipath architecture and logical partitioning This kind of partitioning uses static assigned resources. There is no sharing of these resources (tape drives and cartridge slots), which means servers from one partition cannot access tape drives or cartridges in another partition. The assignment of resources to the different logical partitions is defined through static rules and must use contiguous resources. In other words, you create barriers around the logical library. This type of partitioning is also called first generation of multipath architecture. The second generation of multipath architecture, also called Advanced Library Management System (ALMS), does not have the need to partition the library using static rules and contiguous resources. ALMS virtualizes the affinity to physical resources. This second type of partitioning allows heterogeneous applications to share the library robotics independent of each other. ALMS is offered as a feature for the IBM For further details, see 2.3, ALMS on page Homogenous drive sharing Because a tape drive cannot be accessed simultaneously by several servers, a mechanism is required to manage and control access. Currently, there are different solutions available that allow some kind of tape drive sharing. The most common way is to do a homogenous drive sharing. Homogenous means that one master host takes care of the access control, and allows other servers that are running the same application to share the tape drives. All servers access the medium changer through the master such as multiple IBM Tivoli Storage Manager servers communicating through one IBM Tivoli Storage Manager Library Manager 40 Implementing IBM Tape in Linux and Windows

69 server. The master server controls physical access (such as mount and demount cartridges) and sequencing to the medium changer (see Figure 2-3). The tape drives appear to each server as locally attached devices. When a server requests a tape to be loaded for a tape operation, the server contacts the master with the request. The master mounts the tape and then passes control back to the requesting server. The server then reserves (SCSI reserve) the same drive to itself (to ensure that no other server can access the tape drive and overwrite data). When the operation is complete, the server unloads the cartridge, releases (SCSI release) the reserve on the drive, and notifies the master to demount the cartridge. The master then demounts the media. Read Data clients LAN Mount a tape Read Data Write Data TSM Server Library client SCSI I/O FC Tape Library FC SCSI I/O TSM server Library manager select drive mount, dismount volumes release, query volumes Figure 2-3 Tivoli Storage Manager library sharing Such homogenous drive sharing is commonly used for LAN-free backups (see Figure 2-4 on page 42). Chapter 2. IBM LTO Tape Library sharing and partitioning 41

70 TDP Client TSM API Storage Agent 1 Meta data LAN TSM server (manages the tape library) 2 Read Data 3 Write Data SAN Client Disk Tape Library Figure 2-4 LAN-free backup What should I use? Whenever multiple servers running the same storage management (homogenous) application have to share the same tape library, we suggest using the applications s own sharing capabilities. This will ensure the most efficient library and drive sharing. The master server can normally provide sharing functions for all tape drives to all client servers. The master server also manages the cartridges in the library; so that you need only one scratch pool, instead of several scratch pools (one for each server). Figure 2-5 on page 43 shows an example of how sharing capabilities from the application can address the sharing requirements. This example is built on IBM Tivoli Storage Manager, but it works also with other applications, such as VERITAS NetBackup or EMC Legato NetWorker. There are two locations in the example, each with its own data processing application, server, and storage. The SAN spans both locations. There are three backup servers, with many clients attached to them performing the backup jobs. For disaster recovery reasons, all backup data are copied to the second location. One or more tape libraries are installed in each location. In every location, one backup server manages the tape library (library manager) and handles all mount requests issued by the other backup servers. Any backup server from location 1 asks Library Manager Server 1 (TSM Server 1) to assign a tape to it and mount a cartridge in Library 1. If a backup server from location 1 copies the data to location 2, then it asks Library Manager Server 2 (TSM Server 2) to mount a tape on Library 2. An overview of library sharing with IBM Tivoli Storage Manager is in Chapter 7, Configuring IBM Tivoli Storage Manager on Windows and Linux on page 255. For complete details, see the redbook Get More Out of Your SAN with IBM Tivoli Storage Manager, SG Implementing IBM Tape in Linux and Windows

71 Library and Drive requests for Library1 Library and Drive requests for Library2 TSM Server 1 Library Manager for Lib 1 TSM Server TSM Server TSM Server 2 Library Manager for Lib 2 Primary Data SAN Copy Data IBM Tapelibrary1 IBM Tapelibrary 2 Figure 2-5 Library sharing done by TSM Location 1 Location 2 However, in some cases, even if you use one homogenous backup application, it might not be adequate to use the sharing option of the application itself; instead, use the partitioning capabilities of the library. This is the case if you have to separate (for security reasons) the data coming from the different backup servers; in this situation, you need the partitioning function of the library to guarantee separation of the data. Of course, if you use different applications, then you have to use the partitioning function, such as when you have iseries on one hand and Tivoli Storage Manager running on Windows or UNIX on the other hand, connected to the same library. 2.2 Partitioning multi-path tape libraries The IBM 3582, 3583, and 3584 tape libraries all use the patented multi-path architecture and those libraries can be partitioned. You can use multiple logical libraries to share the physical library between applications, or to support mixed drive types for any application. You can create multiple logical libraries by partitioning the physical library storage slots and tape drives into two or more logical libraries. Each logical library consists of: Tape drives Storage slots Input/output (I/O) slots Cartridge accessor Each logical library has its own control path (a logical path into the library through which a server sends standard SCSI medium changer commands to control the logical library). Each logical library control path is available to servers through a Logical Unit Number 1 (LUN 1) of the first drive that is defined within that logical library. A logical library cannot share another logical library s tape drives and storage slots. However, it does share the I/O slots, and the cartridge accessor on a first-come, first-served basis. Chapter 2. IBM LTO Tape Library sharing and partitioning 43

72 2.2.1 Partitioning the IBM 3582 The IBM 3582 can be partitioned into two logical libraries if two tape drives are installed. Each partition provides its own separate and distinct drive, control path, and storage slots. The input/output (I/O) slot is shared on a first-come-first-served basis. This type of partitioning allows heterogeneous applications to share the library robotics independent of each other. Cartridges under library control are not shared between logical libraries, nor can they be moved between logical libraries. The first drive module is assigned to the first partition and the second drive module is assigned to the second partition. The slots in the magazine on the left are always partition 1, and the slots in the magazine on the right are always partition 2. You can designate a minimum of eight slots for each partition (seven magazine slots and one rear slot). You can designate a maximum of 16 slots for partition 1 (seven magazine slots, eight rear slots, and the I/O slot, if configured as a data slot). You can designate a maximum of 15 slots for partition 2 (seven magazine slots and eight rear slots). If you configure cleaning slots, the total number of slots available for both partitions is reduced (see Figure 2-6). Each partition can operate in one of two modes: random or sequential. You can configure the partition using either the Operator panel or using the IBM 3582 Tape Library Specialist Web browser based interface. Drive1 Drive2 IO Slot Partition 1 Partition 2 Figure 2-6 IBM 3582 partitioning For a description on how to configure the logical partitions, see the IBM TotalStorage 3582 Tape Library Setup, Operator, and Service Guide, GA , available at: Partitioning the IBM 3583 The IBM 3583 supports partitioning the library into up to three logical libraries. Each logical library has its own separate and distinct drives, storage slots, and control paths. Input/Output (I/O) slots are shared on a first come, first served basis. The multi-path feature (#1450 or #9450) must be installed in order to partition the library - it is required on all IBM 3583s that will contain an LTO 2 or LTO 3 drive, and for all libraries shipped after June 13, Libraries shipped before June 13, 2003 that do not have LTO 2 drives installed require feature #1450 to achieve partitioning. 44 Implementing IBM Tape in Linux and Windows

73 Guidelines for partitioning the IBM 3583 Each logical library must contain at least one drive and one storage column. If your application supports it, LTO 1, LTO 2, and LTO 3 drives and media are allowed in the same logical library. At least one tape drive must have the control path enabled. Support for two logical libraries requires that at least storage column 2 and 4 be installed. This means that an IBM 3583 L18 needs at least one feature code #8007 to be partitioned. At least two drives must be installed. Support for three logical libraries requires that columns 2, 4, and 5 be installed. Only the IBM 3583 L72, the IBM 3583 L36 with one FC #8007, or IBM 3583 L18 with two FC #8007 can be partitioned into three logical libraries. At least three drives must be installed. The I/O station is a shared resource for all logical libraries. The six-slot fixed magazine below the I/O station on column 1 is included as part of the first partition. Each logical library has a predefined, unchangeable default control path as follows (for an overview of the IBM 3583, see Figure 2-7 on page 46): Logical library A: Drive 1 Logical library B: Drive 3 Logical library C: Drive 5 Logical libraries have predetermined, fixed configurations: Two logical libraries with a 12-slot I/O station Logical library 1: 24 slots (column 1 and column2), 1-2 tape drives (drive 1 and drive 2) Logical library 2: slots (column 4, column 5), 1-4 tape drives (drive 3, drive 4, drive 5, and drive 6) Two logical libraries with a 1-slot I/O station Logical library 1: 18 slots (column 2), 1-2 tape drives (drive 1 and drive 2) Logical library 2: slots (column 4 and column 5), 1-4 tape drives (drive 3, drive 4, drive 5, and drive 6) Three logical libraries with a 12-slot I/O station Logical library 1: 24 slots (column 1 and column 2), 1-2 tape drives (drive 1 and drive 2) Logical library 2: 18 slots (column 4), 1-2 tape drives (drive 3 and drive 4) Logical library 3: 18 slots (column 5), 1-2 tape drives (drive 5 and drive 6) Three logical libraries with a 1-slot I/O station Logical library 1: 18 slots (column 2), 1-2 tape drives (drive 1 and drive 2) Logical library 2: 18 slots (column 4), 1-2 tape drives (drive 3 and drive 4) Logical library 3: 18 slots (column 5), 1-2 tape drives (drive 5 and drive 6) Chapter 2. IBM LTO Tape Library sharing and partitioning 45

74 Column 5 Storage Column 1 I/O Station Column 4 Storage Picker Assembly Column 2 Storage Interface Modules 1-6 Drives Power Modules Figure 2-7 IBM 3583 IBM 3583 Partitioning the IBM 3583 with the Library Specialist or Operator panel Partitioning is set up using the Operator panel. Partitioning can be invoked from either the physical library operator interface or through the Tape Library Specialist Operator interface. They have the same interface: one is the physical representation and the other is the logical representation. If you are using Tape Library Specialist to set up partitioning, select the Operator Panel tab. You will be asked to authenticate and then will see the screen shown in Figure 2-8. Figure 2-8 IBM 3583 Tape Library Specialist Operator panel From the Operator panel, select More and then Setup (shown in Figure 2-9 on page 47). 46 Implementing IBM Tape in Linux and Windows

75 Figure 2-9 IBM 3583 setting up partitioning 1 Select Library and Partitions (Figure 2-10). To enable partitions, you need at least one tape drive and control path enabled for each partition, that is, there must at least be one tape drive in slots 1 and 3 from the bottom, as shown in Figure 2-8 on page 46. Figure 2-10 IBM 3583 setting up partitioning 2 The panel indicates the default non-partitioned environment. To change the partition configuration, click Next to select which of the listed partition options is required. Click OK to confirm the selection. Figure 2-11 shows before and after setting up for a two partition library. Figure 2-11 IBM 3583 setting up partitioning 3 The library will reboot to affect the partition change (Figure 2-12). Figure 2-12 IBM 3583 setting up partitioning 4 The second error screen is displayed as the library is rebooting, and is informational only. Once the library has rebooted, the screen will be refreshed with the Operator panel. For more details on configuring partitions, see IBM TotalStorage 3583 Tape Library 3583 Setup and Operator Guide for Multi-Path Libraries, GA , at: Chapter 2. IBM LTO Tape Library sharing and partitioning 47

76 2.2.3 Partitioning the IBM 3584 (ALMS not enabled) You can partition the IBM 3584 into multiple logical libraries. Each logical library requires at least one tape drive and one storage slot. Therefore, you can theoretically configure as many logical libraries as there are tape drives installed in the library, that is, the IBM 3584 supports up to 192 logical libraries. Ultrium drive types (Generation 1, 2, or 3) can be mixed in a logical library if the backup application supports it, but Ultrium and IBM 3592 tape drives cannot be mixed within a logical library (LTO and 3592 must be installed in different frames). Note: If using mixed media and drives (LTO and 3592) within one IBM 3584, then at least two logical libraries (one for LTO and one for 3592) must be created. Storage slots within one logical library must be in contiguous order, but can span over different frames. Also, tape drives within one logical library must be in contiguous order, but can be in different frames, and can contain gaps in the order (such as having two drives installed in frame 1 and two drives in frame 2; then you have a gap of 10 drives). However, although the IBM 3584 allows you to have gaps in the tape drive order, some applications such as EMC Legato NetWorker or VERITAS BackupExec do not support such gaps. Plan your logical library configuration carefully, because the need for contiguous storage slots and drives makes future changes to the configuration very difficult. For example, if you have an IBM 3584 with six logical libraries defined, and you have to change the configuration of the first library, then all of the five remaining libraries must be changed as well. Consequently, plan your logical library configuration according to these rules: Put the logical library that has the most expected growth at the end of the library. Put the logical library that is the least likely to grow in the front. Do not configure logical libraries with just the required minimum of resources (tape drives and storage slots); instead, configure logical libraries with a buffer (reserve) of storage slots. Do not put the first drive of a logical library just behind the last drive of the preceding logical library. Keep some free drive locations between two logical libraries in order to install additional drives if needed. Figure 2-13 on page 49 shows an example. This is an L52 frame with nine LTO drives installed, and with a capacity of 261 storage slots. Three logical libraries are required: logical library 1 needs 40 slots and two drives, logical library 2 needs 60 slots and two drives, and logical library 3 needs 120 slots and five drives. The third library is expected to grow heavily. The first logical library was configured with 60 slots and two tape drives. The second logical library was configured with 81 slots and two tape drives. The first tape drive for logical library 2 was installed in the fourth drive location; this gives the ability to install one additional drive in the first logical library if needed. The library with the highest expected growth was put at the end. If needed, an additional D-frame can be added to the library and logical library 3 can be expanded to the next frame without changing the configuration of the first two libraries. 48 Implementing IBM Tape in Linux and Windows

77 Library CONTROLLER Logical Library 1 Storage Slots needed - 40 Slots free 20 DRIVE 1 DRIVE 2 free Logical Library 2 Storage Slots needed - 60 Slots free 21 DRIVE 1 DRIVE 2 free free Logical Library 3 Storage Slots needed DRIVE 1 DRIVE 2 DRIVE 3 DRIVE 4 DRIVE 5 Figure 2-13 IBM 3584 partitioning example There are two ways to partition the IBM 3584 into multiple logical libraries: Configuring the library by using labels With this method, you must manually label the storage elements (storage slots and drives) that you want in each logical library, then select Configure Library to identify them to the library. With this method, you can view the boundaries of your logical library whenever you open the front doors. However, because a logical library bar code label applies to an entire column of storage slots (and not individual slots), this method does not allow you to choose any number of slots from that column. Configuring the library by using menus With this method, you choose the exact number of storage elements that you want by selecting them from the Advanced Configuration menu selection (or using the Tape Library Specialist menu). If you use this method, you do not need to manually label the library elements, and you can choose individual slots from any column. However, you have no visual indication of your logical library whenever you open the front doors. Both methods require you to take the library offline while configuring. For further details on setting up partitions using the Operator panel, see the IBM Total Storage UltraScalable Tape Library 3584 Operator Guide, GA Chapter 2. IBM LTO Tape Library sharing and partitioning 49

78 2.2.4 Partitioning the IBM 3584 using the wizard (ALMS not enabled) First, plan the number and location of storage slot columns and tape drives that you want in each logical library. Now, the logical libraries can be configured from the Tape Library Specialist using the configuration wizard or the menu system. Using the Tape Library Specialist In this example, we have a 1-frame library with 175 cartridge slots, and with six drives already installed. It is defined as three logical libraries, but we will reconfigure the logical libraries using the configuration wizard: Logical library Redbook 1 : Three drives, 60 cartridge slots Logical library Mt Lemon : Two drives, 60 cartridge slots Logical library Tucson : One drive, 55 cartridge slots We assume (as an example) that the requirements for the first two logical libraries are stable, but that for the third library they might change. Therefore, we put the third library at the end. Whenever needed, we can enlarge this third logical library by adding one additional frame. To use the IBM 3584 Tape Library Specialist Web interface, do the following: 1. Enter the library s IP address as a URL in your browser window; the introduction window displays (see Figure 2-14). If login security is enabled, there will be a login prompt first. For experienced Library Specialist users, you will see a button Switch to Original Navigation. Clicking this reverts the Library Specialist to its previous layout. The alternate entry Switch to New Navigation takes you to the format (as of July 2005) used here. Figure 2-14 IBM 3584 Specialist main screen 2. Click Manage Logical Library on the main pane, or select Manage Library and by Logical Library on the left side. The Manage Logical Libraries window displays (Figure 2-15 on page 51). 50 Implementing IBM Tape in Linux and Windows

79 . Figure 2-15 IBM 3854 Tape Library Specialist Logical Libraries entry window 3. This shows the library s current configuration. Select the Launch Configuration Wizard. A warning window informs you that the library goes offline and that it may take up to 30 minutes to complete (depending on the library configuration; a small library with just one or two frames and a couple of drives may take less than a minute); click Next to continue. 4. The Select Configuration Method window displays (Figure 2-16) showing the alternatives: Automated configuration (configuration with barcode labels) or Advanced configuration. Select Advanced configuration and click Next. Figure 2-16 IBM 3854 Tape Library Specialist configuration wizard 5. The library starts its configuration discovery, which can take several minutes. The current configuration will be displayed. Check that the displayed configuration matches the real configuration (Figure 2-17 on page 52). If not, then stop here and try the configuration discovery again. If the problem is still not solved, call your service representative. Chapter 2. IBM LTO Tape Library sharing and partitioning 51

80 Figure 2-17 Current physical configuration 6. Click Next. The number of logical partitions can now be selected (Figure 2-18). Figure 2-18 IBM 3584 Tape Library Specialist Logical Libraries 7. Select the number of logical libraries from the drop-down list. Select Next. The desired number of drives and slots can now be assigned to each logical library (Figure 2-19 on page 53). Begin with the first logical library and use the Tab key to jump from one field to the other. Every time you press the Tab key, the remaining number of drives and storage slots is re-calculated. 52 Implementing IBM Tape in Linux and Windows

81 Note: All resources (tape drives and cartridge slots) must be assigned! If you have both LTO and 3592 in the physical library, there will be more than one configuration range, and more than one selection and configuration info in the screens. For example, you can first configure a range of LTO elements, and then a range of 3592 elements. Select Next when finished. Figure 2-19 IBM 3854 Tape Library Specialist drives and slots 8. A new window shows the selections. The configuration can now be reviewed before being applied. Select Next to accept the configuration, and then select Finish to apply the new configuration, which takes some minutes. After completion the library gives you a Library configuration successful message. After setting a new configuration, the new logical libraries are simply named using numbers. You may change this to more meaningful names: From the Manage Logical Libraries screen (Figure 2-15 on page 51), select the library to be renamed and click Rename. On the next screen (Figure 2-20 on page 54), enter a new name. The logical library name is only used by the Library Specialist, and has no effect on the communication with your backup application. Chapter 2. IBM LTO Tape Library sharing and partitioning 53

82 Figure 2-20 Rename logical library Before we can work again with the library, we have to adjust the logical library configuration with the backup application that uses this library. If the storage slot capacity on the logical library is increased or decreased, the backup application must reflect this change. Refer to your backup application manuals for information on how to change an existing library configuration. Some applications like IBM Tivoli Storage Manager handle this easily; other applications like Legato NetWorker require that you run configuration wizards (NetWorker s jbconfig) in order to reflect the changes. Also, cartridges that belong to the logical library must be moved to the appropriate set of storage cells Partitioning the IBM 3584 with the Operator panel (ALMS not enabled) These are the steps: 1. From the library s Activity window, click MENU. The Main Menu displays (Figure 2-21). Panel 0002 Main Menu Library Status Manual Operations Settings Usage Statistics Vital Product Data Service BACK DOWN ENTER Figure 2-21 IBM 3584 Operator panel: Main Menu 2. Click UP or DOWN to highlight Settings, then click ENTER. The Settings menu displays. 3. Click UP or DOWN to highlight Configuration and click ENTER. The Configuration menu displays. 54 Implementing IBM Tape in Linux and Windows

83 4. Click UP or DOWN to highlight Advanced configuration and click ENTER (Figure 2-22). The library displays the message: If you continue with configuration the library will go offline. Click ENTER to continue. Panel 0101 Configuration Display Configuration Configure Library Advanced Configuration BACK DOWN ENTER Figure 2-22 IBM 3584 Operator panel: configuration 5. Click ENTER twice. The library displays the message: Searching for installed devices and may take several minutes to discover the physical configuration. The Physical Configuration panel displays, with the library s existing physical configuration (see Figure 2-23). The panel shows the total quantity of drives, storage slots, and I/O slots in the library s physical configuration. If the configuration includes both LTO and 3592 drives, the list will show them separately. Check that the displayed configuration matches the real configuration. If not, stop here, resolve the problem and start again. Panel 0102 Physical Configuration Total Frames: 3 Total LTO: 2 Total 3592: 1 Total Drives: 34 Total LTO: 22 Total 3592: 12 Total Storage Slots: 930 Total LTO: 571 Total 3592: 359 Total I/O Slots: 26 Total LTO: 10 Total 3592: 16 Configuration Mode: Advanced BACK DOWN ENTER Figure 2-23 IBM 3584 configuration display 6. Click ENTER. The library displays the message: Do you want to commit the new physical configuration? 7. Click YES to accept the new physical configuration and to set up any logical library configurations. The Set Logical Libraries panel displays indicating the type of media used by the logical library (Figure 2-24 on page 56). The following panels will not display if the ALMS feature has been enabled. Chapter 2. IBM LTO Tape Library sharing and partitioning 55

84 Panel 0105 Set Logical Libraries Media Type : LTO Frames 1-1 Number of Logical Libraries 1 Select 1-12 CANCEL UP ENTER Figure 2-24 IBM 3584 Operator panel: Set Logical Libraries 8. Specify the number of logical libraries that you want by clicking UP or DOWN to increase or decrease the value. 9. When the desired quantity of libraries displays, click ENTER. The Set Storage Slots panel displays (Figure 2-25). Panel 0106 Set Storage Slots Logical Library 1 Storage Slots 139 Select Cartridges in the following storage slots will now be part of logical library 2 Location Start: Location End: [F1,C07,R42] [F1,C07,R43] BACK UP DOWN ENTER Figure 2-25 IBM 3584 Operator panel: Set Storage Slots 10.Specify the quantity of storage slots that you want in the logical library by clicking UP or DOWN to increment or decrement the value. When the desired quantity of storage slots displays, click ENTER. The Set Drives panel displays (Figure 2-26 on page 57). 56 Implementing IBM Tape in Linux and Windows

85 Panel 0107 Set Drives Logical Library 1 Nunber of Drives 1 Select 1-12 BACK UP DOWN ENTER Figure 2-26 IBM 3584 Operator panel: Set Drives 11.Specify the quantity of drives that you want in the logical library by clicking UP or DOWN to increment or decrement the value. When the desired quantity of drives displays, click ENTER. 12.It then displays the Configuration Summary panel for Logical Library 1 (Figure 2-27). The panel contains the range of SCSI element addresses for the cartridge storage slots and the drives. Panel 0103 Configuration Summary Key:[F=Frame, C=Column, R=Row] Logical Library 1 Storage Slots: 0064 Elem Addr Range: Location Start: [F1,C01,R02] Location End: [F1,C03,R21] Drives: 001 Elem Addr Range: Location Start: [F1,R01] Location End: [F1,R01] Control Path Drives: [F01,R01] ENTER Figure 2-27 IBM 3584 Operator panel: Configuration Summary 13.Click ENTER to display the Configuration Summary panel for each logical library. After displaying the panel of the last logical library, the library displays the message: Do you want to commit the new logical configuration? 14.Click YES to accept the new configuration (the library may take several minutes to process). When finished, it displays the message: The configuration process is complete. Chapter 2. IBM LTO Tape Library sharing and partitioning 57

86 2.3 ALMS The Advanced Library Management System (ALMS), an optional extension to the IBM patented multi-path architecture (FC #1690), provides enhanced flexibility and capabilities for partitioning the IBM ALMS virtualizes the SCSI element addresses while maintaining the approach of the multi-path architecture and using SCSI-3 Medium Changer commands. Without ALMS all library references are based on the SCSI element address (location-centric). Partitioning is based on real cartridge slots and drive slots. With ALMS, there is no affinity between a real slot address and a SCSI Element address reported to the server and used by the server. Instead, there is now an affinity with the VOLSER (Volume Serial Numbers on the bar code label of the cartridge). ALMS allows the following new capabilities on the IBM 3584: Dynamic partitioning Storage slot pooling Flexible drive assignment Add / remove storage capacity transparent to any host application Configure drives or Lxx storage capacity without taking the library offline Virtualize I/O slots to automatically manage the movement of cartridges between I/O station slots and storage slots The IBM 3584 is compliant with the SCSI Medium Changer standard whether ALMS is enabled or not, and once enabled, ALMS is completely transparent to the application. The SCSI Medium Changer can be thought of as a location-centric interface. The application controlling a SCSI Medium Changer device specifies a source and destination location for each request to move a cartridge. The traditional SCSI library does not have control of the cartridge locations; instead, the SCSI library just acts on behalf of the server. Restriction: Only the IBM 3584 can be enabled for ALMS. FC #1690 is required to enable ALMS Functional description In this section, we give a functional description of the ALMS features. The information is based on the IBM TotalStorage UltraScalable Tape Library 3584 Advanced Library Management System Technology White Paper, by Lee Jesionowski, which can be found at: stem.pdf Storage slot virtualization The host-view of a cartridge location is known as the SCSI storage element address. Without ALMS, the storage element address maps directly to a specific storage slot after the library is configured. With ALMS enabled, a given storage element address is no longer associated with a specific storage slot. Instead, storage slots are virtualized by dynamically associating them with element addresses, as required. An element address will be associated with a storage slot, selected by the library, as cartridges are moved and inventoried. In the case of a storage element that is empty due to a move, that source element address will become un-associated. Association of storage element addresses is accomplished in a way that is completely transparent to the application software. The number of storage element addresses for a logical library (as reported to the host application software) is selectable by changing the Maximum Number of Cartridges setting for 58 Implementing IBM Tape in Linux and Windows

87 that logical library using the Web user interface (the Tape Library Specialist). For each logical library, the default value for Maximum Number of Cartridges is the number of addressable storage slots that are installed in the library for that cartridge type at the time that ALMS is first enabled or, after ALMS is enabled, at the time the logical library is created. The Maximum Number of Cartridges setting can be changed for each logical library, but the value must always be greater than or equal to the number of actual cartridges currently assigned to that logical library. It is possible to set Maximum Number of Cartridges to a value that is higher than the number of addressable storage slots installed at the time. This will allow future library capacity expansion to be transparent to the host application software. However, application performance may degrade slightly due to the greater number of addresses. Care should be taken to not exceed any license limitations of the host application software. The starting element address for storage slots of each new logical library will be x'400' (1024) plus the associated logical library number. For example, logical library 1 would start at x'401' (1025), logical library 2 would start at x'402', and so on (see Figure 2-28 on page 60). The reason they do not all start at x'401' is because some applications need to be able to differentiate different logical libraries from the same physical library. If there are logical libraries defined with a set of cartridge element addresses assigned, these same addresses will be kept when enabling ALMS. Thus, previously defined logical libraries will not follow the rule above. Drive assignment Using the ALMS flexible drive assignment capability, any drive in any position within any frame can be assigned to any logical library without creating any gaps in drive addresses. Drive (data transfer) element addresses will still be mapped to specific drive locations when the drive is assigned, but any drive location may now be assigned to any logical library (intermix supported) using the Tape Library Specialist. Each drive added to a logical library will be assigned to the lowest available element address, regardless of drive location. When ALMS is first enabled, the Data Transfer Element (DTE) addresses of all installed/assigned drives are not changed from their previous values. However, after ALMS is enabled, the DTE addresses for any newly installed/assigned drives no longer depend on the drive s position. Instead, the DTE address for any newly installed or assigned drive is determined by the sequence in which the drive is assigned to each logical library. With ALMS enabled, drives are assigned to logical libraries using the Drive Assignment page of the Tape Library Specialist. Using this interface, the DTE address for the first drive assigned to a new logical library is 257 (x 101 ) (see Figure 2-28 on page 60). The DTE address for any other drive assigned to a logical library is based on the next available DTE address in that particular logical library. The next available DTE address is the lowest available DTE address after the starting DTE address (this will fill any gaps that are created when drives are unassigned/removed from a logical library). When a drive is un-assigned from a logical library using the Web interface, only that DTE address is made available for future usage; no other DTE addresses are affected. By using the dynamic Drive Assignment capability of ALMS, any drive in any position within any frame is available to be assigned to any logical library without creating gaps in DTE addresses. Chapter 2. IBM LTO Tape Library sharing and partitioning 59

88 Library LL 2 Storage Pool CONTROLLER ALMS 80 Slots DRIVE 1 DRIVE 2 free Host 1 Drive SCSI Element: 257, 258 Storage SCSI Element: LL 3 Storage Pool 200 Slots DRIVE 1 DRIVE 5 free free SAN Host 2 Drive SCSI Element: 257,258 Storage SCSI Element: LL 1 Storage Pool DRIVE 4 DRIVE 1 DRIVE 3 Host 3 Drive SCSI Element: Storage SCSI Element: Slots DRIVE 2 DRIVE 2 Figure 2-28 IBM 3584 with ALMS Shared drive assignment Some users require the ability to easily share a drive on an exception basis, for example, a drive might be required for a once-a-month job or as a temporary replacement for a failed drive. The Tape Library Specialist Drive Assignment page supports the option to share a drive between multiple logical libraries, to a maximum of 10. The drive will be assigned a DTE address in more than one logical library. Note that the DTE addresses that are assigned to a shared drive may differ by logical library. Therefore, each logical library will consist of dedicated drives and shared drives. Each logical library will map a drive element address to the location of both dedicated and shared drives. This option reduces the requirement to configure and unconfigure the tape drive every time it is needed or not. The Drive Assignment Web screen supports the following point-and-click capabilities, which are nondisruptive to other logical libraries: Assign the drive Remove the drive assignment Reassign the drive When a cartridge is mounted in a shared drive, the library will only accept a de-mount command requested via the source logical library; any de-mount command requested via other logical libraries will be rejected. However, the data path to the tape drive itself is not protected by the library. Therefore, the client must make sure that shared drives are not accessed by the wrong application via the data path. To ensure this, one option is to use the SCSI reserve / release option on open and close. The device driver together with the application handles this. When opening a tape drive, the application initiates a SCSI reserve through the tape device driver. No other server can access the tape drive at this point (except for commands such as Inquiry). This ensures 60 Implementing IBM Tape in Linux and Windows

89 that data is not overwritten by any other host or application. After the device is closed, the application must send a SCSI release to the tape drive. Most applications handle this, but it should be confirmed with the backup software provider. SAN zoning can also be used to prevent access to the same tape drives by different servers. When a tape drive is shared by applications, any application using the drive has no knowledge of the other applications sharing the tape drive. For example, if there is already a cartridge loaded and in use by application A, application B does not know it and tries also to mount a cartridge in the same drive. Application B would in that case get a failure, and the job application B was executing would fail. Some applications periodically scan all the tape drives and if they recognize that there is a cartridge mounted without initiation from the application itself, the application will consider this tape drive offline. In any case, we recommend to not allow multiple applications to use shared tape drives concurrently. In other words, set tape drives offline (or in service mode) from the application whenever it is not used by that application. The sharing option is mainly intended for environments where some drives are just needed once in a while and must be pre-configured for the application. Attention: An application that occasionally leaves cartridges in drives or that periodically scans all configured drives will not be a good candidate for sharing drives between logical libraries. Eliminates downtime for total capacity changes With ALMS enabled, the total library capacity (number of addressable storage slots) can be changed transparent to each application, as the Maximum Number of Cartridges value is not impacted by changes to the number of storage slots. The additional storage slots are simply more slots the cartridges can be moved to upon insertion. Further, using the new Intermediate and Full Capacity on Demand capabilities of the 3584 Model L22 and L52, no downtime is required at all for the change to total L-frame capacity. Storage slot pooling ALMS allows logical libraries to be added or deleted nondisruptively. The minimum logical library simply has a name it can be thought of as a file which initially has no contents. Drives can be placed in this file by using the Drive Assignment page of the Tape Library Specialist Web interface. Cartridges can also be placed in this file, based on their volume serial (VOLSER) numbers and by using one of the following methods (in priority order): Migration from static partitioning (UI enablement of ALMS) Cartridge assignment policy (automatic at time of insertion) Insert notification (Operator panel selection at time of insertion) Software application move from I/O Station (based on source of command) Manual assignment using the Tape Library Specialist The VOLSER assignment and physical location of cartridges are stored in non-volatile RAM (both primary and backup copies). All storage slots are first come, first served to each logical library based on cartridge insert operations. Therefore, storage slots are pooled as a shared resource so that changes to the capacity allocation for each logical library do not require any downtime or administrator involvement at all. Indications of a full or nearly full physical library will continue to be provided via the Operator panel, Tape Library Specialist, and SNMP traps. Chapter 2. IBM LTO Tape Library sharing and partitioning 61

90 Cartridge Assignment Policy The cartridge assignment policy (CAP) of the IBM 3584 allows you to assign ranges of cartridge volume serial (VOLSER) numbers to specific logical libraries through the Tape Library Specialist. When a cartridge is inserted into the I/O station, the cartridge assignment policy will be used to attempt to associate the cartridge with a logical library. If the cartridge is not in the CAP and insert notification (see Insert notification on page 62) is enabled, you can assign the cartridge to a logical library by using the insert notification process on the library s Operator panel or keep the cartridge as unassigned and assign it later by using the Tape Library Specialist. If the insert notification feature is not enabled, and the cartridge was not in the CAP, the cartridge will eventually be available to all hosts. Unassigned cartridges can also be assigned to a logical library by creating a new VOLSER range, then performing a manual inventory to assign those cartridges through the cartridge assignment policy. The cartridge assignment policy is media-type specific. As such, it is based on the six most significant characters of the cartridge label and the ranges of VOLSERs do not include the media-type indicator (L2, L3, JA, and so forth). This means that two identical labels (except for the media-type indicator) could be assigned to two different logical libraries, for example, libraries that contain Ultrium or 3592 drives. Note: The cartridge assignment policy does not reassign an assigned tape cartridge. To reassign a cartridge, use the procedure for assigning cartridges to a logical library. Insert notification Insert notification is an option that enables the IBM 3584 to monitor the I/O station for any new media that does not have a logical library assignment. This feature can be enabled through the Operator panel or through the Tape Library Specialist. With Insert Notification enabled, when new media is detected, the Operator panel displays a message that asks you to select a logical library. Any unassigned cartridges in the I/O station will be assigned to the logical library that you select (and all other logical libraries will not be able to access the cartridges). The library includes an option to defer any assignment and there is a timeout period when the deferral will automatically take effect. Virtual I/O The IBM 3584 has input/output (I/O) stations and I/O slots that allow you to import and export up to 32 cartridges at any given time. The I/O slots are also known as import/export elements (IEEs). Virtual I/O slots increase the quantity of available I/O slots by allowing storage slots to appear to the host as I/O slots. Storage slots appearing to the host as I/O slots are called virtual import/export elements (VIEEs). The goal of virtual I/O slots is to reduce the dependencies between the system administrator and library operator so that each performs their import and export tasks without needing the other to perform any actions. With virtual I/O slots, the library automatically moves cartridges from the I/O stations to physical storage slots and from physical storage slots to the I/O stations. With virtual I/O slots, you can configure up to 255 VIEEs per logical library. Each logical library will have a unique VIEE address space that is not accessible by other logical libraries. The number of VIO (virtual I/O) slots can be set using the Max VIO Slots button for the logical libraries (see Figure 2-33 on page 67). New logical libraries will, by default, be assigned the maximum number, while logical libraries defined before ALMS is enabled will initially have the number of physical I/O slots in the library. Before virtual I/O slots, the IEE space consisted of physical I/O station slots (10, 30, 16, or 32, depending on the frame model type) that were shared by all logical libraries. If the application or system administrator did not explicitly import the cartridges from the I/O station into library 62 Implementing IBM Tape in Linux and Windows

91 storage, the cartridges would remain in the I/O station. This reduced the number of IEEs available to process imports and exports. With virtual I/O slots, when cartridges are inserted into the I/O station, the library will work with the cartridge assignment policy or insert notification to assign a cartridge to the correct logical library VIEE space, and cartridges will automatically be moved into library storage slots. If there is no cartridge assignment policy assigned, and insert notification is disabled for a particular cartridge, then that cartridge will be inserted into the VIEE space of all logical libraries and automatically be moved into a library storage slot. The VIEE temporarily takes on the attributes of an IEE until a host moves the cartridge into a storage element (StE). If a cartridge cannot be assigned, this will be reported as Assignment Pending. This can occur if the assigned logical library has no available VIEE slots, or if all of the logical libraries do not have a common VIEE to share. To resolve this, either free up VIEE addresses so this is available in all libraries, or make a specific assignment of this cartridge to a logical library. When the host move occurs, if the cartridge is in a storage slot, no physical move is needed and the element transitions from a VIEE to an StE. Similarly, when a host exports a cartridge from an StE, the physical storage slot will be reported as a VIEE without moving the cartridge to the I/O station. The library will monitor when free space is available in the I/O station and move exported cartridges at the library s convenience. As seen in Figure 2-33 on page 67, there is also a button for Hide/Show Exports. Show Exports is the default, and this will show a VIEE inventory of cartridges exported from the logical library. These cartridges will then fill one of the VIEE slots for that logical library. Export Complete will be shown when the exported cartridge is physically in an I/O station slot. Selecting Hide Exports will move the exported cartridges to a library maintained export queue, and the VIEE is free immediately for other import/exports, and the exported cartridge will disappear from the host application s inventory data. Exporting a cartridge will be reported as Export in Progress if there is no available VIEE, and will not complete until one is available. With Hide Exports, this situation will not occur. Support for virtual I/O slots is provided at the latest released level of library microcode (5360) and will be enabled by default when ALMS is enabled. For existing clients whose IBM 3584 has already enabled ALMS, a newer level of library microcode that supports virtual I/O Slots will be required and virtual I/O slots will need to be manually enabled Configuring ALMS The ALMS Feature Code #1690 is required for ALMS operation. This feature code provides a License Key that must be installed through the Operator panel (unless it was part of the initial order and was thus already installed by manufacturing). Enter ALMS license key To enter the ALMS license key, do the following: 1. From the library Operator panel, select MENU Service Library Firmware Update Features ENTER. The Features screen displays a list of features, including the Advanced Library Management System. Select it and select ENTER. 2. For each character of the license key, select UP or DOWN to enter the value that you want. 3. Select ENTER. The Features screen now states Advanced Library Management Feature Is Installed. 4. Select BACK until you return to the main screen. Chapter 2. IBM LTO Tape Library sharing and partitioning 63

92 Enable ALMS 1. After the License Key is installed, you can enable ALMS using the Tape Library Specialist. Enter the library s IP address as a URL in your browser. If login security has been enabled, there will be a login prompt, and then you will see the welcome screen with the message that ALMS is disabled at the bottom (see Figure 2-29). Figure 2-29 Welcome screen before enabling ALMS 2. On the left hand side, select Manage Library Enable ALMS. This will display a warning and a specific selection to Enable ALMS (see Figure 2-30). Figure 2-30 Enable ALMS Note: You can enable or disable ALMS in the IBM 3584 using the Tape Library Specialist, but not the Operator panel. 64 Implementing IBM Tape in Linux and Windows

93 When ALMS is enabled, you can easily: Name, add, and remove logical libraries Reassign a cartridge to another logical library Change the maximum quantity of cartridges that can be assigned to a logical library Add, remove, and edit ranges of volume serial (VOLSER) numbers (also known as cartridge assignment policy) Assign shared drives, change control path drives, unassign drives, and assign new drives without using manual configuration methods ALMS can also be disabled, but this should done with care. After ALMS is enabled, the screen shown in Figure 2-30 on page 64 has the option Disable ALMS instead. Important: When you disable ALMS, the library returns to an unconfigured state and all cartridge and drive assignments are lost. You must manually reconfigure the library. However, switching between definitions, the library will use the previous definitions as a basic starting configuration. Attention: If you manually configure the library, your changes may result in the loss of cartridge or logical library assignments, cartridge assignment policies, maximum cartridge assignments, and logical library names. When using ALMS, cartridges belong to one logical library based on their VOLSER. Without ALMS, logical libraries are based on physical boundaries within the library. This means that after disabling ALMS, you might have to move several cartridges. When switching from an environment with ALMS disabled to one with ALMS enabled, the library will use the previous definitions as a basic starting configuration. The library will perform an inventory operation similar to when the frame door has been opened. The library status during this inventory process will show a cartridge assignment status of pending (see Figure 2-31 on page 66). Create and manage logical libraries 1. From the Tape Library Specialist (Figure 2-29 on page 64), select Manage Library by Logical Library and on the next screen, Figure 2-31 on page 66, click Create. Chapter 2. IBM LTO Tape Library sharing and partitioning 65

94 Figure 2-31 Create Logical Library 2. Type a unique name (up to 15 characters) for your new logical library (in our case, Redbook2) and select a Media Type (LTO or 3592) for this logical library, as in Figure Click Apply. You cannot mix LTO and 3592 media types in one logical library, but you can have different LTO generations in one logical library, for example, LTO 2 and LTO 3. Figure 2-32 Create Logical Library 3. The library created will appear in the Manage Logical Library display, as in Figure 2-33 on page 67, but with no cartridges or drives assigned; these columns show a zero count. Therefore, after creating a new logical library, you need to add cartridge pools and tape drives. 66 Implementing IBM Tape in Linux and Windows

95 Figure 2-33 Added new Logical Library Cartridge assignment policy A new logical library does not have any cartridges assigned to it. You can assign single cartridges that are currently unassigned, or that are assigned to another logical library (the cartridge will then be removed from this logical library). Or, you can assign a pool of unassigned cartridges (establish a cartridge policy) to the logical library. Such a cartridge assignment policy defines a range based on the VOLSER. 1. To assign a cartridge assignment policy, on the left hand side, select Manage Cartridges Cartridge Assignment Policy. The Cartridge Assignment Policy window appears (see Figure 2-34). Figure 2-34 Cartridge assignment policy main screen Chapter 2. IBM LTO Tape Library sharing and partitioning 67

96 2. Choose the logical library to which you want to assign the cartridge policy, enter the starting and ending VOLSER for the range to be defined (see Figure 2-35), and click Apply. Figure 2-35 Cartridge Assignment Policy assignments 3. All unassigned cartridges and all new inserted cartridges within the specified range now, by definition, belong to the specified logical library. However, new cartridges have to be inserted, or there must be a re-inventory to have existing unassigned cartridges in this range assigned to the logical library. Previously assigned cartridges within the specified range remain untouched. Cartridge assignment A single cartridge can be assigned to a specified logical library as well, or even be moved between libraries. 1. To begin, select Manage Cartridges Data Cartridges (see Figure 2-36). Select the frame or logical library, select one or more cartridges to assign, and click Assign. Figure 2-36 Assign Data Cartridge menu 68 Implementing IBM Tape in Linux and Windows

97 2. Select the library to which you want to assign the cartridge(s) (see Figure 2-37). Click Next to complete the operation. The cartridge will then logically be moved to the new library. Figure 2-37 Assign cartridge to a logical library 3. Figure 2-38, the Data Cartridges menu, shows that the cartridge has moved to the new library. However, the cartridge remains in the same physical slot as before. Figure 2-38 Cartridge list In our example, we now have cartridges assigned to the logical library, but no tape drives have been assigned. With ALMS, you can configure a logical library without any drives assigned to it. A driveless logical library may be used for: Tape vaulting: Move the cartridge to a location that cannot be accessed by the application. Use as a scratch pool. Chapter 2. IBM LTO Tape Library sharing and partitioning 69

98 Assign drives The flexible drive assignment option supports the following capabilities: Assign drive (nondisruptive to other logical libraries) Unassign drive (nondisruptive to other logical libraries) Reassign drive (nondisruptive to other logical libraries) Assign drive to multiple logical libraries Change control paths Although the drive assign procedure is nondisruptive, the application or server to which the drive is assigned must be configured. This server or application configuration may not necessarily be nondisruptive. In addition, a reconfiguration of the SAN may be needed. At least one assigned drive must have the control path enabled. Therefore, the first assigned tape drive will get the control path enabled by default. You may, however, enable or disable control paths for your drives. Drives with a control path enabled cannot be shared with other logical libraries. You cannot assign LTO and IBM 3592 tape drives to the same logical library. Be sure that the drives you are working on do not have any cartridges loaded. The Tape Library Specialist will not allow you to change any assignment of tape drives with a cartridge loaded. Therefore, we suggest first running a manual inventory to be sure that there is not a forgotten cartridge in any drive. To assign tape drives, select Manage Drives Drive Assignment. In the introduction window, you can select specific drives or logical libraries, or a list of the full drive assignment. If you select the last option, the full assignment displays as in Figure 2-39 on page 71. On the drive assignment panel, you can easily assign and unassign tape drives to a logical library. On the left hand side of the screen, you can see all available tape drives identified by their WWN. At the top, you see all the logical libraries. The first column is called Unassigned. All unassigned drives (such as newly installed drives) belong to this column. By simply clicking the check boxes, you can easily assign tape drives to logical libraries. After you have completed your settings, click Apply to make the changes effective. 70 Implementing IBM Tape in Linux and Windows

99 Figure 2-39 Drive Assignment Tape drives with control path enabled are indicated by the icon shown in Figure Figure 2-40 Drive with control path The first tape drive assigned to a logical library automatically gets the control path enabled; if you want to enable more control paths, click the placeholder for the control path icon of the selected drive. If you want to delete a tape drive from one logical library, you have to set this tape drive to unassigned by checking the Unassigned check box for this tape drive. We do not recommend that you assign a tape drive to multiple logical libraries unless required. If you need to share a tape drive, follow the recommendations given in Shared drive assignment on page 60. One drive may be shared by a maximum of 10 logical libraries. In the example in Figure 2-39, all logical libraries and applications need at least one tape drive to fulfill their backup jobs. Therefore, we assigned at least one tape drive to each logical library. In addition to the minimum required tape drive, we assigned one shared tape drive to each logical library. For all applications, we configured at least two tape drives for use, but set the shared tape drive as offline, in service, or unavailable, depending on the application. This enables us to easily use a shared tape drive (by setting it online, out of service, or available from the application) whenever it is needed; for example, if one dedicated tape drive becomes defective, or one application needs temporarily more tape bandwidth due to additional workload (additional restores). Chapter 2. IBM LTO Tape Library sharing and partitioning 71

100 Because the application needs to know the SCSI element address of the drive for configuring the library, check the SCSI element address of all tape drives by selecting Manage Drives Drive Summary. This displays the drive information (see Figure 2-41). Notice that this is now the virtualized element addresses, and that each logical library may show the same element address. Figure 2-41 Drive details Alternatively, if you let the cursor hover over the assigned element as in Figure 2-42, you will get a small pop-up identifying the element number for that drive. Figure 2-42 Display drive element number By default, all drives will be assigned the lowest available SCSI element address, which for Redbook1 above will be elements 257, 258, and 259 (the shared drive). It is possible to be creating gaps in the assignment. If Redbook1 drive 2 is set to unassigned, and we try to Apply, we will get a warning message that there may be an element gap (see Figure 2-43 on page 73). 72 Implementing IBM Tape in Linux and Windows

101 Figure 2-43 Drive gap warning Avoid any gaps in the drive assignment. Gaps may easily be removed by simply unassigning and then reassigning the drive with the highest SCSI element address until all gaps are filled. Gaps in the drive SCSI element address will cause configuration problems on some backup applications like EMC Legato NetWorker or VERITAS BackupExec. Change the maximum number of storage slots Since ALMS virtualizes the SCSI element address of the storage slots, the library is able to report any desired amounts of storage slots. Of course the number reported cannot be less than the actual number of cartridges in the library. The library will allow the user to select a 16-frame maximum limit (6887). The default value is based on the physical slots currently in the library. In Example 2-1, we want to set the maximum reported number of storage slots. Currently, there are 175 slots available (because we are working on a one-frame library with a total of 175 slots), but there are just two slots assigned and the assigned maximum is set to 15 for the logical library Tucson. Therefore, we must set the maximum to a number equal or greater than two (we will set it to 80). Here we are using the NTUTIL/IBMtapeutil program, which is part of the IBM-supplied device driver. For more information about NTUTIL/IBMtapeutil, see 3.5.1, Testing the library with NTUTIL on page 122 and 4.4.1, Installing the IBM tape device driver and utilities on page 203. Example 2-1 Reported storage slots # IBMtapeutil -f /dev/smc1 elementinfo Getting element information... Number of Robots... 1 First Robot Address... 1 Number of Slots First Slot Address Number of Import/Exports First Import/Export Address Number of Drives... 1 First Drive Address To change the Maximum Number, select Manage Logical Library; select the logical library and click Maximum Cartridges (as in Figure 2-31 on page 66). Warning: Changing the maximum settings for a logical library may interrupt drive and library activities and require reconfiguration of the host applications for the selected logical library. A window similar to Figure 2-44 on page 74 appears. Enter the new maximum number of cartridges and click Apply. Chapter 2. IBM LTO Tape Library sharing and partitioning 73

102 Figure 2-44 Change maximum number of cartridges Now the library reports the new maximum storage slots of 80, as shown in Example 2-2. Example 2-2 Reported storage slots #IBMtapeutil -f /dev/smc1 elementinfo Getting element information... Number of Robots... 1 First Robot Address... 1 Number of Slots First Slot Address Number of Import/Exports First Import/Export Address Number of Drives... 1 First Drive Address You can also look at these details by selecting Details in the Logical Library menu (Figure 2-31 on page 66). This will then display the window shown in Figure Figure 2-45 Logical Library details This change is nondisruptive for the library operation, but not necessarily for your backup application. For example, with NetWorker, you must run jbconfig, and with IBM Tivoli Storage Manager, you must halt and re-start the server. The ability to change the maximum number may helpful if: You just have a license for a smaller library. You expect capacity growth, which will force you to enlarge your library physically over time, but want to avoid configuration changes in your application. Therefore, on the first set up, configure your logical library with a greater number of logical slots to avoid an outage later on, because you would then have to reconfigure the application. 74 Implementing IBM Tape in Linux and Windows

103 However, a large number of reported storage slots may decrease the application performance in working with the library (such as an inventory or audit library, which takes longer from the application point of view). Migration from partitioning without ALMS to ALMS A library that was previously installed without ALMS can be upgraded to ALMS by enabling the ALMS license key. The license key must be entered using the Operator panel (see Enter ALMS license key on page 63). When enabling ALMS, it reuses the existing library configuration. This means that you get the same number of logical libraries. Cartridges and tape drives that were already assigned to the logical library remain assigned to the same logical library. Tape drives will get the same SCSI element address (even if there was a gap in the SCSI element address) and all cartridges will get the same SCSI element address as in the non-alms definition. However, the storage element address of the storage slots for new logical libraries will change, as described in Storage slot virtualization on page 58. For the first logical library, the storage address begins with 1025, for the second one with 1026, and so on. Adding a new logical library (Redbook2) to the three logical libraries that were already defined without ALMS means that this library will be number four, and accordingly start with a cartridge element address of Also, in libraries with mixed media, the reported number of maximum storage slots may change to the number of currently installed cartridge slots. Consequently, when you enable ALMS, your application may also need to be reconfigured. For some applications, such as the IBM Tivoli Storage Manager, you just have to stop and restart the server; for other applications, such as EMC Legato NetWorker, you have to run a configuration wizard (run jbconfig). You can enable ALMS by using the Tape Library Specialist. Select Manage Library Enable ALMS (refer Enable ALMS on page 64). To illustrate how ALMS changes the configuration of the logical libraries, we show the detailed information for the logical library named Redbook1 in Figure 2-46 and Example 2-3 on page 76. It indicates three tape drives with SCSI element addresses 257, 258, and 259. The storage element address range is 1025 to 1104 (80 storage slots). The physical library has 175 storage slots in total. Figure 2-46 Detailed info before ALMS is enabled Chapter 2. IBM LTO Tape Library sharing and partitioning 75

104 Example 2-3 Element info from logical library Redbook 1 # IBMtapeutil -f /dev/smc4 elementinfo Getting element information... Number of Robots... 1 First Robot Address... 1 Number of Slots First Slot Address Number of Import/Exports First Import/Export Address Number of Drives... 3 First Drive Address Then we enable ALMS. In Figure 2-47 and Example 2-4, we show again the detailed view of the logical library. The drive element addresses are the same as before, but the storage element addresses were changed. Because it is seen as the first logical library, the storage element addresses begin with With ALMS, the physical limitation of 175 cartridge slots is removed, and we have assigned 160 slots to this one logical library. There is now also a listing of the default 30 Virtual IO elements. Figure 2-47 Detail Info after ALMS enabled Example 2-4 Element info after ALMS enabled # IBMtapeutil -f /dev/smc4 elementinfo Getting element information... Number of Robots... 1 First Robot Address... 1 Number of Slots First Slot Address Number of Import/Exports First Import/Export Address Number of Drives... 3 First Drive Address Using ALMS Because ALMS virtualizes the SCSI element addresses of the cartridge slots, some library commands will not generate a physical action on the library. If you issue a move media command, the library replies with a new SCSI element address, even though the cartridge was not moved. For example, suppose that we want to move the cartridge stored in Frame 1, Column 1, Row 19 (see Figure 2-48 on page 77) from SCSI element address 1028 to a 76 Implementing IBM Tape in Linux and Windows

105 vacant SCSI element address. Select Manage Cartridges Data Cartridges and then select Move to move the cartridge. Figure 2-48 Inventory before move medium Now, we check the inventory of the library again (see Figure 2-49). We see that the SCSI element address has changed to 1032, but the cartridge is still in the same physical location of Frame 1, Column 1, Row 19. Figure 2-49 Inventory after moving cartridge On a library without ALMS, you have to run a library inventory every time after moving some cartridges manually to get the application in a state consistent with the library. With ALMS, Chapter 2. IBM LTO Tape Library sharing and partitioning 77

106 this may no longer be necessary, as ALMS always tries to assign the same SCSI element address to the cartridge, even though the cartridge was moved manually. Because ALMS is based on the affinity between VOLSER (barcode label) and the reported SCSI element address, you have to make sure that the barcode label is readable. The library tries to keep the same SCSI element address for an unreadable barcode label if this cartridge is stored in the same physical slot. But, if the cartridge was moved manually, and the library does an inventory, a cartridge with an unreadable barcode label is placed in an unassigned status. The same is true if you work with unlabeled cartridges (no barcode label): As long as you do not move this cartridge manually, the library tries to assign a SCSI element address. If you move such a cartridge manually, the cartridge will be placed in an unassigned status. The same happens with cartridges having duplicate barcode labels. Using duplicate barcode labels is generally not supported, and can easily lead to confusion. It is possible that the storage capacity of the library, as reported by each logical library, may exceed the physical storage capacity of the library. As such, it is possible to run out of storage space while still reporting available space to a host. SNMP and Operator panel messages will notify the client as the library approaches near full capacity. In addition, if cartridges are placed in the I/O station when a library has reached its capacity, the cartridges will be marked inaccessible to all hosts to prevent the condition where the host tries to move the cartridge to storage that does not really exist. When ALMS is enabled, auto clean is automatically enabled, and there will be no mechanism to disable it. Cleaning cartridges are never associated to a logical library, so there will be no host awareness that they exist in the library. Static partitioning cannot be used when ALMS is enabled. The partitioning for the entire library is either static or dynamic. 78 Implementing IBM Tape in Linux and Windows

107 3 Chapter 3. Basic IBM tape setup for Windows This chapter provides detailed information about the basic setup of LTO drives, the IBM TotalStorage 3592 Tape Drive, and LTO libraries for Windows 2000 and 2003, including: HBA drivers installation and update Device and library drivers installation and update Removable Storage Manager and Windows 200x backup with LTO Using the Tape Library Specialist for the IBM Tape Libraries IBM U Tape Library Specialist IBM 3582 Tape Library Specialist IBM 3583 Tape Library Specialist IBM 3584 Tape Library Specialist Device, library, and RMU firmware upgrade Drive upgrade using the LTO-TDX tool At the end of this chapter, you should be able to understand and implement the tasks required to: Install and configure the required Host Bus Adapter drivers. Install the required device drivers. Understand the use of the IBM Tape Library Specialist product. Upgrade the library and drive microcode. Test basic library operation. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 79

108 3.1 IBM tape installation overview The basic setup for IBM tape devices involves: Planning Installing the adapter card and driver For SCSI Adapter installation, see 3.6, Windows 200x SCSI adapter installation on page 137. For Fibre Channel HBA installation, see 3.7, Windows 200x Fibre Channel HBA driver installation on page 142. Attaching the library and drives Installing the IBM Device Driver (see 3.2, Installing IBM tape device drivers for Windows 2000 on page 82, 3.3, Installing IBM tape device drivers for Windows 2003 on page 91, and 3.4, Control Path Failover on page 103). Configuration and testing The IBM Ultrium Tape and Medium Changer Device Drivers are designed specifically to take advantage of the features provided by the IBM Ultrium Tape Drives and Medium Changer Devices. The objective is to give applications access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as cartridge mount and dismount), as well as the advanced functions needed by full tape management systems. Note: Ultrium drives and libraries usually are used with vendor-provided software applications. These may work with the IBM-provided device drivers, their own provided device drivers, or even native operating system device drivers for the tape drive and medium changer (or some combination of these, for example, the IBM drive device driver and application-provided medium changer driver). For correct operation, follow the specific implementation instructions for the software that you are installing to determine if the IBM-supplied device drivers are suitable for your installation. In Part 2, LTO libraries and backup software on page 243, we describe specific implementation for some of the most common application software for Windows 200x. For further information and specific installation instructions for Windows 200x, refer to IBM Ultrium Device Drivers: Installation and User s Guide, GA The device drivers allow the operating system and the application software to manage tape devices and medium changers to automate the use of the tape media Determine requirements To check if your environment has the correct operating system level, combined with the appropriate server and the supported Host Bus Adapter (HBA) and SAN fabric components, check the following link: 80 Implementing IBM Tape in Linux and Windows

109 IBM tape libraries and devices are generally supported, at the time of writing this Redbook, on Windows 2000 build 2195 (Service Pack 2) or later, or Windows 2003 build 3790 or later. Even though device driver media was shipped with your IBM tape hardware, we recommend that you always download the latest version from the appropriate Web site: ftp://ftp.software.ibm.com/storage/devdrvr/windows/win2000/ ftp://ftp.software.ibm.com/storage/devdrvr/windows/win2003/ Beginning with V , the IBM Tape device drivers for Windows 2000 and Windows 2003 have been converged into a single install package with common inf files. Use this single package to install a driver on either operating system. The system detects which version of the driver binary files to install. The 3592 and Ultrium drivers have also been converged. For Windows 2000, the file to download is named IBMTape.W32_xxxx.zip, where xxxx is the version number. Always download the latest version unless specifically directed otherwise by IBM Support. For Windows 2003, the file to download is named IBMTape.Wnn_xxxx.zip, where nn is either 32 or 64 and xxxx is the version number. Always download the latest version unless specifically directed otherwise by IBM Support. Also, consult the readme file located in the same download directory for any additional considerations. The readme file is IBM.W200x.Readme.txt. Note: For Windows 2000, before V , there were separate files for the LTO and the 3592 drivers. The driver file name for the LTO drives was IBMUtrium.Win2k_xxxx.zip, where xxxx was the version number and the readme file was IBMUltrium.Win2K.Readme.txt. The 3592 Enterprise Tape Drive was named IBMMag.Win2K_xxxx.zip, and the readme file was IBMMag.Win2K.Readme.txt. Note: A Windows certified version of the LTO device driver for 3580 drives is also available. The files are contained in a folder named LTO_WHQL_Cert. For Windows 2000, the file to download is named LTOCertW32_xxxx.zip, where xxxx is the version number. For Windows 2003, the file to download is named LTO_CertWnn_xxxx.zip, where nn is either 32 or 64 and xxxx is the version number. The readme file is named LTOCert.Readme.txt. Always download the latest version unless specifically directed otherwise by IBM Support. This certified driver will operate only IBM Ultrium 3580 tape drives, generations 1, 2, and 3, installed in a tape library or running standalone. The driver that operates other IBM tape drives, such as the IBM 3590 and 3592, has not been certified, nor has the driver that operates IBM tape libraries, including the IBM 3582, 3583, and 3584 libraries Note: There is a debug version of the Ultrium drivers available with the installed package located in the checked directory. The checked directory can be found in the directory where the device drivers were unpacked. This version may be coupled with a debugging tool to identify and resolve any issues encountered when installing the device driver. For more information regarding the use of the debug driver version, refer to the IBM Ultrium Device Drivers: Installation and User s Guide, GA Chapter 3. Basic IBM tape setup for Windows 81

110 3.2 Installing IBM tape device drivers for Windows 2000 Attention: If your library has Control Path Failover (feature #1680) installed and you want to enable it for Windows 2000, follow the instructions in 3.4, Control Path Failover on page 103. If the LTO Tape Library is physically attached, Windows 2000 will attempt to automatically install the drivers upon boot. The Driver Installation Wizard will appear and will request details regarding the location of the drivers and information files. The IBM tape library may be hot-plugged into the SCSI or fibre adapter; in this case, you may perform a hardware scan from Device Manager, as shown in Figure 3-1, to detect the added devices and initiate the Device Driver Install Wizard. Figure 3-1 Performing a hardware scan Execute the following steps: 1. Download and extract the latest IBM tape Device Drivers for Windows Shut down the system. 3. Attach the library. 4. Restart the system. 5. Install the device drivers. Downloading the drivers Obtain the latest drivers for IBM tape libraries, as described in 3.1.1, Determine requirements on page 80. Extracting the drivers The IBM tape Device Driver will be downloaded as a zipped package. Unzip the package (we used the directory C:\IBMdrv\IBMUltrium\6082), as shown in Figure 3-2 on page Implementing IBM Tape in Linux and Windows

111 Figure 3-2 Extracted device driver package contents Uninstalling the previous version If an older version of IBM tape Device Driver is already installed on the system, uninstall it first. See Removing the IBM tape device driver from the system (un-install) on page 135 for more details Installing the medium changer device driver This step is not required if you have installed an IBM 3580, because it does not have a medium changer. In this case, you can go straight to 3.2.2, Installing the tape drive device driver on page The devices, which have been attached and for which Windows 2000 has no device driver, should appear as unknown devices. If the devices do not appear, then carefully check the preceding steps (is the right cable being used, LVD/HVD issues, correct SCSI adapter card, and so on). Right-click My Computer, select Manage, open Device Manager and select Medium Changer. You should see an Unknown Medium Changer Device or an entry with a library model number (for example, IBM 3584-L22). Right-click it and select Properties (Figure 3-3 on page 84). Chapter 3. Basic IBM tape setup for Windows 83

112 Figure 3-3 Device Manager window: pre-configured 2. Click the Driver tab, and then click Update Driver (Figure 3-4). Figure 3-4 The driver tab of the medium changer s properties box 3. You will see the Upgrade Device Driver window (Figure 3-5 on page 85) prompting you to search for a driver or display a known list of drivers for installation. Click the Search option, and then click Next. 84 Implementing IBM Tape in Linux and Windows

113 Figure 3-5 Device Driver Wizard install options 4. Check the box Specify a location and click Next, as in Figure 3-6. Figure 3-6 Device driver location search options 5. The path to the location of the drivers displays, as in Figure 3-7. Specify the directory where you extracted the downloaded driver.zip file and click OK. Figure 3-7 Specify a location Chapter 3. Basic IBM tape setup for Windows 85

114 6. The wizard locates a device driver, as shown in Figure 3-8. If this is the driver version you want to install, click Next; otherwise, select the box labelled Install one of the other drivers and click Next. Typically, the latest driver version is installed unless there is a specific reason not to install it, such as for ISV application support issues. Figure 3-8 Search results 7. The Device Driver Wizard proceeds to install the device driver and informs you when the installation is complete, as shown in Figure 3-9. Figure 3-9 Device Driver Wizard completion Installing the tape drive device driver The tape drive device driver installation basically follows the same steps as the medium changer installation. You will need to install the driver for each individual tape device if using a multi-drive library like the IBM 3583 or IBM Even when the names are different for each type of drive, the installation procedures are the same. If not otherwise noted, follow the same procedures. Note: In Version , the tape device drivers for LTO and 3592 tape drives were converged into a single file. Please refer to 3.1.1, Determine requirements on page Implementing IBM Tape in Linux and Windows

115 1. Right-click My Computer on the Windows desktop and select Manage. Open Device Manager and expand Other Devices to show the tape drives (they may be listed under Tape drives, as in our example (Figure 3-10), but checking the driver property (Figure 3-11) will show that the drivers are not configured yet). Figure 3-10 Pre-configured tape drives in Device Manager 2. Select Properties for the first drive and install the driver, using the same process as for the medium changer. Click the Driver tab, and then click Update Driver (Figure 3-11). Figure 3-11 The driver tab of the unconfigured tape drive s properties box 3. The Upgrade Device Driver window displays (Figure 3-12 on page 88), prompting you to search for a driver or display a known list of drivers for installation. Click the Search option, and click Next. Chapter 3. Basic IBM tape setup for Windows 87

116 Figure 3-12 Device Driver Wizard install options 4. Check the box Specify a location and click Next, as in Figure Figure 3-13 Device driver location search options 5. The path to the location of the drivers is presented, as shown in Figure Specify the directory where you extracted the downloaded driver.zip file and click OK. Figure 3-14 Specify a location 88 Implementing IBM Tape in Linux and Windows

117 6. The wizard will locate a device driver, as shown in Figure If this is the driver version you want to install, click Next; otherwise, select the box labelled Install one of the other drivers and click Next. Typically, the latest driver version is installed unless there is a specific reason not to, such as for ISV application support issues. Figure 3-15 Search results 7. The Device Driver Wizard proceeds to install the device driver and informs you when the installation is complete, as shown in Figure Figure 3-16 Device Driver Wizard completion Rebooting the system is recommended to ensure a clean installation of the drivers. Now your medium changer and tape drives should appear as shown in Figure 3-64 on page 120. Note for Removable Storage Manager (RSM) users Windows 2000x Device Driver V through V permit multiple opens on a single tape drive. This change was made to enable the use of Removable Storage Manager (RSM ) on Windows 200x. For those levels of the device drivers, system administrators are responsible for ensuring that a single tape drive is never accessed by more than one application at a time to prevent potential data loss. Chapter 3. Basic IBM tape setup for Windows 89

118 With V and higher, two versions of the device driver are made available, one that prohibits multiple opens on a single tape drive and one that allows multiple opens on a single tape drive. Drivers that prohibit multiple opens on a single tape drive are indicated (when presented by the Windows Plug and Play Device Manager during device configuration) with the text string (for Tivoli Storage Manager) in them. These drivers will use the file exctape.inf from the install package during installation. Drivers that allow multiple opens on a tape drive do not have the text string (for Tivoli Storage Manager) in them. These drivers use the file magtape.inf from the install package during the installation. For example, if you have attached a IBM Ultrium III tape drive to your server, you will see the following: IBM ULTRIUM III TAPE DRIVE (for Tivoli Storage Manager) IBM ULTRIUM III TAPE DRIVE IBM strongly recommends that you use the "(for Tivoli Storage Manager)" drivers whether or not you are a Tivoli client to prevent a tape drive from being accessed by more than one process and potentially causing data corruption or loss. However, if you are a client that uses RSM, you will need to use the other driver and take steps to prevent multiple uncoordinated opens to a tape drive. If you are using V or later, the Driver Files Search Results screen will prompt you to choose between drivers during installation (Figure 3-17). This screen displays a default driver choice and a check box labeled Install one of the other drivers. Select this check box and click Next. (Figure 3-19 on page 91). Figure 3-17 To install the version for RSM, select the check box Install one of the other drivers Choose the appropriate driver from the list (Figure 3-18 on page 91) and click Next. 90 Implementing IBM Tape in Linux and Windows

119 Figure 3-18 Choose the driver from the list The Device Driver Wizard proceeds to install the device driver and informs you when the installation is complete, as shown in Figure Figure 3-19 Device Driver Wizard completion for clients that use RSM 3.3 Installing IBM tape device drivers for Windows 2003 Attention: If your library has Control Path Failover (feature #1680) installed and you want to enable it for Windows 2003, please follow the instructions in 3.4, Control Path Failover on page 103. If the LTO Tape Library is physically attached, Windows 2003 will attempt to automatically install the drivers upon boot. The Driver Installation Wizard will appear and will request details regarding the location of the drivers and information files. The IBM tape library may be hot-plugged into the SCSI or fibre adapter; in this case, you may perform a hardware scan from Device Manager, as shown in Figure 3-20 on page 92, to detect the added devices and initiate the Device Driver Install Wizard. Chapter 3. Basic IBM tape setup for Windows 91

120 Figure 3-20 Performing a hardware scan Execute the following steps: 1. Download and extract the latest IBM Ultrium Device Drivers for Windows Shut down the system. 3. Attach the library. 4. Restart the system. 5. Install the device drivers. Downloading the drivers Obtain the latest drivers for IBM tape libraries, as described in 3.1.1, Determine requirements on page 80. Extracting the drivers The IBM Tape Device Driver will be downloaded as a zipped package. Unzip the package (we used the directory D:\IBMdrv\6.0.82), as shown in Figure 3-21 on page Implementing IBM Tape in Linux and Windows

121 Figure 3-21 Extracted device driver package contents Uninstalling the previous version If an older version of the IBM Tape Device Driver is already installed on the system, uninstall it first. See Removing the IBM tape device driver from the system (un-install) on page 135 for more details Installing the medium changer device driver This step is not required if you have installed an IBM 3580, because it does not have a medium changer. With an IBM 3580 you can go straight to 3.2.2, Installing the tape drive device driver on page The devices, which have been attached and for which Windows 2003 has no device driver, should appear as unknown devices. If the devices do not appear, then carefully check the preceding steps (is the right cable being used, LVD/HVD issues, correct SCSI adapter card, and so on). Right-click My Computer, select Manage, open Device Manager, and select Medium Changer. You should see an Unknown Medium Changer Device or an entry with a library model number (for example, IBM 3584-L22). Right-click it and select Properties (Figure 3-22 on page 94). Chapter 3. Basic IBM tape setup for Windows 93

122 Figure 3-22 Device Manager window: pre-configured 2. Click the Driver tab, and then click Update Driver (Figure 3-23). Figure 3-23 The driver tab of the medium changer s properties box 94 Implementing IBM Tape in Linux and Windows

123 3. You will see the Hardware Update Wizard window (Figure 3-24), prompting you to allow the wizard to automatically install the driver or to install the driver from a list or a specific location. Click the Install from a list or specific location option, and then click Next. Figure 3-24 Device Driver Wizard install options 4. Click Search for the best driver in these locations, check the box for Include this location in the search, enter the directory which contains the unzipped files in the entry box, and click Next, as shown in Figure Figure 3-25 Device Driver Wizard Install Search and Installation Options: search for driver 5. Figure 3-26 on page 96 will display advising you to wait while the wizard searches. If the system does not find the medium changer driver, a screen displays which indicates the Chapter 3. Basic IBM tape setup for Windows 95

124 wizard was unable to find a driver for the device, as occurred when trying to install this version of the driver (see Figure 3-26). Figure 3-26 Device Driver Wizard: no driver found 6. If this occurs, click Back to redisplay the previous screen (see Figure 3-27). You can then select the option Don t search. I will choose the drive to install and click Next. Figure 3-27 Device Driver Wizard Install Search and Installation Options: choose driver 7. In the next window, Figure 3-28 on page 97, enter the directory path containing the unzipped driver files. 96 Implementing IBM Tape in Linux and Windows

125 Figure 3-28 Device Driver Wizard: specify location 8. The wizard locates a device driver, as shown in Figure If this is the driver version you want to install, click Next; otherwise, select the box labelled Show compatible hardware and click Next. Typically, the latest driver version is installed unless there is a specific reason not to install it, such as for ISV application support issues. Figure 3-29 Device Driver Wizard: select driver 9. If you are installing a driver that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL), you will see a warning screen (see Figure 3-30 on page 98). To continue installing the driver, click Continue Anyway. Note: All drivers released by IBM have been through a complete test to ensure that they are stable and conform to specified requirements. Chapter 3. Basic IBM tape setup for Windows 97

126 Figure 3-30 Device Driver Wizard: warning 10.The Device Driver Wizard proceeds to install the device driver and informs you when the installation is complete, as shown in Figure Figure 3-31 Device Driver Wizard: upgrade complete Installing the tape drive device driver The tape drive device driver installation basically follows the same steps as the medium changer installation. You need to install the drivers for each individual tape device if using a multi-drive library like the IBM 3583 or IBM Even when the names are different for each type of drive, the installation procedures are the same. Unless otherwise noted, follow the same procedures. Note: In Version , the tape device drivers for LTO and 3592 tape drives were converged into a single file. See 3.1.1, Determine requirements on page Implementing IBM Tape in Linux and Windows

127 1. Right-click My Computer on the Windows desktop and select Manage. Open Device Manager and expand Other Devices to show the tape drives. Figure 3-32 Pre-configured tape drives in Device Manager 2. Select Properties for the first drive and install the driver, using the same process as for the medium changer. Click the Driver tab, and then click Update Driver (Figure 3-33). Figure 3-33 The driver tab of the unconfigured tape drive s properties box Chapter 3. Basic IBM tape setup for Windows 99

128 3. The Hardware Update Wizard window (Figure 3-24 on page 95) prompts you to allow the wizard to automatically install the driver or to install the driver from a list or a specific location. Click Install from a list or specific location and click Next. Figure 3-34 Device Driver Wizard: install options 4. Click Search for the best driver in these locations, check Include this location in the search, enter the directory containing the unzipped files, and click Next, as in Figure Figure 3-35 Device Driver Wizard Install Search and Installation Options: search for driver 5. Figure 3-36 on page 101 shows the list box of available device drivers for the tape drive. Highlight the required driver and click Next. Typically, the latest driver version is installed unless there is a specific reason not to, such as for ISV application support issues. If you are an RSM user, please see Note for RSM users on page Implementing IBM Tape in Linux and Windows

129 Figure 3-36 Device Driver Wizard: select a driver 6. If you are installing a driver that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL), you are presented with a warning screen (see Figure 3-37). To continue installing the driver, click Continue Anyway. Note: All drivers released by IBM have been through a complete test to ensure that they are stable and conform to specified requirements. Figure 3-37 Device Driver Wizard: warning 7. The Device Driver Wizard proceeds to install the device driver and informs you when the installation is complete, as shown in Figure 3-38 on page 102. Chapter 3. Basic IBM tape setup for Windows 101

130 Figure 3-38 Device Driver Wizard completion Rebooting the system is recommended to ensure a clean installation of the drivers. Now your medium changer and tape drives should appear as shown in Figure 3-64 on page 120. Note for RSM users The Window 2003 Device Driver permits multiple opens on a single tape drive. This enables the use of Removable Storage Manager (RSM). System administrators are responsible for ensuring that a single tape drive is never accessed by more than one application at a time to prevent potential data loss. Two versions of the device driver are available. One that prohibits multiple opens on a single tape drive has the text string for Tivoli Storage Manager, and one that allows multiple opens on a single tape drive does not have the text string for Tivoli Storage Manager. IBM strongly recommends that you use the for Tivoli Storage Manager drivers whether or not you are a Tivoli client to prevent a tape drive from being accessed by more than one process and potentially causing data corruption or loss. However, if you are using RSM, you must use the other driver and take steps to prevent multiple uncoordinated opens to a tape drive. When installing the tape drive device drivers, you follow the same directions as for a non-rsm user (see 3.3.2, Installing the tape drive device driver on page 98). The Select Best Match screen will prompt you to choose between drivers (either the Tivoli Storage Manager driver or the non-tivoli Storage Manager driver) during installation (Figure 3-39 on page 103). Select the non-tivoli Storage Manager driver and click Next. The remainder of the instructions are the same as described in 3.3.2, Installing the tape drive device driver on page Implementing IBM Tape in Linux and Windows

131 Figure 3-39 To install the version for RSM select the second driver listed If you have Control Path Failover installed, you must also configure the library. For information about library configuration, please see 3.4, Control Path Failover on page Control Path Failover The Control Path Failover (CPF) feature of the IBM medium changer device drivers provides a mechanism whereby commands sent to a failing control path on a medium changer may fail over to a working control path. On Windows 2000 and Windows Server 2003, this support requires two kernel-level device drivers to be running on the system, in addition to the medium changer driver ibmcgxx.sys (the base driver). If CPF support is not provided, the base driver will be adequate to operate the changer. One of the two additional drivers required to enable CPF support is a filter driver that will be installed automatically if the magchgrf.inf (rather than the magchgr.inf) file is used for the base driver install. Depending on the version of the driver you have, you may see either or both these inf files when unzipping. The other additional driver is a virtual software bus, called the Changer Bus Enumerator, which must be installed using ibmcgbs.inf. The Changer Bus Enumerator must be installed before the base driver and filter driver installation. Because it is a virtual bus, no hardware will be plugged in and Windows will not recognize the presence of new hardware by the standard plug-and-play protocols. V and later of the IBM medium changer driver support Control Path Failover (CPF). Major architectural changes were made to the driver to include this support, and these changes are in effect regardless of whether your environment includes support for the CPF feature. A new procedure for installing the driver has been introduced. In particular, the changer driver on any given platform requires installation of three.sys files with their corresponding.inf files: ibmcgbsxx.sys (installed by ibmcgbs.inf) ibmcgxx.sys and ibmcgftxx.sys (installed by magchgrf.inf) ('xx' in the file names refers to either 2k or 2k3.) Chapter 3. Basic IBM tape setup for Windows 103

132 Instructions on how to install ibmcgbsxx.sys are included in the document CPF_install.doc. Installation of the other two.sys files follows the instructions for Windows 200x in the IBM Ultrium Device Drivers Installation and User s Guide, GA In order to reduce complexity, the file install.exe is included in the driver package to perform the steps in CPF_install.doc automatically. However, at the time of writing, this install.exe has the following limitations: It may not work correctly on Windows running on Intel Itanium. It may require a reboot. Please follow the prompts on your screen. It must not be run from the command line or from a network share. Please copy the entire driver package to a LOCAL directory and double click the install.exe icon to run. If you are installing lower than V , or one of the previously listed limitations applies to your installation, the CPF_install.doc instructions are included in 3.4.2, CPF driver installation using the CPF_install.doc on page 107. Note: We recommend that you check the latest version of the readme file for any changes to the installation process CPF driver installation using install.exe 1. To run install.exe, open Device Manager to verify that Windows has discovered all library devices on your system (Figure 3-40). The medium changer may show as the library type or as Unknown Medium Changer. If the tape drives are not listed under Tape Drives, they may be listed in Other Devices. Figure 3-40 Device manager with library installed 2. If the devices do not display, then attempt a manual rescan by selecting Action Scan for Hardware Changes (Figure 3-41 on page 105). 104 Implementing IBM Tape in Linux and Windows

133 Figure 3-41 Hardware scan 3. Once Windows has discovered the tape libraries, double-click install.exe in the directory where the driver file was unzipped (see Figure 3-42). Figure 3-42 install.exe in driver install directory 4. You may see a screen during installation indicating Windows cannot verify the software has not been modified since it was published (Figure 3-43 on page 106). Click Yes and continue. Chapter 3. Basic IBM tape setup for Windows 105

134 Figure 3-43 Changer Bus Enumerator installation warning 5. If you are installing a driver that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL), you will be see a warning screen (see Figure 3-44). To continue installing the driver, click Continue Anyway. Note: All drivers released by IBM have been through a complete test to ensure that they are stable and conform to specified requirements. Figure 3-44 Driver installation certification warning 6. At the end of the installation process, a message box indicates the installation is complete. Subject to the limitations previously listed, the virtual and actual hardware are installed correctly on your system. To continue with the library installation process, see either 3.2, Installing IBM tape device drivers for Windows 2000 on page 82 or 3.3, Installing IBM tape device drivers for Windows 2003 on page Implementing IBM Tape in Linux and Windows

135 3.4.2 CPF driver installation using the CPF_install.doc Note: If you have driver V or later, you may use the instructions in 3.4.1, CPF driver installation using install.exe on page 104. The Control Path Failover (CPF) feature of the IBM medium changer device drivers provides a mechanism whereby commands sent to a failing control path on a medium changer may fail over to a working control path. On Windows 2000 and Windows Server 2003, this support requires two kernel-level device drivers to be running on the system, in addition to the medium changer driver ibmcgxx.sys (the base driver). If CPF support is not provided, the base driver will be adequate to operate the changer. One of the two additional drivers required to enable CPF support is a filter driver that will be installed automatically if the magchgrf.inf (rather than the magchgr.inf) file is used for the base driver install. Depending on the version of the driver you have, you may see either or both these inf files when unzipping. The other additional driver is a virtual software bus, called the Changer Bus Enumerator, which must be installed using ibmcgbs.inf. The Changer Bus Enumerator must be installed prior to the base driver and filter driver installation. Because it is a virtual bus, no hardware will be plugged in and Windows will not recognize the presence of new hardware by the standard plug-and-play protocols. The Control Panel's Add/Remove Hardware feature will be used to instruct the system to recognize the virtual hardware. This documentation outlines the procedure required to install the Changer Bus Enumerator. Please note that minor differences may exist between the screen shots below and the windows displayed by the wizard on your system. Unless otherwise specified, the documentation is based on the look and feel of Windows Server This is similar enough to Windows 2000 to eliminate confusion. These instructions assume that you have obtained a copy of the IBM Tape Device Driver (IBMTape.W32_6xxx.zip or IBMTape.W64_6xxx.zip) with CPF support and have unzipped it into the c:\driver_install directory. Any directory on your system will work, but you need to specify this directory when the system prompts for driver location. 1. If there is an IBM medium changer device driver already installed on your system, you must uninstall it. Right-click My Computer, select Manage, and go to Device Manager. Under the subheading Medium Changers, right-click each device and select Uninstall. Follow the prompts to uninstall the device. Under the subheading System devices, if there is an entry called Changer Bus Enumerator, right-click the entry and uninstall it also. Then run the utility uninst.exe from the driver install package and reboot your system. 2. From the Control Panel, double-click Add/Remove Hardware (Windows 2000) or Add Hardware (Windows Server 2003). This starts the Add Hardware Wizard (Figure 3-45 on page 108). Click Next. Chapter 3. Basic IBM tape setup for Windows 107

136 Figure 3-45 Welcome window 3. If running Windows 2000, Figure 3-46 prompts you to add/troubleshoot a device or uninstall/unplug a device. Select Add/Troubleshoot a Device and click Next. Figure 3-46 Add/Remove window 4. Windows now searches for new plug-and-play hardware, as in Figure 3-47 on page 109. Within a few seconds, you are prompted if you have connected the hardware. Select Yes, I have already connected the hardware and click Next (Figure 3-48 on page 109). 108 Implementing IBM Tape in Linux and Windows

137 Figure 3-47 Searching Wizard window Figure 3-48 Is hardware connected window 5. A list of installed hardware appears. Select Add a new hardware device and click Next (see Figure 3-49 on page 110). Chapter 3. Basic IBM tape setup for Windows 109

138 Figure 3-49 Installed hardware window 6. On Figure 3-50, you are asked either to have the system search for and install the hardware or to manually select the hardware from a list. Select Install the hardware that I manually select from a list and click Next. Figure 3-50 Hardware location window 7. A list of hardware device classes is displayed. Select System devices and click Next (see Figure 3-51 on page 111). 110 Implementing IBM Tape in Linux and Windows

139 Figure 3-51 Hardware classes window 8. A list of suggested system devices is displayed. The actual contents of this list will vary from system to system. Select Have Disk (Figure 3-52). Figure 3-52 System devices window 9. In Figure 3-53 on page 112, enter the directory of the.inf file for the Changer Bus Enumerator and click OK. We unzipped the zip file into c:\driver_install, so we enter this directory. Chapter 3. Basic IBM tape setup for Windows 111

140 Figure 3-53 Location of the inf file 10.Figure 3-54 shows a list of hardware containing one item, the Changer Bus Enumerator. Ensure that Changer Bus Enumerator is selected and click Next. Figure 3-54 Changer Bus Enumerator found 11.Verify that you want to install the Changer Bus Enumerator. Click Next (Figure 3-55 on page 113). 112 Implementing IBM Tape in Linux and Windows

141 Figure 3-55 Verifying the install 12.If you are installing a driver that has not been certified by the Microsoft Windows Hardware Quality Laboratories (WHQL), you will see a warning screen (Figure 3-56). To continue installing the driver, select Yes. Note: All drivers released by IBM have been through a complete test to ensure that they are stable and conform to specified requirements. Figure 3-56 WHQL warning window 13.If the driver is properly installed, Figure 3-57 on page 114 will open, indicating that Windows has finished installing the software. Click Finish. Chapter 3. Basic IBM tape setup for Windows 113

142 Figure 3-57 Completing the Wizard window 14.To verify that the Changer Bus Enumerator is properly installed, right click My Computer, select Manage, and go to Device Manager. Changer Bus Enumerator is listed under System devices, as in Figure Figure 3-58 Device manager 15.Once the Changer Bus Enumerator has been installed, the base driver/filter driver pair must be installed. 114 Implementing IBM Tape in Linux and Windows

143 To continue with the library installation process, see either 3.2, Installing IBM tape device drivers for Windows 2000 on page 82 or 3.3, Installing IBM tape device drivers for Windows 2003 on page 91, with one exception: Instead of installing the drivers with magchgr.inf, you should install the drivers with magchgrf.inf from the driver_install directory. Disabling control path failover To disable the CPF feature after installation, so that the driver runs in single-path mode, double-click the file reg\disablecpf.reg from the driver install package and reboot your machine. To re-enable the feature, double-click reg\enablecpf.reg and reboot Configuring control path failover in the library After installing the required drivers for CPF (see 3.4, Control Path Failover on page 103), you need to configure the library for CPF. The IBM LTO or IBM 3592 device driver alternate pathing support can optionally configure multiple physical control paths (communications paths for controlling the library) to the same logical library and provide automatic failover to an alternate control path when a permanent error occurs on one path. This is transparent to the running application. Control path failover is an optional priced feature that must be enabled with a license key. For example, consider a simple multi-path architecture connection with two HBAs in a Windows 200x host, connected to a library with two drives. Each drive has the control port enabled. The first HBA is connected to the first drive, and the second HBA is connected to the second drive. This simple configuration provides two physical control paths to the same library (one on each drive) for redundancy if one path from an HBA to the library fails. When the Windows 200x server is booted, each HBA detects a control port to the library and two medium changer devices (changer0 and changer1) will be configured. Each logical device is a physical path to the same library; however, an application can open and use only one logical device at time, either changer0 or changer1. Without the IBM LTO or 3592 device driver alternate pathing support, if an application opens changer0 and a permanent path error occurs (for example, because of an HBA, cable, or drive control port failure), the current command to the library fails. It is possible to initiate manual failover by changing the device path to the alternate path (changer1), but this is a manual operation, and the last failing command has to be resent. When alternate pathing support is enabled on both changer0 and changer1, the device driver configures them internally as a single device with multiple paths. The application can still open and use only one logical device at a time (either changer0 or changer1). If an application opens changer0 and a permanent path error occurs, the current operation continues on the alternate path without interrupting the application. Important: The library Control Path Failover Feature Code 1680 must be installed and enabled on the library (IBM 3582, 3583, and 3584) prior to enabling the alternate pathing support in the IBM LTO or IBM 3592 device driver. In addition, you have to enable the control path for additional drives on the library using either the library Operator panel or the TotalStorage Specialist. This is shown in Enabling additional control paths on page 116 for the 3582, 3583, and Chapter 3. Basic IBM tape setup for Windows 115

144 Enabling additional control paths The following three sections show how to enable additional control paths via the Operator panel or TotalStorage Specialist for the 3582, 3583, and Enable additional control path on IBM 3582 Access Mode enables you to set control path failover and additional control paths. From the Setup menu, select the SCSI/Fibre Option and then Access Mode. Highlight Failover and toggle it to Addl ctrl paths. Then select Enabled (see Figure 3-59) and exit the Setup menu. Figure 3-59 IBM 3582: Enable control paths Enable additional control path on IBM 3583 To enable the control path for one or more drives, select, from the Operator panel, Operator Panel Setup Drives SCSI. Select the drives on which you want to enable the control path, and set the Control path to ON, as shown in Figure Figure 3-60 IBM 3583: Enable control path Enable additional control path on IBM 3584 To enable additional control paths with the Operator panel on an IBM 3584, select Menu Settings Control Paths Change Control Paths, and select the drive for which you want to enable the control path. To enable additional control paths using the Tape Library Specialist without ALMS, select Manage Drives Control Paths, select the drive which you want to enable for the control path, and click Change (see Figure 3-61 on page 117). 116 Implementing IBM Tape in Linux and Windows

145 Figure 3-61 IBM 3584: Enabling additional control paths without ALMS To enable additional control paths using the Tape Library Specialist with ALMS enabled, do the following: 1. Select Manage Drives Drive Assignments 2. From the Drive Assignments page, either select the drive you want to enable or select the logical library from which you would like to select a drive to enable and click Continue. 3. Locate the drive that you want to enable (or disable) as the control path drive by clicking the blue icon to the left of the check box; a drive icon appears, as shown in Figure 3-64 on page 120. In the example, drive 2703 was selected to enable as an alternate control path. Do not select a drive with a cartridge in it, such as drive 2702 in the example. 4. To confirm the changes, click the Apply button. 5. The Operation in Progress screen displays, followed by a Success screen that indicates that the changes are complete. Click Close. 6. The Drive Assignment screen redisplays with the new assignments (Figure 3-62 on page 118). Chapter 3. Basic IBM tape setup for Windows 117

146 Figure 3-62 IBM 3584: Enabling additional control paths with ALMS enabled IBM 3584 high availability The IBM 3584 already provides many high availability options, as described in IBM TotalStorage Tape Libraries Guide for Open Systems, SG By using control path failover, you can achieve a fully redundant configuration, as shown in Figure 3-63 on page 119. You should also consider your infrastructure and attach the additional control paths on redundant components including: SAN switch SAN fabric Server HBA If you have a multi-frame configuration, enable the additional control paths on a different frame, so that you can still use your library even if the AC power for the first frame is lost. In Figure 3-63 on page 119, the second control path is enabled on the second frame, and goes over a separate SAN switch and fabric (there is no interswitch link between these switches) to a second HBA. You can still work with the library if any one of these conditions occurs: AC power is lost on the first frame. Drive one in the first frame is down. The FC cable between the drive and switch or switch and HBA is broken. One switch fails. One SAN fabric is down. One HBA is broken. 118 Implementing IBM Tape in Linux and Windows

147 LIBRARY CONTROLLER AC LIBRARY CONTROLLER AC DRIVE DRIVE 1 1 Control path required for Drive 1 DRIVE 2 DRIVE 2 DRIVE DRIVE 3 3 DRIVE DRIVE 4 4 Control path enabled for Drive 4 SERVER Frame 1 Frame 2 FC ADAPTER smc0 smc1 Figure 3-63 High availability control path configuration on an IBM Verifying the IBM tape device installation The IBM Tape Device Driver installation for the medium changer and tape devices may be initially verified through the Device Manager. To view any installed tape devices and medium changers, right-click My Computer on the desktop and then select Manage Device Manager. 1. To determine whether there are LTO devices present, look under Medium Changers and Tape Devices (Figure 3-64 on page 120). Note that if you have installed an IBM 3580 stand-alone device, there will be no medium changer listed. All the other 358x models will have a Medium Changer device entry. Chapter 3. Basic IBM tape setup for Windows 119

148 Figure 3-64 Viewing IBM tape device in Device Manager 2. Right-click each of the devices and select Properties. If properly configured, this window should show Manufacturer as IBM Corporation (Figure 3-65), Driver provider as IBM Corporation and Driver version as the version you have installed (Figure 3-66 on page 121). Figure 3-65 Driver details The driver level for the devices are shown in the Driver tab in Figure 3-66 on page 121. Note that the driver is not digitally certified by Microsoft at this time, but is still supported by IBM. 120 Implementing IBM Tape in Linux and Windows

149 Figure 3-66 Driver tab 3. To view the driver file details, click Driver Details (Figure 3-67). Figure 3-67 Driver File details You can now use the NTUTIL utility to test the library. This utility will allow you to open the device, issue inquiry commands, read and write, and move media within the library to ensure that the devices are functioning and operating correctly with the installed driver. Chapter 3. Basic IBM tape setup for Windows 121

150 3.5.1 Testing the library with NTUTIL NTUTIL is a utility that is packaged with the IBM Tape changer and device drivers. It may be used to perform several functions, including: Read and write operations Media mounts and dismounts Microcode updates Forcing driver dumps Sending and obtaining status of SCSI commands and retrieving sense data from commands that encounter errors For our purposes, we used NTUTIL to test basic operations as a way of verifying correct installation of the IBM tape library and drives. Note that you must stop the Removable Storage Manager (RSM) service in Windows before you can use NTUTIL. NTUTIL will not be able to see the devices until RSM releases them. Alternatively, you may simply disable the IBM tape library in RSM. For more information about RSM, see Chapter 6, Configuring RSM on page 245. NTUTIL can run in either interactive or batch mode. Interactive mode will present you with a menu of commands that you can use to drive the library and drives. Batch mode will pass on a series of commands from a user-generated file to the utility. NTUTIL is unpacked with the device drivers. It can be installed at any location, but is typically installed in the c:\winnt\system32 or C:\Windows\system32 directory. Since this directory is in the system path, you can run NTUTIL from any command line. When NTUTIL is invoked without arguments, it will start in interactive mode. There are two modes that NTUTIL can run in: Base Mode and Library Mode. The default mode is Base Mode. Option 8 toggles between the two modes. Both modes support Open/Close/Read/Write operations. However, you may only use medium changer commands such as move media while in library mode. Example 3-1 shows the main menu, which presents the option to run the utility in interactive (manual) or batch mode. Note: The NTUTIL samples provided used the Windows 2003 NTUTIL Version The menus displayed with other versions may vary slightly. Example 3-1 NTUTIL main menu NTutil - Copyright (c) IBM Corporation Main Menu: Microsoft Windows 2003 version ========== 1: Manual test 2: Batch test 9: Exit ntutil Enter selection: 122 Implementing IBM Tape in Linux and Windows

151 Selecting 1: Manual test provides the menu in Example 3-2 for interactive commands. Example 3-2 NTUTIL manual test menu (Base Mode) Test tool version Variable settings ==================== BASE MODE ======================================== tape-special-file-name: tape0 gp->fd0=ffffffff gp->fd1=ffffffff block size=1024 block count=1 hex block id = return_error_when_fail 1 exit_on_unexpected_result 0 trace_flag 0 manual test menu: ======================================================================= 1: set device special file 2: display symbols 3: set block size R/W (now!0 fixed) 5: set return error when fail 6: set/reset trace 7: set exit on unexpected result 8: Library Mode ======================================================================= 20: open 21: close 22: read 23: write 24: read and display block 25: flush (buffer->media) 26: read block id 27: erase 28: locate block id 29: display block data ======================================================================= 30: write filemark(s) 31: rewind 32: forward space filemark(s) 33: unload 34: reverse space filemark(s) 35: load 36: forward space record(s) 37: return error 38: reverse space record(s) 39: test unit ready 43: set media parms (block size) 44: set dev parms(compression) 46: get device information 47: restore data 48: get medium information 49: inquiry 50: poll registered devices 53: space EOD 54: display message ======================================================================= 70: system command ======================================================================= 80: Force Dump 81: Read Dump 82: Update MicroCode 83: Log Sense 84: Get Last Sense 85: Get Version 86: Associative/Persistent WProtect 87: Read/Write Test 88: List registered devices 89: Get MTDevice Info ======================================================================= 99: return to main menu ======================================================================= enter selection: Note that option 8 says Library Mode. This indicates that NTUTIL is running in base mode. To change to library mode, select 8: Library Mode. The menu in Example 3-3 on page 124 displays. Chapter 3. Basic IBM tape setup for Windows 123

152 Example 3-3 NTUTIL manual test menu (Library Mode) Test tool version Variable settings ==================== LIBRARY MODE ===================================== tape-special-file-name: tape0, changer-special-file-name: Changer0 gp->fd0=ffffffff gp->fd1=ffffffff block size=1024 block count=1 hex block id = return_error_when_fail 1 exit_on_unexpected_result 0 trace_flag 0 manual test menu: ======================================================================= 1: set device special file 2: display symbols 3: set block size R/W (now!0 fixed) 5: set return error when fail 6: set/reset trace 7: set exit on unexpected result 8: Base Mode ======================================================================= 10: return library inventory 11: move medium 12: initialize element status 13: get changer parameter 14: exchange medium 15: get changer bus info ======================================================================= 20: open 21: close 22: read 23: write 24: read and display block 25: flush (buffer->media) 26: read block id 27: erase 28: locate block id 29: display block data ======================================================================= 30: write filemark(s) 31: rewind 32: forward space filemark(s) 33: unload 34: reverse space filemark(s) 35: load 36: forward space record(s) 37: return error 38: reverse space record(s) 39: test unit ready 43: set media parms (block size) 44: set dev parms(compression) 46: get device information 47: restore data 48: get medium information 49: inquiry 50: poll registered devices 53: space EOD 54: display message ======================================================================= 70: system command ======================================================================= 80: Force Dump 81: Read Dump 82: Update MicroCode 83: Log Sense 84: Get Last Sense 85: Get Version 86: Associative/Persistent WProtect 87: Read/Write Test 88: List registered devices 89: Get MTDevice Info ======================================================================= 99: return to main menu ======================================================================= enter selection: To view the installed library and drive, select 88: List registered devices. Medium changer devices are given a device special name of Changerx, and tape drives are known as Tapex. The bus, target ID, and LUN ID for each device are also shown here. Example 3-4 on page 125 shows the devices listed when using SCSI attachment, and Example 3-5 on page 125 shows the device listing for a SAN attachment. 124 Implementing IBM Tape in Linux and Windows

153 Example 3-4 Registered devices on a SCSI bus enter selection: 88 Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 1" Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 2" Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 4" Total elapsed time in seconds = 0.00 Return to continue: Example 3-5 Registered devices on a SAN enter selection: 88 Device found: Port 2\Scsi Bus 0\Target Id 2\Logical Unit Id 0" Device found: Port 2\Scsi Bus 0\Target Id 2\Logical Unit Id 1" Device found: Port 2\Scsi Bus 0\Target Id 3\Logical Unit Id 0" Device found: Port 2\Scsi Bus 0\Target Id 4\Logical Unit Id 0" Device found: Port 2\Scsi Bus 0\Target Id 4\Logical Unit Id 1" Device found: Port 2\Scsi Bus 0\Target Id 5\Logical Unit Id 0" Total elapsed time in seconds = 0.00 Return to continue: To perform any operations, you usually need to open the desired device (select 1: Set device special file, then select the appropriate device from the device listing, and open it with 20: Open). Example 3-6 and Example 3-7 show these selections. Example 3-6 Selecting a device special file ======================================================================= enter selection: 1 Enter device special file (tape path) name or return for no change: tape1 Total elapsed time in seconds = 6.00 Return to continue: Example 3-7 Performing an open call on a selected device special file ======================================================================= enter selection: 20 Enter open mode (1) RW (2) RO: 1 special file (\\.\tape1) will be opened analyze() called with rc 6 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 1.00 Return to continue: To test the Medium Changer, we load a tape to a drive, perform a read/write test on it, and then unload the tape. Select Library Mode first and then open the device. By default, changer0 and tape0 will be selected unless overridden. Select 20: Open. In this case, tape 1 is opened (Example 3-8), because it was previously selected in Example 3-6. Example 3-8 Opening the selected special device file enter selection: 20 Enter open mode (1) RW (2) RO: 1 special file (\\.\tape1) will be opened special file (\\.\changer0) will be opened analyze() called with rc 11 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 1.00 Return to continue: Test tool version Variable settings Chapter 3. Basic IBM tape setup for Windows 125

154 ==================== LIBRARY MODE ===================================== tape-special-file-name: tape1, changer-special-file-name: changer0 machine type IBM 3584 SCSI MaxScatterGather = 65 (MaxBlkSz = ), AlginmentMask = 0 MAX_TRANSFER = gp->fd0=000003b8 gp->fd1=000003b4 block size=1024 block count=1 hex block id = return_error_when_fail 1 exit_on_unexpected_result 0 trace_flag 0 manual test menu: ======================================================================= To display information about the Medium Changer, select 13: get changer parameter, as shown in Example 3-9. Example 3-9 Get Changer parameters ======================================================================= enter selection: 13 NumberofTransports: 2, FirstTransportNumber: 0x0001 NumberofStorageElements: 150, FirstStorageElement: 0x04b1 NumberofIEElements: 1, FirstIEElement: 0x0000 NumberofDataTransferElements: 2, FirstDataTransferElement: 0x010d Features0: 0x04027c23 Features1: 0x Features: CHANGER_BAR_CODE_SCANNER_INSTALLED CHANGER_INIT_ELEM_STAT_WITH_RANGE CHANGER_EXCHANGE_MEDIA CHANGER_POSITION_TO_ELEMENT CHANGER_REPORT_IEPORT_STATE CHANGER_STORAGE_DRIVE CHANGER_STORAGE_IEPORT CHANGER_STORAGE_SLOT CHANGER_PREDISMOUNT_EJECT_REQUIRED CHANGER_SERIAL_NUMBER_VALID analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 0.00 Return to continue: To move the cartridge, you need to know the source and destination addresses for the media. These are obtained by selecting 10: return library inventory, as shown in Example 3-10 on page 127. The addresses are given in hexadecimal format and need to be entered as such when using the move medium command. Each entry in the inventory has an element type and a number in hexadecimal format. The element type indicates the classification of the element and is one of the following: 1. MTE: Medium Transport Element (picker) 2. SE: Storage Element (storage slot) 3. IEE: Import/Export Element (Medium Changer bulk I/O slots) 4. DTE: Data Transfer Element (the drives) The command output (Example 3-10 on page 127) shows that there is one MTE (cartridge picker), 12 I/O slots (IEE), two drives (DTE), and 42 storage slots (SE) in the 3583 s inventory. Each entry also shows if there is a cartridge present (by indicating full or empty). 126 Implementing IBM Tape in Linux and Windows

155 Example 3-10 Return library inventory enter selection: 10 Type: MTE, Addr: 0x , Empty Type: MTE, Addr: 0x , Empty Type: DTE, Addr: 0x , Empty Access TgtId: 0x21 Type: DTE, Addr: 0x , Empty Access TgtId: 0x22 Type: SE, Addr: 0x , Full Access Type: SE, Addr: 0x , Full Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x a, Empty Access Type: SE, Addr: 0x b, Empty Access Type: SE, Addr: 0x c, Empty Access Type: SE, Addr: 0x d, Empty Access... Type: SE, Addr: 0x e, Empty Access Type: SE, Addr: 0x f, Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type: SE, Addr: 0x , Empty Access Type:???, Addr: 0x , Empty analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 1.00 Return to continue: You can see that there is a slot (SE) with a state of Full Access. This is the cartridge we want to move in our example. We will be loading that cartridge into a tape drive, specifically, the DTE (tape drive) with an address of Example 3-11 shows how to move a tape cartridge from a slot in the library and mount it in a drive. We selected option 11: ioctl move medium. At this stage, we simply want to mount a tape volume into the drive using the Medium Changer. We specify SE (Storage Element Slot) as the source type. NTUTIL then prompts for a valid source address, which we enter in hexadecimal format ( ). We then provide a destination type, which is a tape drive (DTE) followed by a destination address ( ). Example 3-11 Move media enter selection: 11 source type [moving from]: 2 = SE, 3 = IEE, 4 = DTE:2 source address moving from: destination type [moving to]: 2 = SE, 3 = IEE, 4 = DTE:4 destination address moving to: execute move_medium stype = 2, saddr = 0, dtype = 4, daddr = 1 analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = Return to continue: Chapter 3. Basic IBM tape setup for Windows 127

156 Once the tape is mounted (indicated by the ERROR_SUCCESS output), you may perform a read/write test (option 87) on the cartridge (Example 3-12). Note this overwrites any data on the tape; NTUTIL does not interact with any applications, so it is not aware of whether the tape has valid data on it or not. Therefore, be careful about which tape you choose for this operation. Example 3-12 Read/write test enter selection: 87 This will rewind and write on tape! Are you sure?? Y or N y ntutil execute_command_read_write test rewinding Rewind OK, set blocksize to 32K Set Block Size OK, writing 32K Write 32K OK, rewinding Rewind after Write OK, reading data Read after Rewind OK, comparing data analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 6.00 Return to continue: The tape has been successfully written to, as shown in Example We may now unload the cartridge by selecting 33: Unload, then selecting again 11: move medium, but this time the source and destination elements are reversed from the load operation, so the cartridge is moved from the drive back to its original slot (Example 3-13 and Example 3-14). Example 3-13 Unload enter selection: 33 analyze() called with rc 0 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = Return to continue: Example 3-14 Move media back to the slot enter selection: 11 source type [moving from]: 2 = SE, 3 = IEE, 4 = DTE:4 source address moving from: destination type [moving to]: 2 = SE, 3 = IEE, 4 = DTE:2 destination address moving to: execute move_medium stype = 4, saddr = 1, dtype = 2, daddr = 0 analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = Return to continue: To display information about the library or drive, use 49: inquiry (Example 3-15). In Library Mode, you must specify from which device (changer or tape drive) you want to gather information. In Base mode, NTUTIL returns information only about the opened drive. Example 3-15 Inquiry enter selection: 49 Drive = 0, Library = 1: 0 Device Path SCSI data: PortNumber 2, PathId 0 TargetId 2, Lun 1 INQUIRY data: devtype(0): 01, rmb(1): 80 ASO/ECMA/ANSI(2): 03, resp_data_fmt(3): Implementing IBM Tape in Linux and Windows

157 additional_length(4): 33, reserved(5): 00 SCSI_3(6): 10, flags(7): 00 vendor_id (8-15): IBM product_id (16-31): 03592J1A Microcode Revision Level (32-35): 04C4 vendor specific (bytes 36-55): analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 8.00 Return to continue: NTUTIL can also be run in batch mode. For more information about NTUTIL, refer to the IBM Ultrium Device Drivers Installation and User s Guide, GA This guide is installed with the packaged device drivers. The manual IBM TotalStorage Ultrium Device Drivers Programming Reference, GC , has information about issuing commands to tape device drivers and manipulating tape APIs Creating a library device table Operating system device names may not necessarily reflect the same order that the devices are physically installed in the library. Therefore, check your drive configuration carefully. We recommend creating a table like Table 3-1. Table 3-1 Library device table Windows device name Serial number or WWN Tape drive in the library SCSI element address Tape drive Tape drive Tape drive Tape drive Keep in mind that rebooting the server may alter the device order. See Set up persistent binding on page 149 to understand how the operating system assigns device special file names, and the ways to keep it persistent across reboots. To create this table, use the ntutil inquiry command. The function to return the device serial number is available at NTUTIL V and above. In Example 3-16, the device special file tape0 represents the tape drive with serial number Compare this serial number to the number written on the drives in the library. Example 3-16 Verify device by ntutil inquiry command enter selection: 1 Enter device special file (tape path) name or return for no change: tape0 Total elapsed time in seconds = 2.00 Return to continue:... enter selection: 20 Enter open mode (1) RW (2) RO: 1 special file (\\.\tape0) will be opened analyze() called with rc 6 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 1.00 Return to continue: Chapter 3. Basic IBM tape setup for Windows 129

158 ... enter selection: 49 Device Path SCSI data: PortNumber 0, PathId 0 TargetId 0, Lun 0 INQUIRY data: devtype(0): 01, rmb(1): 80 ASO/ECMA/ANSI(2): 03, resp_data_fmt(3): 02 additional_length(4): 33, reserved(5): 00 SCSI_3(6): 10, flags(7): 00 vendor_id (8-15): IBM product_id (16-31): 03592J1A Microcode Revision Level (32-35): 04C9 Unit Serial Number: vendor specific (bytes 36-55): analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = Testing the library with NTBACKUP The Windows 200x native backup utility NTBACKUP can use the IBM tape library and drives to perform basic backup, restore, and system state backup functions. To use the Windows backup utility, you must start the RSM service, and prepare within the libraries before it can be made available to the application. For more information about RSM operation and features, refer to Chapter 6, Configuring RSM on page 245. NTBACKUP will give an error if it is started without the RSM service running. To start NTBACKUP, select Start Programs Accessories System Tools Backup, or run NTBACKUP at the command line. If you start NTBACKUP without any allocated media, you will see the message shown in Figure Figure 3-68 Import media present message If you want to allocate all free media at this time, you may do so, bearing in mind that this operation will cause NTBACKUP to take ownership of all media. If there are other backup applications that use this media, do not allocate all media. Again, you may prepare (format) the tape volumes as needed through RSM, and NTBACKUP will allocate free (prepared) volumes when required. The Windows 200x backup and restore functions, as used with IBM LTO tape libraries, are illustrated below, and are much the same as for any other natively attached tape libraries and drives. If new media is requested to be written to, then the tape mount preparations take place with RSM driving the Medium Changer in the background. Similarly, mount requests for restore operations are transparent to the application. From the Backup tab (Figure 3-69 on 130 Implementing IBM Tape in Linux and Windows

159 page 131) you may select the files and directories to be backed up, the backup destination device, and the media to mount for the operation. Figure 3-69 The NTBACKUP Backup tab In our example, we have selected a full directory for backup. The backup destination is listed as LTO Ultrium (this has been configured through RSM), and the backup media as New Media, which means that NTBACKUP will automatically query the RSM database for a free scratch volume and ask for it to be mounted. Figure 3-70 on page 132 shows the NTBACKUP restore window. Here you may select the media contained within the IBM tape library from which you want to restore. The available restore media are listed as defined in the RSM database. The LTO Ultrium tape pool shows the tape volumes that are candidates for restore operations. They are automatically stamped with the time of the backup operation. If we click the media, we will be able to see the backed up files and directories that it contains. Chapter 3. Basic IBM tape setup for Windows 131

160 Figure 3-70 The NTBACKUP Restore tab NTBACKUP with a SAN It is not possible (by default) to use RSM, and therefore, NTBACKUP to drive the medium changer in a SAN-attached configuration. RSM can only auto-configure a robotic library when the following conditions are true: The robotic library hardware unit supports drive element address reporting with the Read ElementStatus SCSI command. (Consult the manufacturer to find out if your library hardware unit supports this feature.) All drives inside the robotic library are on the same SCSI bus as the library itself. The TAPE library is not attached to a Fibre Channel switch. (This may change in future versions of RSM.) RSM will attempt to auto-configure any libraries attached to the SAN Data Gateway (SDG), but it is unable to do so, since the SDG remaps SCSI device IDs and LUNs. Consequently, RSM is unable to resolve the SDG addresses with those contained in the Read Element Status data for the drives. For native Fibre Channel attached drives, typically, a switch would be involved. RSM devices, however, may be configured using the RSMConfg.exe tool in the Windows 200x resource kit utility, or manually by editing the registry. To manually configure the registry, use the process shown in 6.3, RSM with a SAN on page 252. Once this operation has been performed, you may be able to use NTBACKUP. Note: IBM SAN Data Gateway and the 3583 SDG module were withdrawn from marketing in October Configuring tape and medium changer devices Some default operating parameters for the medium changer and tape devices may be altered using NTUTIL. NTUTIL has a series of Set commands, which can change these parameters: Drive Compression - default: (0=off) Block size - default: (0=variable) Block ID 132 Implementing IBM Tape in Linux and Windows

161 To activate or deactivate drive compression (on/off), open NTUTIL, select 20: Open, then 44: set dev parms (compression). A value of 0 indicates compression is off and any other value indicates on (see Example 3-17). Example 3-17 Activating compression enter selection: 44 Compression off = 0, on = 1: 1 execute set_device_parameters compression = ON analyze() called with rc 0 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 4.00 Return to continue: The drive block size may also be altered with option 43: Set media parms (block size). The blocksize is 0 (variable) by default. This value may be overwritten by some backup applications. You can view the current device parameters such as target ID and LUN by selecting 88: List registered devices (see Example 3-18). Example 3-18 List registered devices enter selection: 88 Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 1" Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 2" Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 4" Total elapsed time in seconds = 0.00 Return to continue: When devices are attached via an IBM SAN Data Gateway, SCSI target IDs and LUNs on the gateway's SCSI channels are remapped to other values that are then presented to the host operating system. Note: IBM SAN Data Gateway and the 3583 SDG module were withdrawn from marketing in October When the server boots, the devices, attached to the first gateway encountered by the boot I/O scan process, are assigned SCSI target ID 0 (with LUNs between 0-127); devices attached to the second gateway have SCSI target ID 1, and so on. Important: For every SDG attached to the server, LUN 0 is used by the gateway itself, and LUNs are used for tape devices attached to the gateway. Tape drives are always assigned an even number LUN and start at 2. The Medium Changer will have an odd number. Then for the tape devices, the gateway assigns LUNs sequentially as the devices are discovered on its attached SCSI channels. This means that adding and removing devices, cabling changes, and readdressing of devices may cause gaps in the sequence of assigned LUNs, because the LUN number assignments are made every time the server reboots. This problem may be overcome by enabling persistent binding on the Fibre Channel HBA. For more details regarding persistent binding, refer to 5.3, Persistent binding on page 237. Chapter 3. Basic IBM tape setup for Windows 133

162 Updating microcode using NTUTIL NTUTIL also allows you to update the drive microcode. Refer to 3.9, Updating library, drive, and RMU firmware on page 168 for instructions Deleting LTO devices You may need to remove the tape device or the Medium Changer from the Windows device configuration. This is required for some application software that needs a specific device driver for the Medium Changer or the Tape Drive. You may also want to simply disable a driver, perhaps for troubleshooting purposes. In this section, we describe how to disable an IBM tape device in Windows 200x, and how to remove a device driver. Disabling tape medium changer or tape drive To disable IBM tape device in Windows 200x, open Device Manager, locate the device (in this case, under Medium Changers or Tape Drives), right-click the device and select Disable. Alternatively, you can do this from the Properties box for the device under the General tab. This is shown in Figure Figure 3-71 Disabling an IBM tape device Disabling RSM We recommend disabling RSM from the services window (select Start Programs Administrative Tools Services, as shown in Figure 3-72 on page 135) before removing the Ultrium devices. Ensure that all device activity has been halted before performing this step. 134 Implementing IBM Tape in Linux and Windows

163 Figure 3-72 The Services window Double-click Removable Storage and select the General tab (Figure 3-73). From here, you may stop and then disable RSM. Figure 3-73 Disabling RSM Removing the IBM tape device driver from the system (un-install) To remove the IBM Tape Device Driver, do the following: 1. Open Device Manager and right-click the device (Figure 3-74 on page 136). Chapter 3. Basic IBM tape setup for Windows 135

164 Figure 3-74 Accessing the Device Uninstall option 2. Click Uninstall. You will see a pop-up warning window to confirm that you really want to uninstall the device. Click OK to continue. Windows will proceed to remove the device drivers. Repeat these steps for all tape devices and the Medium Changer. 3. Run the file uninst.exe, located in the directory where the driver was extracted (refer to Figure 3-75). If you were in the process of upgrading the IBM Tape Device Driver, you can now proceed to install the new version. Note: Older versions of the driver installation files use an uninstall script called uninstalllto.exe instead of uninst.exe. Figure 3-75 Uninst.exe in extracted driver directory Note: Previous versions of the IBM Tape Device Driver have used the Windows Install Shield for the installation. If your version used Windows Install Shield, remove it using Control Panel Add/Remove Program. 136 Implementing IBM Tape in Linux and Windows

165 4. Shut down the operating system and physically detach the library if required. Uninstall.exe will not remove the.zip file or the files extracted from the.zip file. If you want to remove these files, you will need to do so manually. Figure 3-76 Executing uninst.exe Figure 3-77 Uninst.exe completed successfully 3.6 Windows 200x SCSI adapter installation To illustrate this topic, we use the IBM 3583 library directly SCSI-attached to a Windows, Intel based server, as depicted in Figure The installation consists of: Intel server with Windows 2000 Server Adaptec LVD SCSI adapter IBM 3583 with LVD drives SCSI Intel Windows server IBM LTO 3583 Figure 3-78 Windows SCSI attached configuration SCSI host adapter compatibility for Windows 200x with IBM LTO devices is listed in 1.3.1, Windows 2000/2003 SCSI direct attach on page 29. Chapter 3. Basic IBM tape setup for Windows 137

166 Additional information regarding SCSI interfaces and connector types may be found in: 1.7, LVD or HVD on page , SCSI HD68 and VHDCI cable connectors on page 34 For Adaptec adapters, we suggest that you obtain the latest driver levels and firmware updates for SCSI adapters from the Adaptec Web site: echnology%2fscsi+host+adapters Our configuration uses an Adaptec (LVD). When installed in a Windows 200x machine, Windows 200x will detect the card and load its own drivers automatically. You may, however, update the adapter to a later driver level from the Adaptec Web site. Note: The screens included in this section were obtained on a Windows 2000 system. Windows 2003 screens may vary slightly. 1. You will need to shut down the system to install the card. When Windows starts up, you will be prompted to reboot, as in Figure 3-79, since it has already loaded its own drivers. Figure 3-79 System settings change 2. Select Yes to reboot for a clean install. After the reboot, you may update to a later version of the device driver using Device Manager. Right-click My Computer, select Device Manager SCSI and RAID controllers, right-click the SCSI card to be updated (Adaptec SCSI Card in our example), and select Properties, as shown in Figure Figure 3-80 Accessing SCSI controller properties 3. On the Properties window (Figure 3-81 on page 139), click the Drivers tab and select Update Driver. 138 Implementing IBM Tape in Linux and Windows

167 Figure 3-81 Adaptec properties: Driver tab 4. The Upgrade Device Driver Wizard starts, as in Figure Click Next to begin. Figure 3-82 Upgrade Device Driver Wizard 5. You are prompted to either search for a device driver or display a known list of drivers (Figure 3-83 on page 140). Select the Search option and click Next. Chapter 3. Basic IBM tape setup for Windows 139

168 Figure 3-83 Device driver search options 6. In the Locate Driver Files window (Figure 3-84), check Specify a location. Figure 3-84 Device driver search location 7. Specify the location of the driver file to use for the upgrade (Figure 3-85). This is either the CD-ROM (if using a CD) or the directory where you downloaded the device driver. Figure 3-85 Device driver copy location 8. The Search results window appears (Figure 3-86 on page 141). Click Next. 140 Implementing IBM Tape in Linux and Windows

169 Figure 3-86 Device driver search results 9. Figure 3-87 indicates there is a newer version of the driver than the currently installed one. Click Next. Figure 3-87 Driver file search results 10.If the driver is not digitally certified by Microsoft, you will see a warning message, Figure 3-88 on page 142. This does not necessarily mean that the driver will not function with the LTO library. If you are unsure of the implications, see the readme file for the downloaded driver. Chapter 3. Basic IBM tape setup for Windows 141

170 Figure 3-88 Digital signature warning The driver is installed. You are notified of the successful installation of the device driver. You may also be prompted to restart the computer. We suggest that you reboot for a clean install. 3.7 Windows 200x Fibre Channel HBA driver installation To connect the server to an IBM tape library using the Fibre Channel interface, your server must have a Fibre Channel Host Bus Adapter (HBA) installed. It is possible to connect through a storage area network or directly to the tape drive, using either direct Fibre Channel attach (using native FC drives where available) or through an external SAN Data Gateway or SDG Module, depending on the IBM tape library models. Note: IBM SAN Data Gateway and the IBM 3583 SDG module were withdrawn from marketing in October The Fibre Channel Host Bus Adapter must be supported and certified by IBM for the IBM library model that you are connecting to the server. To locate supported HBA adapters for Windows, visit the following Web sites to verify that your HBA is supported, selecting the appropriate IBM tape library model and the corresponding server: Once you have verified that your HBA is supported, you have to check the driver level, and if necessary, download an updated driver QLogic QLAxxxx HBA driver installation To determine the latest QLogic adapters supported by IBM LTO libraries and drives, go to the URL corresponding to your device type: Select the Ultrium product and operating system of choice. Clicking the View Details link for each HBA will take you to the vendor s Web site, from which you can download device drivers and microcode. In our case, we want the Windows 200x 142 Implementing IBM Tape in Linux and Windows

171 device driver link. We download the Windows 200x certified device driver, which is in zip format. Unzip the files to a temporary directory. The unzipped files include one file with extension SYS and one with extension INF. This process works for either a new device driver installation, or an upgrade to the existing driver. To install the driver, do the following: 1. Shut down the machine. 2. Install the HBA. 3. Start up the machine. 4. Install the driver using the Found New Hardware wizard. 5. We suggest shutting down to connect the Fibre Channel devices, then rebooting QLogic QLAxxxx HBA driver configuration Much of the Qlogic HBA driver configuration may be performed using the SANSurfer utilities, which are HBA Management Packages from QLogic. You can get SANSurfer for Windows from: Choose the HBA type, go to the Windows 200x link, and download the SANSurfer for Windows package. Notes for installing SANSurfer SANSurfer for Windows consists of several distinct components: SANBlade NT Agent: This utility allows a user to access the SANBlade Manager on a local or remote computer through an authentication mechanism. SANBlade Manager: This is the application that provides an interface through which the adapter and connected devices are viewed. With this utility, adapter settings may be viewed and altered. During the installation phase, a product readme is displayed. Be sure to read this before completing the installation. It contains valuable notes about the adapter setup and discovery of SAN attached devices. Using SANSurfer After SANSurfer is installed, it will place an icon on the desktop. Click it to display a window similar to Figure 3-89 on page 144. Chapter 3. Basic IBM tape setup for Windows 143

172 Figure 3-89 SANSurfer main window Click Connect and enter the host name or IP address to which you want to connect. By default, it will look at the local host and display adapters and discovered devices. You can also specify an alternate SANSurfer host, allowing it to connect to, display, and control another host s HBAs and devices. All configured HBAs will be displayed as in Figure Our configuration contains one QLA2300 adapter. Figure 3-90 SANBlade Manager with HBA 144 Implementing IBM Tape in Linux and Windows

173 Click Configure to show the detailed window for each HBA (see Figure 3-91). Attached SAN devices can now be configured/associated with the HBA. Figure 3-91 Configuring SAN devices By default, auto-configure paths is enabled. This option will list all SAN-attached devices that can be seen by the host. The WWN, WWPN, Port ID, and topologies are displayed. We recommend configuring persistent binding, which is explained in detail in the following section. Apply and save the configuration when all desired devices have been configured. The HBA and devices are now displayed in the HBA tree (Figure 3-92). Figure 3-92 Configured devices Selecting individual SAN devices from the list on the left-hand side displays general information (Figure 3-93 on page 146). Chapter 3. Basic IBM tape setup for Windows 145

174 Figure 3-93 SAN device details The settings for the HBA itself can also be modified based on the device types connected to the HBA. Select the Settings tab from the SANSurfer GUI to modify default parameters. We checked Enable Fibre Channel Tape Support (Figure 3-94). Figure 3-94 SANSurfer Settings tab 146 Implementing IBM Tape in Linux and Windows

175 Select Advanced HBA Port Settings from the drop-down menu to modify additional parameters. If connecting the IBM tape library with the Multi-LUN architecture, LUNs per Target must be set higher than zero (see Figure 3-95). Figure 3-95 SANSurfer Advanced Adapter Settings After specifying the desired settings, click Save and enter the password (the default password is config). You need to reboot to enable the changes. There are other functions and settings that can be set. Refer to the SANblade Manager User s Guide Management Application for SANblade Host Bus Adapters for your specific HBA, which can be found at: Note for IBM Tivoli Storage Manager users To allow the HBA to properly handle larger block sizes when using IBM Tivoli Storage Manager, modify MaximumSGList in the Windows registry under: HKEY_LOCAL_MACHINE->SYSTEM->Current Control Set->Services->vendor device name->parameters->device vendor device name is substituted with the name of the vendor s device. For example, the Qlogic 2200 uses Ql2200 for the respective vendor device name. MaximumSGList is set to hex 41 to work properly with TSM (Figure 3-96 on page 148). Chapter 3. Basic IBM tape setup for Windows 147

176 Figure 3-96 Recommended MaximumSGList value Emulex LPxxxxx HBA driver installation The currently supported Emulex adapters for the IBM tape library and tape drives can be found at the following URL: Check off the IBM tape product and operating system of your choice. If you click the View Details link for each HBA, this will take you to the vendor s Web site to download device drivers and microcode. Note: Emulex provides two driver sets. The miniport driver provides support for the SCSI protocol only. The Multi-Protocol Port Driver provides support for the SCSI and IP protocols, either separately or concurrently. The Multi-Protocol Port Driver also has an additional tool called elxcfg that allows us to do LUN mapping. This tool is not in the miniport driver. Currently, only the Multi-Protocol Port Driver is available for download. Download the installation file that comes in ZIP format. This can be unzipped to a temporary directory. The unzipped files will include a file with the extension SYS and another file with the extension INF. You will find detailed installation instructions for the Emulex adapter (PCI) at the same link. You can download the instructions, or click the Installation link and you will find the installation information. Be sure to read this information before proceeding with the driver installation. To install the driver, do the following: 1. Shut down the machine. 2. Insert the HBA. 3. Start up the machine. 4. We recommend that you reboot or shut down the machine before establishing the Fibre Channel connection. Based upon the specifics of your SAN environment, select the appropriate driver. If using a SAN fabric environment, select fabric, no automap of SCSI ids. 148 Implementing IBM Tape in Linux and Windows

177 3.7.4 Emulex HBA driver configuration The Emulex Multi-Protocol Port Driver for Windows has many options that can be set to provide different behaviors. The options can be set using the configuration utility (elcfg) included in the downloaded.zip file. To start the program, select Start Programs Emulex elxcfg. For our environment, we have set the parameters listed below. Normally this would be all you need to set to use the IBM tape library with the Emulex HBA. Enable FCP-2 recovery Check the box Enable FCP-2 Recovery to enable FC tape support (Figure 3-97). Disable target reset for tape devices Check the box Disable Target Reset for Tape Devices so the driver does not send a Target Reset command to tape drives and media changers in response to a SCSI Bus Reset command (Figure 3-97). Figure 3-97 Emulex Configuration Tool Set up persistent binding We recommend setting up persistent binding, which will permanently assign a SCSI ID to a specific target and maintain a constant view of the same SCSI ID/target relationship between the server reboots , Persistent binding with an Emulex HBA on page 239 describes, in detail, how to set the persistent binding using the Emulex Configuration Tool. Chapter 3. Basic IBM tape setup for Windows 149

178 3.7.5 Emulex LPxxxxx HBA driver removal To remove the Emulex LPxxxxxx HBA, perform the following: 1. Ensure there is no activity on the HBA. 2. Disable the device (recommended, but not mandatory). 3. Uninstall the device. 4. Shut down the machine. 5. Remove the adapter and reboot. You can disable the device from Device Manager, as shown in Figure Locate the device under SCSI and RAID Controllers, right-click, and select Disable. Figure 3-98 Disabling the Emulex HBA To uninstall, follow the same procedure to locate the device, right-click it, and select Uninstall. A pop-up warning box will appear asking for confirmation of the removal of the device. Click OK and the device will be removed. The device should no longer be visible in the Device Manager. You may now shut down the machine and physically remove the adapter. 3.8 IBM Tape Library Specialists We introduce the IBM Tape Library Specialist application in this section and illustrate how to use it to determine or upgrade the library and drive firmware. The IBM Ultrium Tape Library Specialist is a Web-based graphical interface for configuring, updating, and administering IBM LTO libraries. You need the optional RMU on the IBM U and the IBM 3582 to take advantage of the IBM Ultrium Tape Library Specialist. On the IBM 3583, the RMU comes as a standard feature. On the IBM 3584, the IBM Ultrium Tape Library Specialist is embedded in the firmware of the Media Changer Pack (MCP), which is part of the library. The communication is through an Ethernet connection between the host (where the Web browser runs) and the RMU. The Ethernet speed is 10/100MB full duplex and is auto negotiated with the host or switch. Once the library is set up for using the IBM Ultrium Tape Library Specialist, you can connect to the Library using a Web browser, for example, Microsoft Internet Explorer. We recommend that you upgrade your Java runtime environment to the latest available version, which is available at: Implementing IBM Tape in Linux and Windows

179 In the following sections, we describe, in more detail, the IBM Ultrium Tape Library Specialist Specialist applications for the IBM U, 3582, 3583, and Note: In all our examples, we are using the default user ID and password to connect to the library using the RMU. However, for obvious security reasons, we recommend that you change the default password IBM U Tape Library Specialist The IBM Ultrium Tape Library Specialist is embedded in the firmware of the optional Remote Management Unit (RMU). The RMU provides remote access to the library over a network. You can attach the library to your network through a 10/100 Ethernet port on the RMU and the access the IBM Ultrium Tape Library Specialist functions using a Web browser. If you have already installed the RMU, then you need to connect the Ethernet port of the RMU unit to your network. Using the IBM U Operator panel, set the IP address, Subnet Mask, and gateway address. Follow these steps to configure the RMU: 1. Go to OFFLINE MODE. Press Enter to confirm the change, navigate to the Configuration menu. Press Enter to go to the NET PARAMETER menu. 2. Press Enter to go to the NETWORK screen. It displays the current NETWORK value. Press Enter to go to the NETWORK CHANGE TO screen. Use Next and Previous to select ON. Press Enter to initiate the change. 3. Click Next to change to the Dynamic Host Configuration Protocol (DHCP) screen. It displays the current DHCP value. Press Enter to go to the DHCP CHANGE TO screen. Use Next and Previous to select ON or OFF. Press Enter to initiate the change and return to the DHCP screen. Note: We recommend using a fixed IP address for the RMU. When DHCP is used, it is hard to determine the IP address of the RMU. 4. Click Next to display the IP ADDRESS screen. It shows the current value of the IP ADDRESS. Press Enter to go to the CHANGE IP ADDRESS screen. Use Next and Previous to select each digit in the new address. Press Enter to initiate each new digit and move to the next digit to be changed. After all digits have been changed and initiated, click Cancel to return to the IP ADDRESS screen. 5. Click Next to display the GATEWAY ADDRESS screen. It shows the current value of the GATEWAY ADDRESS. Press Enter to go to the CHANGE GATEWAY screen. Use Next and Previous to select each digit in the new address. Press Enter to initiate each new digit and move to the next digit to be changed. After all digits have been changed and initiated, click Cancel to return to the GATEWAY ADDRESS screen. 6. Click Next to display the NETMASK screen. It shows the current value of the NETMASK. Use Next and Previous to select each digit in the new address. Press Enter to initiate each new digit and move to the next digit to be changed. After all digits have been changed and initiated, click Cancel to return to the NETMASK screen. 7. Click Cancel once to return to the NET PARAMETER screen, twice to return to the Configuration Menu screen, and three times to return to the Home screen. Figure 3-99 on page 152 shows the Net Parameter configuration tree. Chapter 3. Basic IBM tape setup for Windows 151

180 Figure 3-99 Configuration menu s NET PARAMETER command You should now be able to access the Tape Library Specialist from a Web browser by entering the RMU s IP address. Figure shows the login screen. Figure IBM 3581 Tape Library Login screen Log in as an Administrator with the default password of secure. When logged in as a Standard User, you can only access the Status and Information functions; configuration changes cannot be made. If you cannot log on, check that the library is not in Offline Mode. Notice that only one connection type can be used to communicate with the library. If you are already logged on using the RMU and then try to log on using the Operator panel, a warning is displayed in the Operator panel. 152 Implementing IBM Tape in Linux and Windows

181 Click the Login button to log in. To operate and maintain the library, select Maintenance Operations. This shows a quick status of the library and can select the main operating tasks (see Figure 3-101). Use the menu bar on the left of the panel, to navigate between the menus. You can choose from the following options: Information Status Configuration Maintenance Logs Autoloader Drive Autoloader Media Media Device Network User RTC Log Event Notification Configuration Reset Operations General Diagnostic Advanced Diagnostic Firmware Reset Loader Drive Figure IBM U operation screen From the Maintenance menu, select Firmware to upgrade the firmware of the drive and the autoloader. For more information about upgrading the drive and autoloader firmware, see Updating the IBM U drive firmware using the Specialist on page 178. Chapter 3. Basic IBM tape setup for Windows 153

182 Figure IBM U firmware update screen You can download the latest firmware from one of the following sites: ftp://index.storsys.ibm.com/358x IBM 3582 Tape Library Specialist The IBM Ultrium Tape Library Specialist for the IBM 3582 is embedded in the firmware of the optional Remote Management Unit (RMU). The RMU provides remote access to the library over a network. You can attach the library to your network via a 10/100 Ethernet port on the RMU and access the IBM Ultrium Tape Library Specialist functions through a browser interface. If you have already installed the RMU, then you need to connect the Ethernet port of the RMU unit to your network. Use the IBM 3582 Operator panel to set the IP address for the RMU. Select Main Menu Setup RMU. The panel shown in Figure is displayed. Figure Operator panel: Configuring RMU IP address Use the Up and Down buttons to enter the IP address and use the Left and Right buttons to move between fields. Next enter the subnet address and gateway (if present). From the last field of the Gateway address, click Right to set the Gateway mask and highlight Execute. Click the Enter button twice to accept the RMU settings. 154 Implementing IBM Tape in Linux and Windows

183 You should now be able to access the Specialist from a browser by entering in the IP address. Figure shows the welcome window of the IBM 3582 Ultrium Tape Library Specialist. Figure IBM 3582 Specialist welcome screen The first time you use the Specialist, log in as admin with the password secure. Then you can access the Configuration menu to add any additional users that need access. Remember that every user defined can potentially access every option available on the IBM 3582 Operator panel. Use the menu bar at the top of the panel, right below the title bar, to navigate between the menus. You can choose between the following options: Status Configuration Firmware Diagnostic file Library Status. Drive Status. RMU User. Hostname. IP Address. MAC Address. Library Serial #. SNMP. SNMP Alerts. Library Firmware. RMU Firmware. Network Configuration. User Configuration. SNMP Configuration. Date and Time. Reboot. Update RMU Firmware. Update Library Firmware. Update Drive 1. Update Drive 2. Library Command Log. Library Error Log. RMU Support Log. RMU Error Log. Drive 1 Error Log. Chapter 3. Basic IBM tape setup for Windows 155

184 Operator Logs Drive 1 Dump. Drive 2 Error Log. Drive 2 Dump. Access every option available on the IBM 3582 Operator panel. Current Command Log. In the black column, on the left-hand side of the Specialist window, you will find the help and documentation links that allow you to directly access the IBM 3582 publications online. Next, we show some examples of the IBM 3582 Specialist panels. In the configuration panel shown in Figure 3-105, you can set the network configuration parameters and Simple Network Management Protocol (SNMP) settings to send the alerts generated by the RMU to an SNMP server in your private network. We describe setting up SNMP for the 3582 in Configuring SNMP for the IBM 3582 on page 405. The configuration panel also provides user management for the Specialist interface. Figure IBM 3582 Specialist: Configuration panel In the Diagnostics file panel shown in Figure on page 157, you can view and download the library and RMU logs. These are discussed further in Troubleshooting on page Implementing IBM Tape in Linux and Windows

185 Figure IBM 3582 Specialist: Diagnostics file panel In the Operator panel shown in Figure 3-107, you can operate the library exactly as though you were at the real IBM 3582 Operator panel. The graphic display shows an image of the IBM 3582 LCD panel that has exactly the same functions as the physical library display. This feature allows you to view or update the configuration, reboot the library, vary drives offline, and all other Operator panel tasks remotely from any browser window. Figure IBM 3582 Specialist: Operator panel IBM 3583 Tape Library Specialist The IBM Ultrium Tape Library Specialist is embedded in the firmware in the RMU, which comes as a standard feature in the IBM The RMU provides remote access to the library over a network. You can attach the library to your network through a 10/100 Ethernet port on the RMU and access the IBM Ultrium Tape Library Specialist functions through a browser interface. Chapter 3. Basic IBM tape setup for Windows 157

186 If you have already installed the RMU, then you need to connect the Ethernet port of the RMU unit to your network. Using the IBM 3583 Operator panel, set the IP address for the RMU. Select More Setup Library RMU. The panel in Figure is displayed. Figure IBM 3583 Operator panel: Configuring RMU Use the Up and Down buttons to enter the IP address, subnet address, gateway (if present), and host name. When finished, select OK. You should now be able to access the Specialist from a browser by entering the IP address. Figure shows the welcome window of the IBM 3583 Tape Library Specialist. Figure IBM 3583 Specialist: Welcome screen The first time you use the Specialist, log in as admin with the password secure. Then you can access the Configuration menu and add the users that need access to the Specialist. Remember that every defined user can potentially access every option available on the IBM 3583 Operator panel. Use the menu bar at the top of the panel, right below the title bar, to navigate between the menus. You can choose between the following options: Status Library status. Drive status. RMU user. Hostname. IP address. MAC address. Library serial #. 158 Implementing IBM Tape in Linux and Windows

187 Configuration Firmware Diagnostic file Operator panel Logs SNMP alerts. Library firmware level. RMU firmware level. Network configuration. SNMP configuration. User configuration. Date and time. Reboot. Update library firmware. Update RMU firmware. Update drive firmware. Library command log. Library error log. RMU support log. RMU error log. Drive error logs. Drive dumps. Access every option available on the IBM 3583 Operator panel. (This is a graphical interface updated every few seconds.) View the current command log. The black column on the left-hand side of the Specialist window contains the help and documentation links that allow you to directly access the IBM 3583 publications. Next, we show some examples of the IBM 3583 Ultrium Tape Library Specialist panels. In the configuration panel shown in Figure on page 160, you can set the network configuration parameters and Simple Network Management Protocol (SNMP) settings to send the alerts generated by the RMU to an SNMP server in your private network. We will describe setting up SNMP for the IBM TotalStorage 3583 Tape Library in Configuring SNMP for the IBM 3583 on page 406. The configuration panel also provides user management for the Specialist interface. Chapter 3. Basic IBM tape setup for Windows 159

188 Figure IBM 3583 Specialist: Configuration panel In the Diagnostics file panel shown in Figure 3-111, you can view and download the library and RMU logs. These are discussed further in Troubleshooting on page 435. Figure IBM 3583 Specialist: Diagnostics file panel In the Operator panel shown in Figure on page 161, you can operate the library exactly as though you were at the real 3583 Operator panel. The graphic display showing the image of the 3583 LCD panel has exactly the same functions as the physical library display. This 160 Implementing IBM Tape in Linux and Windows

189 feature allows you to view or update the configuration, reboot the library, vary drives offline, and do all other Operator panel tasks remotely from any browser window. Figure IBM 3583 Specialist: Operator panel IBM 3584 Tape Library Specialist The IBM 3584 Tape Library Specialist is embedded in the Media Changer Pack (MCP). You will need to attach the Ethernet port to your network with a suitable cable and configure the TCP/IP address information. Choose Settings Network Ethernet. You will see the current interface MAC address (which cannot be changed), and the assigned TCP/IP address, subnet mask, and gateway. If the library has more than one frame and you want to use several connections, then each frame requires a separate address. Use the Up and Down buttons to access the panels for the additional frames. The current configuration window is shown in Figure Panel 0175 Ethernet Current Settings Frame 1: MAC Address: 18:36:F3:98:4F:9A IP Addresses: Subnet Mask: Gateway: [Change Settings] BACK UP DOWN ENTER Figure Change Ethernet parameters on 3584 Click ENTER to make the changes. You can select to disable the Ethernet interface, use DHCP for automatically address assignment (if supported in your network), or manually configure the parameters. After configuring the network connection for the IBM Ultrium Tape Library Specialist, enter the TCP/IP address of the library in your browser. The welcome page of the IBM 3584 Specialist Web interface displays, as shown in Figure on page 162. With the Specialist, you can monitor library status and perform library operations from a remote location. Use the Work Chapter 3. Basic IBM tape setup for Windows 161

190 Items area on the left to navigate to available Specialist tasks. For more information, click the? icon in the top right of the screen Figure IBM 3854 Specialist: Welcome page Use the left-hand side of the panel to navigate between the menus. You can choose between the following options: Manage Cartridges Manage Drives Manage Library Manage Ports Manage Access Service Library Data Cartridges Cleaning Cartridges I/O Station Cartridge Assignment Policy Insert Notification Drive Summary Drive Assignment Control Paths World Wide Names Cleaning Mode by Frame by Logical Library Accessor Preferred Accessor Zones Disable ALMS Virtual I/O Date and Time 6 Character VOLSER Reporting Fibre Channel Summary Change Password SNMP Settings SNMP Destinations System Data Library VPD Drive VPD 162 Implementing IBM Tape in Linux and Windows

191 Node Card VPD Download Library Logs Download Drive Logs Firmware Update Master Console Adjust Scanner Speed You may also choose between managing the physical library or the logical libraries. For more information about the Advanced Library Management Services, please see 2.3, ALMS on page 58. The IBM 3584 Tape Library Specialist is a complete interface that allows you to easily configure and monitor the library operations, with graphics and tables like those shown in Chapter 3-115, 3584 Specialist: Physical Library Summary panel on page 163. Figure Specialist: Physical Library Summary panel The IBM 3584 Library Specialist has menus to manage the cartridges, drives, or library. To view a list of the cartridges in the library, select Manage Cartridges Data Cartridges. Using the drop-down boxes, you can filter the cartridges displayed by frame or logical library. Figure on page 164 lists the cartridges in the logical library LTO3Fibre. After selecting a cartridge, you may move it to a tape drive, remove it from the library, or assign it to a logical library. Chapter 3. Basic IBM tape setup for Windows 163

192 Figure IBM 3584 Specialist: Cartridges For information about Cartridge Assignment Policy, please see Cartridge Assignment Policy on page 62. To view a list of the drives in the library, select Manage Drives Drive Summary. On the Drives screen, you can use the drop-down boxes to limit the drives selected to a specific frame or a specific logical library, or you can select all frames or all logical libraries. In Figure on page 165, the 3592 Fibre drives are listed. As shown in Figure on page 165, after selecting a tape drive, you can clean it, change its SCSI ID (or Loop ID if FC), view drive details, move a cartridge, or do a power cycle of a drive. This feature can be especially useful when sharing drives in a SAN (for example, LAN-free backup). In this circumstance, when a server is using a drive, it issues a SCSI reserve command, which blocks it from other servers. The drive is unavailable to other jobs until the server with the reserve sends a release command to the tape drive. But if the server with the reserve cannot release it (for example, because it is powered down), a power cycle is required on the tape drive to release the block. 164 Implementing IBM Tape in Linux and Windows

193 Figure IBM 3584 Specialist: drive summary To change a drive s settings, select that drive from the Drives screen and click Change ID. You will get a warning (Figure 3-118) stating this function may interrupt the library activity. Indeed, changing the Drive SCSI/Loop ID will interrupt library and drive activities and may require reconfiguring the host computers. Figure IBM 3584 Specialist: ID change warning Select Manage Drives Drive Assignment to display the Drive Assignment Filter screen. You can select all drives or a specific drive, and all logical libraries or a specific logical library. In Figure on page 166, all drives for logical library LTO3 Fibre are selected for display. Chapter 3. Basic IBM tape setup for Windows 165

194 Figure IBM 3584 Specialist: Drive Assignment Filter As shown in Figure 3-120, after selecting a tape drive, you may unassign the drive or assign the drive as a control path. To assign a drive as a control path, click the block to the left of the check box for the drive and click the Apply button above the Drives column. In Figure 3-120, drive B is a control path, as is indicated by the icon shown on the left of the check box in the LTO3 Fibre column. Figure IBM 3584 Specialist: Drive Assignment 166 Implementing IBM Tape in Linux and Windows

195 You will see a warning (Figure 3-121) that changing a drive or control path assignment may affect the associated host applications and that a reset or rediscovery of its devices may be needed. Figure IBM 3584 Specialist: Assignment Change warning You can also configure the library directly from the Specialist panels, specifying the SAN parameters, or the SCSI control paths, control ports, and security options. Note that the TCP/IP configuration function is not available from the IBM Tape Library Specialist. With password protection on, users may change their password by selecting Manage Access Change Password (see Figure 3-122). Note that in some versions of the Tape Library Specialist, the navigation sequence is Manage Access Security. Figure Change Password screen A password is required to access some functions of the Specialist, such as firmware update and the modification of the library configuration. The Specialist interface offers three levels of security access for its windows (also called pages). Before performing library functions, you must determine the type of security access that you need. Table 3-2 describes each level. Table 3-2 Types of password protection Type of password protection No password protection Password protection for administration pages Description You are never prompted to sign on. You are prompted to sign on to access the administration pages. Administration pages are functions that allow you to change library settings. Chapter 3. Basic IBM tape setup for Windows 167

196 Type of password protection Password protection for all pages Description You are prompted to sign on whenever you use the IBM 3584 Specialist. This type of protection allows you to view all pages (by using a user password) or to change administration pages (by using an admin password). The factory default for the IBM 3584 Specialist is no password protection. The first time that you choose password protection for administration pages or for all pages, the library generates an initial password, which can be changed. Also, if you set the security level back to no password protection, the password will deactivate. The following administration functions are protected if the admin password is enabled: Change control port SCSI IDs. Change drive SCSI or Loop IDs. Change the cleaning mode. Change the date and time. Change the Specialist Web interface admin password. Clean the drive. Configure logical libraries. Cycle power to the drive. Download logs. Enable or disable control paths. Import data or scratch cartridges (importing cleaning cartridges is not password-protected). Inventory the library. Move cartridges. Remove cartridges. Update control port firmware. Update library and drive firmware. 3.9 Updating library, drive, and RMU firmware It is a good habit to check periodically for available updates on the IBM Web site; newer code can provide additional support functions or fix problems. To upgrade the installed microcode level of the library, refer to the Operator Guide for your library or drive. In our example, we describe the procedures to check and update the library and drive microcode for various IBM LTO models Keeping up-to-date with drivers and firmware using My Support My Support registration provides notification when new firmware levels have been updated and are available for download and installation. To register for My Support: 1. Visit the Web at: Implementing IBM Tape in Linux and Windows

197 2. Under Personalized support, click My support. 3. If this is your first access, under Sign in, click Register; otherwise, go to step Fill in the information required for registration. Items with an asterisk (*) are required fields. 5. Enter your user ID and password and click Submit to access My Support. 6. Enter the information required for your My personalized page. a. Select Add products. a. Under the Products drop-down, select Storage. b. In the next drop-down, select Computer Storage. c. In the next drop-down, select Computer Tape Storage. d. In the next drop-down, select either Computer tape autoloaders (IBM 3581) or Computer tape libraries (IBM 3582, IBM 3583, or IBM 3584). e. Click the check boxes for the appropriate products. f. Click Add products at the bottom of the page. g. Review your profile for correctness. h. Under Subscribe to , select Storage and then check the boxes labeled Flashes and Downloads and Drivers, and click Update. i. Under Welcome, (your name), click Sign out to end your session. You will be notified whenever there is new firmware available for the products you selected during registration Check the installed firmware To check for microcode updates, use one of the following links: ftp://ftp.software.ibm.com/storage/358x ftp://index.storsys.ibm.com/358x/ You can find the latest microcode releases for the LTO library, drives, and RMU (if installed) here. For the library microcode, use the compressed file appcode.zip for Windows systems, or appcode.tar for UNIX systems. It contains the Vn_n_n.lif file that is the microcode image file to upload in the library. For the drive code, download the latest.ro file. Check IBM 3580 installed firmware level To determine the current level of firmware on the IBM 3580, watch for the message Drive FW xxxx (where xxxx is the firmware level) to display while you power the drive off and then back on. Check IBM 3581 installed firmware level Note: All models of the IBM TotalStorage 3581 Tape Autoloader (IBM 3581-L17/H17, IBM 3581-L13/H13, and IBM 3581-L23/H23) were withdrawn from marketing in October To check the installed firmware level from the IBM 3581 operator pane, make sure that LdR REAdY appears on the message display. Chapter 3. Basic IBM tape setup for Windows 169

198 1. Click and hold the NEXT button and then the MODE button until diag MENU displays (approximately five seconds). 2. Click MODE until dsp FW displays. 3. Click SELECT. dsp LdR FW displays. 4. Click SELECT. Ld FW NNNN displays (where NNNN is the revision number of the autoloader firmware). 5. Click NEXT. dsp drv FW displays. At this point, you can select the firmware for the drive 1. Click SELECT. dr FW NNNN displays (where NNNN is the revision number of the drive firmware). 2. Click NEXT. dsp MTN FW displays. 3. Click SELECT. LdR REAdY displays. Go back to the main menu. Check IBM U installed firmware level To check the installed firmware level from the IBM U Operator panel: Autoloader firmware: Click Previous or Next until Information is displayed. Press Enter. Click Next or Previous until you see LOADER INFO. Press Enter. Firmware REV. X.XX is displayed, where X.XX is the firmware level of the autoloader Drive firmware: Click Next or Previous until Information is displayed. Press Enter. Click Next or Previous until Drive Info is displayed. Press Enter. Product REV. XXXX is displayed, where XXXX is the current firmware of the drive. Check IBM 3582 installed firmware level To check the installed firmware level from the IBM 3582 Operator panel: 1. Select Main menu Status menu display F/W. 2. This shows the firmware levels of the following components: RMU, APPLICATION, DRIVE 1, DRIVE 2, and PICKER. Check IBM 3583 installed firmware level To check the installed firmware level from the IBM 3583 Operator panel: Library firmware: Select More About Details. The Version field displays the microcode level. Drive firmware: Select Status Drives. The Version field displays the microcode level. Check IBM 3584 installed firmware level To check the installed firmware level from the IBM 3584 Operator panel: Library firmware: Select MENU and then select Vital Product Data Node Card VPD. The Firmware Version field displays the firmware level. Drive firmware: Select MENU and then select Vital Product Data Drive VPD. The fourth column displays the drive firmware level for each drive. You can also check the installed firmware level with the IBM Ultrium Tape Library Specialist. Select Services Drive VPD to show the drive Firmware level (Figure on page 171). 170 Implementing IBM Tape in Linux and Windows

199 Figure IBM 3584 Specialist: Check drive firmware version How to update the firmware You can use the following methods to update the firmware: Using the RMU and the IBM Ultrium Tape Library Specialist Using NTUTIL Using the Field Microcode Replacement (FMR) tape (drive firmware only) (not supported on the IBM 3581 (not covered in this redbook)) Using the library serial port (not covered in this redbook) Using LTO-TDX Here is an example of the firmware upload time using different methods. We used the IBM 3581 to compare the different methods (see Figure 3-3). This table is for general information only; your times may vary. Table 3-3 Firmware upload times via different methods Method Type of firmware Update time Autoloader Drive SCSI (using NTUTIL or TAPEUTIL) Autoloader and Drive Not tested 66 seconds SCSI (using LTO-TDX) Drive Only N/A 90 seconds Serial Port Autoloader and Drive 6 minutes 13 minutes RMU Autoloader and Drive 45 seconds 6 minutes Detailed instructions on how to update the firmware are at the following Web site. Select the appropriate LTO model and then Download: Chapter 3. Basic IBM tape setup for Windows 171

200 If you have an IBM 3583 with the optional SAN Data Gateway module installed, you can update the firmware using the gateway itself. For more information, see IBM Storage Area Network Data Gateway Module Setup, Operator, and Service Guide, GA Note: The IBM SAN Data Gateway and the 3583 SDG module were withdrawn from marketing in October Note: Before updating firmware on the drives, the library, or the RMU, vary the library OFFLINE to ALL attached hosts. As an example, we show how to upgrade the library and drive microcode through the SCSI bus interface using the NTUTIL utility for Windows 200x. Then we show how to update the RMU code from the IBM Tape Library Specialist panels and using the LTO-TDX tool. Upgrading library firmware using NTUTIL The following procedure describes how to update the library firmware in the IBM 3581, U, 3582, 3583, or 3584, over the SCSI bus using NTUTIL. 1. Download the latest library firmware from either of these sites to a directory: ftp://ftp.software.ibm.com/storage/358x 2. If you have an application device driver other than the IBM Tape Device Driver, you will need to stop it and start the IBM Tape Device Driver. NTUTIL will only work with this device driver, so you will need to install it if you have not already done so. You must also stop the Removable Storage Manager (RSM) if it started. You will find RSM under Start Settings Control Panel Administrative Tools. 3. Open an NTUTIL session on a command line from the directory where the library firmware image was saved (for example, c:\winnt\system32) by typing NTUTIL at a command prompt. This is not necessary, but if you do it now, then in a later step you do not need to type in the complete path. 4. Enter 1 for a manual test (Example 3-19). Example 3-19 NTUTIL main menu NTutil - Copyright (c) IBM Corporation Main Menu: Microsoft Windows 2000 version ========== 1: Manual test 2: Batch test 9: Exit ntutil Enter selection: 1 5. The NTUTIL interactive menu will be displayed (Example 3-20 on page 173). 172 Implementing IBM Tape in Linux and Windows

201 Example 3-20 Manual test menu manual test menu: ======================================================================= 1: set device special file 2: display symbols 3: set block size R/W (now!0 fixed) 5: set return error when fail 6: set/reset trace 7: set exit on unexpected result 8: Library Mode ======================================================================= 20: open 21: close 22: read 23: write 24: read and display block 25: flush (buffer->media) 26: read block id 27: erase 28: locate block id 29: display block data ======================================================================= 30: write filemark(s) 31: rewind 32: forward space filemark(s) 33: unload 34: reverse space filemark(s) 35: load 36: forward space record(s) 37: return error 38: reverse space record(s) 39: test unit ready 43: set media parms (block size) 44: set dev parms(compression) 46: get device information 47: restore data 48: get medium information 49: inquiry 50: poll registered devices 53: space EOD 54: display message ======================================================================= 70: system command ======================================================================= 80: Force Dump 81: Read Dump 82: Update MicroCode 83: Log Sense 84: Get Last Sense 85: Get Version 86: Associative/Persistent WProtect 87: Read/Write Test 88: List registered devices 89: Get MTDevice Info ======================================================================= 99: return to main menu ======================================================================= enter selection: 6. Change to Library mode by entering 8 (Example 3-21). Example 3-21 Changing modes ======================================================================= enter selection: 8 Closing any open device before changing mode Total elapsed time in seconds = 0.00 Return to continue: 7. Obtain the device names that will be used to set the device special file in the next step by entering 88 (Example 3-22). Example 3-22 List registered devices enter selection: 88 Device found: Port 2\Scsi Bus 0\Target Id 0\Logical Unit Id 0" Device found: Port 2\Scsi Bus 0\Target Id 1\Logical Unit Id 1" Device found: Port 2\Scsi Bus 0\Target Id 1\Logical Unit Id 0" Device found: Port 2\Scsi Bus 0\Target Id 1\Logical Unit Id 1" Total elapsed time in seconds = 0.00 Return to continue: Chapter 3. Basic IBM tape setup for Windows 173

202 8. Select 1: set device special file. Enter the name of the tape and library path displayed in the previous step. In this example, we use Tape0 and Changer0 (Example 3-23). Example 3-23 Set special file enter selection: 1 Enter device special file (tape path) name or return for no change: tape0 Enter device special file (changer path) name, or "def" for default lun1 changer or return for no change: changer0 Total elapsed time in seconds = Return to continue: 9. Enter 20 to open the tape device and Medium Changer. Enter 1 for read/write (RW) operations when prompted (Example 3-24). Example 3-24 Open the library and tape devices enter selection: 20 Enter open mode (1) RW (2) RO: 1 special file (\\.\tape0) will be opened special file (\\.\changer0) will be opened analyze() called with rc 8 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 1.00 Return to continue: 10.Verify the connection by entering 49 (Example 3-25). Example 3-25 Inquiry enter selection: 49 Drive = 0, Library = 1: 1 Changer Path SCSI data: PortNumber 2, PathId 0 TargetId 0, Lun 1 INQUIRY data: devtype(0): 08, rmb(1): 80 ASO/ECMA/ANSI(2): 02, resp_data_fmt(3): 02 additional_length(4): 33, reserved(5): 00 SCSI_3(6): 20, flags(7): 00 vendor_id (8-15): IBM product_id (16-31): ULT3582-TL Microcode Revision Level (32-35): 237B vendor specific (bytes 36-55): analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 2.00 Return to continue: 11.Enter 82 from the menu to update the microcode. 12.Enter the name of the saved.lif file. 13.Enter 1 for the library. 14.Press Enter. Do not touch the drive until the firmware load has completed. During this time the library will reboot. The NTUTIL session will lose visibility to the library and will have to be restarted to enable communication (Example 3-26 on page 175). 174 Implementing IBM Tape in Linux and Windows

203 Example 3-26 Update library firmware enter selection: 82 Enter microcode image name (1 to 8 characters), or return to skip: 370B_001.lif Drive = 0, Library = 1: 1 Image size = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring 480 image bytes, total bytes = Waiting for tape device to write flash-prom Do not touch drive until complete analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = Return to continue: The output indicates the firmware update was successful (ERROR_SUCCESS), as shown in Example To verify that the firmware installed correctly, at the LTO tape library operator console, follow the instructions for your library listed in 3.9.2, Check the installed firmware on page 169 and check if the version shown is the same as the firmware version used to update the library. Example 3-27 Firmware version (C) 2003 IBM SerNum:xxxxxxx Version:370B Upgrading drive firmware using NTUTIL The following procedure describes how to update the drive firmware over the SCSI bus using the NTUTIL utility. 1. Download the latest drive firmware (xxxx.zip) to a local directory from either of these sites: ftp://ftp.software.ibm.com/storage/358x Chapter 3. Basic IBM tape setup for Windows 175

204 2. If you have an application device driver other than the IBM Tape Device Driver, you will need to stop it and start the IBM Tape Device Driver. NTUTIL will only work with this device driver, so you need to install it if you have not already done so. You also have to stop RSM if started. You will find the RSM under Start Settings Control Panel Administrative Tools. 3. Open an NTUTIL session on a command line from the directory where the library firmware image was saved, by typing NTUTIL at a command prompt. 4. Select 1: manual test (Example 3-28). Example 3-28 NTUTIL main menu Main Menu: Microsoft Windows 2003 version ========== 1: Manual test 2: Batch test 9: Exit ntutil Enter selection: 5. Open the device by entering 20 (Example 3-29). Example 3-29 Open tape device enter selection: 20 Enter open mode (1) RW (2) RO: 1 special file (\\.\tape0) will be opened analyze() called with rc 6 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 8.00 Return to continue: 6. Select read/write operations Update the microcode by entering Enter the name of the *.ro file. 9. Press Enter. Do not touch the drive until the firmware load has completed (Example 3-30). Example 3-30 Update firmware enter selection: 82 Enter microcode image name (1 to 8 characters), or return to skip: 53Y2L2F.ro Image size = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = Transferring image bytes, total bytes = ======================================================================= Waiting for tape device to write flash-prom 176 Implementing IBM Tape in Linux and Windows

205 Do not touch drive until complete (Avg sec) Microcode updated, standby for the drive to initialize analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = Return to continue: 10.The rc 1 err 0 (ERROR_SUCCESS) message will be displayed after a successful download, and just above it, the instruction to exit NTUTIL and reboot the drive Upgrading RMU firmware using the IBM Tape Library Specialist To update the IBM U, 3582, or 3583 RMU firmware, use the IBM Tape Library Specialist panels. 1. Download the latest RMU firmware (xxxx.zip) to a directory. Visit the following sites for the firmware: ftp://ftp.software.ibm.com/storage/358x 2. Open the RMU Web page using a browser and select the Firmware tab (log in if necessary). Put the library offline. 3. Select Update RMU Firmware. Enter the path and firmware file name or browse for the downloaded firmware file and click Update Firmware (see Figure 3-124). Figure Tape Library Specialist: Updating RMU firmware Check the IBM Ultrium Tape Library Specialist from the main panel for the updated RMU firmware level information after the successful completion of the operation. Chapter 3. Basic IBM tape setup for Windows 177

206 3.9.4 Upgrading drive firmware using the IBM Tape Library Specialist To update the U, 3582, 3583, or 3584 drive firmware, use the IBM Tape Library Specialist panels. Updating the IBM U drive firmware using the Specialist To update the drive firmware using the IBM 3581 Tape Library Specialist, download the latest version at: ftp://ftp.software.ibm.com/storage/358x ftp://index.storsys.ibm.com/358x/3581 Log on to the Specialist as Administrator; the default password is secure. Select Maintenance Firmware. Select the new firmware and click the Update button. A warning message pops up asking for confirmation. Click Yes to start the update. The Specialist does not show any status screen until the update is complete, but on the Operator Control Panel, the Drive Firmware Upgrade message is shown. After the firmware update is finished, a reboot is initiated. Updating the IBM 3582 drive firmware using the Specialist To update the drive firmware using the IBM Tape Library Specialist, the latest firmware for the Ultrium drives can be found at: ftp://ftp.software.ibm.com/storage/358x From the Ultrium Tape Library Specialist Welcome screen, select the Firmware tab. Enter the user name and password. The default settings are Admin for the user and secure for the password. Select the drive you want to update and select the new firmware. Click the Update Firmware button. A status of the drive update process is displayed. It can take more than one hour to update one single drive. Updating the IBM 3583 drive firmware using the IBM Specialist The latest firmware for the Ultrium drives can be found at: ftp://ftp.software.ibm.com/storage/358x From the Ultrium Tape Library Specialist Welcome screen, select the Firmware tab. Enter the user name and password. The default settings are Admin for the user and secure for the password. Select the drive you want to update and use Browse to select the new firmware. Click the Update Firmware button. The status of the drive update process is displayed. Updating the IBM 3584 drive firmware using the IBM Specialist To update the drive firmware using the IBM Tape Library Specialist, the latest firmware for the Ultrium drives can be found at: ftp://ftp.software.ibm.com/storage/358x From the Service Library menu, select Firmware Update. An attention screen pops up to verify that you have the firmware update that you want to apply. If not, select the link to the Ultrium support site and download the appropriate firmware update. When you have the appropriate firmware downloaded, click the Launch Firmware Update Wizard icon. Select the model for the drive you want to update and click the Next button. 178 Implementing IBM Tape in Linux and Windows

207 A warning will pop up indicating that the drive will be taken offline during the update. If you wish to continue, click the Next button. Select a specific drive in the drop-down list to be updated or select All drives. Use the Browse button or enter the file name to load the firmware file you downloaded from the support page. Click Update to finish the firmware update. The drive will be taken offline during the firmware update process. The library should then activate the new firmware automatically Upgrading the drive firmware using LTO-TDX LTO-TDX is a SCSI and Fibre Drive Firmware Download and LTO Dump Upload tool. LTO-TDX is an alternative method for downloading LTO drive firmware across the SCSI bus or Fibre Channel. In addition, this tool can be used to upload LTO drive error dumps, which can be sent to the Support Center for further analysis. LTO-TDX needs no additional drivers and it is the fastest and easiest way to update a drive firmware. Note: LTO-TDX is available for Windows, Linux, and NetWare operating systems. The following information describes how to obtain the tool and lists its capabilities. The tool supports all IBM LTO Gen 1, Gen 2, and Gen 3 SCSI and FC drives. The tool will not support any other manufacturer s LTO drive. The tool can perform two functions: Download firmware to the drive. Upload a dump of the drive firmware logs from the drive to a host where the FC or SCSI HBA is installed. The tool can load back-level (older) code. The tool is distributed through the IBM Web site: Select Linear Tape-Open (LTO) in the Product family drop-down, enter your library model in the Product drop-down and click Go. Click the Download tab, and under Tools and Utilities, click Software. You should see a link to download LTO-TDX. Run the downloaded tool file (executable file) to install it. It creates an icon on the Windows desktop and two folders called LTO firmware and LTO dump. Any firmware downloaded for install must go in the firmware folder. Any dumps created are placed in the dump folder. The tool presents a list of the supported devices on the bus. The tool allows selection of a target device and then performs the download or the dump on the target device. To save time, verify that the drive is empty. The tool checks to see if a cartridge is in the drive (cartridge present sensor activated). If a cartridge is present, it will post an error and request that you remove the cartridge. Double-click the LTO-TDX icon from the Windows Desktop. Figure on page 180 displays. Chapter 3. Basic IBM tape setup for Windows 179

208 Figure LTO-TDX selection screen 1 Verify the firmware you want to download to the drive is in the LTO firmware folder. Press Enter. It will scan the bus for attached LTO devices and display them (see Figure 3-126). Figure LTO-TDX selection screen 2 In our example, two LTO drives are found. Enter the device number to upgrade (for example, Device 1) and press Enter (see Figure on page 181). 180 Implementing IBM Tape in Linux and Windows

209 Figure LTO-TDX Selection screen 3 Enter 1 and press Enter to load the firmware to the drive (see Figure 3-128). Figure LTO-TDX selection screen 4 A list shows the firmware levels available for selection from the LTO Firmware folder. Enter the number of the firmware for the program to load (see Figure on page 182). Chapter 3. Basic IBM tape setup for Windows 181

210 Figure LTO-TDX selection screen 5 The download takes about 90 seconds. After the firmware has been loaded into the drive memory, the drive automatically reboots. During the download process, a message is displayed on the Operator Control Panel saying Updating...Please Wait until the reboot. If the program tries to load code and it fails with a sense Key 5 and an ASC/ASCQ of 82/83, it displays the message: Bad Firmware Detected. This means the firmware is the wrong type for your tape drive or the file is corrupted. Consult your drive service provider for the correct file. Drive log dump function For the drive log dump function: When the dump function is executed on a drive, the tool reads the existing dump on the drive, forces a dump, then reads the forced dump. This creates two dump files: The two dump files created by the dump function are time stamped with year, month, day, and seconds, and contain the drive serial number. The first dump file read has an A suffix. The second file produced has a B suffix. The tool places the files that are created in the LTO Dumps folder in the directory with the tool. The tool creates the dump files with a file type of.dmp. These files are now ready to be sent to the Support Center for further analysis. 182 Implementing IBM Tape in Linux and Windows

211 4 Chapter 4. Basic IBM tape setup for Linux This chapter provides detailed information about the basic setup of the IBM tape drives and libraries on Linux on Intel and zseries platforms. This includes: Linux native tape driver usage IBM tape device driver installation Host Bus Adapter driver configuration At the end of this chapter, you should be able to understand and implement the tasks required to: Install the required device drivers. Verify and use the IBM tape device. Configure the required Host Bus Adapter drivers. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 183

212 4.1 Hardware and software requirements IBM LTO devices on Linux are supported on Intel, pseries, and zseries platforms. Up-to-date information about supported Linux and LTO hardware and software configurations can be found at: Select the LTO model of interest, click Product Details, then on the next page, click the Interoperability link. Download the interoperability matrix, scroll down, and select the appropriate server to view which OS versions and HBAs are supported. While the Intel systems support all the IBM Ultrium devices, at the time of writing, pseries and zseries may only support a subset of the libraries with LTO and 3592 drives and associated functionality. Be sure to check the Web site for supported operating system versions, kernel levels, adapters, and device drivers. 4.2 Installing library and tape device drivers After physically installing and connecting your IBM tape drive or library to your environment, the next step in the basic implementation of the IBM tape library and drives is to make the devices accessible for your operating system. In Linux, you can choose to use either the IBM tape drivers or the native Linux drivers to access the tape drive and library devices. The IBM tape and medium changer device drivers are designed specifically to take advantage of the features provided by the IBM tape drives and medium changer devices. This means that you should use the IBM tape device drivers wherever this is possible. Nevertheless, you can use the Linux native drivers when that is required for your solution. The examples in Chapter 9, Configuring BakBone NetVault on Windows and Linux on page 341, and Chapter 10, Configuring Arkeia on Linux on page 369 in this redbook worked perfectly using the native Linux Device Drivers. Note: IBM tape drives and libraries are usually used with vendor-provided software applications. These may work with the IBM-provided device drivers, their own provided device drivers, or even native operating system device drivers for the tape drive and medium changer (or some combination of these, for example, the IBM drive device driver and application-provided medium changer driver). For correct operation, follow the specific implementation instructions for the software that you are installing to determine if the IBM-supplied device drivers are suitable for your installation. In the following sections, we show how to give access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as cartridge mount and dismount). For more information and specific installation instructions for every platform, refer to IBM Ultrium Device Drivers: Installation and User s Guide, GA , for LTO tape drives and libraries, and IBM TotalStorage Tape Device Drivers Installation and User s Guide, GC , for the IBM 3592 drive. These can be downloaded from: ftp://ftp.software.ibm.com/storage/devdrvr/doc/ 184 Implementing IBM Tape in Linux and Windows

213 In addition, there are several files in the IBM device driver download directory that provide additional information regarding the use of IBM Ultrium tape drives and libraries with Linux. See these at: ftp://ftp.software.ibm.com/storage/devdrvr/linux/ We recommend reading at least IBMtape_Ultrium.ReadMe s for LTO or IBMtape_Magstar.ReadMe for 3592, IBMtape.fixlist, and LinuxNative.pdf. The Readme files are located in the relevant OS folders. The IBMtapeutil.ReadMe and IBMtapeutil.fixlist files contain additional information for the users of IBMtapeutil for particular versions and levels of Linux. The LinuxNative.pdf file contains hints and tips about using the native device drivers and standard Linux commands, such as mt or tar. The device drivers allow the operating system and the application software to interface with tape devices and medium changers to automate the use of the tape media. The tape devices and medium changer are managed using a special device file name. The special device file name is the name used to address the tape or media changer device (see Table 4-1 for more information). Table 4-1 Special device file names used with Linux Native Linux device drivers Native Linux device drivers with scsidev IBM Ultrium device drivers Medium changer /dev/sg[0-32] /dev/scsi/sgh0-0c0i1l0 /dev/ibmchanger[0-32] Tape device /dev/st[0-32] /dev/nst[0-32] /dev/sg[0-32] /dev/scsi/sth0-0c0i1l0 /dev/scsi/nsth0-0c0i1l0 /dev/scsi/sgh0-0c0i1l0 /dev/ibmtape[0-32] /dev/ibmtape[0-32]n In our examples using native Linux device driver, we used SUSE Linux 7.2 and Red Hat Linux 7.1, but the tools and methods are independent of the specific Linux distribution. With both distributions, we used a kernel. For the examples using the IBM tape device driver, we used Red Hat Enterprise Linux AS 3 with kernel level of Using multi-path tape library with Red Hat Linux If your system is running Red Hat Linux, like our sample system, you need to do the following to enable multiple LUNs recognition: Edit the /etc/modules.conf file (use /etc/modprobe.conf for kernel 2.6) (Example 4-1). If the options scsi_mod max_scsi_luns entry already exists, change the value of max_scsi_luns to 128; otherwise add the line options scsi_mod max_scsi_luns=128. Example 4-1 /etc/modules.conf in our sample environment [root@saab root]#cat /etc/modules.conf alias eth0 e100 alias scsi_hostadapter qla2200 alias scsi_hostadapter1 aic7xxx alias usb-controller usb-ohci options scsi_mod max_scsi_luns=128 Chapter 4. Basic IBM tape setup for Linux 185

214 Remake the corresponding initrd with the following command: mkinitrd -f -v <file_name> <kernel_version> For example, if your are running e.25enterprise kernel: mkinitrd -f -v /boot/initrd e.25enterprise.img e.25enterprise Or if you are running e.25smp kernel: mkinitrd -f -v /boot/initrd e.25smp.img e.25smp Example 4-2 shows the mkinitrd command at our sample environment. Example 4-2 mkinitrd command in our sample environment root]# mkinitrd -f -v /boot/initrd elsmp.img ELsmp Looking for deps of module scsi_mod Looking for deps of module sd_mod scsi_mod Looking for deps of module scsi_mod Looking for deps of module unknown Looking for deps of module qla2200 scsi_mod Looking for deps of module scsi_mod Looking for deps of module aic7xxx scsi_mod Looking for deps of module scsi_mod Looking for deps of module ide-disk Looking for deps of module ext3 jbd Looking for deps of module jbd Using modules:./kernel/drivers/scsi/scsi_mod.o./kernel/drivers/scsi/sd_mod.o./kernel/drivers/addon/qla2200/qla2200.o./ kernel/drivers/scsi/aic7xxx/aic7xxx.o./kernel/fs/jbd/jbd.o./kernel/fs/ext3/ext3.o Using loopback device /dev/loop0 /sbin/nash -> /tmp/initrd.lsmgaw/bin/nash /sbin/insmod.static -> /tmp/initrd.lsmgaw/bin/insmod `/lib/modules/ elsmp/./kernel/drivers/scsi/scsi_mod.o' -> `/tmp/initrd.lsmgaw/lib/scsi_mod.o' `/lib/modules/ elsmp/./kernel/drivers/scsi/sd_mod.o' -> `/tmp/initrd.lsmgaw/lib/sd_mod.o' `/lib/modules/ elsmp/./kernel/drivers/addon/qla2200/qla2200.o' -> `/tmp/initrd.lsmgaw/lib/qla2200.o' `/lib/modules/ elsmp/./kernel/drivers/scsi/aic7xxx/aic7xxx.o' -> `/tmp/initrd.lsmgaw/lib/aic7xxx.o' `/lib/modules/ elsmp/./kernel/fs/jbd/jbd.o' -> `/tmp/initrd.lsmgaw/lib/jbd.o' `/lib/modules/ elsmp/./kernel/fs/ext3/ext3.o' -> `/tmp/initrd.lsmgaw/lib/ext3.o' Loading module scsi_mod with options max_scsi_luns=128 Loading module sd_mod Loading module qla2200 Loading module aic7xxx Loading module jbd Loading module ext3 Reboot the system. 186 Implementing IBM Tape in Linux and Windows

215 4.3 Using native Linux device driver to configure IBM tape Basic support for SCSI devices has been available as part of the Linux kernel for several years. Typically, the driver for the SCSI controller of a Linux system is already compiled into the Linux kernel, and therefore available for use. This allows the Linux kernel to continue the boot process from a device connected to the SCSI controller after the kernel has been loaded and started from the Linux boot loader. In this section, we describe the built-in device drivers of the Linux kernel and the naming conventions for the Linux device file names. We use a direct attached IBM 3583 with two drives direct attached to an 1Adaptec SCSI controller, as shown in Figure 4-1. To use the IBM tape device driver, see 4.4, Using IBM Tape Device Driver on page 203. SCSI Intel Linux server IBM LTO 3583 Figure 4-1 Linux SCSI lab environment During startup, the Linux kernel scans the SCSI bus for all available adapters and recognizes the disk and tape devices that are connected and accessible. As a result of this process, every disk and tape device that has been recognized by the kernel will be accessible through a device file in the /dev directory. The concept of device files is common to all UNIX variants, but every UNIX variant has its own naming conventions. Under Linux, every SCSI bus is scanned from low to high SCSI IDs, and the devices that are found are assigned to the device files in /dev in an ascending order. Disk devices are assigned to the device files /dev/sda, /dev/sdb, and so on. Tape devices are assigned to the device files /dev/st0, /dev/st1, and so on. Additional function in a physical device is often achieved by using different device names. For tape devices, the device files /dev/st? will cause a rewind whenever the device file is closed. The device files following the naming convention /dev/nst? represent non-rewinding devices. These devices will keep the tape in the position where it stopped after the last operation. Additional information can be found under the man pages for st and in the file readme.st in the kernel source code. In addition to the device files mentioned before, every SCSI device detected by the kernel will be represented by a generic device file. This includes not only device types that are recognized by the kernel, such as disk and tape devices, but also every device that answers to an inquiry command on the SCSI bus. Generic devices are represented by the device files /dev/sg0, /dev/sg1, and so on. For all device types that are recognized by the kernel, the sg device file exists in addition to the regular device file. For all device types that are not otherwise recognized by the kernel, this entry is the only device file representing the physical device. Additional information about the Linux generic device interface and the source code for a number of useful tools can be found at: Chapter 4. Basic IBM tape setup for Linux 187

216 The native drivers for tape devices as provided by the Linux kernel support basic read and write operations on IBM Ultrium tape drives via the /dev/st? and /dev/nst? device files. The medium changer device can be accessed via its /dev/sg? representation. Later in this chapter, we discuss additional device naming concepts that are available with Linux. See Table 4-1 on page 185 for an overview of the possible device names on Linux. The middle column shows the device names that will be used if the scsidev utility is installed. We discuss this in 4.3.9, Alternative device file names in Linux on page 200. While the Linux device support for SCSI devices is generally included in the kernel sources, some installations do not include the generic device utilities. This means some commands such as sg_scan may not be available. To access them, download the sg3 rpm packages from the link above. The two packages that need to be downloaded and installed are: libsgutils-1_ i386.rpm sg3_utils i386.rpm After downloading them, install them with rpm. Example 4-3 gives sample output for installing libsgutils-1_ i386.rpm. Install it first, then sg3_utils. These tools provide a convenient way to identify our library and tape drives later in this chapter. Example 4-3 Installing the utilities related to Linux generic SCSI device support # rpm -ivh libsgutils-1_ i386.rpm Preparing... ########################################### [100%] 1:libsgutils-1_0 ########################################### [100%] Identifying and activating the SCSI controller In most cases, your Linux distribution will provide a kernel that automatically configures the most common SCSI adapters without requiring further modification. This section describes how to identify and set up a SCSI adapter if it is not already supported by the kernel. In 4.5, Intel Linux Fibre Channel HBA installation on page 216, we will use the same procedure to make a Fibre Channel HBA available to the system. In the first step, we check if the adapter is visible on the SCSI bus of the system. For this purpose, we use a tool called lspci. If lspci is not part of your Linux distribution, it can be downloaded from: As shown in Example 4-4, the command lspci creates a listing of all PCI devices visible to our Linux system. Example 4-4 Output of lspci showing PCI devices including our SCSI adapter [root@diomede /root]# lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX BX/ZX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX BX/ZX AGP bridge (rev 03) 00:02.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:02.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:02.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:02.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:03.0 Ethernet controller: Intel Corporation [Ethernet Pro 100] (rev 05) 00:10.0 SCSI storage controller: Adaptec 7892A (rev 02) 01:01.0 VGA compatible controller: S3 Inc. Trio 64 3D (rev 01) The result of lspci shows that an Adaptec 7892A SCSI controller is available in the system (second line from the bottom). Linux reports the type of the controller and not the product name, which is, in our case, an Adaptec LVD adapter. If the adapter is not recognized 188 Implementing IBM Tape in Linux and Windows

217 during system startup (and is therefore not reported in the lspci output), we have to either activate the appropriate module or install a kernel that includes support for this adapter. If we assume that our Linux distribution contains no precompiled modules or kernel that includes the required SCSI support, we have to compile and install a new kernel with the appropriate support. Note: We will not describe the procedure of configuring, compiling, and installing a Linux kernel in detail. This topic is covered by the manuals of the Linux distribution and the Linux Kernel HOWTO. The Linux Kernel HOWTO can be found at: The initial configuration of the kernel sources may not be identical to the kernel that is actually running. Therefore, it is important to check that all the drivers required by the current system environment are really activated. From the kernel source directory (which is usually /usr/src/linux) we can configure a new kernel using the make xconfig command. If the environment is not running XWindows, use make menuconfig or make config instead. The kernel configuration window will open, as shown in Figure 4-2. Figure 4-2 Kernel configuration main window To activate support for our SCSI controller and devices, we selected the menu entry SCSI support. The SCSI configuration window will offer the options seen in Figure 4-3 on page 190. Chapter 4. Basic IBM tape setup for Linux 189

218 Figure 4-3 Configuration for SCSI disk, tape, generic device support The first entry enables SCSI support in general. All the types of devices (that is, disk, tape, and CD-ROM) that we want to access, either at boot time, or before the kernel module support is available, should be compiled into the kernel. For these devices, we select y. It is important that all the drivers that are required to access the boot devices and boot file systems are compiled into the kernel. Most of the other kernel features can be configured as modules. We recommend activating the feature Probe all LUNs on each SCSI device. This is especially important with multi-path libraries where the changer device appears as LUN 1 on the same SCSI ID as the first tape drive. It is also important in SAN environments where device addressing via LUNs is standard. If Probe all LUNs on each SCSI device is not enabled at kernel compile time, it can be activated later via a kernel or module parameter. To probe for eight LUNs, use the parameter max_scsi_luns=8. The parameter max_scsi_luns must be present as a kernel parameter if the driver is compiled into the kernel. If the driver is loaded as a module, LUN probing can be activated by adding the following line to/etc/modules.conf: options scsi_mod max_scsi_luns=8 The menu entry SCSI low level drivers brings up the configuration window for the SCSI adapters that are supported by the Linux kernel, as shown in Figure 4-4 on page 191. Here we activate the support for our Adaptec SCSI controller. 190 Implementing IBM Tape in Linux and Windows

219 Figure 4-4 Kernel configuration for the Adaptec SCSI controller Having completed the SCSI setup, we can now compile and install a new kernel. We strongly recommend that you review all kernel settings before doing this, to ensure that the new kernel setup matches the actual system environment. When compiling a new kernel, it is a good idea to save the old kernel so that the machine can reboot even if the new kernel fails Kernel compilation and installation checklist We do not describe kernel configuration and installation in detail, but provide this short checklist that should serve as a reminder of the individual steps in the process. cd /usr/src/linux* Goes to the directory where the kernel version resides that we want to configure and install. make clean or make mrproper Throws away everything that remains from previous kernel builds that may interfere with the new kernel build. The command make mrproper can be used to clean up the kernel sources completely. It will also remove a previous kernel configuration. make xconfig & Configures the new kernel. Equivalent commands are make menuconfig and make config at an ASCII terminal. make dep Analyzes dependencies for the newly configured kernel. make bzimage Creates a compressed image of the new kernel. make modules Creates the modules that have been selected during kernel configuration. make modules_install Installs the modules generated by the previous step. cp arch/i386/boot/bzimage /boot/<ourkernelname> Copies the kernel image into the /boot directory and renames it to the appropriate name <ourkernelname>. The file /etc/lilo.conf should contain an entry that references <ourkernelname>. Chapter 4. Basic IBM tape setup for Linux 191

220 mkinitrd -f -v /boot/<ramdiskimg> If our boot process uses an initial ramdisk, we should create a new image /boot/<ramdiskimg> for this ramdisk. Any changes to the modules and to /etc/modules.conf should be done before this step. The exact command depends on the version of our new kernel. lilo Creates a new bootsector. If we want to have an emergency boot kernel available, it should be configured in /etc/lilo.conf in addition to the new kernel. We are now ready to boot with the new kernel unless we want to boot our Linux system from a Windows NT or Windows 2000 boot menu. In this case, the two following steps are also required: a. if=/dev/<ourbootdiskorpart> of=/<ourbootsect> bs=512 count=1 Writes the content of the bootsector on the bootdisk or partition /dev/<ourbootdiskorpart> to the file /<ourbootsect>. b. cp /<ourbootsect> /<ourwinbootdisk> Copies the file /<ourbootsect> containing the bootsector to the Windows boot disk /<ourwinbootdisk>. This assumes that the Windows boot menu has been edited to include a boot entry for Linux previously. Following this checklist, we prepare our Linux system for the reboot with a new kernel. As soon as the system is running with the new kernel, we are able to access the IBM LTO Ultrium tape and library devices, as shown in 4.3.3, Identifying and accessing the LTO device on page Identifying and accessing the LTO device When the driver for our SCSI controller is compiled into the kernel of our Linux system and the library is correctly attached to the SCSI controller, we will see messages similar to Example 4-5 while the system is booting or if we issue the dmesg command after boot. Note that at this stage we have not installed the IBM Ultrium device driver; we are simply using native Linux utilities and drivers. Example 4-5 Detecting LTO tape drives and library during system boot [root@diomede /root]# dmesg (...) SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 10 for device 00:10.0 (scsi0) <Adaptec AIC-7892 Ultra 160/m SCSI host adapter> found at PCI 0/16/0 (scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs (scsi0) Downloading sequencer code instructions downloaded scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0 <Adaptec AIC-7892 Ultra 160/m SCSI host adapter> Vendor: IBM Model: ULT3580-TD1 Rev: 16E0 Type: Sequential-Access ANSI SCSI revision: 03 Vendor: IBM Model: ULT3580-TD1 Rev: 16E0 Type: Sequential-Access ANSI SCSI revision: 03 Vendor: IBM Model: ULT3583-TL Rev: 2.50 Type: Medium Changer ANSI SCSI revision: 02 (...) st: bufsize 32768, wrt 30720, max init. buffers 4, s/g segs 16. Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0 Attached scsi tape st1 at scsi0, channel 0, id 1, lun Implementing IBM Tape in Linux and Windows

221 In our case, the SCSI driver reports two tape drives of type ULT3580-TD1 and one device for the tape library (ULT3583-TL). The Ultrium tape drives are recognized as tape devices and made available under /dev/st0 and /dev/st1. The media changer will be accessible as a generic SCSI device. To identify the correct /dev/sg? device file for the changer device, we can use the information from the /proc directory using the device_strs command (see Example 4-6). Example 4-6 Identifying the generic device that represents the Ultrium library [root@diomede /root]# cat /proc/scsi/sg/device_strs IBM ULT3580-TD1 16E0 IBM ULT3580-TD1 16E0 IBM ULT3583-TL 2.50 The IBM Ultrium tape library appears in line three and should therefore be accessible as /dev/sg2 (/dev/sg0 is the first device and would in this case represent the first tape drive). With the sg_scan command (from the sg utilities installed in Example 4-3 on page 188), we get a more detailed list of generic SCSI devices, which we see in Example 4-7. Example 4-7 Listing generic SCSI devices using sg_scan [root@diomede /root]# sg_scan -i /dev/sg0: scsi0 channel=0 id=0 lun=0 type=1 IBM ULT3580-TD1 16E0 [wide=1 sync=1 cmdq=0 sftre=0 pq=0x0] /dev/sg1: scsi0 channel=0 id=1 lun=0 type=1 IBM ULT3580-TD1 16E0 [wide=1 sync=1 cmdq=0 sftre=0 pq=0x0] /dev/sg2: scsi0 channel=0 id=6 lun=0 type=8 IBM ULT3583-TL 2.50 [wide=0 sync=0 cmdq=0 sftre=0 pq=0x0] Tools like scsi_info (Example 4-8) or scsiinfo (Example 4-9) may be used to retrieve and check device information. Example 4-8 Retrieving device information with scsi_info [root@diomede /root]# scsi_info /dev/sg2 SCSI_ID="0,6,0" MODEL="IBM ULT3583-TL" FW_REV="2.50" Example 4-9 Retrieving device information with scsiinfo [root@diomede /root]# scsiinfo -i /dev/sg2 Inquiry command Relative Address 0 Wide bus 32 0 Wide bus 16 0 Synchronous neg. 0 Linked Commands 0 Command Queueing 0 SftRe 0 Device Type 8 Peripheral Qualifier 0 Removable? 1 Device Type Modifier 0 ISO Version 0 Chapter 4. Basic IBM tape setup for Linux 193

222 ECMA Version 0 ANSI Version 2 AENC 0 TrmIOP 0 Response Data Format 2 Vendor: IBM Product: ULT3583-TL Revision level: The mtx utilities A set of low level driver utilities, known as mtx, is available to control features of SCSI backup related devices, such as autoloaders, tape changers, media jukeboxes, and tape drives. These utilities can also report data, including serial numbers, maximum block sizes, and messages from the tape drives. They are designed to be a low level driver for use in larger scripted backup solutions, rather than a high level interface to the SCSI devices that it controls. In our context, this utility set is very useful for checking the basic operation of the LTO Ultrium Tape Library. We download and install the latest mtx version from: The package comes as a compressed tar file and can be unpacked and installed, as shown in Example Example 4-10 Unpacking and installing mtx [root@bonnie /root]# tar xzf mtx tar.gz [root@bonnie /root]# cd mtx [root@bonnie mtx ]#./configure creating cache./config.cache checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking for gcc... gcc (...) updating cache./config.cache creating./config.status creating Makefile creating config.h config.h is unchanged [root@bonnie mtx ]# make gcc -g -O2 -Wall -DVERSION="\"1.2.13\"" -I/usr/src/linux/include -DLONG_PRINT_REQUEST_SENSE=1 -c -o mtx.o mtx.c (...) gcc -g -O2 -Wall -DVERSION="\"1.2.13\"" -I/usr/src/linux/include -DLONG_PRINT_REQUEST_SENSE=1 -c -o scsitape.o scsitape.c scsitape.c:99: warning: `PeripheralDeviceType' defined but not used gcc -o scsitape scsitape.o mtxl.o [root@bonnie mtx ]# make install for file in mtx tapeinfo loaderinfo scsitape; do \ strip $file; \ done /usr/bin/install -c -m 755 -d /usr/local/sbin 194 Implementing IBM Tape in Linux and Windows

223 /usr/bin/install -c -m 755 mtx tapeinfo loaderinfo scsitape /usr/local/sbin /usr/bin/install -c -m 755 -d /usr/local/man /usr/local/man/man1 /usr/bin/install -c -m 644 mtx.1 tapeinfo.1 scsitape.1 loaderinfo.1 /usr/local/man/man1 Now we have the mtx command available and can have a closer look at our LTO Ultrium Tape Library. We use the status subcommand of mtx to get detailed status information from our LTO Ultrium Tape Library (see Example 4-11). Immediately after system startup or whenever cartridges have been put into or taken out of the library, we recommend issuing an inventory subcommand via mtx to be sure that the information we get from the status subcommand is correct. Example 4-11 Using mtx to get a detailed inventory of the tape library bonnie:/usr/src/linux # mtx -f /dev/sg2 status Storage Changer /dev/sg2:2 Drives, 54 Slots ( 12 Import/Export ) Data Transfer Element 0:Empty Data Transfer Element 1:Empty Storage Element 1:Empty Storage Element 2:Empty Storage Element 3:Empty Storage Element 4:Empty Storage Element 5:Empty Storage Element 6:Empty Storage Element 7:Full :VolumeTag=ABA927L1 Storage Element 8:Empty Storage Element 9:Empty Storage Element 10:Empty Storage Element 11:Empty Storage Element 12:Empty Storage Element 13:Empty Storage Element 14:Full :VolumeTag=ABA926L1 Storage Element 15:Empty (...) Storage Element 39:Empty Storage Element 40:Full :VolumeTag=ABA928L1 Storage Element 41:Full :VolumeTag=ABA990L1 Storage Element 42:Full :VolumeTag=ABA922L1 Storage Element 43 IMPORT/EXPORT:Empty (...) Storage Element 54 IMPORT/EXPORT:Empty The result shows that our tape library has two tape drives and 54 storage elements for cartridges. Twelve of the storage elements (numbers 43 to 54) are part of the IMPORT/EXPORT unit. The tape drives are designated as Data Transfer Elements. In addition, the command output shows which storage elements contain cartridges, and the labels found on these cartridges. Apart from the subcommands inventory and status that request information from the library, mtx will allow us to move cartridges in the library. The subcommand load will load a tape into a tape drive. In Example 4-12, we insert the cassette from storage element 41 into the second drive. Example 4-12 Using mtx to insert a tape into the tape drive [root@diomede /root]# mtx -f /dev/sg2 load 41 1 Now we are ready to use the second tape drive /dev/st1 for read or write operations on the tape. Programs like tar, cpio, or mt can be used to work with the tape drive. Chapter 4. Basic IBM tape setup for Linux 195

224 We have to unload the tape drive, as shown in Figure 4-13, before we can move the tape back to the storage element. Example 4-13 Using mt to unload a tape from the tape drive [root@diomede /root]# mt -f /dev/st1 offline Finally, we can move the tape back to its storage element using the unload subcommand (Example 4-14). Example 4-14 Using mtx to remove a tape from the tape drive [root@diomede /root]# mtx -f /dev/sg2 unload 41 1 Unloading Data Transfer Element into Storage Element 41...done Another useful command from the mtx package is loaderinfo. Example 4-15 shows the information that loaderinfo retrieves from the IBM Example 4-15 Using loaderinfo to retrieve information from the library [root@diomede /root]# loaderinfo -f /dev/sg2 Product Type: Medium Changer Vendor ID: 'IBM ' Product ID: 'ULT3583-TL ' Revision: '2.50' Attached Changer: No Bar Code Reader: Yes EAAP: Yes Number of Medium Transport Elements: 1 Number of Storage Elements: 42 Number of Import/Export Element Elements: 12 Number of Data Transfer Elements: 2 Transport Geometry Descriptor Page: Yes Invertable: No Device Configuration Page: Yes Can Transfer: Yes The loaderinfo command provides some additional information about the features of the library, such as the availability of a barcode reader. For some operations, mt and mtx may return before the device has completed its operation. If this happens, it is important to wait until the device operation has finished before the next command starts. If a tape or library command fails, it is a good idea to retry the command after waiting for a few seconds Identification and correct implementation of mt Linux provides the standard mt command to control most aspects of tape operation except writing and reading data from the tape. For example, you can use mt to position the tape, set parameters, or request status information. Depending on the Linux distribution and installation, there are two different implementations of mt available. One of them is GNU mt, the other one is called mt-st. We strongly recommend using mt-st because it has been developed specifically for the operation of SCSI tape devices on Linux and offers a comprehensive set of commands that is not available with GNU mt. Sometimes both mt implementations are installed. In this case, the mt-st version may be available as the command mtst. If this is the case, we recommend deinstalling the GNU mt command and making a symbolic link to the mtst command. 196 Implementing IBM Tape in Linux and Windows

225 The latest version of mt-st can be downloaded from: ftp://metalab.unc.edu/pub/linux/system/backup/ Example 4-16 shows how both implementations of mt can be identified. The two systems, CADDI and DIOMEDE, each have a different version of the commands. You can see that they also use different syntax. Example 4-16 Identifying which mt implementation is installed [root@diomede /root]# mt -v mt-st v. 0.5b caddi:~ # mt -V GNU mt version 2.5 In Example 4-13 on page 196, we showed how a tape can be unloaded from the drive using the mt command. In 4.3.7, Working with user-defined block sizes on page 198, and 4.3.8, Controlling hardware compression on page 199, we provide some additional examples using mt Module and kernel parameters for the Linux tape driver Up to this point, we have used the native Linux tape drivers with the default setup provided by our Linux system. There are several ways to modify the behavior of the Linux tape device driver and the tape drives. Some of them can be changed via module or kernel parameters, and others can be controlled using subcommands of mt. The buffers of the Linux tape device driver can be specified by module or kernel parameters. If the Linux tape device driver is loaded as a module, the following parameters are available: buffer_kbs=xxx The buffer size in kilobytes is set to xxx. write_threshold_kbs=xxx The write threshold in kilobytes is set to xxx. max_buffers=xxx The maximum number of tape buffer is set to xxx. Note that if the buffer size is changed, but the write threshold is not set, the write threshold is set to the new buffer size of 2 KB. To optimize the buffer settings for your specific application, it may be necessary to do some benchmarking with different settings. If the Linux tape device driver is compiled into the kernel, the same parameters can be provided to the kernel, for example, via the LILO configuration file /etc/lilo.conf. The keywords are the same as when loading the driver as a module. If several parameters are set, the keyword-value pairs are separated with a comma (no spaces allowed). A colon can be used instead of the equal sign. The definition is prefixed by the string st=. Example 4-17 shows how kernel parameters for the Linux tape device driver are defined in /etc/lilo.conf. Example 4-17 /etc/lilo.conf with kernel parameters that define larger tape buffers boot=/dev/hda1 map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=linux image=/boot/vmlinuz label=linux Chapter 4. Basic IBM tape setup for Linux 197

226 read-only root=/dev/hda7 append="max_scsi_luns=128 st=buffer_kbs:256,write_threshold_kbs:64" After a reboot of the Linux system, we can see if our changes to the tape buffer settings have been successful. During startup and in the information displayed by dmesg, we should see that the new buffer settings are active, as shown in Example Compare the new value for wrt with the default shown in Example 4-5 on page 192. Example 4-18 Boot messages with modified SCSI tape buffer settings [root@diomede /etc]# dmesg (...) SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 10 for device 00:10.0 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev <Adaptec Ultra160 SCSI adapter> aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs Vendor: IBM Model: ULT3580-TD1 Rev: 16E0 Type: Sequential-Access ANSI SCSI revision: 03 (scsi0:a:0): MB/s transfers (40.000MHz, offset 23, 16bit) Vendor: IBM Model: ULT3580-TD1 Rev: 16E0 Type: Sequential-Access ANSI SCSI revision: 03 (scsi0:a:1): MB/s transfers (40.000MHz, offset 23, 16bit) Vendor: IBM Model: ULT3583-TL Rev: 2.50 Type: Medium Changer ANSI SCSI revision: 02 st: Version , bufsize , wrt 65536, max init. bufs 4, s/g segs 16 Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0 Attached scsi tape st1 at scsi0, channel 0, id 1, lun 0 Attached scsi generic sg2 at scsi0, channel 0, id 6, lun 0, type 8 (...) Note that the value for write_threshold_kbs has been set only for demonstration purposes and does not represent a typical value for real use. The buffer settings for the Linux tape device driver are the only tape-related parameters that can be set by module or kernel parameters. Some additional parameters of the device driver, and several parameters of the tape device, can be modified via the mt command Working with user-defined block sizes To optimize tape performance, it may be necessary to define a blocksize that is larger than the 1024 bytes used by the default settings. Before we change any parameters, we will display the initial settings. Example 4-19 shows a status request to our first tape drive. Example 4-19 Requesting the status from /dev/st0 [root@diomede /etc]# mt -f /dev/st0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 1024 bytes. Density code 0x40 (unknown to this mt). Soft error count since last status=0 General status bits on ( ): BOT ONLINE IM_REP_EN We can see that the block size is set at 1024 bytes. One of the status bits indicates that the tape drive is ONLINE, which means that there is a tape mounted in the drive. BOT indicates 198 Implementing IBM Tape in Linux and Windows

227 that the drive is at the beginning of the tape. With the mt command shown in Example 4-20, we change the blocksize to 32 KB. Example 4-20 Setting the tape block size with mt /root]# mt -f /dev/st0 setblk As seen in Example 4-21, the status request shows the tape block size has changed. This change only applies until the system is rebooted; the easiest way to make it permanent is to put the mt command into a startup file. Example 4-21 Using mt to check if the block size was changed successfully [root@diomede /root]# mt -f /dev/st0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size bytes. Density code 0x40 (unknown to this mt). Soft error count since last status=0 General status bits on ( ): BOT ONLINE IM_REP_EN Now we can use the tape drive with the new blocksize. In Example 4-22, we write to the tape with the tar command. Note that the blocksize for the tar command has to be specified according to our tape block size definition. The -b parameter of tar specifies the blocksize in 512 byte units. Example 4-22 Writing 32 kilobyte blocks with tar [root@diomede /root]# tar -b 64 -cf /dev/st0 /usr tar: Removing leading `/' from member names Controlling hardware compression In some situations, such as when storing already compressed material like audio or video files, it may be useful to switch off the built-in compression of the LTO tape drive. In Example 4-23, we show the output of the tapeinfo command. The tapeinfo command is the equivalent to the loaderinfo command and is included with the mtx software. Like the loaderinfo command, it works on the generic SCSI device and provides more information about the tape drive than the mt command. As the example shows, it also reports some information about the compression settings of the tape drive. Example 4-23 Using tapeinfo to get a detailed status report from the tape drive [root@diomede /root]# tapeinfo -f /dev/sg0 Product Type: Tape Drive Vendor ID: 'IBM ' Product ID: 'ULT3580-TD1 ' Revision: '16E0' Attached Changer: No SerialNumber: ' ' MinBlock:1 MaxBlock: SCSI ID: 0 SCSI LUN: 0 Ready: yes BufferedMode: yes Medium Type: Not Loaded Density Code: 0x40 BlockSize: Chapter 4. Basic IBM tape setup for Linux 199

228 DataCompEnabled: yes DataCompCapable: yes DataDeCompEnabled: yes CompType: 0x1 DeCompType: 0x1 BOP: yes Block Position: 0 We use another mt subcommand to switch off data compression on our tape drive, as shown in Example Example 4-24 Using mt to switch off data compression [root@diomede /root]# mt -f /dev/st0 datcompression 0 Compression off. Example 4-25 shows a second call to tapeinfo, which reports that we switched off compression successfully. Note that this change only applies until the system is rebooted; the easiest way to make it permanent is to put the mt command into a startup file. Example 4-25 Checking the effect of the previous mt command [root@diomede /root]# tapeinfo -f /dev/sg0 Product Type: Tape Drive Vendor ID: 'IBM ' Product ID: 'ULT3580-TD1 ' Revision: '16E0' Attached Changer: No SerialNumber: ' ' MinBlock:1 MaxBlock: SCSI ID: 0 SCSI LUN: 0 Ready: yes BufferedMode: yes Medium Type: Not Loaded Density Code: 0x40 BlockSize: DataCompEnabled: no DataCompCapable: yes DataDeCompEnabled: yes CompType: 0x1 DeCompType: 0x1 BOP: yes Block Position: 0 The examples in this section and in the previous sections represent only a small part of the available mt subcommands. The manual page for mt contains a complete overview of the available subcommands Alternative device file names in Linux The device naming concept described in 4.3, Using native Linux device driver to configure IBM tape on page 187, has the advantage of creating short and easy to remember device file names. A disadvantage of the concept can be seen in the fact that device file names are created dynamically during the boot process. For larger installations, this means that device names may change if a tape drive is removed temporarily from a library, such as for maintenance purposes. If this happens, an application that uses the tape library will have 200 Implementing IBM Tape in Linux and Windows

229 incorrect device definitions. We know of two methods for avoiding this using alternative device file names. The utility scsidev To avoid this effect, the scsidev utility creates the directory /dev/scsi and populates it with device names that are independent of SCSI bus reconfiguration. The scsidev utility is available from: After downloading the latest version, we installed the scsidev package, as shown in Example Example 4-26 Installing the scsidev package /root]# tar xzf scsidev-2.22.tar.gz /root]# cd scsidev scsidev]#./configure creating cache./config.cache checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for working const... yes checking how to run the C preprocessor... gcc -E checking for linux/scsi.h... no checking for scsi/scsi.h... yes checking for /usr/src/linux/drivers/scsi/scsi.h... yes checking for a BSD compatible install... /usr/bin/install -c updating cache./config.cache creating./config.status creating Makefile creating config.h [root@diomede scsidev]# [root@diomede scsidev]# make gcc -g -O2 -Wall -DVERSION=\"2.22\" -o scsidev scsidev.c [root@diomede scsidev]# make install install -o root -g root -m 755 -s scsidev /bin install -o root -g root -m 644 scsidev.8 /usr/share/man/man8 gzip -9f /usr/share/man/man8/scsidev.8 if [! -d /dev/scsi ]; then mkdir /dev/scsi; fi #install -d /usr/share/doc/packages/scsidev #install COPYING boot.diff README scsi.alias /usr/share/doc/packages/scsidev/ Example 4-27 shows how scsidev can be used to create an alternative set of device files. Example 4-27 Creating SCSI device files with scsidev [root@diomede scsidev]# scsidev -sdn Found /dev/scsi/sgh0-0c0i0l0 (Type 01) R on Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0 Found /dev/scsi/sgh0-0c0i1l0 (Type 01) R on Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0 Chapter 4. Basic IBM tape setup for Linux 201

230 Found /dev/scsi/sgh0-0c0i6l0 (Type 08) R on Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.4/5.2.0 Serial number of /dev/scsi/sgh0-0c0i6l0: "IBM " Serial number of /dev/scsi/sth0-0c0i1l0: " " Serial number of /dev/scsi/sgh0-0c0i1l0: " " Serial number of /dev/scsi/sth0-0c0i0l0: " " Serial number of /dev/scsi/sgh0-0c0i0l0: " " Example 4-28 shows the device files that scsidev generates. Example 4-28 SCSI device files generated by scsidev [root@diomede scsidev]# ls /dev/scsi/ nsth0-0c0i0l0 sgh0-0c0i0l0 sgh0-0c0i6l0 sth0-0c0i1l0 nsth0-0c0i1l0 sgh0-0c0i1l0 sth0-0c0i0l0 The set of device special files created by scsidev contains the same devices that are available in the standard /dev directory, but it uses a different naming convention. The naming is based on the address of the SCSI adapter and the SCSI address of every device. Therefore, the name of a device special file will not change even if a device with a lower SCSI address is temporary unavailable. Similar to the standard Linux SCSI handling, scsidev recognizes disk and tape devices. The device file names for disks start with sd, tapes are represented by device file names that start with st for the rewinding, and nst for the non-rewinding behavior of the tape drive. Generic SCSI device file names start with sg. The rest of the device name is created from device addressing information. The device name sgh0-0c0i6l0, for example, can be read as SCSI generic device on host 0 - hostid 0x000 (IOPORT) channel 0 scsi id 6 lun 0. Example 4-29 shows that our LTO tape library is also available under the new naming scheme. Example 4-29 Accessing the LTO library independent from SCSI reconfiguration [root@diomede scsidev]# scsi_info /dev/scsi/sgh0-0c0i6l0 SCSI_ID="0,6,0" MODEL="IBM ULT3583-TL" FW_REV="2.50" The scsidev command (as shown in Example 4-27 on page 201) should be executed at every system boot. If we access our LTO tape library and drives via the device files created by scsidev, it is possible to remove or add a tape drive from the library without needing to reconfigure the application software. In addition to the scsidev package, the script rescan-scsi-bus.sh should be copied into the /bin directory with the permissions shown in Example The script rescan-scsi-bus.sh is available at: Example 4-30 Permissions for rescan-scsi-bus.sh [root@diomede /root]# ll /bin/rescan-scsi-bus.sh -rwxr-xr-x 1 root root 2675 Oct 30 11:59 /bin/rescan-scsi-bus.sh Whenever the configuration of the SCSI bus changes, the script rescan-scsi-bus.sh must be executed to make the system aware of the change. Example 4-31 on page 203 shows which parameters are available for rescan-scsi-bus.sh. For SAN environments, -l is especially important. It is very common to use several LUNs in a SAN, and without this parameter, only LUN 0 will be recognized. 202 Implementing IBM Tape in Linux and Windows

231 Example 4-31 Command line parameters for rescan-scsi-bus.sh /root]# rescan-scsi-bus.sh --help Usage: rescan-scsi-bus.sh [-l] [-w] [-c] [host [host...]] -l activates scanning for LUNs [default: 0] -w enables scanning for device IDs [def.: 0.. 7] -r enables removing of devices [default: disabled] -c enables scanning of channels 0 1 [default: 0] If hosts are given, only these are scanned [default: all] The devfs special device file system Another alternative to the traditional Linux device naming scheme is offered by the devfs special device file system. We do not discuss this approach in our redbook. For further reading on this topic, we recommend the devfs Web site: Using IBM Tape Device Driver The IBM Tape Device Driver is certified specifically to a particular Linux distribution and kernel versions. If you want to use a kernel version that is not supported by the IBM tape device driver, you will need to use the native Linux device driver, as shown in the previous sections Installing the IBM tape device driver and utilities The IBM tape device driver for Linux can be downloaded from the following site or one of its mirror sites: ftp://ftp.software.ibm.com/storage/devdrvr/linux/ Find the sub-directory corresponding to your Linux distribution and version. The driver comes in an RPM package in the form IBMtape-x.x.x-y.y.y.i386.rpm.bin, where x.x.x is the version of the driver itself, and y.y.y. is the version of the Linux kernel that it supports. You also need to download, from the same directory, the IBMtapeutil program (which includes the IBMtapeconfig tool). IBMtapeutil provides a comprehensive collection of tape and library commands. The IBMtapeutil utilities exist in a separate tar package from the device driver. The package is called IBMtapeutil.x.x.x.i386.tar.bin. We are installing the IBM tape device driver in the following environment: IBM ^ xseries 335 with SUSE 9 QLogic QLA bit PCI Fibre Channel HBA IBM TotalStorage 3584 Tape Library with native FC drives Example 4-32 on page 204 shows the installation of the IBM tape device driver and the IBMtapeutil package. Details can also be found in the IBM Ultrium Device Drivers: Installation and User s Guide, GA To install the device driver, use rpm. To install IBMtapeutil, untar the package into a directory and from that directory run make install. Chapter 4. Basic IBM tape setup for Linux 203

232 Example 4-32 Installing IBM tape driver and library utilities on Linux # rpm -i IBMtape i386.rpm.bin Installing IBMtape IBMtape loaded # cd caddi:~ # tar xvf IBMtapeutil i386.tar.bin IBMtapeutil.1.3.1/ IBMtapeutil.1.3.1/IBMtapeconfig IBMtapeutil.1.3.1/IBMtapeutil.c IBMtapeutil.1.3.1/IBMtapeutil.h IBMtapeutil.1.3.1/makefile IBMtapeutil.1.3.1/IBMtapeutil.ReadMe IBMtapeutil.1.3.1/IBMtapeutil caddi:~ # cd IBMtapeutil caddi:~/ibmtapeutil # make make: `IBMtapeutil' is up to date. caddi:~/ibmtapeutil # make install cp -f IBMtapeutil /usr/bin/. cp -f IBMtapeconfig /usr/bin/. If you are running the IBM tape device driver, V1.4.1 or higher, and the IBMtaped daemon is running, IBMtaped will automatically create the special files under the /dev directory for you. In our case, the IBMtaped started automatically. Otherwise, you need to run IBMtapeconfig to manage the creation of special files for the attached devices. The following two commands, shown in Example 4-33, allow you to view the devices (tape drives and changer) created by the IBMtape device driver: cat /proc/scsi/ibmtape cat /proc/scsi/ibmchanger Example 4-33 Viewing devices created via IBMTapeconfig caddi:~ # cat /proc/scsi/ibmtape IBMtape version: IBMtape major number: 253 Attached Tape Devices: Number Model SN HBA FO Path 0 ULTRIUM-TD qla2xxx NA 1 ULTRIUM-TD qla2xxx NA 2 ULTRIUM-TD qla2xxx NA caddi:~ # cat /proc/scsi/ibmchanger IBMtape version: IBMtape major number: 253 Attached Tape Devices: Number Model SN HBA FO Path L qla2xxx NA To verify that the installation was successful, use the command rpm -qs IBMtape, as shown in Example 4-34 on page 205. For a successful install, the status should show normal. 204 Implementing IBM Tape in Linux and Windows

233 Example 4-34 Checking the status of the IBM Ultrium driver caddi:~ # rpm -qs IBMtape normal /etc/ibmtaped.conf normal /lib/modules/ bigsmp/kernel/drivers/scsi/ibmtape.ko normal /lib/modules/ default/kernel/drivers/scsi/ibmtape.ko normal /lib/modules/ smp/kernel/drivers/scsi/ibmtape.ko normal /usr/bin/ibmtaped normal /usr/bin/startibmtape normal /usr/include/sys/ibm_tape.h normal /usr/share/doc/packages/ibmtape normal /usr/share/doc/packages/ibmtape/ibmtape_359x.readme normal /usr/share/doc/packages/ibmtape/ibmtape_ultrium.readme normal /usr/share/doc/packages/ibmtape/ibmtaped.readme Now we are ready to use the Ultrium tape and library devices with the IBM driver. Even if you plan to use the Ultrium tape and library devices with the native Linux drivers, we recommend installing the IBM drivers to allow microcode updates of the Ultrium tape and library devices. If you are using a Linux kernel version that is not supported by the IBM drivers, we recommend installing a supported kernel as an alternative boot kernel for this purpose. Example 4-35 shows the initial invocation screen for IBMtapeutil. Example 4-35 Start screen of IBMtapeutil IBMtapeutil for Linux, Version 1.3.1, Sept. 14, 2004 ========================================= 1. Tape 2. Changer 3. Quit ========================================= Enter your choice: Example 4-36 shows the general SCSI commands as well as the tape-specific commands that are available via IBMtapeutil. Example 4-36 Tape command selection screen of IBMtapeutil for Linux General Commands: Open a Device 9. Mode Sense Pag 2. Close a Device 10. Switch Tape/Changer Devic 3. Inquiry 11. Create Special Files 4. Test Unit Ready 12. Query Driver Version 5. Reserve Device 13. Query Device Path 6. Release Device 14. Display All Paths 7. Request Sense 15. Enable A Path 8. Log Sense Page 16. Disable A Path Q. Quit IBMtapeutil Tape Commands: Rewind 33. Set Block Size 21. Forward Space Filemarks 34. Retension Tape 22. Backward Space Filemarks 35. Query/Set Tape Position 23. Forward Space Records 36. Query Tape Status 24. Backward Space Records 37. Load Tape 25. FSFM 38. Unload Tape 26. BSFM 39. Lock Tape Drive Door 27. Space to End of Data 40. Unlock Tape Drive Door 28. Read and Write Tests 41. Take Tape Offline 29. Write Filemarks 42. Enable/Disable Compression Chapter 4. Basic IBM tape setup for Linux 205

234 30. Read or Write Files 43. Flush Drive's Buffer 31. Erase 44. Self Test 32. Reset Drive 45. Display Message IBMtape Commands: Query Sense 52. Locate Tape Position 47. Query Inquiry 53. Read Tape Position 48. Query/Set Tape Parameters 54. Query Mtdevice Number 49. Query/Set Tape Position 55. Synchronize Buffers 50. Query/Set MT/ST Mode 56. List Tape Filemarks 51. Report Density Support Service Aid Commands: Dump Device 74. Read Persistent Reservation Keys 71. Force Dump 75. Read Persistent Reservations 72. Load Ucode 76. Register Persistent Reservation Key 73. Reset Drive 77. Remove Persistent Reservation 78. Clear All Persistent Registrations Back To Main Menu Enter Selection: Example 4-37 shows, as an example for using IBMtapeutil, how a SCSI inquiry command can be sent to the tape device. Example 4-37 Sending a SCSI inquiry command to an LTO tape drive with IBMtapeutil Enter Selection: 1 Enter device name (<enter> for /dev/ibmtape0): /dev/ibmtape1 Select mode (<enter> or 1=Read/Write, 2=Read Only, 3=Write Only, 4=Append): 1 Opening device... Hit <enter> to continue... (...) Enter Selection for /dev/ibmtape1: 3 Enter page code in hex or <enter> for standard inquiry: Issuing inquiry... Inquiry Data: Peripheral Qualifer x00 Peripheral Device Type x01 Removal Medium Bit Device Type Modifier x00 ISO version x00 ECMA version x00 ANSI version x03 Asynchronous Event Notification Bit---0 Terminate I/O Process Message Bit Response Data Format x02 Additional Length x35 Medium Changer Mode x00 Relative Addressing Bit Bit Wide Data Transfers Bit Bit Wide Data Transfers Bit Synchronous Data Transfers Bit Linked Commands Bit Command Queueing Bit Implementing IBM Tape in Linux and Windows

235 Soft Reset Bit Vendor ID IBM Product ID ULTRIUM-TD3 Product Revision Level KC vendor1, Length A B C D E F ABCDEF [... 0] [... ] vendor2, Length A B C D E F ABCDEF [...] [... ] Hit <enter> to continue... (...) Enter Selection for /dev/ibmtape1: 2 Device closed... Example 4-38 shows that a similar set of commands are available to interact with the tape library (Option 2 from the start screen in Example 4-35 on page 205). Example 4-38 Library command selection screen of IBMtapeutil for Linux General Commands: Open a Device 9. Mode Sense Pag 2. Close a Device 10. Switch Tape/Changer Devic 3. Inquiry 11. Create Special Files 4. Test Unit Ready 12. Query Driver Version 5. Reserve Device 13. Query Device Path 6. Release Device 14. Display All Paths 7. Request Sense 15. Enable A Path 8. Log Sense Page 16. Disable A Path Q. Quit IBMtapeutil Medium Changer Commands: Element Information 65. Load/Unload Medium 61. Position To Element 66. Initialize Element Status 62. Element Inventory 67. Prevent/Allow Medium Removal 63. Exchange Medium 68. Initialize Element Status Range 64. Move Medium 69. Read Device Identifiers Service Aid Commands: Dump Device 72. Load Ucode 71. Force Dump 73. Reset Drive Back To Main Menu Enter Selection: Example 4-39 on page 208 shows how the Ultrium Tape Library Medium Changer answers to a SCSI inquiry command. Chapter 4. Basic IBM tape setup for Linux 207

236 Example 4-39 Sending a SCSI inquiry command to an LTO library with IBMtapeutil Enter Selection: 1 Enter device name (<enter> for /dev/ibmchanger0): /dev/ibmchanger0 Opening device... Hit <enter> to continue... (...) Enter Selection for /dev/ibmchanger0: 3 Enter page code in hex or <enter> for standard inquiry: Issuing inquiry... Inquiry Data: Peripheral Qualifer x00 Peripheral Device Type x08 Removal Medium Bit Device Type Modifier x00 ISO version x00 ECMA version x00 ANSI version x03 Asynchronous Event Notification Bit---0 Terminate I/O Process Message Bit Response Data Format x02 Additional Length x35 Medium Changer Mode x00 Relative Addressing Bit Bit Wide Data Transfers Bit Bit Wide Data Transfers Bit Synchronous Data Transfers Bit Linked Commands Bit Command Queueing Bit Soft Reset Bit Vendor ID IBM Product ID L32 Product Revision Level u vendor1, Length A B C D E F ABCDEF [ ] [... ] vendor2, Length A B C D E F ABCDEF [...] [... ] Hit <enter> to continue... (...) Enter Selection for /dev/ibmchanger0: 2 Device closed Implementing IBM Tape in Linux and Windows

237 4.4.2 Creating a library device table Operating system device names may not necessarily reflect the same order as the devices physically installed in the library. Therefore, check your drive configuration carefully. We recommend creating a table like Table 4-2. Table 4-2 Library device table Device name Serial number/wwn Tape drive in the library SCSI element address IBMtape Drive IBMtape Drive IBMtape Drive Here are some ways to create this table: Check the /proc/scsi/ibmtape file on page 209 Issue IBMtapeutil inqpage command on page 211 You should keep in mind that rebooting the server or executing the IBMtapeconfig command will refresh the list. You should also refer to 5.3, Persistent binding on page 237 to understand how the operating system assigns device special file names, and how to keep them persistent across reboots. Check the /proc/scsi/ibmtape file In this section, we discuss the /proc/scsi/ibmtape file. In Example 4-40, we have three LTO Ultrium 3 drives, /dev/ibmtape0 to /dev/ibmtape2, with the serial numbers as shown. Compare the serial number to the number written on the drives in the library. You may also determine the serial by correlating the SCSI element address on the medium changer using the command: IBMtapeutil -f /dev/ibmchangerx devids Example 4-41 on page 210 shows the output of this command. Example 4-40 Verify device by checking the serial number in /proc/scsi/ibmtape file caddi:~ # cat /proc/scsi/ibmtape IBMtape version: IBMtape major number: 253 Attached Tape Devices: Number Model SN HBA FO Path 0 ULTRIUM-TD qla2xxx NA 1 ULTRIUM-TD qla2xxx NA 2 ULTRIUM-TD qla2xxx NA Chapter 4. Basic IBM tape setup for Linux 209

238 Example 4-41 The tapeutil devids command output sample caddi:~ # IBMtapeutil -f /dev/ibmchanger0 devids Reading element device ids... Drive Address 290 Drive State... See ASC/ASCQ ASC/ASCQ (Drive Present) Media Present... No Robot Access Allowed... No Source Element Address Valid... No Media Inverted... No Same Bus as Medium Changer... Yes SCSI Bus Address Vaild... No Logical Unit Number Valid... No Device ID, Length A B C D E F ABCDEF D C D2D [IBM ULTRIUM-] [TD ] [55 ] Drive Address 291 Drive State... See ASC/ASCQ ASC/ASCQ (Drive Present) Media Present... No Robot Access Allowed... No Source Element Address Valid... No Media Inverted... No Same Bus as Medium Changer... Yes SCSI Bus Address Vaild... No Logical Unit Number Valid... No Device ID, Length A B C D E F ABCDEF D C D2D [IBM ULTRIUM-] [TD ] [77 ] Drive Address 292 Drive State... See ASC/ASCQ ASC/ASCQ (Drive Present) Media Present... No Robot Access Allowed... No Source Element Address Valid... No Media Inverted... No Same Bus as Medium Changer... Yes SCSI Bus Address Vaild... No Logical Unit Number Valid... No Device ID, Length A B C D E F ABCDEF D C D2D [IBM ULTRIUM-] [TD ] [76 ] 210 Implementing IBM Tape in Linux and Windows

239 Issue IBMtapeutil inqpage command Another method to verify a device is to issue an IBMtapeutil inquiry on log sense page 0x80. This command will return a serial number for the device represented by the specified device special file. Compare the number to the number written on the drives, or to the number returned by the IBMtapeutil devids command (see Example 4-41 on page 210). IBMtapeutil -f /dev/ibmtapex inqpage 80 Example 4-42 shows that /dev/ibmtape0 is a tape drive with the serial number of Example 4-42 Verify device by IBMtapeutil inqpage command caddi:~ # tapeutil -f /dev/ibmtape0 inqpage 80 Issuing inquiry for page 0x80... Inquiry Page 0x80, Length A B C D E F ABCDEF A [ ] Uninstalling the Ultrium device drivers and utilities If you need to de-install the IBM Ultrium device driver from the Linux system, this can be done as shown in Example Example 4-43 Deinstalling IBM tape device driver and utilities caddi:~ # rpm -e IBMtape Note: All tape devices that use the IBMtape driver must be closed and cannot be in use when IBMtape is uninstalled or the uninstall fails Setting up control path failover on Linux The Linux IBMtape device driver alternate pathing support will configure multiple physical control paths to the same logical library within the device driver and provide automatic failover to an alternate control path when a permanent error occurs on one path. This is transparent to the running application. For example, consider a simple multipath connection that consists of two Host Bus Adapters (HBAs), which are connected to a library with two drive control ports enabled. The first HBA is connected to the first control port drive, and the second HBA is connected to the second control port drive. This connection provides two physical control paths to the same library for redundancy. When the HBA device drivers are loaded into the running system, each HBA detects a control path to the same library, and two logical devices can be created (for example, /dev/ibmchanger0 and /dev/ibmchanger1) by the IBMtaped daemon or the IBMtapeconfig script. Each logical device represents a physical path to the same library. An application can open and use only one logical device at a time, either IBMchanger0 or IBMchanger1, because they represent the same physical device. Without the IBMtape alternate pathing support, if an application opens IBMchanger0 and a permanent path error occurs (because of an HBA, cable, or drive control port failure, for example), the application fails. It is possible to Chapter 4. Basic IBM tape setup for Linux 211

240 initiate a manual failover by restarting the application on the alternate logical device (IBMchanger1), but the failed transaction has to be restarted from the beginning. When the alternate pathing support is enabled, the device driver configures them internally as a single device with multiple paths. The application can still open and use only one logical device at a time (either IBMchanger0 or IBMchanger1). If an application opens IBMchanger0 and a permanent path error occurs, the device driver initiates failover error recovery automatically on the alternate path (IBMchanger1). If successful, the current operation continues on the alternate path without interrupting the application. Important: The library Control Path Failover Feature Code 1680 must be installed and enabled on the library (IBM 3582, 3583, and 3584) in order for the Linux device driver to detect alternate control paths. In addition, you have to enable the control path for additional drives on the library using either the library Operator panel or the TotalStorage Specialist. For instructions on enabling the control path via these interfaces, see 3.4.3, Configuring control path failover in the library on page 115. Enabling/disabling alternate control path support Alternate pathing support is not enabled automatically when the device driver is installed. The Linux IBMtape device driver provides a driver parameter alternate_pathing for you to enable the library control path failover. To enable the failover support in the IBMtape device driver software, you need to do the following after installing the IBMtape rpm package: 1. Stop the IBMtaped daemon: IBMtaped stop 2. Unload the IBMtape driver from the memory: rmmod IBMtape 3. Add the following line in your /etc/modules.conf file for the 2.4 kernel or /etc/modprobe.conf.local file for the 2.6 kernel file: options IBMtape alternate_pathing=1 4. Run depmod. 5. Re-load the IBMtape driver into memory: modprobe IBMtape 6. Re-start the IBMtaped daemon: IBMtaped You may ignore the Unresolved symbols in /lib/modules/<your kernel name>/drivers/scsi/ibmtape.o message after the depmod command. 7. You can check if the IBMtape driver has recognized multiple control paths for your library by reading the /proc/scsi/ibmchanger file. If your library lists Primary or Alternate under the FO Path, as in Example 4-44 on page 213, then you have successfully enabled the control path failover feature for your library. If NA is listed under the FO Path, then the control path failover is not enabled. When IBMtape is loaded into kernel memory, the first logical medium changer device that IBMtape sees in the system will be the primary path for that medium changer. The other logical medium changers that IBMtape attached for the same medium changer will be configured as alternate paths. The device driver supports up to 16 physical paths for a single device. 212 Implementing IBM Tape in Linux and Windows

241 Example 4-44 An example of /proc/scsi/ibmchanger file root]# cat /proc/scsi/ibmchanger IBMtape version: IBMtape major number: 253 Attached Changer Devices: Number Model SN HBA FO Path 0 ULT3583-TL IBM QLogic Fibre Channel 2200 Primary 1 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate 2 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate Alternatively, you can display the primary and alternate path configuration for any device by running the following command: IBMtapeutil -f /dev/ibmchangerx path IBMchangerx is the logical name of any device. After the alternate pathing support is enabled, it remains set until the IBMtape driver is reloaded with the alternate_pathing driver parameter set to OFF. The alternate pathing setting is retained even if the system is rebooted. If you want to turn off the control path failover feature in the IBMtape device driver, execute the following steps: 1. Run IBMtaped stop. 2. Run rmmod IBMtape. 3. Delete the following line in your /etc/modules.conf file: options IBMtape alternate_pathing=1 4. Run depmod. 5. Run modprobe IBMtape. 6. Run IBMtaped. Disabling and enabling primary and alternate control paths Once you load the IBMtape device driver with the alternate_pathing parameter set ON, by default, all the available paths for a physical device are enabled. If, for some maintenance reason, you need to disable a path and do not want to fail over to this path, you may run the following commands: IBMtapeutil -f /dev/ibmchangerx path This command is used to know what the number of this path is. IBMtapeutil -f /dev/ibmchangerx disablepath number number will be the number of the path you want to disable. IBMtapeutil -f /dev/ibmchangerx path This command is used to make sure the path is labeled as disabled. Correspondingly, in the /proc/scsi/ibmchanger file, the disabled path will be listed as Disabled under the FO Path column. To enable a path from a disabled state, use the following command: IBMtapeutil -f /dev/ibmchangerx enablepath number number will be the number of the path you want to enable. Chapter 4. Basic IBM tape setup for Linux 213

242 4.4.5 Setting up data path failover on Linux The Linux IBMtape device driver alternate pathing support will configure multiple physical paths to the same device within the device driver to provide Data Path Failover (DPF) and dynamic load balancing for devices using multiple Host Bus Adapters (HBA). Note: These functions are supported only on IBM Ultrium 2 and 3 native Fibre Channel drives and IBM 3592 tape drives. It is not supported on IBM Ultrium 1 drives or for devices that are attached through an IBM SAN Data Gateway. Consider a simple multipath connection that consists of two Host Bus Adapters (HBA) in a Linux host that is connected through a switch to the tape drive. This connection provides two physical paths to same tape drive for redundancy if one path from an HBA to the drive fails. When the HBA device driver is loaded into the running system, the HBA detects two logical devices of the tape drive. For example, /dev/ibmtape0 and /dev/ibmtape1 will be created by the IBMtaped daemon or the IBMtapeconfig script. Each logical device is a physical path to the same tape drive. A backup and restore application can open and use only one logical device at a time, either /dev/ibmtape0 or /dev/ibmtape1, because they represent the same physical device. Without the IBMtape alternate pathing support, if an application opens /dev/ibmtape0 and a permanent path error occurs (because of an HBA or cable failure, for example), the application fails. It is possible to initiate manual failover by restarting the application on the alternate logical device (/dev/ibmtape1), but the application has to be restarted from the beginning. A long backup or restore operation could have been in progress when the path error occurred. Sometimes manual failover can require operator intervention to reset the drive because a SCSI Reservation could still exist on the failing HBA path. When the alternate pathing support is enabled on both /dev/ibmtape0 and /dev/ibmtape1, the device driver configures them internally as a single device with multiple paths. The application can still open and use only one logical device at a time (either /devibmtape0 or /dev/ibmtape1). If an application opens /dev/ibmtape0 and a permanent path error occurs, the device driver initiates failover error recovery automatically on the alternate path (/dev/ibmtape1). If successful, the current operation continues on the alternate path without interrupting the application. The failover error recovery first restores the previous device state, SCSI reservation, and tape position, then retries the failing operation. The dynamic load balancing support optimizes resources for devices that have physical connections to multiple Host Bus Adapters (HBA) in the same machine. When an application opens a device that has multiple HBA paths configured, the device driver determines which path has the HBA with the lowest usage, and assigns that path to the application. When another application opens a different device with multiple HBA paths, the device driver again determines the path with the lowest HBA usage and assigns that path to the second application. The device driver will update the usage on the HBA assigned to the application when the device is closed. Dynamic load balancing will use all Host Bus Adapters whenever possible and balance the load between them to optimize the resources in the machine. Important: The library data path failover feature code 1681 must be installed on the library (IBM 3582, 3583, and 3584) prior to enabling alternate data path support in the Linux device driver for IBM Ultrium 2 and 3 drives. The feature code is not required for IBM 3592 Enterprise drives. 214 Implementing IBM Tape in Linux and Windows

243 Enabling/disabling alternate data path support Alternate pathing support for tape drives is not enabled automatically when the device driver is installed. You will need to provide the data path failover feature key (required for Ultrium drives only) and enable the Linux IBMtape device driver parameter alternate_pathing. To enable data path failover support in the IBMtape device driver software, you need to complete the following steps after installing the IBMtape rpm package: 1. Stop the IBMtaped daemon: IBMtaped stop 2. Unload the IBMtape driver from the memory: rmmod IBMtape 3. Add the following line in your /etc/modules.conf file for the 2.4 kernel or /etc/modprobe.conf.local file for the 2.6 kernel file: options IBMtape alternate_pathing=1 dpf_keys="abcdefghijklmnop" where abckdefghijklmnop is an example of a data path failover feature key. If you have multiple libraries and multiple data path failover feature keys, input your keys as follows: dpf_keys="key1;key2;..." Note that no feature key is required for 3592 drives. 4. Run depmod. 5. Re-load the IBMtape driver into memory: modprobe IBMtape 6. Re-start the IBMtaped daemon: IBMtaped You may ignore the Unresolved symbols in /lib/modules/<your kernel name>/drivers/scsi/ibmtape.o message after the depmod command. 7. You can check if the IBMtape driver has recognized multiple data paths for your library by reading the /proc/scsi/ibmtape file. If your library lists Primary or Alternate under the FO Path, as shown in Example 4-45, then you have successfully enabled the data path failover feature for your library. If NA is listed under the FO Path, then the data path failover feature is not enabled. Example 4-45 An example of /proc/scsi/ibmtape file IBMtape version: IBMtape major number: 253 Attached Tape Devices: Number Model SN HBA FO Path 0 ULT3583-TL IBM QLogic Fibre Channel 2200 Primary 1 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate 2 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate Alternatively, you can display the primary and alternate path configuration for any device by running the following command: IBMtapeutil -f /dev/ibmtapex path IBMtapex is the logical name of any device. Chapter 4. Basic IBM tape setup for Linux 215

244 After the alternate pathing support is enabled, it remains set until the IBMtape driver is reloaded with the alternate_pathing driver parameter set to OFF. The alternate pathing setting is retained even if the system is rebooted. If you want to turn off the data path failover feature in the IBMtape device driver, execute the following steps: 1. Run IBMtaped stop. 2. Run rmmod IBMtape. 3. Delete the following line in your /etc/modules.conf file: options IBMtape alternate_pathing=1 4. Run depmod. 5. Run modprobe IBMtape. 6. Run IBMtaped. Disabling and enabling primary and alternate data paths Once you load the IBMtape device driver with the alternate_pathing parameter to be ON, by default, all the available paths for a physical device are enabled. If, for some maintenance reason, you need to disable a path and do not want to fail over to this path, you may run the following commands: IBMtapeutil -f /dev/ibmtapex path This command is used to know what the number of this path is. IBMtapeutil -f /dev/ibmtapex disablepath number number will be the number of the path you want to disable. IBMtapeutil -f /dev/ibmtapex path This command is used to make sure the path is labeled as disabled. Correspondingly, in the /proc/scsi/ibmtape file, the disabled path will be listed as Disabled under the FO Path column. To enable a path from a disabled state, run the following command: IBMtapeutil -f /dev/ibmtapex enablepath number number will be the number of the path you want to enable. 4.5 Intel Linux Fibre Channel HBA installation The following sections shows how to install the QLogic 2300 HBA in a Linux environment. The Linux kernels of the major distributions will often already contain a driver for this HBA; nevertheless, we will describe how the latest drivers can be integrated into a Linux kernel that does not contain the Fibre Channel drivers. This will be necessary in any case if you need to update the kernel or driver in your Linux environment. Note: Newer HBAs use similar processes for installation and configuration. Refer to the manufacturer s documentation for specifics. 216 Implementing IBM Tape in Linux and Windows

245 4.5.1 QLogic 2300 The driver for the QLogic 2300 Fibre Channel adapter can be found at: Check carefully for the correct driver version related to the Linux and kernel version. The driver for the QLogic card comes as a source code tgz-archive. Download and unpack the.tgz file and follow the instructions in the Readme.qla2x00 for installation steps. As always, it is a good idea to review all kernel settings and to keep a backup kernel that allows the machine to be rebooted in case anything goes wrong with the new kernel. At this point, check 4.3.2, Kernel compilation and installation checklist on page 191 to ensure that no steps are overlooked in the kernel build process. If the new kernel boots successfully, the boot messages should look similar to the output in Example Example 4-46 Boot messages from the QLA2300 adapter caddi:~ # dmesg (...) SCSI subsystem initialized QLogic Fibre Channel HBA Driver (f918ba20) ACPI: PCI interrupt 0000:01:02.0[A] -> GSI 18 (level, low) -> IRQ 18 qla :01:02.0: Found an ISP2312, irq 18, iobase 0xf90f6000 qla :01:02.0: Configuring PCI space... qla :01:02.0: Configure NVRAM parameters... qla :01:02.0: Verifying loaded RISC code... qla :01:02.0: LIP reset occurred (f7f7). qla :01:02.0: Waiting for LIP to complete... qla :01:02.0: LOOP UP detected (2 Gbps). qla :01:02.0: Topology - (F_Port), Host Loop address 0xffff scsi0 : qla2xxx qla :01:02.0: QLogic Fibre Channel HBA Driver: QLogic QLA MHz PCI-X to 2Gb FC, Single Channel ISP2312: PCI-X ( :01:02.0 hdma-, host#=0, fw= IPX Vendor: IBM Model: ULTRIUM-TD3 Rev: 54KC Type: Sequential-Access ANSI SCSI revision: 03 qla :01:02.0: scsi(0:0:0:0): Enabled tagged queuing, queue depth 32. Vendor: IBM Model: 03584L32 Rev: 465u Type: Medium Changer ANSI SCSI revision: 03 qla :01:02.0: scsi(0:0:0:1): Enabled tagged queuing, queue depth 32. Vendor: IBM Model: ULTRIUM-TD3 Rev: 54KC Type: Sequential-Access ANSI SCSI revision: 03 qla :01:02.0: scsi(0:0:1:0): Enabled tagged queuing, queue depth 32. Vendor: IBM Model: ULTRIUM-TD3 Rev: 54KC Type: Sequential-Access ANSI SCSI revision: 03 qla :01:02.0: scsi(0:0:2:0): Enabled tagged queuing, queue depth 32. Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0 st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA Attached scsi tape st1 at scsi0, channel 0, id 1, lun 0 st1: try direct i/o: yes (alignment 512 B), max page reachable by HBA Attached scsi tape st2 at scsi0, channel 0, id 2, lun 0 st2: try direct i/o: yes (alignment 512 B), max page reachable by HBA Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 1 Attached scsi generic sg1 at scsi0, channel 0, id 0, lun 1, type 8 Attached scsi generic sg2 at scsi0, channel 0, id 1, lun 0, type 1 Attached scsi generic sg3 at scsi0, channel 0, id 2, lun 0, type 1 (...) Chapter 4. Basic IBM tape setup for Linux 217

246 All the devices found at the Fibre Channel are made available via a generic device entry (sgx). In Example 4-47, we can see how the sg_scan command displays the devices that are available. Example 4-47 Showing all devices accessible via the FC HBA caddi:~ # sg_scan -i /dev/sg0: scsi0 channel=0 id=0 lun=0 IBM ULTRIUM-TD3 54KC [rmb=1 cmdq=1 pqual=0 pdev=0x1] /dev/sg1: scsi0 channel=0 id=0 lun=1 IBM 03584L32 465u [rmb=1 cmdq=1 pqual=0 pdev=0x8] /dev/sg2: scsi0 channel=0 id=1 lun=0 IBM ULTRIUM-TD3 54KC [rmb=1 cmdq=1 pqual=0 pdev=0x1] /dev/sg3: scsi0 channel=0 id=2 lun=0 IBM ULTRIUM-TD3 54KC [rmb=1 cmdq=1 pqual=0 pdev=0x1] If more than one HBA is installed, there are three possibilities for handling the duplicate devices generated by multiple HBAs: Configure only one device representation in the backup application. The other representations can be used for a manual failover solution if the backup application provides an easy way to update the device definitions. Hide the remaining appearances via Switch Zoning on the FC switch. Assign a specific device to a specific host adapter via persistent binding. Refer to 5.3, Persistent binding on page 237 for more details. While the first two alternatives are always possible, the third possibility depends on the capabilities of the FC device driver. Persistent binding is a function of the adapter and adapter device driver. Please check with the adapter vendor for support. 4.6 Using IBM tape driver in Linux on zseries LTO drives and libraries can connect to Linux on zseries using the Fibre Channel Protocol (FCP). Only Fibre Channel connectivity to 35XX drives and libraries are supported when connecting to Linux on the zseries platform. Here are the requirements to enable FC connectivity to a native FC connected tape library only. This section assumes that the correct FICON adapter(s) have been installed and firmware has been loaded to enable the Fibre Channel Protocol on the FICON device. Figure 4-5 on page 219 shows a typical connectivity setup. For additional FCP connectivity information, refer to: Implementing IBM Tape in Linux and Windows

247 zseries Linux Server Native Fibre Channel SAN IBM 2109 FC Switch Native Fibre Channel LTO 3584 Figure 4-5 Typical zseries SAN The Fibre Channel topology supported for the zseries models is fabric only. Neither point-to-point connection nor arbitrated loops are supported by the current zseries Fibre Channel Protocol. Please see the Redpaper Getting Started with zseries Fibre Channel Protocol, REDP0205, for more details on the supported configurations for Fibre Channel device attachment on zseries models. This document can be downloaded from this Web site: The Linux Fibre Channel adapter device driver zfcp is available in the kernel that supports the zseries Fibre Channel Protocol. The zfcp device configuration methods in 2.6 and 2.4 kernels are different. For 2.6 kernels, see Chapter 5, SCSI-over-Fibre Channel device driver, in Linux for zseries and S/390: Device Drivers, Features, and Command, November 30, 2004, LNUX-1403, found at: For 2.4 kernels, there are three ways to load the zfcp device driver in order to see the attached tape devices. Create an /etc/zfcp.conf file and make a ramdisk to statically attach tape devices to your system. You may use this method only if you have a persistent mapping in a SAN environment. Every time you reboot the system, the zfcp will be automatically loaded and the tape devices can be seen from the system. Modify the /etc/modules.conf file to add the zfcp module parameters; then run the depmod -A and modprobe zfcp commands. Please do not use this choice together with option 1, or it will cause conflicts. The zfcp map in /etc/modules.conf always takes higher priority than the map in /etc/zfcp.conf. Run the modprobe zfcp command first, then dynamically add a tape device into the system after you physically attach a Fibre Channel tape device to the switch. These three options are described further in the following sections. Chapter 4. Basic IBM tape setup for Linux 219

248 4.6.1 Use /etc/zfcp.conf file First, you need to add the device map into this file. The following is an example of zfcp.conf: 0xf1c0 0x1:0x x0:0x ;\ 0xf1c1 0x1:0x x0:0x The zfcp device driver uses the map module parameter to recognize a physically attached tape device. map takes the following format: map="<devno><port scsi-id>:<wwpn><unit-scsi-lun>:<fcp-lun>; Where: devno: The device number of the HBA (16 bits, see /proc/subchannels). It is 0xf1c0 or 0xf1c1 in the above example. port scsi-id: The Linux internal SCSI ID assigned to the Fibre Channel port of the SCSI target device (32-bit, must not be 0, and must be a unique one-to-one mapping for each World Wide Port Name). It is 0x1 in the above example. wwpn: The World Wide Port Name that identifies the Fibre Channel port of the SCSI target device (64-bit). It is 0x in the above example. unit scsi-lun: The Linux internal SCSI Logical Unit Number (32-bit). It is 0x0 in the above example. fcp-lun: The Logical Unit Number associated with the SCSI target device (64-bit). In the above example, 0x is the Logical Unit Number 0, and 0x is the Logical Unit Number 1. We recommend, for tape attachment, that each LUN be associated with a unique devno. If you use the same devno numbers for several logical units, you should ensure that each <unit-scsi-lun> is unique. After /etc/zfcp.conf is created, run the following commands: >mk_initrd >zipl Reboot the system. After it is booted up, your tape device should be shown in the /proc/scsi/scsi file , Identifying and accessing the LTO device on page 192 describes a number of different ways of identifying an attached LTO device Modify the /etc/modules.conf file You may add tape device mapping into /etc/modules.conf if you do not want to use /etc/zfcp.conf. The following example demonstrates the zfcp configuration in /etc/modules.conf: options zfcp map="\ 0xf1c0 0x1:0x x0:0x ;\ 0xf1c1 0x1:0x x0:0x " The map arguments are the same as the ones listed in for the /etc/zfcp.conf file. After modifying /etc/modules.conf, save and close it. Then run the following commands: >depmod -A >modprobe zfcp This will install the zfcp device driver and all of its prerequisite kernel modules. 220 Implementing IBM Tape in Linux and Windows

249 Now you can check the /proc/scsi/scsi file to see if all of the attached tape devices are shown in this file. If not, then check the Fibre Channel connection, such as the fibre cables, or if the devices are powered on, and so on. Then run the following commands to install zfcp: >rmmod zfcp >modprobe zfcp Dynamically attaching a tape device If you physically attach a tape device on the switch and zfcp is already loaded, you do not need to reboot the Linux system to add this entry in the /proc/scsi/scsi file. The zfcp device driver provides an add_map proc system entry under the directory /proc/scsi/zfcp to allow you to dynamically add the device into the system. For example, to add two LUNs from the above example into the system, you may issue the following commands: >echo "0xf1c0 0x1:0x x0:0x ;\ 0xf1c1 0x1:0x x0:0x ">/proc/scsi/zfcp/add_map >echo "scsi add-single-device ">/proc/scsi/scsi >echo "scsi add-single-device ">/proc/scsi/scsi The scsi add-single-device takes four parameters, corresponding to the four parameters scsi, channel, id, and lun in the /proc/scsi/scsi file. The value of scsi is 0 for the first devno, 1 for the second devno (if it is different from the first devno), and so on. The value of channel can start from 0 for each different SCSI value. The value of id is the one you use for <unit scsi-lun> in the above mapping. The value of lun is the LUN of the target device, for example, the last number in the above mapping. Currently, the zfcp device driver does not support dynamically removing the attached devices. If you need to remove the tape devices from the system, run rmmod zfcp. Then you can delete the entry in /etc/modules.conf and reload zfcp, or reload zfcp first and dynamically add the devices you want. After you have done all the mapping, if you can see all of the attached tape devices in /proc/scsi/scsi, you have successfully attached those devices to your system. Refer to 4.4.1, Installing the IBM tape device driver and utilities on page 203 for details on installing the IBM Ultrium Device Drivers. Chapter 4. Basic IBM tape setup for Linux 221

250 222 Implementing IBM Tape in Linux and Windows

251 5 Chapter 5. SAN considerations In this chapter, we discuss considerations for SAN attached tapes and libraries. We emphasize issues generally relevant to SAN tape attachment, including: Design considerations for SAN attached tape libraries Switch fabric zoning Persistent binding We also provide additional information about SAN setup for the IBM TotalStorage 3583 Tape Library and IBM TotalStorage 3584 Tape Library where necessary. We assume the reader is already familiar with basic SAN concepts. For more information about general SAN concepts and design, please refer to these Redbooks: Designing an IBM Storage Area Network, SG IBM TotalStorage: Implementing an Open IBM SAN, SG IBM SAN Survival Guide, SG Introduction to Storage Area Networks, SG Designing and Optimizing an IBM Storage Area Network, SG Note: The IBM SAN Data Gateway (SDG) Router models 2108-R03 and 2108-G07 were withdrawn from marketing in September The SAN Data Gateway Integrated Module is no longer available as a feature in a new IBM The SAN Data Gateway features were withdrawn from marketing in October For more information about the SDG, please see Appendix A, IBM SAN Data Gateway on page 385. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 223

252 5.1 SAN design considerations for IBM tape libraries In this section, we cover the following IBM tape SAN design considerations: What bandwidth do we need for FC Tape? How do we handle multiple paths to tape drives? The IBM LTO Ultrium 2 and 3 tape drives with Fibre Channel interface and the IBM 3592 tape drive support either point-to-point or Fibre Channel arbitrated loop attachment. The IBM Ultrium 1 Tape drives with Fibre Channel interface only support the FC-AL protocol. If you connect an IBM LTO Ultrium 1 Tape drive to a SAN, then the FC-AL protocol must be supported at that physical connection What bandwidth do we need for FC tape? Many SANs are designed for disk I/O, which means they are optimized for high input/output per second (IOPS) and not necessarily for high bandwidth, which is needed for tape and backup I/O. During backup sessions, high volumes of data are generally transferred from disk to tape media. High speed transfer is also a necessity to minimize backup time. Current tape drives, like the IBM LTO3 with 80 MB/sec, the IBM LTO2 with 35 MB/sec, and the IBM 3592 with 40 MB/sec, can easily saturate a single FC link, if several drives operate concurrently. Using a SAN fabric configuration, you can potentially attach and access many tape drives through one or more HBAs. But how will this affect performance if several tape drives run concurrently? The theoretical maximum data transfer rate for one FC connection in a 2 Gbit SAN is 200 MB/sec. In reality, we typically see an effective data transfer rate of about 160 MB/sec. In a 1 Gbit SAN, we just see an effective data transfer rate of 80 MB/sec. Ultrium 3 drives have a sustained data transfer rate of 80 MB/sec uncompressed, and 160 MB/sec using 2:1 compression. In theory, this means you should be able to run two uncompressed tape drives or one compressed tape drive concurrently on an HBA without performance degradation. Ultrium 2 drives have a sustained data transfer rate of 35 MB/sec uncompressed, and 70 MB/sec using 2:1 compression. In theory, this means you should be able to run four uncompressed tape drives or two compressed tape drives concurrently on an HBA without performance degradation. However, the data transfer rates which will be achieved will depend heavily on the type of data. Typically, most system environments have a mix of data types achieving very different compression rates. If writing very large files with a good compression ratio, you may get a transfer rate of up to 160 MB/sec (Ultrium 3) or 70 MB/sec (Ultrium 2) or even more. In that case, you should only run one Ultrium 3 or two Ultrium 2 drives together on one HBA. On the other hand, if writing small files or uncompressible files, then you may see transfer rates of less than 80 MB/sec (Ultrium 3) or 35 MB/sec ((Ultrium 2). In this case, more than one Ultrium 3 drive or two tape Ultrium 2 drives can be run together on one HBA. Nevertheless, it is not recommended that you try to work concurrently with more than two Ultrium 3 drives or four Ultrium 2 drives using a single HBA. As well as the number of devices per HBA, the overall SAN design must be capable of supporting the volume of data transferred during the backup process (see Figure 5-1 on page 225). The SAN might be able to easily sustain the overall load and normal data traffic, but still have an insufficient bandwidth when backups take place. This is specially in complex fabrics with multiple switches, where the inter switch links (ISLs) can become saturated. 224 Implementing IBM Tape in Linux and Windows

253 As already described, a FC link can sustain about 160 MB/sec. An ISL may handle slightly more, but as already discussed, with four to five (depending on the data and compression) Ultrium 2 tape drives running simultaneously, you can overload one single 2 Gbit ISL. Overloaded ISLs or HBAs may cause problems, like job aborts, timeouts, tape drives not responding, and bad performance. Therefore, it is essential to provide enough bandwidth for tape operations. You can enlarge your bandwidth if you install additional HBAs and increase the number of ISLs. Table 5-1 provides a rule of thumb for how many tape drives per HBA and ISL could run concurrently. Figure 5-1 shows a typical SAN layout with ISL between the servers and tapes. Table 5-1 How many tape drives can run concurrently on HBA or ISL Drives per HBA / ISL per Drive 1Gbit 2Gbit LTO Gen MB/sec drives LTO Gen2 35 MB/sec 1-2 drives 3-4 drives LTO Gen3 80 MB/sec 1 drive 1-2 drives MB/sec 1-2 drives 3-4 drives?????? Figure 5-1 SAN Bandwidth for tape Most SAN fabric hardware provides the ability to measure the real data transfer rate achieved on the SAN. For example, if you have an IBM SAN Fibre Channel Switch, you can use the Fibre Channel Switch Specialist to measure data throughput. Enter the IP address of one of the IBM SAN Fibre Channel switches in the browser window, and select the switch to which your HBA is attached (Figure 5-2 on page 226) to bring up the Switch Management View. Chapter 5. SAN considerations 225

254 Figure 5-2 Switch Management window Click the Performance icon to display the performance window, as in Figure 5-3 on page 227. You can see traffic on ports 3 and 25 of around MB/sec generated by an LTO 2 drive. If any ports consistently show traffic around 80 MB/sec with 1 Gb FC, or 160 MB/s with 2 Gb FC, you should consider load balancing by adding additional HBAs and ISL, or enabling trunking. 226 Implementing IBM Tape in Linux and Windows

255 Figure 5-3 Port performance You can also use the command line interface on the IBM 2109 switches. Use the portperfshow command to show the data transfer rate on the switch Multiple paths to tape drives We have discussed the reasons for using more than one HBA on the server to give good performance for all drives. However, if you implement this configuration, you will see duplicate tape drive definitions on your server. Let us discuss this in the context of our lab configuration. We have one xseries with two FC HBAs. These HBAs are connected to a SAN Fabric consisting of IBM 2109 switches. We have an IBM 3584 with two drives installed (see Figure 5-4). Intel Server Fibre Channel Aapter 2109 FC Switches 3584 Figure 5-4 Our lab configuration Chapter 5. SAN considerations 227

256 The IBM Ultrium drivers have been installed. Boot the server to detect the new devices. To display the devices, select Start Settings Control Panel System Hardware Device Manager. In Figure 5-5, you can see that the medium changer and two tape drives have been detected twice, once on each HBA in the server, giving a total of four tape drives and two SCSI Medium Changers. This gives the impression there are more devices available than are actually physically present. Figure 5-5 Device Manager To solve this problem: You can enable zoning, which allows one HBA to see only certain tape drives. You can use persistent binding for the HBAs to see only certain WWN. You can use the alternate path function within the IBM Tape Device Driver. The different options are described in: 5.2, Zoning on page , Persistent binding on page , Control Path Failover on page , Setting up control path failover on Linux on page Tape and disk on the same HBA Tape and disk I/O are by their nature different. While tape drives use large blocks and data streaming to maximize performance, disk drives use smaller block sizes appropriate for random I/O; therefore, mixing disk and tape on a single SCSI bus is not recommended and rarely done. Tape drives use large blocks and data streaming that can tie up the SCSI bus for long periods of time, meaning that disk drives get less than their fair share of the SCSI bus. Conversely, tape drives might have difficulty getting access to the bus because disk drives can respond faster. The best practice is thus to keep disk and tape on separate SCSI buses. 228 Implementing IBM Tape in Linux and Windows

257 With Fibre Channel, there is, in principle, less contention. I/O can be multiplexed and small blocks can be interleaved in the middle of large blocks. There is no shared bus to keep a slow device from sending whenever it is ready. So, it is certainly possible with Fibre Channel to have both disk and tape sending or receiving with little interference. Indeed, in a switched fabric, data is not directly sent to the device, but rather to the Fibre Channel switch. However, even with FC, for bandwidth reasons, disk and tape I/O sharing an HBA is still not recommended (although the bandwidth issue is independent of having mixed device types). For example, during a backup operation, your server has to read the data from the disk and write it to a tape drive. With an LTO 3 tape drive, if you write at an average of 80 MB/sec, then you have also to read 80 MB/sec from the disk. With both data streams going through the same HBA, it means that the HBA must handle at least 160 MB/sec (Figure 5-6). Important: IBM does not recommend sharing disk and tape I/O on the same HBA. 160 MB/sec SAN 80 MB/sec 80 MB/sec LTO 3 80 MB/sec Figure 5-6 Tape and disk on the same HBA As long as there is no other disk I/O activity during the backup operation, it may work without problems. But, if during the backup, other applications are running that also access the disk, performance will be impacted. Because disk access uses smaller blocksize and is quicker and more frequent, the disk I/O will occupy the FC link and cause the tape to wait to get on the link, causing backhitches and thus affecting performance. Or even worse, the disk I/O will keep the command queue filled up so that no tape command can go through. For a backup server where a high I/O load exists and for LAN-free clients, where during the backup some other disk I/O occurs, you should use multiple HBAs and separate the disk and tape I/O (see Figure 5-7 on page 230). This is especially true for backup servers using a disk storage pool (for example, with Tivoli Storage Manager) where the backup data is staged to disk and then migrated to tape. If the backup and migration run simultaneously, it will cause a high I/O load. Chapter 5. SAN considerations 229

258 Keep in mind that your environment will evolve over time (usually the data traffic will increase). Although it might have been justified (generally from a cost perspective) in a simple installation with low traffic to share the HBA, you must reevaluate the situation on a regular basis. In most cases, you will reach a point where it becomes necessary to install additional HBAs. Note: Monitor your environment over time, and when traffic grows, consider the installation of additional HBAs. LAN-free Clients with low bandwith LAN-free Clients with high bandwith Backup Server Tape&Disk IO Disk IO Tape IO SAN SAN Figure 5-7 SAN example for backup If you cannot avoid combining disk and tape I/O (for example, no more PCI slots available on the host), you should at least implement your SAN in accordance with the following rules and configure your FC HBAs accordingly: Create different zones for disk and tape. Create a different zone for every server. Enable FCP-2 recovery (also called FC Tape Support) on the FC HBA. Set up persistent binding (as described in 5.3, Persistent binding on page 237). Disable SCSI Bus Reset to tape devices, if possible. Enable PLOGI instead of PDISC after LIP. Design your SAN for high bandwidth, as high bandwidth is needed for tape I/O. Do not overload the HBA. Provide enough HBAs, as described in 5.1.1, What bandwidth do we need for FC tape? on page 224. Pay attention to the PCI bus performance (see PCI bus performance on page 231). 230 Implementing IBM Tape in Linux and Windows

259 Provide enough bandwidth between the switches (ISLs), and consider enabling trunking for the ISL (see also 5.1.1, What bandwidth do we need for FC tape? on page 224). Most SANs are designed for disk I/O (high IOPS) rather than high bandwidth (for example, tape), which means there may not be enough ISLs for high bandwidth. As discussed in 5.1.1, What bandwidth do we need for FC tape? on page 224, you need at least one ISL for every 3 4 tape drives. If you have more than one ISL between two switches, you should also consider enabling trunking. This is because there is no load balancing on the basis of real I/O over several ISLs as long there is no trunking enabled. Many switches (for example, IBM 2109 and IBM 2005) have DLS (dynamic load balancing on the basis of the routing table) disabled, which means that load balancing is done during startup of the switch only; you should check periodically if all ISLs are working. After installing an additional ISL, you should run the dynamic load balancing at least once by setting dlsset. When done, remember to disable it again, as recommended by IBM. Another potential issue is the device driver level. IBM attempts to be on the same supported FC HBA device driver levels for tape and disk, but it is possible that because of a temporary issue, a given tape device will require a different device driver level than disk or vice-versa. For all of these reasons, IBM's general recommendation is that, wherever possible, a single HBA should not be shared for concurrent disk and tape operation. IBM will support mixing disk and tape on an HBA, and the IBM Support Center will accept problems reported on these configurations. However, if the problem determination process reveals that the cause is the mixing of tape and disk traffic, IBM may choose to tell the client that the only fix is to separate the traffic. Important: IBM does not recommend sharing of disk and tape I/O on the same HBA. PCI bus performance Different types of PCI buses have different performance specifications, as shown in Table 5-2. It does make sense to put one 2 Gbps HBA in a 32/33 PCI bus; however, it does not make sense to put more than one 2 Gbps HBA in a 64/33 PCI bus, as the throughput will be saturated. Note: Bandwidth throughputs in Example 5-2 are burst rates. Sustained throughput rates are typically around 50% of the burst rates. Table 5-2 PCI buses Width Speed Bandwidth 32-bit 33 MHz 132 MB/sec 64-bit 33 MHz 264 MB/sec 64-bit 64 MHz 512 MB/sec 64-bit 132 MHz 1056 MB/sec Chapter 5. SAN considerations 231

260 5.1.4 Different SAN fabrics for disk and tape To guarantee the availability of your SAN, either during necessary maintenance or to protect against human error, the best practice is to build redundancy through independent SAN fabrics, thus avoiding any single point of failure. Some large installations also separate disk and tape into different SANs. There are some advantages for separating SAN into Storage (Disk) and Backup (Tape): Backup and Storage teams can manage their SAN separately and independently. Backup and Storage teams can design their SAN for their specific needs and requirements. If there are different vendors for Storage and Backup, then service and maintenance will likely be easier and simpler. Each vendor is responsible for its own SAN. Therefore, separating disk and tape into different SANs is principally useful for: A large environment with a need for high availability An environment with different vendors for disk and tape 5.2 Zoning Zoning allows you to partition your SAN into logical groupings of devices so that each group is isolated from each other and can only access the devices in their own group. Using zoning, you can arrange fabric-connected devices into logical groups, or zones, over the physical configuration of the fabric. Zones can be configured dynamically. They can vary in size depending on the number of fabric connected devices, and devices can belong to more than one zone. Because zone members can access only other members of the same zone, a device not included in a zone is not available to members of that zone. Therefore, you can use zones to: Create closed user groups, for example, between test and development environments. Create a barrier between different environments, such as Windows and UNIX operating systems. Secure fabric areas. Figure 5-8 on page 233 shows two slightly overlapping zones, represented by the solid lines and the dotted lines. 232 Implementing IBM Tape in Linux and Windows

261 UNIX Windows NT/2000 Zone green Zone red Figure 5-8 Zoning IBM Tape Device Driver for AIX, Windows, Linux, HP-UX, and Sun Solaris supports multiple paths to the same tape. It provides automatic control path and automatic data path failover to preconfigured redundant paths in the event of a loss of an HBA, drive, or control path, without aborting the current jobs in progress. Other drivers do not support these features. Servers using other drivers can also use multiple HBAs and multiple connections to the SAN fabric, but there is no automatic failover to an individual tape device. What generally occurs is that the physical device is represented twice by the operating system. To solve this, we must hide the additional paths to the library and tapes using zoning, persistent binding, or software. Figure 5-9 on page 234 shows how we can set up a zone to eliminate dual pathing so that there is only one connection from the host to the tape devices. The physical FC connections enclosed in the circled zone could be zoned by WWN or a physical port connection on the FC switch creating a single path between host and tape drive. Chapter 5. SAN considerations 233

262 Host FC ISL FC FC Host FC 2109 FC Switch FC 2108 SDG SCSI Disk System Figure 5-9 Zone to restrict the tapes to one HBA only In the next example (shown in Figure 5-10), there are multiple tape drives and HBAs. You might use zones as shown so that the drives are split between the HBAs for performance or security reasons. Without zoning or other configurations, you would see the same dual pathing issue, as mentioned in 5.1.2, Multiple paths to tape drives on page 227. Server Fibre Channel Aapter Zone B 3584 with FC LTO Drives Zone A Figure 5-10 IBM 3584 with 8 FC LTO Drives, 1 server with 2 HBA, 2 zones You may also manage this scenario by using persistent binding, as described in 5.3, Persistent binding on page Some basic information about zoning Zones can be configured dynamically. Configuring new zones does not interrupt traffic on unaffected ports or devices. Also, new zones do not affect data traffic across interswitch links (ISLs) in cascaded switch configurations. However, zone changes interrupt traffic on affected ports and devices and should be done with care. 234 Implementing IBM Tape in Linux and Windows

263 Zoning configuration is generally a function of the switch devices. For an IBM 2109/2005, zoning can be configured and administered by telneting to the switch or using the Web browser based IBM TotalStorage Specialist. Devices can belong to more than one zone. Zoning can be administered from any switch in the fabric. Changes that are configured to one switch automatically replicate to all switches in the fabric; if a new switch is added to an existing fabric, all zone characteristics are automatically applied to the new switch. Because each switch stores zoning information, zoning ensures a high level of reliability and redundancy. For detailed information about setting up zoning, please refer to the SAN Redbooks cited in the introduction to this chapter, or to your switch documentation Types of zoning There are two types of zoning used: hardware zoning and software zoning. Hardware zoning Hardware zoning is based on the physical fabric port number. It can be implemented in the following configurations: One-to-one One-to-many Many-to-many Disadvantage The zoning configuration can become unusable if the device is connected to a different port, since hardware zoning relies on each device being connected to a specific port. Advantage Hardware zoning works independently of influence from other sources, such as HBA firmware. The switch hardware ensures that there is no data transfer between unauthorized zone members. However, devices can transfer data between ports within the same zone. Consequently, hard zoning provides the greatest security possible. Use it where security must be rigidly enforced. Hardware zoning also has a very low impact on the routing performance. If you use hardware zoning, you must carefully document and update your SAN fabric. Careful documentation is always a necessary task for managing a SAN. Software zoning Software zoning is implemented within the Simple Name Server (SNS) running inside the fabric switch. In a soft zone, at least one zone member is specified by WWN, which is a globally unique 8-byte number. When a device logs in, it queries the name server for devices within the fabric. If zoning is in effect, only the devices in the same zone(s) are returned. Other devices are hidden from the name server query reply. The members of a zone can be defined with: Node WWN (WWNN) Port WWN (WWPN) Chapter 5. SAN considerations 235

264 Advantage Software zoning is not affected by moving devices to different physical switch ports. If you use WWNs for the zone members, even if a device is connected to another physical port, it will still remain in the same zoning definition because the device s WWN remains the same. Disadvantage Each component of the SAN fabric must support soft zoning. The switch does not control data transfer, so there is no guarantee against data transfer from unauthorized zone members. You can intermix hardware and software zoning Suggestion on zoning for tapes Consider the following suggestions if you plan your zone configuration: Create different zones for disk and tape. Create a zone for every server or for every HBA. Adopt a meaningful naming convention for your zones, such as ServerA_Tape World Wide Names of FC Host Bus Adapter To set up software zoning to eliminate the dual pathing issue, you need to know the World Wide Names of your installed FC HBAs. Each HBA vendor offers its own software products to gather this information on the different systems. WWN of QLogic HBA Figure 5-11 shows the SANSurfer from QLogic, which is described in more detail in 3.7.2, QLogic QLAxxxx HBA driver configuration on page 143 and 5.3, Persistent binding on page 237. If you select the HBA in the left-hand panel, you can see the adapter information, including the WWN, on the right side. Figure 5-11 WWN with QLogic SANSurfer 236 Implementing IBM Tape in Linux and Windows

265 5.3 Persistent binding This function allows a subset of discovered targets to be bound to an HBA. Some operating systems do not guarantee that devices will always be allocated on the same SCSI target and LUN IDs after a reboot. This can cause problems for application software that expects tape devices always to have the same SCSI target ID/LUN. Persistent binding allows a tape device s WWN to be bound to a specific SCSI LUN. Another reason to use persistent binding is to ensure that the operating system drive names are configured in their physically installed order. Many backup applications (for example, EMC Legato NetWorker and VERITAS NetBackup DataCenter) will assume that the devices have been assigned their drive names in the same order as the element numbers. If the drives were configured in a different order, then the application will not correctly access the drives and, for example, will wait indefinitely for a media mount or until the request is manually killed. We show how to display element addresses for drives as well as the slots in Appendix C, Additional information on page 421. Once a configuration has been set, it will survive reboots and any hardware configuration changes. Binding also solves the dual pathing problem. Binding can be implemented by WWNN or WWPN. Tip for IBM Tivoli Storage Manager users: Recent releases of Tivoli Storage Manager eliminate the need for persistent binding with the SAN discovery feature. For more information, see 7.13, Tivoli Storage Manager V5.2 SAN device mapping on page 314. Note: The default Microsoft Windows naming scheme for tape devices means that dynamic and device names change as devices are added and removed. It assigns device names in the form \\.\Tapex, where x is a number. In this naming scheme, tape devices are given names starting with the tape device with the lowest SCSI address first and then numbered in ascending order starting from zero. The disadvantage of this is that regardless of persistent binding, the name assigned to a physical device can easily change if new devices are added with lower SCSI addresses. Windows will name the new devices starting from \\.\Tape0 and the names assigned to existing devices will change. Correspondingly, if devices fail or are removed from the fabric, existing \\.\Tapex device names can change Persistent binding with a QLogic HBA QLogic provides SANSurfer, which is a collection of device drivers and management software for controlling, configuring, and managing devices in a SAN environment that uses QLogic Fibre Channel HBAs. One function of this software is persistent binding. To set up persistent binding, the appropriate QLogic FC driver needs to be installed. See 3.7.1, QLogic QLAxxxx HBA driver installation on page 142 and 4.5.1, QLogic 2300 on page 217 for more details. Having installed the QLogic FC driver, we can now use SANSurfer to configure persistent LUN mapping. Run Start Program QLogic Management Suite SANSurfer. Click the Connect button on the SANSurfer main window toolbar, enter the host name or IP address of the host, and click Connect. Your host system is shown in the left-hand panel (see Figure 5-12 on page 238). Chapter 5. SAN considerations 237

266 Figure 5-12 SANSurfer In the HBA tree, select the host (or adapter, device, or LUN connected to the host) and click the Configure button on the toolbar. The Fibre Channel Port Configuration dialog box displays (Figure 5-13). You can recognize the WWNNs of the drives in the Node Name column. The first WWNN has the value C The World Wide Names of the drives are assigned by the tape library. This technique is referred to as library-centric world wide names. Potential drive slots are each assigned a WWN that does not change when a drive is swapped or replaced. Figure 5-13 Fibre Channel Port Configuration From the Fibre Channel Configuration dialog box, right-click in the cell in the Adapter n column, and select Set Visible to set this path as visible by the operating system during the boot process (Figure 5-14 on page 239). 238 Implementing IBM Tape in Linux and Windows

267 Figure 5-14 Set visible The target IDs will be assigned to the operating system in the same order as they were set to be visible (Figure 5-15). Figure 5-15 All devices visible Click Save to save the new configuration. The new configuration is saved as persistent configuration data so it will be used the next time the system is rebooted. The current boot configuration remains in memory and redisplays after the save operation completes. If the save was successful, you will see a message to reboot the system. Click OK. After rebooting, the new configuration will be available. Note: Some older versions of the QLogic drivers do not support persistent configuration data, and the application does not save persistent configuration entries for these drivers Persistent binding with an Emulex HBA Emulex provides a configuration tool with the multiport driver called elxcfg, which provides persistent mapping of device LUNs to HBAs. To control persistent mapping, the multiport driver needs to be installed. See 3.7.4, Emulex HBA driver configuration on page 149 for more details. Having installed the multiport driver, we can now use elxcfg to configure persistent LUN mapping. Select Start Program Emulex_Configuration_Tool. Select the adapter on which the tape drives are connected. Under Adapter Controls, select LUN mapping, but not Automatic LUN mapping, as shown in Figure 5-16 on page 240. Chapter 5. SAN considerations 239

268 Figure 5-16 Configuring LUN mapping Select the WWN to which you want to add a SCSI target ID and click Add Mapping. Then you can select the SCSI ID to which you map the selected WWN (Figure 5-17) and click OK. Figure 5-17 Select target ID 5.4 Connection type of IBM tapes Earlier IBM tape drives, including the IBM 3590, and IBM LTO1 FC drives, use the FC-AL protocol. Therefore, those drives must be connected to a port (switch or HBA if direct connected), which can also use FC-AL. Not all SAN switches or SAN directors support FC-AL. Some McData Directors and switches (6064, 6140, 3232) need a switch in front that supports FC-AL (McData 4500) to connect IBM 3590 and IBM LTO 1. The IBM LTO2 and 240 Implementing IBM Tape in Linux and Windows

269 LTO3 Fibre Channel tape drive and the IBM 3592 can arbitrate to communicate using either a loop or fabric protocol. Because all IBM tape drives use a public loop if connected via FC-AL to a SAN switch, the server sees no difference whether the tape drive is connected as FC-AL or FCP. Through the public loop capabilities, the tape drive sends its WWN to the name server of the switch during the FLOGI (fabric login). If a server wants to communicate to the tape drive, then the server queries the name server of the switch, gets the WWN of the drive, and proceeds with a PLOGI (N-Port login) (see Figure 5-18). The same PLOGI will happen if the tape drive is connected as a FCP device. Server Name Server query FCP Name Server WWN Drive Switch FC-AL N-Port Login Public loop WWN Drive Figure 5-18 N-Port login Per SNIA specification, IBM LTO2 and LTO3 drives attempt first to negotiate as a Loop device. If unsuccessful, then the drive attempts to log in as a fabric device. If you want the LTO2 or LTO3 drive to login always as a fabric device, then you need to change the settings on your switch so that FC-AL login is disallowed. Here is an example, for an IBM 2109 or 2005 switch, of how to change the settings so that the switch only allows FCP devices: 1. Telnet to the switch. 2. Display Port Config: portcfgshow nn 3. Disable the switchport: disableport nn 4. Set port characteristics: portcfggport nn 1 5. Enable the switchport: enableport nn Chapter 5. SAN considerations 241

270 For other switches, refer to your vendor documentation. With the appropriate microcode, you can change the port settings for LTO2 and LTO3 drives within the IBM 3584 operator console or Web interface. To change the settings for the IBM 3592 tape drive on the Operator panel, select Service Fibre Options Set Port x Set Topology. 242 Implementing IBM Tape in Linux and Windows

271 Part 2 Part 2 LTO libraries and backup software In Part 2, we describe how to implement LTO drives and libraries with popular backup software packages. In general, the following steps are required for each package: 1. Identify the correct device driver to use for both the drives and the medium changer. This can be the IBM Ultrium driver, a native operating system driver, or a driver provided by the application itself. 2. Install the application. 3. Define and configure the drives and library to the application. 4. Perform any application-specific steps to make the drives and library available as a backup destination. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 243

272 244 Implementing IBM Tape in Linux and Windows

273 6 Chapter 6. Configuring RSM This chapter covers Microsoft Removable Storage Manager (RSM) and its benefits and purpose. It then describes how to define and configure LTO devices to RSM so that they can be used with RSM-compliant applications. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 245

274 6.1 Removable Storage Manager RSM benefits Removable Storage Manager (RSM) is a standard interface in Microsoft Windows 2000 and 2003 to control most types of removable media, including CD-ROM, DVD-ROM, magneto-optical, Jaz, and Zip in both stand-alone and library configurations. RSM is installed by default on all versions of Windows 2000 and 2003 and can be used to manage anything except the A and B floppy drives. RSM uses functionality of the NTFS 5 file system, so there are no plans to port RSM to Windows 95/98 or Windows NT 4.0. RSM models all changers as subsets of an ideal changer. A given minidriver tells RSM what functionality the actual changer implements, so that RSM can treat it appropriately. The implementation of the features varies from changer to changer, but client applications can access them in the same way, using the ideal model. This library model supports changer-based libraries as well as stand-alone drives, by simply modeling them as changers with one drive, no slots, and no robot. Client programs, such as backup applications and Hierarchical Storage Management (HSM) services, can use RSM to gain access to their media. Essentially, RSM is an API that is called by these programs to make media accessible. Once media is accessible, these client programs use other Microsoft Win32 APIs to read and write the media. In addition, there is a Microsoft Management Console (MMC) snap-in client (called Removable Storage) that provides a human interface to most functionality such as inject/eject, cleaning, and so on. Here are some of the benefits of including media and device management in the operating system with RSM. Common drive model RSM implements a common driver model. A single driver will allow a tape library to be used with any RSM-compatible application. Conversely, an RSM-aware application will work with all changers on the market that have RSM drivers. Library sharing Multiple applications can now share a single library. Previously, a user who wanted to use backup and HSM solutions from two different vendors needed two changers. With RSM, both applications can share the same changer. Abstraction of offline media A backup application does not need to worry about whether a tape is in a changer or on a shelf. It simply requests the media, and RSM loads it or asks an operator to fetch it as appropriate. Media tracking RSM tracks recognized media in an internal database. Applications can register with RSM so that it can identify their media. They can also use the API to search the database and load particular media. 246 Implementing IBM Tape in Linux and Windows

275 6.1.2 Software support Care must be taken when using RSM with pre-existing or existing storage management applications. By default, RSM binds exclusively to all media changers on the system. This will break applications that expect to access these changers through other methods. All existing applications that are changer-aware must be reauthored to access changers through RSM. Disabling RSM control of the device might allow the application to function, but this has not been widely tested, and will not be supported by Microsoft. The Windows 2000/2003 NTBACKUP application uses RSM for tape media, but not for media with file systems (such as Zip or Jaz). The HSM tool called Remote Storage Server (RSS) that is included with Windows 2000 Server uses RSM to interface with tapes. Third-party data management application vendors may have RSM-aware versions of their applications. Check if your backup vendor has an RSM version of their application. 6.2 RSM implementation RSM keeps a database of all media, organized by both pool and media type. Each application creates its own pool, so (for example) backup media and HSM media can be identified separately, even if they are present in the same library. The database is system-wide, so a tape removed from a library and inserted into a stand-alone drive on the same system will still be properly identified Enabling RSM The environment for the RSM configuration is shown in Figure 6-1 and consists of: Intel Pentium II Server with Windows 2000 Advanced Server (build 2195). Adaptec LVD SCSI card. IBM 3583 SCSI attached. A single SCSI bus supported both the library controller and the two 3580 tape drives. VERITAS Backup Exec Version 8.6 Revision SCSI Intel Windows 2000 server IBM LTO 3583 Figure 6-1 SCSI lab environment Chapter 6. Configuring RSM 247

276 6.2.2 Attaching the IBM 3583 We performed the following steps to attach the IBM 3583 to the server: 1. Shut down Windows. 2. Install the SCSI card. 3. Boot the system. 4. Install the latest Ultrium device drivers. 5. Verify that the RSM service is enabled. 6. Shut down Windows. 7. Attach the 3583 library. 8. Boot the system. Install SCSI card Follow the instructions in 3.6, Windows 200x SCSI adapter installation on page 137 to install and configure the SCSI card and drivers. Verifying RSM RSM comes as a base component of Windows 2000/2003 and is installed as a service. The default behavior of the RSM service is to start automatically. To verify everything is working correctly, first check the RSM services (select Start Programs Administrative Tools Computer Management Services and Applications Services), as in Figure 6-2. Figure 6-2 Windows 2000 system services Right-click the Removable Storage entry and select Properties to display the service properties for RSM. Startup should be set to automatic. If not, change it, as shown in Figure 6-3 on page Implementing IBM Tape in Linux and Windows

277 Figure 6-3 RSM Services properties Now when we reboot the system, RSM will start automatically. Shut down the server, connect the tape device, and reboot. RSM will discover the library and associated tape drives and make them available for data backup and restore. Verifying tape connection There are two parts for verifying the tape (IBM 3583 in this case) function: Determine that Windows 2000 has correctly seen the device. Determine that RSM has identified the device and is correctly manipulating the changer and drive functions. The process of correctly installing the library and the Ultrium drivers is described in 3.6, Windows 200x SCSI adapter installation on page 137. To verify RSM connectivity to the changer and drives using RSM, access the RSM interface by selecting Start Programs Administrative Tools Computer Management. From the Storage heading, select Removable Storage, as shown in Figure 6-4 on page 250. Chapter 6. Configuring RSM 249

278 Figure 6-4 Removable Storage administration This will display objects and fields associated with RSM. In Figure 6-5, we have selected the Physical Locations and the library. Figure 6-5 RSM library We now select the drive objects associated with the library (Figure 6-6 on page 251). 250 Implementing IBM Tape in Linux and Windows

279 Figure 6-6 RSM drives If we have been successful in seeing these physical objects then the configuration should be acceptable to RSM. The final check is to physically install the media and then prepare the media for use. This process exercises the library and drives and verifies the configuration. Select Media Pools and expand each category. Media not containing valid data is listed under Free LTO Ultrium. These tapes need to be idle and available for RSM usage. The default media pools are: Free: Tapes that do not contain backup data. These tapes are available for usage once they have been prepared. Import: These are tapes that have been imported into the library through an I/O port. These tapes will be moved to the Free Media Pool once they have been prepared. Unrecognized: These tapes have formats that are not recognized by RSM. In Figure 6-7 on page 252, a volume from the Free Media Pool is being prepared. Select Prepare from the pull-down menu for this volume. Chapter 6. Configuring RSM 251

280 Figure 6-7 Preparing tapes The Prepare step needs to be performed for any media you want RSM to use. A volume that contains valid backup data (ABA925L) is shown in Figure 6-8. Figure 6-8 Allocated media 6.3 RSM with a SAN It is not possible (by default) to use RSM to drive the LTO medium changer in a SAN-attached configuration. RSM can only auto-configure a robotic library when the following conditions are true: The robotic library hardware unit supports drive element address reporting with the Read ElementStatus SCSI command. (Consult the manufacturer to find out if your library hardware unit supports this feature.) All drives inside the robotic library are on the same SCSI bus as the library itself. The TAPE library is not attached to a Fibre Channel switch. (This may change in future versions of RSM.) 252 Implementing IBM Tape in Linux and Windows

281 RSM will attempt to auto-configure the libraries attached to the SAN Data Gateway (SDG), but is unable to do so, since the SDG remaps SCSI device IDs and LUNs. Consequently, RSM is unable to resolve the SDG addresses with those contained in the Read Element Status data for the drives. For Fibre Channel attached drives in an IBM 3584, typically, a switch would be involved. RSM devices, however, may be configured using the RSMConfg.exe tool in the Windows 2000 resource kit utility or manually by editing the registry. To edit the registry, the following procedure is required: 1. Stop RSM by typing the following command at a command prompt: net stop removable storage 2. Back up the RSM database by copying the files in the %SystemRoot%\System32\Ntmsdata folder to another (secure) location. 3. Restart RSM by typing the following command at a command prompt: net start "removable storage" 4. Using the RSM console, make a note of all the drives that appear as stand-alone drive libraries. RSM displays all drives that are not mapped to a changer as stand-alone drive libraries, including drives that are actually in the changer but are unmapped. 5. Eject any tapes that are located in the drives in the library. 6. Place a disk in a drive in the library you are trying to configure, either by opening the library door or through a front panel and port (refer to your changer's documentation for details about how to do this). Click Refresh in the RSM console for each of the stand-alone drives, and locate the drive that now shows that it contains a tape. Open the Property sheet for that drive and note the device name on the Device Information property page (for example, \\.\Tape0). Repeat this step for each drive in the changer that you are trying to configure. 7. Click Start, click Run, type regedt32.exe, and then click OK. 8. Locate the following registry key (as shown in Figure 6-9): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtmsSvc\Config\Changerx Figure 6-9 Registry changer key 9. Change the AutoCfg:REG_DWORD:0x1 value to 0. If AutoCfg does not exist, create a new value called AutoCfg with a data type of REG_DWORD, and then type 0 for the data. 10.Stop RSM again. 11.In the Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtmsSvc\Config Chapter 6. Configuring RSM 253

282 12.The Config key contains a subkey for each changer (for example, Changer0) and a subkey for each stand-alone drive. Each changer subkey contains an entry for each drive bay in the changer (for example, DriveBay0). 13.For each DriveBayx entry that has a??? value, replace that value with the device name extracted in Step 6 with the drive in that bay, without the leading "\\.\" characters (for example, Tape3). For example: DriveBay0:REG_SZ:Tape0 DriveBay1:REG_SZ:Tape1 Exit the Registry Editor. 14.Restart RSM. RSM reads the new configuration information and initializes the devices. 15.Using the snap-in, put a tape in each drive in the library after RSM is initialized. If any of the configurations are incorrect, RSM generates an error message during the initialization, or when you insert a tape in a drive. 16.If the manual configuration is unsuccessful, stop the RSM process. Copy your backup version of the RSM database files back to the %SystemRoot%\System32\Ntmsdata folder to restore the database and restart the manual configuration process. If RSM does not generate any error messages, the manual configuration was successful. You should be able to now use SAN-attached devices with RSM-aware applications. 254 Implementing IBM Tape in Linux and Windows

283 7 Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux This chapter describes the installation and implementation of IBM Tivoli Storage Manager in Windows 2000 and Linux environments, explaining the ways to install IBM tape library with either LTO or 3592 drives. Windows 2003 environments will be similar to this. In particular, we review Tivoli Storage Manager s ability to: Achieve normal backup/restore processing Allow multiple servers to share the IBM tape libraries Provide LAN-free backup services Considerations for device and media coexistence and migration We provide information on migrating between the generations of LTO technology with Tivoli Storage Manager, how to define various types of LTO and 3592 cartridges to Tivoli Storage Manager, and discuss some features available with Tivoli Storage Manager V5.2 and V5.3 useful for IBM tape devices. We begin with a brief overview of Tivoli Storage Manager. For more in-depth information about this product, refer to these Redbooks: IBM Tivoli Storage Management Concepts, SG IBM Tivoli Storage Manager Implementation Guide, SG Get More Out of Your SAN with IBM Tivoli Storage Manager, SG IBM Tivoli Storage Manager Version 5.3 Technical Guide, SG Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 255

284 7.1 IBM Tivoli Storage Manager overview As part of the IBM TotalStorage Open Software Family, IBM Tivoli Storage Manager protects data from hardware failures, errors, and unforeseen disasters by storing backup and archive copies on offline and offsite storage. It scales to protect hundreds to thousands of computers running more than a dozen operating systems, ranging from mobile computers to mainframes and connected together via the Internet, WANs, LANs, or SANs. Tivoli Storage Manager Extended Edition's centralized Web-based management, intelligent data move and store techniques, and comprehensive policy based automation all work together to minimize administration costs and the impact to both computers and networks. Optional software modules allow business-critical applications that must run 24x7 to utilize Tivoli Storage Manager's centralized data protection with no interruption to their service. Optional software extensions also allow SAN connected computers to use the SAN for data protection data movements, and provide Hierarchical Storage Management to automatically move unused data files from online disk storage to offline tape storage. Tivoli Storage Manager Extended Edition provides disaster planning capability, NDMP control for NAS filers, and support for large tape libraries. Tivoli Storage Manager is ideal for heterogeneous, data-intensive environments, supporting over 35 platforms and over 250 storage devices across LANs, WANs and SANs, plus providing protection for leading databases and applications (see Figure 7-1). INFORMIX LOTUS DOMINO DB2 MICROSOFT Exchange Server SQL Server APPLE Macintosh ORACLE IBM Tivoli Storage Manager for Mail Lotus Notes on AIX Lotus Notes on Windows NT Domino on AIX Domino on Windows NT Microsoft Exchange Server IBM Tivoli Storage Manager for Databases Microsoft SQL Server Oracle Backup on AIX Oracle Backup on HP-UX Oracle Backup on Sun Solaris Informix IBM DB2 (included in DB2) NAS NDMP IBM* AIX AS/400*** HEWLETT- Linux zseries DIGITAL PACKARD OpenEdition MVS Tru64 FUJITSU*** HP-UX zos IBM Tivoli Storage Manager Client Platforms SYBASE mysap WebSphere SUN SILICON Application Solaris GRAPHICS Server SunOS IRIX IBM ESS LINUX xseries pseries zseries iseries MICROSOFT Windows XP Windows NT Server/WS Windows 2000 Windows 2003 LINUX Red Hat SuSE TurboLinux IBM Tivoli Storage Manager for Hardware IBM Tivoli Storage Manager for ERP Data Protection for mysap on DB2 and Oracle IBM Tivoli Storage Manager for Data Retention IBM Tivoli Storage Manager for Hardware IBM ESS IBM Tivoli Storage Manager for Application Servers Data Protection for Websphere Application Server NOVELL NETWARE VM Linux OS/400 zos AIX Solaris HP-UX Windows W2K /2003 IBM Tivoli Storage Manager Servers Supported Networks APPC IPX/SPX Named Pipes Shared Memory TCP/IP 3270 Emulation Disk Optical Tape Storage Hierarchy Figure 7-1 Tivoli Storage Manager supported platforms Tivoli Storage Manager allows users to confidently protect and manage information; it integrates unattended network backup and archive capabilities with centralized storage management and powerful disaster recovery functions. Tivoli Storage Manager is intended for companies with homogeneous or heterogeneous platforms and complex environments that include both traditional LANs as well as SANs. It is a best-of-breed, scalable storage management solution that helps provide consistent and reliable protection and management of mission-critical data that is spread across your company's enterprise. It protects a broad range of data across the enterprise from the mobile computer to the data center. Tivoli 256 Implementing IBM Tape in Linux and Windows

285 Storage Manager is an industrial-strength centralized storage management product for your enterprise. Tivoli Storage Manager can protect almost any backup-archive client, as shown in Figure 7-1 on page 256. A Tivoli Storage Manage server is provided for OS/390, z/os, Windows 2000/2003, AIX, Solaris, HP-UX, Linux, and OS/400. This breadth of platform coverage affords you the choice in selecting the storage management platform that suits your environment and leverages your hardware and software investments. Tivoli Storage Manager can help control the cost of distributed storage management by leveraging storage resources, helping to reduce the cost of downtime and lost data, and helping to increase the productivity of storage administrators and end users. Tivoli Storage Manager exploits the numerous advantages of SANs with its LAN-free, server-free, and library sharing functions. These help to remove traffic from the LAN, allow for multiple Tivoli Storage Manger servers to share a library, and off-load backup processing from mission-critical servers. Tivoli Storage Manager includes LAN-free backup/restore functionality for many databases and applications, as well as the file-based backup/archive clients. It exploits Tivoli SANergy to allow for LAN-free transfers to file-based storage pools on disk. For more information about IBM Tivoli Storage Management, visit: For the list of currently available storage management products and supported servers and clients, see: Tivoli Storage Manager commonly used terms Here are a few basic Tivoli Storage Manager terms: Server A server is a computer system that provides services to one or more clients or other devices over a network. A Tivoli Storage Manager server is the repository and manager of all the backed up client data. Administrative policies defined at the server control the types of backup performed and retention policies for the data. The server also manages the physical media and devices where the backed up data is stored. Client A client is a computer system that requests a service of another computer system that is typically referred to as a server. Multiple clients may share access to a common server. In Tivoli Storage Manager terms, a client is a computer system that has data assets requiring protection by the Tivoli Storage Manager server. The client decides what data will be backed up and is subject to the server s defined administrative policies for data retention. Typically, a client s data is backed up automatically by a server-scheduled operation. Tape library A tape library consists of the physical robotics that move cartridges, one or more tape drives, and slots for tape storage. It must also have a mechanism for controlling the robotics (a library controller), and may also have a library manager that maintains inventory and mediates sharing. In most cases, a library does not have a built-in Library Manager, so server-based software has to provide the library management function. As an example, the IBM 3494 has a built-in library manager, while the IBM 3584 does not. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 257

286 Tape library partitioning Some tape libraries (for example, IBM 3582, 3583, and 3584) have the ability to be physically partitioned into multiple logical libraries. Each logical library will have its own storage slots and tape devices, but will share the robotics and import/export station with other logical libraries in the same physical library. Each library partition can be managed by a backup application (such as Tivoli Storage Manager). Tape library sharing Tape library sharing is two or more servers sharing the robotics of a tape library. The tape drives and slots within the library may or may not be shared among the attached servers Tivoli Storage Manager and tape library sharing Now, let us look at the Tivoli Storage Manager implementation of tape library sharing. This feature allows multiple Tivoli Storage Manager servers to use the same tape library and drives on a SAN to improve both tape hardware asset utilization and potentially backup/restore performance. When two or more Tivoli Storage Manager servers share a library, one server is defined as the Library Manager, and controls the library operations. Other servers, known as library clients, use server-to-server communications to contact the Library Manager and request library services. This process is shown in Figure 7-2. LAN Read Data clients Mount a tape Write Data Storage Agent or TSM Server Library client SCSI I/O FC Tape Lib FC SCSI I/O TSM server Library manager select drive mount, dismount volumes release, query volumes Figure 7-2 Tivoli Storage Manager library sharing overview Library Manager The Library Manager physically controls the library. All the communication with the library is done by this server. The Library Manager also serializes access to the tape drives, so that only one server is using a tape drive at the same time. The check-in and check-out of volumes will be performed by the Library Manager. This Tivoli Storage Manager server is the only server with a library inventory table for that library. The ownership is added to the inventory table to keep track of which tape belongs to a certain library client. This is the only server in the environment that knows all the volumes. 258 Implementing IBM Tape in Linux and Windows

287 The Library Manager can also use the library for its own purposes, without being a library client at the same time (no library client configuration is necessary on the manager). Library client The library client uses server-to-server communications to contact the Library Manager for the handling of the physical hardware. The client sends the requests to the Library Manager, and, afterwards, reads or writes to the tape drive it was given access to. Server-to-server communication protocol is used to send requests from the library client to the Library Manager, and to send the response from the manager to the client. LAN-free data transfer LAN-free data transfer with Tivoli Storage Manager allows the SAN to be used as an alternative path for moving data between the Tivoli Storage Manager clients and the server. LAN-free data transfer exploits this SAN path by enabling the Tivoli Storage Manager client to back up and restore data directory to and from SAN-attached storage (disk and tape), which is shared between the Tivoli Storage Manager server and client, and managed by the client. This means that the data is not transferred over the LAN to the server as in traditional Tivoli Storage Manager backup, but transfers directly from the client to the SAN-attached storage devices. Tivoli Storage Manager currently provides LAN-free data transfer for normal files, the database, and other applications through certain IBM Tivoli Storage Manager for Mail, IBM Tivoli Storage Manager for Databases, and IBM Tivoli Storage Manager for ERP products. These clients require an additional Storage Agent to be installed, which directs the movement of the data from the client disk to the SAN-attached storage. This process is shown in Figure 7-3 on page 260. For a complete list of operating systems and applications supported in a LAN-free environment, see: Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 259

288 TSM Client Storage Agent 1 Meta data LAN 3 TSM server 2 Read Data 3 Write Data SAN Client Disk Tape Library Disk Server Storage Hierarchy Figure 7-3 Tivoli Storage Manager LAN-free data transfer overview 7.2 Non-shared tape device with Tivoli Storage Manager for Windows In this section, we discuss installing IBM tape libraries with Tivoli Storage Manager in the Windows environment. We used a tape library with both Fibre Channel and direct SCSI connections. The actual installations in the Windows environment was for Windows The environment in our lab for the Tivoli Storage Manager installation with FC connected LTO was: Intel server, Windows 2000 SP2 (build 2195), and QLogic QLA2300 HBA IBM 2109 FC switch IBM 3584 with two 3592 drives For direct SCSI connected LTO, our environment was: Intel server, Windows 2000 SP2 (build 2195), and Adaptec LVD IBM 3583 with two LVD drives Installing Tivoli Storage Manager To install Tivoli Storage Manager Version 5.2, use the Tivoli Storage Manager Quick Start manuals for the relevant operating system. For Windows, this will be IBM Tivoli Storage Manager for Windows Quick Start V5.2, GC The manuals can be found at this URL: Implementing IBM Tape in Linux and Windows

289 To install Tivoli Storage Manager Version 5.3, use the Tivoli Storage Manager Installation Guide manuals for the relevant operating system. For Windows, this will be IBM Tivoli Storage Manager for Windows Installation Guide V5.3, GC The manuals can be found at this URL: Notice that there is now a new Web site for the Tivoli Storage Manager V5.3 publications. Note: Tivoli Storage Manager V4.1.2 supports Ultrium 1 tape drives in the IBM 3580, 3581, 3583, and Tivoli Storage Manager V5.1.6 is required to support Ultrium 2 drives. Tivoli Storage Manager V is required to support the IBM 3582 library. Tivoli Storage Manager V5.2 supports mixing Ultrium 1 and 2 in the same logical library. Tivoli Storage Manager V , V5.2.1, or V5.3 support IBM 3592 tape drives. Tivoli Storage Manager V5.2.3 supports the IBM U library. Tivoli Storage Manager V5.2.4 or V5.3 supports Ultrium 3 tape drives, and a mix of Ultrium 1, 2, and 3 in the same logical library. Installation summary When installing Tivoli Storage Manager, the default configuration sets up a disk storage pool for storing backup data. Before you can begin using a tape device as a backup destination, you must do the following: 1. Disable RSM (using the procedure in Disabling RSM on page 134). 2. Attach the devices to your system. 3. Install the LTO Ultrium device drivers for the Windows system you are using (as described in 3.2.1, Installing the medium changer device driver on page 83). 4. Install the Tivoli Storage Manager server software. 5. Initialize the server. 6. Define the library. 7. Define the library path. 8. Define the drives in the library. 9. Define the drive paths. 10.Define a device class using the library. 11.Define a storage pool associated with the device class. 12.Include the storage pool in the storage hierarchy. 13.Label the tape library media. After completing step 3, follow the instructions in IBM Tivoli Storage Manager for Windows Installation Guide (for your version of Tivoli Storage Manager) to install Tivoli Storage Manager (step 4). We installed the Tivoli Storage Manager server first (using the Custom option with the default features), then the Tivoli Storage Manager device driver (tsmscsi). Before installing, you should always check that you have the latest code fixes. Refer to the following Web site for Tivoli product requirements, supported devices, and code levels: Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 261

290 To perform the subsequent tasks, you can use any one of the following interfaces: Tivoli Storage Manager configuration wizard Administrative client command line Web administration interface We will continue the configuration (step 5 on page 261) by initializing the server using the Tivoli Storage Manager configuration wizard. The other configuration tasks will be shown using the configuration wizards and the administrative command line. The command line interface is the same across all present Tivoli Storage Manager versions, while the Web based administrator interface has changed completely between the Tivoli Storage Manager Versions 5.2 and 5.3 with the introduction of the Administrative Console with V5.3. Refer to the Tivoli Storage Manager manuals and Redbooks for details for using the Administrative Console interface. Initialize the server After the Tivoli Storage Manager server and device driver installation, you will have rebooted the server to initialize the device driver. You may begin to configure your Tivoli Storage Manager server and, in particular, configure your IBM tape library and drives for use. The examples are shown using the Tivoli Storage Manager configuration wizard, with additional examples showing the commands associated with each action taken. You must use the wizard to initialize your server before running additional configuration commands via the Web administrator or command line interface (CLI). If you want to use the CLI (dsmadmc) to configure your server, you must install the client code on the Tivoli Storage Manager server using a Custom installation, during which you may opt to install the administrative command line. If you are new to the product, we suggest that you run through the wizard configuration first to quickly get the server up and running. The server parameters may be reconfigured later using the Web browser interface or the command line. We will here specifically show how to get the Tivoli Storage Manager server up and running with the LTO tape library and drives only. You can start the configuration wizard by clicking the Tivoli Storage Manager Management Console icon on the desktop, or from Start Programs Tivoli Storage Manager Management Console. Note that the Management Console is an application for the Microsoft Management Console (MMC). If the Initial Configuration Task Window (Figure 7-5 on page 263) does not appear automatically, click Tivoli Storage Manager and scroll down to the entry that matches the server just installed. In this instance, this is server LILO. Right-click the server name and select Add a new Tivoli Storage Manager Server, as shown in Figure 7-4 on page Implementing IBM Tape in Linux and Windows

291 Figure 7-4 Initializing the Tivoli Storage Manager server This will begin the Initial Configuration Task List (Figure 7-5). In the list window, click Start and the wizard will commence. Note that the wizard will perform all of the listed tasks in succession. You may, however, choose the Minimal configuration, or cancel out of the wizard at any stage to configure the server later. We will show you how to configure IBM tape devices using the wizard configuration, and using the command line. Figure 7-5 Initial configuration task list Disabling Tivoli Storage Manager Device Driver from boot We recommend installing the Tivoli Storage Manager Device Driver, even though we will use IBM Tape Device Driver for the LTO devices. The Tivoli Storage Manager device driver allows you to see the Tivoli Storage Manager device names in the Tivoli Storage Manager Management Console. However, you need to disable the Tivoli Storage Manager Device Driver from starting at boot time and claiming the devices that the IBM Tape Device Driver is supposed to claim. To do this, modify the options for the Tivoli Storage Manager Device Driver service to startup type Manual, by accessing the Tivoli Storage Manager Management Console. Select Start Programs Tivoli Storage Manager Management Console. Select Servername (Windows - Local) TSM Device Driver Reports Service Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 263

292 Information. In the Service Information pane, right-click the TSM Device Driver service and select Properties, as shown in Figure 7-6. Figure 7-6 Tivoli Storage Manager Management Console Service Information As shown in Figure 7-7, the Properties window lists the devices using the alias names as Tivoli Storage Manager would normally see them. The window should look somewhat similar to the one below; you should have all of your IBM tape devices on the right side, meaning that Tivoli Storage Manager will not claim those devices. Note that the setting is different if you are using Tivoli Storage Manager V5.1 or earlier. Figure 7-7 Device Driver options Defining the library and drives using the Configuration Wizard You should have already installed the tape drives and library using the IBM Ultrium device drivers for Windows 2000, according to Chapter 3, Basic IBM tape setup for Windows on page 79. For performance reasons, we suggest that you use a variable block size length (Block Size=0) and have hardware compression turned on. This is the default for Windows servers. You can verify and modify this value through the NTUTIL program that comes packaged with the Ultrium device drivers, as shown in Example 7-1 on page Implementing IBM Tape in Linux and Windows

293 Example 7-1 Turning hardware compression on enter selection: 44 Compression off = 0, on = 1: 1 execute set_device_parameters compression = ON analyze() called with rc 0 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 4.00 Return to continue: Note that hardware compression has been set to ON. However, Tivoli Storage Manager can override the device settings for hardware compression by using the FORMAT parameter in the DEFINE DEVICE class command. (See 7.2.3, Defining the library and drives using the command line on page 269.) The block size may also be viewed from the NTUTIL manual mode menu. Option 3 in the manual test menu (Example 7-2) shows a tape drive configured with Block Size = 0, which means variable length blocks. Example 7-2 Manual test menu manual test menu: ======================================================================= 1: set device special file 2: display symbols 3: set block size R/W (now!0 fixed) 5: set return error when fail 6: set/reset trace 7: set exit on unexpected result 8: Library Mode The Device Configuration Wizard will start automatically if we run through the Tivoli Storage Manager configuration wizard from the beginning, as detailed in Initialize the server on page 262. Alternatively, you may run it at any time if you have not already done so by accessing the Tivoli Storage Manager Management Console from the desktop. Click Wizards and then Device Configuration. Note that the server must have been initialized for use before performing this step. The Device Configuration Wizard will commence, as in Figure 7-8. Click Next. Figure 7-8 Device Configuration Wizard If the Tivoli Storage Manager Device Driver is not running, you will be prompted to start it (Figure 7-9 on page 266). Answer No, since we use IBM tape driver to control both the library medium changer and the tape drives. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 265

294 Note: As of Tivoli Storage Manager V5.2, the Tivoli Storage Manager Device Driver is no longer used to control the IBM tape library medium changer. Use the IBM Ultrium Device Driver for both medium changer and drive (for IBM 3592, use IBM Magstar Device Driver). Figure 7-9 Tivoli Storage Manager Device Driver start prompt The wizard will detect the IBM tape library and drives attached to the system, as shown in Figure The device name, type, and location are listed in the left panel. The device name will be listed as: lbx.x.x.x: Library mtx.x.x.x: Tape device The Xs represent the SCSI ID, LUN, bus, and port numbers, respectively. For instance, a device listed as lb corresponds to a library at SCSI ID 2, LUN1, bus0, and port2. Figure 7-10 Tivoli Storage Manager device selection The element address and serial number will appear on the Detailed tab. When configuring multiple tape drives in a library, you can determine which entry corresponds to which physical tape drive. You may want to reorder them so they match the order of the physical installation. For some cases, such as configuring through SAN Data Gateway module, the element address and serial number may not appear here; in this case, check the device information using the procedures described in 3.5.2, Creating a library device table on page 129 (Windows) or 4.4.2, Creating a library device table on page 209 (Linux). Check the devices you want to define to Tivoli Storage Manager and click Next (Figure 7-11 on page 267). 266 Implementing IBM Tape in Linux and Windows

295 Figure 7-11 Tivoli Storage Manager devices selected You will be asked to select the format type of the device, as in Figure Choose the Ultrium generation (or 3592) that is appropriate for the drives in your library. You would, in most cases, select a format with compression for performance reasons. Refer to 7.2.5, Defining the device class using the command line on page 271 for more details on format types. Figure 7-12 Choose recording format Tape drive element addresses Tivoli Storage Manager V5.2 and later normally obtain the element address of the drive automatically when you define IBM tape devices. However you can also define element_number specifically, and these numbers may be found in the operator guide for your library, for example, IBM Total Storage 3584 Tape Library Operator Guide, GA , IBM Total Storage 3583 Tape Library Setup and Operator Guide for Multi-path Libraries, GA , or IBM Total Storage 3582 Tape Library Setup, Operator, and Service Guide, GA You can also obtain this information at the following Web site: IXHPSUNWIN.html Select LTO Tape libraries, and scroll to the IBM tape libraries. Click either IBM 3582, 3583, or 3584 to obtain the element addresses. It is worth noting that different element addresses are provided for devices controlled by RSM on behalf of Tivoli Storage Manager and for Tivoli Storage Manager controlled devices. We recommend disabling RSM and having Tivoli Storage Manager control the devices. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 267

296 For example, Figure 7-13 shows the SCSI Element address for drives of the IBM 3584, and Figure 7-14 shows the SCSI Element address for drives of the IBM As you may see in the Web page, if you should be using Windows RSM, this would remap the element numbers starting at 0. Since we recommend turning off RSM, these are the relevant element numbers. Figure 7-13 SCSI Element number of tape drives in the IBM 3584 Drive Column 3 105h (261) Drive Sled F 104h (260) Drive Sled E 103h (259) Drive Sled D 102h (258) Drive Sled C 101h (257) Drive Sled B 100h (256) Drive Sled A Figure 7-14 SCSI Element number of tape drives in the IBM 3583 Continuing the installation The wizard will proceed to define the library and drives to the Tivoli Storage Manager server. To complete the device configuration wizard, click Finish on the final window. A pop-up window will appear to show that the device definitions have completed successfully. Now, we have successfully configured the library and drives. The wizard has automatically defined a device class, as well as a storage pool with the device class assigned to it. We will discuss the device class and storage pool definitions in 7.2.5, Defining the device class using the command line on page 271 and 7.2.7, Defining the storage pool using the command line on page 273. Although the wizard has successfully configured the library, drive, device class, and storage pool, the process is less flexible than when using the command line to perform these 268 Implementing IBM Tape in Linux and Windows

297 operations. The wizard uses its own naming conventions and will use default operating parameters Defining the library and drives using the command line Manually defining the library using the command line or Administrative interface allows greater control over the options associated with this action. Use the device names as seen in the Tivoli Storage Manager Management Console (Figure 7-15) for defining the devices to the Tivoli Storage Manager server. Figure 7-15 Checking the Tivoli Storage Manager device name in the Management Console First, define the library and library path using the following commands. When there are multiple choices, the default setting is listed last. DEFINE LIBRARY library_name LIBTYPE=SCSI AUTOLABEL=yes/no DEFINE PATH server_name library_name SRCTYPE=SERVER DESTTYPE=LIBRARY \ DEVICE=dev_name For library_name, enter a user-specified name of the library to be defined: DEFINE LIBRARY lib3584 LIBTYPE=SCSI For server_name, specify the name you have set for your server with the SET SERVERNAME command This can be checked by issuing the QUERY STATUS command. In our case, we used the name lilo. For dev_name, enter the full device name of library, such as lb DEFINE PATH lilo lib3584 SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=lb Next, define each of the library s drives and drives paths with: DEFINE DRIVE library_name drive_name ELEMENT=element_number/AUTODETECT \ CLEANFREQUENCY=Gigabytes/ASNEEDED/NONE DEFINE PATH server_name drive_name SRCTYPE=SERVER DESTTYPE=DRIVE \ LIBRARY=library_name DEVICE=dev_name For library_name, enter the name of your already defined library (lib3584 in our example). Use the operating system device name of the tape drive being defined for dev_name. Enter the full device name for dev_name, such as mt The element_address is a number that indicates the physical location of a drive within an automated library. Tivoli Storage Manager needs the element address to connect the physical location of the drive to the drive s SCSI address. As of Version 5.2, you can now specify autodetect for element_number, and this is the default. The element number will then be automatically detected by Tivoli Storage Manager when the path to the drive is defined. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 269

298 Keep in mind that your drives are not necessarily configured by the operating system in the same order as they are installed physically in the library, as described in 5.3, Persistent binding on page 237. Therefore, check carefully that the element address maps with your drive configuration. Note: The CLEANFREQUENCY parameter in the DEFINE DRIVE command is optional. Tivoli Storage Manager-managed cleaning is intended for drives and libraries that do not have an automatic cleaning function. The IBM 3581, 3582, 3583, and 3584 have an automatic cleaning function, which means they take care of drive cleaning. Therefore, it is not necessary to specify the CLEANFREQUENCY parameter, because the default value is NONE. The IBM U does not have an automatic cleaning function; therefore, we recommend that you let Tivoli Storage Manager manage the cleaning for this device. If you want Tivoli Storage Manager to control drive cleaning, you should use the option ASNEEDED. You will have to change the auto cleaning function setting to the host cleaning function on the autoloader or library. Also, if you use a partitioned IBM 3584, then every logical partition needs its own cleaner cartridge. There is no need to clean LTO drives on a periodic basis (that is, after a set number of gigabytes has been processed by the drive), and additional manual cleanings are discouraged. We configured our drives in the IBM 3584 with: DEFINE DRIVE lib3584 drive1 DEFINE DRIVE lib3584 drive2 DEFINE PATH lilo drive1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=lib3584 \ DEVICE=mt DEFINE PATH lilo drive2 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=lib3584 \ DEVICE=mt Tip: Before defining the drives and libraries, make sure that your library is online and your drives are available. Also, there should not be any cartridge loaded in the drive being defined. Continue the implementation in 7.2.5, Defining the device class using the command line on page Defining the device class using the Configuration Wizard To allow the Tivoli Storage Manager server to correctly use the IBM tape library and drives, we must define a device class. A device class is best thought of as the interface that allows Tivoli Storage Manager to effectively communicate with a device. If we run the Configuration Wizard to install the tape library and drives, the LTO device class and associated storage pool will be created automatically in the background. This will use system generated names, and we have a better control of the options by using the command line. 270 Implementing IBM Tape in Linux and Windows

299 7.2.5 Defining the device class using the command line To manually configure the device class, use the following commands. For LTO drives, use LTO as the DEVTYPE parameter: DEFINE DEVCLASS devclass_name LIBRARY=library_name DEVTYPE=LTO \ FORMAT=Ultrium/UltriumC/Ultrium2/Ultium2C/Ultrium3/Ultrium3C/Drive \ MOUNTLIMIT=mount_limit/DRIVES For IBM 3592 drives, use 3592 as the DEVTYPE parameter: DEFINE DEVCLASS devclass_name LIBRARY=library_name DEVTYPE=3592 \ FORMAT=3592/3592C/Drive MOUNTLIMIT=mount_limit/DRIVES The library_name will match the name of the library you previously defined. The FORMAT parameter has the following valid options for LTO: drive The server selects the highest format that can be supported by the drive on which a volume is mounted. This value will use the settings on the tape drive characteristics (device driver) for hardware compression. This is the default. ultrium This specifies that Tivoli Storage Manager writes data using the ULTRIUM recording format. This format results in a cartridge capacity of 100 GB when using a Ultrium 100 GB data cartridge. This value overrides the settings on the tape drive characteristics for hardware compression. ultriumc This specifies that Tivoli Storage Manager writes data using the ULTRIUM recording format with compression. This format results in a cartridge capacity of approximately 200 GB when using a Ultrium 100 GB data cartridge. This value overrides the settings on the tape drive characteristics for hardware compression. ultrium2 Specifies that Tivoli Storage Manager writes data using the ULTRIUM2 recording format. This format results in a cartridge capacity of 200 GB when using Ultrium2 200 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. ultrium2c Specifies that Tivoli Storage Manager writes data using the ULTRIUM2 recording format with compression. This format results in a cartridge capacity of approximately 400 GB when using Ultrium2 200 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. ultrium3 Specifies that Tivoli Storage Manager writes data using the ULTRIUM3 recording format. This format results in a cartridge capacity of 400 GB when using Ultrium3 400 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression ultrium3c Specifies that Tivoli Storage Manager writes data using the ULTRIUM3 recording format with compression. This format results in a cartridge capacity of approximately 800 GB when using Ultrium3 400 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 271

300 3592 Specifies that Tivoli Storage Manager writes data using the 3592 recording format. This format results in a cartridge capacity of 300 GB when using GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. 3592c Specifies that Tivoli Storage Manager writes data using the 3592 recording format with compression. This format results in a cartridge capacity of approximately 900 GB when using GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. Compression in general improves backup performance. Therefore, we recommend that you use compression either specifically with FORMAT=ultriumc/ultrium2c/ultrium3c/3592c; or with FORMAT= drive, which implies that the server selects the highest format that is supported by the drive on which a volume is mounted. (Do not use FORMAT= drive for a library containing a mix of Ultrium 1, 2, or 3 drives. Use the specific definitions, as described in detail in 7.12, Device migration and coexistence on page 306) If you use recording FORMAT=ultriumc/ultrium2c/ultrium3c/3592c/drive, then your LAN-free clients also use compression regardless of whether hardware compression is enabled. Note that Tivoli Storage Manager also provides optional client compression. If this is enabled, then clients compress their data before sending it to the storage device. This is particularly useful where the network connection between the client and server is slow and traffic needs to be minimized. With client compression on, using tape drive compression has little effect and is not recommended. You should evaluate your environment and requirements (probably by performing some appropriate testing) to determine if client compression is beneficial. If so, then enable it, and use the uncompressed (FORMAT=ultrium/ultrium2/ultrium3/3592) flag when defining the device class. If not, then tape drive compression should be used. The option MOUNTLIMIT specifies the maximum number of sequential access volumes that can simultaneously be mounted for the device class. This parameter is optional. The default is drives, which means that the maximum is set to the number of drives installed and available in the library. There are two reasons why you might use a specific value rather than the default: If you are going to share the library among multiple servers, you may want to specify a number instead of the default drives to limit the number of drives each server has access to. If you have a mixture of LTO generation drives in the same library, see 7.12, Device migration and coexistence on page 306 for more information. We recommend that the default value of drives not be used for the older Ultrium x device classes. For example, when specifying MOUNTLIMIT=drives, the Tivoli Storage Manager server will load Ultrium 1 cartridges into Ultrium 1 drives in preference to Ultrium 2 or 3 drives, but there exists the possibility that all Ultrium 2 or 3 drives could be loaded with Ultrium 1 cartridges and therefore, an Ultrium 2 or 3 cartridge could not be loaded. It may be necessary to set the MOUNTLIMIT parameter to a value that is equal to the number of that version of drives, or certainly to a value less than the total number of drives in the library. To define the IBM 3584 in our Windows environment, we called the device class dev3584, pointing to our previously defined library lib3584. In the example, we have two 3592 drives in the library, so we specified 3592C for the FORMAT parameter and we set the MOUNTLIMIT to 2: DEFINE DEVCLASS dev3584 DEVTYPE=3592 LIBRARY=lib3584 FORMAT=3592C MOUNTLIMIT=2 Example 7-3 on page 273 shows our device class definition. 272 Implementing IBM Tape in Linux and Windows

301 Example 7-3 query devclass dev3584 f=d Device Class Name: DEV3584 Device Access Strategy: Sequential Storage Pool Count: 1 Device Type: 3592 Format: 3592C Est/Max Capacity (MB): Mount Limit: 2 Mount Wait (min): 60 Mount Retention (min): 60 Label Prefix: ADSM Library: LIB3584 Directory: Server Name: Retry Period: Retry Interval: Shared: High-level Address: Minimum Capacity: WORM: No Scaled Capacity: Last Update by (administrator): ADMIN Last Update Date/Time: 07/14/05 20:42: Defining the storage pool using the Configuration Wizard If we run the Configuration Wizard to install the tape library and drives, the LTO device class and associated storage pool will be created automatically in the background. This will use system generated names, and we have a better control of the options by using the command line Defining the storage pool using the command line Define the storage pool with: DEFINE STGPOOL stgpool_name devclass_name MAXSCRATCH=number This storage pool will be assigned (written) to the device class we just defined, so we specify the name dev3584. We used pool3584 as the stgpool_name: DEFINE STGPOOL pool3584 dev3584 MAXSCRATCH=200 Example 7-4 on page 274 shows you the storage pool just defined. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 273

302 Example 7-4 q stgpool pool3584 f=d Storage Pool Name: POOL3584 Storage Pool Type: Primary Device Class Name: DEV3584 Estimated Capacity (MB): 0.0 Pct Util: 0.0 Pct Migr: 0.0 Pct Logical: High Mig Pct: 90 Low Mig Pct: 70 Migration Delay: 0 Migration Continue: Yes Migration Processes: Next Storage Pool: Reclaim Storage Pool: Maximum Size Threshold: No Limit Access: Read/Write Description: Overflow Location: Cache Migrated Files?: Collocate?: No Reclamation Threshold: 60 Maximum Scratch Volumes Allowed: 200 Delay Period for Volume Reuse: 0 Day(s) Migration in Progress?: No Amount Migrated (MB): 0.00 Elapsed Migration Time (seconds): 0 Reclamation in Progress?: No Volume Being Migrated/Reclaimed: Last Update by (administrator): ADMIN Last Update Date/Time: 07/14/05 18:01:50 Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No Last Update Date/Time: 07/14/05 20:50:18 Now you can use this storage pool in your management class copy groups, so that the device will be used for backups or archives Inserting data and cleaning cartridges Once we have set up our definitions, we need to identify the cartridges that Tivoli Storage Manager will use, either for storing data, or for cleaning the drives. LTO cartridges are identified as IBM machine type You can find information about how to buy LTO and 3592 cartridges from IBM, both data and cleaning, from the Web site: LTO and 3592 cartridges are also available from several other licensed manufacturers, which vary from country to country. Tivoli Storage Manager requires each tape used to have a physical label written on it for identification. You can label volumes individually or process multiple volumes with variations of the label command. Here, we want to perform initial labeling of all the new tapes in our library. Since the IBM 3584 model has a barcode reader, and the tapes already have an external barcode label, this command will cause the matching label to be written onto the 274 Implementing IBM Tape in Linux and Windows

303 tape. It is not necessary that the magnetic label be the same as the barcode label; however, you will avoid a lot of confusion by making them identical. We put the new tapes directly into the library, then we can label them using the media labeling wizard or we can use the command line (see Preparing the cartridges using the command line interface on page 278. Preparing the cartridges using the Configuration Wizard To access the Media Labeling Wizard, open up the Tivoli Storage Manager Management Console by selecting Start Program Files Tivoli Storage Manager Management Console. Select Wizards and scroll down to the Configuration Wizard window, as shown in Figure Figure 7-16 Selection for Media Labeling Wizard Click the Media Labeling Wizard and click Start. When the wizard appears (Figure 7-17), click Next. Figure 7-17 Media Labeling Wizard Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 275

304 You are logged into the Tivoli Storage Manager server and it presents you with a list of discovered devices. You will be prompted to make a drive selection. For our purposes, we want to label all tapes in the library so that they are initialized for Tivoli Storage Manager. We must make our selection at the library level by checking the box next to the library name, as shown in Figure This will also automatically select the tape drives attached to it and ensure that every tape in the library is detected as a candidate for the labeling operation. Figure 7-18 Device selection for labeling Click Next and all tape volumes residing in the library will be detected (Figure 7-19). Select the tapes that you want to label. There are several available options for labeling, including: Overwrite existing label: Specify this if you want to write a fresh label to the tape. The default is no, since it might lead to inadvertently overwriting a tape that contains valid data. Barcode reader: Tivoli Storage Manager will read the barcode label and use that to internally label the cartridge. Keep volumes in library: This will retain the volumes inside the library and not check them out once each is labeled. Prompt user to insert volumes: The user will be asked to insert cartridges to be labeled. To avoid this, insert the cartridges directly into the library or in the bulk I/O slot beforehand. Figure 7-19 Volume selection for labeling 276 Implementing IBM Tape in Linux and Windows

305 Click Label Now and the media labeling process begins. The Media labeling Monitor appears (Figure 7-20) showing the progress of the operation. (For brevity, only one volume was actually checked in.) Figure 7-20 Media Labeling Monitor: volume selection for labeling When finished, click Next and the Media Labeling Wizard will ask if you would like to check in the volumes that you have just labelled, as shown in Figure You must check in the tape volumes before they can be used by Tivoli Storage Manager. Select Barcode Reader to use the cartridge barcode label to check in the cartridges (unless you have created labels different from the external barcode label, or your tape device does not have a barcode reader). If you do not specify a barcode reader, you will be prompted to specify the volumes you want to check in. Figure 7-21 Tivoli Storage Manager media check-in Click Check-In Now and the wizard will proceed to check in the library tape volumes. A pop-up window will appear (Figure 7-22 on page 278) indicating that this can take some time and you can monitor the progress through the server console monitor. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 277

306 Figure 7-22 Media check-in issued When the check-in is complete, click Next and another pop-up window will appear indicating that the task was successful. It will also suggest that you verify that the cartridges are able to be written to by performing a backup on an Tivoli Storage Manager client. Preparing the cartridges using the command line interface With the new tapes inserted into the library, use the following command: LABEL LIBVOLUME lib3584 SEARCH=yes LABELSOURCE=barcode CHECKIN=scratch The parameter SEARCH=Yes means that Tivoli Storage Manager searches inside the library for any unlabeled volume with a readable barcode. It then mounts each cartridge in turn and writes the label onto the tape. The tape is finally checked in and available for use by Tivoli Storage Manager. Attention: There should be no cleaning cartridges in the library inventory accessible from the host, as Tivoli Storage Manager will try to label and mount them into a drive. If you have enabled the tape library s autoclean function, and cleaning cartridges were inserted as appropriate, then those cartridges are not accessible from the host, and no labeling operation will occur for them. After the above command, you can check on the status of the inserted volumes with the QUERY LIBVOL command. Example 7-5 shows all the labeled cartridges with scratch status. The element address is also displayed so that we can tell which physical location contains each volume. Example 7-5 query libvol Library Name Volume Name Status Owner Last Use Home Element LIB3584 ABA920 Scratch 1,024 LIB3584 ABA922 Scratch 1,025 LIB3584 ABA923 Scratch 1,026 LIB3584 ABA924 Scratch 1,037 LIB3584 ABA925 Scratch 1,030 LIB3584 ABA926 Scratch 1,031 LIB3584 ABA927 Scratch 1,032 LIB3584 ABA928 Scratch 1,029 LIB3584 ABA929 Scratch 1,028 LIB3584 ABA990 Scratch 1,036 Labeling data cartridges using the I/O Station To insert additional data cartridges to the library, use the command: LABEL LIBVOLUME lib_name SEARCH=bulk LABELSOURCE=barcode CHECKIN=scratch If you have only a few cartridges to insert, use the I/O station and use the option SEARCH=bulk. You will be prompted on the administrator console to insert all the volumes to 278 Implementing IBM Tape in Linux and Windows

307 be labeled into the I/O station, and to indicate that this has been done by issuing the command (at an administrative command prompt): REPLY request_id The server will then load and label the volumes it finds. If you do not have an open administrator console you can also issue the commands QUERY REQUEST or QUERY ACTLOG to display information about pending mount requests. Example 7-6 shows you an output of the activity log when inserting one cartridge into the IBM We used this command: LABEL LIBVOLUME Lib3584 SEARCH=bulk LABELSOURCE=barcode CHECKIN=scratch followed by this command to continue the operation: REPLY 011 Example 7-6 Tivoli Storage Manager: query actlog for inserting new cartridges 04/09/03 18:49:11 ANR2017I Administrator ADMIN issued command: LABEL LIBVOLUME LIBM3584 SEARCH=BULK LABELSOURCE=BARCODE CHECKIN=SCRATCH 04/09/03 18:49:11 ANR0984I Process 23 for LABEL LIBVOLUME started in the BACKGROUND at 18:49:11. 04/09/03 18:49:11 ANR8799I LABEL LIBVOLUME: Operation for library LIB3584 started as process /09/03 18:49:11 ANR0609I LABEL LIBVOLUME started as process /09/03 18:49:12 ANR8373I 011: Fill the bulk entry/exit port of library LIB3584 with all LTO volumes to be processed within 60 minute(s); issue 'REPLY' along with the request ID when ready. 04/09/03 18:49:18 ANR8336I Verifying label of LTO volume ABA922 in drive DRIVE1 (/dev/rmt1). 04/09/03 18:49:44 ANR2017I Administrator ADMIN issued command: REPLY /09/03 18:49:44 ANR8499I Command accepted. 04/09/03 18:49:48 ANR2017I Administrator ADMIN issued command: QUERY ACTLOG 04/09/03 18:51:00 ANR8810I Volume ABA926 has been labeled in library LIB /09/03 18:51:42 ANR8427I CHECKIN LIBVOLUME for volume ABA926 in library LIB3584 completed successfully. 04/09/03 18:52:40 ANR8810I Volume ABA925 has been labeled in library LIB /09/03 18:53:22 ANR8427I CHECKIN LIBVOLUME for volume ABA925 in library LIB3584 completed successfully. Labeling data cartridges without a barcode reader If your library has a barcode reader (such as an IBM 3582, 3583, or 3584), you will almost certainly be using this reader to label the cartridges. However, if you have an LTO model (such as the single drive IBM 3580) without a barcode reader, you will need to manually specify a label. If the media is labeled with a barcode anyway, we strongly recommend that you use this barcode string to label the volume, as this will make it much easier for the operators to distinguish the volumes. To insert an unlabeled cartridge, specify the volume name you want to use for the cartridge and put the cartridge in the I/O station or drive: LABEL LIBVOLUME lib_name volume_name CHECKIN=scratch Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 279

308 You will be prompted to insert the cartridge and to indicate when it is available by issuing the following command (at an administrative command prompt): REPLY request_id You can insert only one cartridge for each command. It will then be labeled by the server. Example 7-7 shows you an output of the activity log for using this method with one unlabeled cartridge in an IBM We use this command: LABEL LIBVOLUME Lib3584 unlab02 CHECKIN=SCRATCH followed by this command to continue the operation: REPLY 013 Example 7-7 Tivoli Storage Manager: query actlog output for manually labelling a cartridge 04/09/03 15:12:04 ANR2017I Administrator ADMIN issued command: LABEL LIBVOLUME LIB3584 unlab02 CHECKIN=SCRATCH OVERWRITE=YES 04/09/03 15:12:04 ANR0984I Process 28 for LABEL LIBVOLUME started in the BACKGROUND at 15:12:04. 04/09/03 15:12:04 ANR8799I LABEL LIBVOLUME: Operation for library LIB3584 started as process /09/03 15:12:04 ANR0609I LABEL LIBVOLUME started as process /09/03 15:12:04 ANR0405I Session 1368 ended for administrator ADMIN (WebBrowser). 04/09/03 15:12:06 ANR8323I 013: Insert LTO volume UNLAB02 R/W into entry/exit port of library LIB3854 within 60 minute(s); issue 'REPLY' along with the request ID when ready. 04/09/03 15:12:25 ANR2017I Administrator SERVER_CONSOLE issued command: REPLY /09/03 15:12:25 ANR8499I Command accepted. 04/09/03 15:15:32 ANR8810I Volume UNLAB02 has been labeled in library LIB /09/03 15:16:15 ANR8427I CHECKIN LIBVOLUME for volume UNLAB02 in library LIB3584 completed successfully. 04/09/03 15:16:16 ANR8800I LABEL LIBVOLUME for volume UNLAB02 in library LIB3584 completed successfully. 04/09/03 15:16:16 ANR0985I Process 28 for LABEL LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 15:16:16. Inserting cleaner cartridges If you have chosen to have Tivoli Storage Manager manage library cleaning, you need to insert some cleaning cartridges. Use the following command: CHECKIN LIBVOLUME LIB3584 STATUS=cleaner CHECKLABEL=barcode SEARCH=bulk \ CLEANINGS=50 The parameter SEARCH=bulk means that Tivoli Storage Manager will search the library I/O station for usable volumes to check in. Set the CLEANINGS parameter to the number of uses specified for your cartridge; for LTO, this is 50. Insert one or more cleaner cartridges into the I/O station, and reply to the request issued by the server, as shown in Example 7-8 on page Implementing IBM Tape in Linux and Windows

309 Example 7-8 Insert cleaner cartridge 04/09/03 20:02:56 ANR2017I Administrator ADMIN issued command: CHECKIN LIBVOLUME LIB3584 STATUS=CLEANER CHECKLABEL=BARCODE MOUNTWAIT=60 SEARCH=BULK CLEANINGS=50 04/09/03 20:02:56 ANR0984I Process 4 for CHECKIN LIBVOLUME started in the BACKGROUND at 20:02:56. 04/09/03 20:02:56 ANR8422I CHECKIN LIBVOLUME: Operation for library LIB3584 started as process 4. 04/09/03 20:02:56 ANR0609I CHECKIN LIBVOLUME started as process 4. 04/09/03 20:03:06 ANR8468I LTO volume ABA922 dismounted from drive DRIVE2 (/dev/rmt1) in library LIB /09/03 20:03:07 ANR8373I 001: Fill the bulk entry/exit port of library LIB3584 with all LTO volumes to be processed within 60 minute(s); issue 'REPLY' along with the request ID when ready. 04/09/03 20:03:09 ANR2017I Administrator ADMIN issued command: QUERY ACTLOG 04/09/03 20:03:21 ANR2017I Administrator ADMIN issued command: REPLY /09/03 20:03:21 ANR8499I Command accepted. 04/09/03 20:03:26 ANR2017I Administrator ADMIN issued command: QUERY ACTLOG 04/09/03 20:03:40 ANR2017I Administrator ADMIN issued command: QUERY ACTLOG 04/09/03 20:03:46 ANR8430I Volume CLNI17 has been checked into library LIB /09/03 20:03:46 ANR1434W No files have been identified for automatically storing device configuration information. 04/09/03 20:03:46 ANR8431I CHECKIN LIBVOLUME process completed for library LIB3584; 1 volume(s) found. 04/09/03 20:03:46 ANR0985I Process 4 for CHECKIN LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 20:03:46. Performance hints for Tivoli Storage Manager and tape Refer to the detailed discussion in 7.3.1, Performance hints for Tivoli Storage Manager, LTO, and 3592 on page 288 for performance hints for Tivoli Storage Manager and tape. 7.3 Non-shared tape device with Tivoli Storage Manager for Linux In this section, we discuss the steps required to configure IBM tape libraries with Tivoli Storage Manager for Linux. Installing Tivoli Storage Manager Before you can begin using a tape device as a backup destination, you must do the following: 1. Install the IBMtape Device Drivers and IBMtapeutil. 2. Attach the devices to your system. 3. Configure the special device files for the tape library and drives. 4. Install the Tivoli Storage Manager Server software. 5. Initialize the server. 6. Define the library. 7. Define the library path. 8. Define the drives in the library. 9. Define the drive paths. 10.Define a device class using the library. 11.Label the tape library media. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 281

310 For steps 1 on page 281 through 3 on page 281, refer to Chapter 4, Basic IBM tape setup for Linux on page 183. Then, follow the instructions in IBM Tivoli Storage Manager for Linux Installation Guide V5.3, GC to install and initialize the Tivoli Storage Manager server (steps 4 on page 281 and 5). Installation of the Tivoli Storage Manager Device Driver (tsmscsi) is not mandatory because we are using the IBMtape Device Drivers. Before installing, you should check that you have the latest code fixes. See the following Web site for Tivoli product requirements, supported devices, and code levels: Note: Tivoli Storage Manager V4.1.2 supports Ultrium 1 drives in the IBM 3580, 3581, 3583, and Tivoli Storage Manager V5.1.6 supports Ultrium 2 drives. Tivoli Storage Manager V supports the IBM 3582 library. Tivoli Storage Manager V5.2 supports mixing Ultrium 1 and 2 in the same logical library. Tivoli Storage Manager V , V5.2.1, or V5.3 supports IBM 3592 drives. Tivoli Storage Manager V5.2.3 supports the IBM U library. Tivoli Storage Manager V5.2.4 or V5.3 supports Ultrium 3 drives, and mixing Ultrium 1, 2, and 3 in the same logical library. After installing and starting the server, we recommend using the administrative client command line interface (CLI) to configure the subsequent steps. The command line interface is the same across all present Tivoli Storage Manager versions, while the Web-based administrative command interface has changed completely between the Tivoli Storage Manager Versions 5.2 and 5.3. This is because of the introduction of the Administrative Console with V5.3. Refer to the Tivoli Storage Manager manuals and Redbooks for details about using the Administrative Console interface. To use CLI (dsmadmc), you must install the client code on the Tivoli Storage Manager server or an Tivoli Storage Manager client. Our examples use the CLI. We show how to set up the Tivoli Storage Manager server with the IBM tape library and drives only. For more general information about the setup of the Tivoli Storage Manager for Linux, see: IBM Tivoli Storage Manager for Linux Administrator's Guide V5.3, GC IBM Tivoli Storage Manager for Linux Installation Guide V5.3, GC IBM Tivoli Storage Manager for Linux Administrator's Reference Guide v5.3, GC We described how to install the IBMtape drivers in Chapter 4, Basic IBM tape setup for Linux on page 183. The following examples summarize the device installation and Tivoli Storage Manager server installation. Defining libraries and drives After installing Tivoli Storage Manager, we must configure the library and devices to Tivoli Storage Manager. To help make the task of determining which device special file to use for each of the devices you define in the Tivoli Storage Manager, you should have prepared a library device table similar to Table 7-1 on page 283. This is important because the operating system does not 282 Implementing IBM Tape in Linux and Windows

311 necessarily assign device special file names in the same order as the devices are physically installed in the library. Table 7-1 Library device table Device name Serial number/wwn Tape drive in the library SCSI element address IBMtape Drive IBMtape Drive IBMtape Drive IBMtape Drive IBMtape Drive IBMtape Drive First, define the library and library path using the following commands. When there are multiple choices, the default setting is listed las: DEFINE LIBRARY library_name LIBTYPE=SCSI AUTOLABEL=yes/no DEFINE PATH server_name library_name SRCTYPE=SERVER DESTTYPE=LIBRARY \ DEVICE=dev_name For library_name, enter a user-specified name of the library to be defined: DEFINE LIBRARY lib3584 LIBTYPE=SCSI For server_name, specify a name you have set for your server with the SET SERVERNAME command, which can be checked by issuing the QUERY STATUS command. In our case, we used the name saab. For dev_name, enter the full device name of library, such as /dev/ibmchanger0: DEFINE PATH saab lib3584 SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=/dev/IBMchanger0 Next, define each of the library s drives and drives paths with: DEFINE DRIVE library_name drive_name ELEMENT=element_number/AUTODETECT \ CLEANFREQUENCY=Gigabytes/ASNEEDED/NONE DEFINE PATH server_name drive_name SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=library_name \ DEVICE=dev_name For library_name, enter the name of your already defined library (lib3584, in our example). Use the operating system device name of the tape drive being defined for dev_name. Enter the full device name for dev_name, such as /dev/ibmtape0. The element_address is a number that indicates the physical location of a drive within an automated library. Tivoli Storage Manager needs the element address to connect the physical location of the drive to the drive s SCSI address. As of Version 5.2, you can specify autodetect for the element_number. This is the default, and the element number will then automatically be detected by Tivoli Storage Manager when the path to the drive is defined. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 283

312 Note: The CLEANFREQUENCY parameter in the DEFINE DRIVE command is optional. Tivoli Storage Manager-managed cleaning is intended for drives and libraries that do not have an automatic cleaning function. The IBM 3581, 3582, 3583, and 3584 have an automatic cleaning function, which means they take care of drive cleaning. Therefore, it is not necessary to specify the CLEANFREQUENCY parameter, because the default value is NONE. The IBM U does not have an automatic cleaning function; therefore, we recommend that you let Tivoli Storage Manager manage the cleaning of this device. If you want Tivoli Storage Manager to control drive cleaning, you should use the option ASNEEDED. You will have to change the auto cleaning function setting to the host cleaning function on the autoloader or library. Also, if you use a partitioned IBM 3584, then every logical partition needs its own cleaner cartridge. There is no need to clean LTO drives on a periodic basis (that is, after a set number of gigabytes has been processed by the drive), and additional manual cleanings are discouraged. We configured our drives in the IBM 3584 with the following commands: DEFINE DRIVE lib3584 drive1 DEFINE DRIVE lib3584 drive2 DEFINE PATH saab drive1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=lib3584 DEVICE=/dev/IBMtape0 DEFINE PATH saab drive2 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=lib3584 DEVICE=/dev/IBMtape1 Tip: Before defining the drives and libraries, make sure that your library is online and your drives are available. Also, there should not be any cartridges loaded in the drive being defined. Defining the device class To configure the device class, use the following commands. For LTO drives, use LTO as the DEVTYPE parameter: DEFINE DEVCLASS devclass_name LIBRARY=library_name DEVTYPE=LTO \ FORMAT=Ultrium/UltriumC/Ultrium2/Ultium2C/Ultrium3/Ultrium3C/Drive \ MOUNTLIMIT=mount_limit/DRIVES For IBM 3592 drives, use 3592 as the DEVTYPE parameter: DEFINE DEVCLASS devclass_name LIBRARY=library_name DEVTYPE=3592 \ FORMAT=3592/3592C/Drive MOUNTLIMIT=mount_limit/DRIVES The library_name will match the name of the library you previously defined. The FORMAT parameter has the following valid options for LTO: drive The server selects the highest format that can be supported by the drive on which a volume is mounted. This value will use the settings on the tape drive characteristics (device driver) for hardware compression. This is the default. 284 Implementing IBM Tape in Linux and Windows

313 ultrium This specifies that Tivoli Storage Manager writes data using the ULTRIUM recording format. This format results in a cartridge capacity of 100 GB when using Ultrium 100 GB data cartridge. This value overrides the settings on the tape drive characteristics for hardware compression. ultriumc This specifies that Tivoli Storage Manager writes data using the ULTRIUM recording format with compression. This format results in a cartridge capacity of approximately 200 GB when using a Ultrium 100GB data cartridge. This value overrides the settings on the tape drive characteristics for hardware compression. ultrium2 Specifies that Tivoli Storage Manager writes data using the ULTRIUM2 recording format. This format results in a cartridge capacity of 200 GB when using Ultrium2 200 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. ultrium2c Specifies that Tivoli Storage Manager writes data using the ULTRIUM2 recording format with compression. This format results in a cartridge capacity of approximately 400 GB when using Ultrium2 200 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. ultrium3 Specifies that Tivoli Storage Manager writes data using the ULTRIUM3 recording format. This format results in a cartridge capacity of 400 GB when using Ultrium3 400 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression.ultrium3c Specifies that Tivoli Storage Manager writes data using the ULTRIUM3 recording format with compression. This format results in a cartridge capacity of approximately 800 GB when using Ultrium3 400 GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression Specifies that Tivoli Storage Manager writes data using the 3592 recording format. This format results in a cartridge capacity of 300 GB when using GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. 3592c Specifies that Tivoli Storage Manager writes data using the 3592C recording format with compression. This format results in a cartridge capacity of approximately 900 GB when using GB data cartridges. This value overrides the settings on the tape drive characteristics for hardware compression. Compression in general improves backup performance. Therefore, we recommend that you use compression either specifically with FORMAT=ultriumc/ultrium2c/ultrium3c/3592c, or with FORMAT= drive, which implies that the server selects the highest format that is supported by the drive on which a volume is mounted. (Do not use FORMAT= drive for a library containing a mix of Ultrium 1, 2, or 3 drives. Use the specific definitions, as described in detail in 7.12, Device migration and coexistence on page 306) Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 285

314 If you use recording FORMAT=ultriumc/ultrium2c/ultrium3c/3592c/drive, then your LAN-free clients also use compression regardless of whether hardware compression is enabled. Note that Tivoli Storage Manager also provides optional client compression. If this is enabled, then clients compress their data before sending it to the storage device. This is particularly useful where the network connection between the client and server is slow and traffic needs to be minimized. With client compression on, using tape drive compression has little effect and is not recommended. You should evaluate your environment and requirements (probably by performing some appropriate testing) to determine if client compression is of benefit. If so, then enable it, and use the uncompressed (FORMAT=ultrium/ultrium2/ultrium3/3592) flag when defining the device class. If not, then tape drive compression should be used. The option MOUNTLIMIT specifies the maximum number of sequential access volumes that can simultaneously be mounted for the device class. This parameter is optional. The default is drives, which means that the maximum is set to the number of drives installed and available in the library. There are two reasons why you might use a specific value rather than the default: If you are going to share the library among multiple servers, you may want to specify a number instead of the default drives to limit the number of drives each server has access to. If you have a mixture of LTO generation drives in the same library, see 7.12, Device migration and coexistence on page 306 for more information. We recommend that the default value of drives not be used for the older Ultrium x device classes. For example, when specifying MOUNTLIMIT=drives, the Tivoli Storage Manager server will load Ultrium 1 cartridges into Ultrium 1 drives in preference to Ultrium 2 or 3 drives, but there exists the possibility that all Ultrium 2 or 3 drives could be loaded with Ultrium 1 cartridges and therefore, an Ultrium 2 or 3 cartridge could not be loaded. It may be necessary to set the MOUNTLIMIT parameter to a value that is equal to the number of that version of drives, or certainly to a value less than the total number of drives in the library. To define the IBM 3584 in our UNIX environment, we called the device class dev3584, pointing to our previously defined library lib3584. In the example, we have two 3592 drives in the library, so we specified 3592C for the FORMAT parameter and we set the MOUNTLIMIT to 2: DEFINE DEVCLASS dev3584 DEVTYPE=3592 LIBRARY=lib3584 FORMAT=3592C MOUNTLIMIT=2 Defining the storage pool using the command line Define the storage pool with the following command: DEFINE STGPOOL stgpool_name devclass_name MAXSCRATCH=number This storage pool will be assigned to the device class we just defined, so we specify the name dev3584. We used pool3584 as the stgpool_name: DEFINE STGPOOL pool3584 dev3584 MAXSCRATCH=200 Example 7-9 on page 287 shows you the storage pool that we defined. 286 Implementing IBM Tape in Linux and Windows

315 Example 7-9 q stgpool pool3584 f=d Storage Pool Name: POOL3584 Storage Pool Type: Primary Device Class Name: DEV3584 Estimated Capacity (MB): 0.0 Pct Util: 0.0 Pct Migr: 0.0 Pct Logical: High Mig Pct: 90 Low Mig Pct: 70 Migration Delay: 0 Migration Continue: Yes Migration Processes: Next Storage Pool: Reclaim Storage Pool: Maximum Size Threshold: No Limit Access: Read/Write Description: Overflow Location: Cache Migrated Files?: Collocate?: No Reclamation Threshold: 60 Maximum Scratch Volumes Allowed: 200 Delay Period for Volume Reuse: 0 Day(s) Migration in Progress?: No Amount Migrated (MB): 0.00 Elapsed Migration Time (seconds): 0 Reclamation in Progress?: No Volume Being Migrated/Reclaimed: Last Update by (administrator): ADMIN Last Update Date/Time: 10/06/03 18:01:50 Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No Last Update Date/Time: 04/08/03 20:50:18 Now you can use this storage pool in your management class copy groups, so that the device will be used for backups or archives. Preparing the cartridges We can now start the process of labelling and checking tapes into the library for use. We used the LABEL LIBVOLUME command (Example 7-10 on page 288) to label and check in the volumes into the library. Specifying search=yes will automatically try to label all the cartridges found in the logical library. For detailed information refer to Preparing the cartridges using the command line interface on page 278. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 287

316 Example 7-10 LABEL LIBVOLUME tsm: SAAB> LABEL LIBVOLUME lib3584 search=yes checkin=scratch labelsource=barcode tsm: SAAB> query process Process Process Description Status Number LABEL LIBVOLUME ANR8805I Labelling volumes in library LIB3584; 0 volumes(s) labelled.\ tsm: SAAB> query actlog search=volume ANR8810I Volume ABA920L1 has been labeled in library LIB3584. ANR8810I Volume ABA922L1 has been labeled in library LIB3584. tsm: SAAB> query libvolume Library Name Volume Name Status Owner Last Use Home Element LIB3584 ABA920L1 Scratch 1,248 LIB3584 ABA922L1 Scratch 1,249 Additional steps, such as creating domains, management classes, and copygroups are described in the Tivoli Storage Manager manuals. They are beyond the scope of this redbook Performance hints for Tivoli Storage Manager, LTO, and 3592 Since Tivoli Storage Manager writes a record in its database of each file backed up, it will perform better with large file workloads than with small file workloads. This is because of the proportion of time spent doing database writes and updates as a fraction of the total backup time. Therefore, to get the best performance from Tivoli Storage Manager with LTO and IBM 3592 drives, be sure to update the parameter TXNGroupmax on the server to a higher value than the default 256. This parameter controls how many files are transferred as a group between the client and server. Note that the larger the txngroupmax value, the bigger the Tivoli Storage Manager database log area needs to be. Tip: Tivoli Storage Manager V5.2 increased the maximum size for TXNGroupmax to 8192, and in V5.3 this is further increased to A value of 4096 or higher is recommended for environments that back up numerous small files, such as 10 KB files. With Tivoli Storage Manager V5.3, this parameter may also be defined for the individual clients. Thus, an intermediate value, say 2048, can be set for the server, and the high values should then be defined individually when registering the client. In the client option file, also set the parameter TXNBytelimit to its maximum of (2 GB). This parameter specifies the number of kilobytes the client program can buffer together in one transaction before it sends data to the server. To set TXNGroupmax, edit dsmserv.opt on the Tivoli Storage Manager server, as shown in Example 7-11 on page 289. If you are using the Storage Agent for LAN-free backup, you should also set this parameter to the same value in the options file dsmsta.opt. The restart of the server process is required to enable this change (for Storage Agent, a restart of the Storage Agent process is required). 288 Implementing IBM Tape in Linux and Windows

317 Example 7-11 TXNGroupmax entry in dsmserv.opt and dsmsta.opt *============================================================================== * * TXNGROUPMAX * * Specifies the maximum number of files transferred as a group between * the client and storage agent. * * Syntax * * TXNGroupmax value * * * Parameters * value Specifies the maximum number of files that are * transferred as a group between the client and * storage agent. The minimum value is 4 and the maximum * value is The default value is 256. * * Examples TXNGroupmax 4096 * Alternatively, the parameter may be set online by the command: SETOPT TXNGROUPMAX 4096 To set the client parameter TXNBytelimit, edit dsm.sys (for UNIX clients) or dsm.opt (for all other clients). The entry should be similar to Example Example 7-12 TXNBytelimit entry in dsm.opt/dsm.sys TXNByte In general, small file workloads will back up faster if they are staged initially to a disk storage pool, which then migrates to the tape pool. More suggestions on storage pool configuration are in IBM Tivoli Storage Manager Implementation Guide, SG We also recommend the use of compression on the tape drives, as previously discussed in this chapter. 7.4 LTO WORM (Write Once Read Many) The Ultrium 3 tape drive now has WORM functionality. Special LTO 3 WORM cartridges (identified as LT cartridges) are designed to provide non-alterable, non-rewritable tape media for long-term records retention. Tivoli Storage Manager supports IBM LTO WORM devices and media at V and V IBM LTO WORM devices are only available with Ultrium 3 devices and media. To use LTO WORM, an LTO WORM device class definition is required. This uses the WORM=YES parameter in the definition: DEFINE DEVCLASS <class name> LIBRARY=<library name> DEVTYPE=LTO WORM=YES Tivoli Storage Manager can only distinguish LTO WORM media from rewritable media only when the media is mounted in a drive. Therefore, all WORM media needs to either be checked in with CHECKLabel=Yes or labeled with the CHECKIN parameter specified. Any media that is checked in without mounting in the drive is considered rewritable by Tivoli Storage Manager. Note that this also means that you cannot make use of the AUTOLABEL Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 289

318 attribute of the library for WORM media. Once the media is checked in to Tivoli Storage Manager, Tivoli Storage Manager is aware that this is a WORM cartridge and will treat it accordingly. Note: This limitation is only for LTO in SCSI libraries, and does not apply to 3592 WORM in either SCSI or 3494 libraries. 7.5 Various IBM 3592 media types and Tivoli Storage Manager This section describes characteristics of the 3592 cartridges and drive functions, and how to use them with Tivoli Storage Manager. For detailed information about the hardware functions mentioned here, refer to the IBM 3592 product manuals. Although this is not an LTO tape drive, it can coexist with the LTO drives in the same IBM 3584 library, and thus it is discussed here. Capacity scaling and segmentation The IBM 3592 supports scaling and segmentation modes on the 300 GB R/W (JA) cartridge to allow a capacity trade off for improved access times. Tivoli Storage Manager can utilize these functions by specifying the SCALECAPACITY parameter with the define/update devclass command. A cartridge is initialized according to the SCALECAPACITY parameter when it is first mounted to the drive. It will stay in the SCALECAPACITY setting until it returns to the scratch state. Each of the SCALECAPACITY parameter settings (20/90/100) will initialize the cartridge, as shown in Figure Figure 7-23 How each of the SCALECAPACITY parameters initialize 3592 JA cartridges When SCALECAPACITY is set to 100 (default), Tivoli Storage Manager will initialize the cartridge as a 300 GB cartridge. When set to 90, it will initialize the cartridge as a segmented tape. When set to 20, it will initialize the cartridge to use only the first 60 GB. Depending on the client requirements, in most cases you should use either the SCALECAPACITY=100 for capacity oriented applications (for example, data backup) or SCALECAPACITY=20 for access oriented applications, such as HSM. 290 Implementing IBM Tape in Linux and Windows

319 There is no practical reason for using SCALECAPACITY=90, because you cannot control where the data is written on the tape. After the first 60 GB segment is filled, the drive will proceed to write on the rest of the (slower-access) tape. Each of the segmented parts need to be defined to a different storage pool to fully utilize the segmented function, but with the current Tivoli Storage Manager architecture, it is not possible to define two storage pools for one volume. Write Once Read Many (WORM) The IBM 3592 WORM data cartridges are designed to provide non-alterable, non-rewritable tape media for long-term records retention. The drive will automatically determine if the mounted volume is a WORM or R/W cartridge. To use this function, specify WORM=yes parameter in the command DEFINE/UPDATE DEVCLASS. Tivoli Storage Manager V5.2.3 or later is required. Because Tivoli Storage Manager can distinguish between WORM and R/W cartridges (assigns media type of 412 for WORM cartridges and 411 for R/W cartridges at the time of check-in), you can have both WORM and R/W cartridges in a single logical library just by defining the device classes, one with WORM=yes and the other with WORM=no. Note: For the IBM TotalStorage 3494 Tape Library, you would also need to specify WORMSCRATCHCATEGORY with the DEFINE/UPDATE LIBRARY command. Short-length (economy) cartridges Both R/W and WORM cartridges are available with the standard-length (300 GB) and the short-length (60 GB) format. The following cartridge formats are available for the 3592: JA (ETC) 609 m 300 GB Standard R/W Tape JJ (EETC) 246 m 60 GB Short R/W Tape JW (EWTC) 609 m 300 GB Standard WORM Tape JR (EEWTC) 246 m 60 GB Short WORM Tape For a JA cartridge, define the device class as below; you have the option to specify the SCALECAPACITY parameter: DEFINE DEVCLASS devclass_name DEVTYPE=3592 FORMAT=3592/3592c/drive \ LIBRARY=library_name SCALECAPACITY=20/90/100 For JJ cartridges, define the device class as below: DEFINE DEVCLASS devclass_name DEVTYPE=3592 FORMAT=3592/3592c/drive \ LIBRARY=library_name For JW and JR cartridges, define the device class as below: DEFINE DEVCLASS devclass_name DEVTYPE=3592 FORMAT=3592/3592c/drive \ LIBRARY=library_name WORM=yes The SCALECAPACITY parameter with a value other than 100 (default) can be specified only with the standard-length R/W cartridge. When the short-length cartridges are initially defined to a storage pool, query volume and query stgpool will show you 300 GB (or 900 GB for compress) for each of the volumes defined. When the EOV (end-of-volume) is reached, query commands will show the actual data written for the volume. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 291

320 Set up fast access storage pool with 3592 and Tivoli Storage Manager To configure a fast access storage pool with 3592 drives, you have two options: 1. Define a device class with SCALECAPACITY=20 and use standard-length R/W cartridges. 2. Use short-length (economy) cartridges. To set up both the fast access storage pool and the non-fast access (optimized for capacity) storage pool in a single logical library: If using method 1 (above) to configure fast access storage pool: Define a separate device class for each storage pool, one with SCALECAPACITY=100 and one with SCALECAPACITY=20. The scratch JA tapes will automatically be initialized to the storage pool it is called for. If using method 2 (above) to configure fast access storage pool: Since Tivoli Storage Manager does not distinguish between the short-length and the standard-length cartridges, you would need to define each of the cartridges explicitly to the storage pool. It may be a better idea to just logically partition the library into a short-length-cartridge-only-partition (fast access partition) and a standard-length-cartridge-only-partition (capacity partition). 7.6 Sharing LTO libraries with Tivoli Storage Manager The concepts of library sharing have been discussed in Chapter 2, IBM LTO Tape Library sharing and partitioning on page 37. In this section, we will briefly discuss configuration parameters to consider; for further in-depth discussion of Tivoli Storage Manager and library sharing and the use of SAN, refer to the redbook Get More Out of Your SAN with IBM Tivoli Storage Manager, SG Several Tivoli Storage Manager servers can share the same tape library using the library sharing feature, as shown in Figure 7-2 on page 258. Tape library sharing is supported between any combination of Windows, AIX, Solaris, Linux, and HP-UX Tivoli Storage Manager servers. We recommend using the latest code level. You can find the link to download the latest code fixes at: All servers that will share the library need to have a FC/SAN connection to the tape drives in the library. One server will control the library robotics and is designated the Library Manager. Other library users are designated Library Clients. Services are requested from the Library Manager, rather than the library itself, as in non-shared library configurations. For example, if a library client wants to write data to a tape, then the client has to ask the Library Manager to mount the tape volume. After the tape is mounted by the Library Manager, then the library client can write the data directly over the physical SAN path to the tape drive Configuring the Library Manager to share libraries Install and configure your tape library and drives on the Library Manager, as described in 7.2, Non-shared tape device with Tivoli Storage Manager for Windows on page 260. Register the license for library sharing, and define the library with the shared=yes parameter, such as: REGISTER LICENSE FILE=libshare.lic NUMBER=1 DEFINE LIBRARY lto_3584 LIBTYPE=SCSI SHARED=YES Define drives and path information as for the non-shared environment. 292 Implementing IBM Tape in Linux and Windows

321 Because library sharing uses server-to-server communication for sending and receiving requests, you need to configure server-to-server communications between the Library Manager and the library clients. Set the following parameters on the Library Manager (servername, password, serverhladdress, serverlladdress, and set crossdefine) to on: SET SERVERNAME server_name SET SERVERPASSWORD server_password SET CROSSDEFINE on SET SERVERHLADDRESS server_ip_address SET SERVERLLADDRESS server_ip_portaddress Configuring the library client The library client is similarly set up for crossdefine.set the parameters servername, password, serverhladdress, serverlladdress, and set crossdefine to on: SET SERVERNAME server_name SET SERVERPASSWORD server_password SET CROSSDEFINE on SET SERVERHLADDRESS server_ip_address SET SERVERLLADDRESS server_ip_portaddress Next, we define the Library Manager server on each of the library clients, so that they will know which system is managing the tape libraries. Use the DEFINE SERVER command and match the parameters to the server definitions on the Library Manager (server name, password, IP address, and port number): DEFINE SERVER library_manager_servername SERVERPASSWORD=library_ manager_password HLADDRESS=library_manager_ip_address LLADDRESS=library_manager_port_number COMM=tcpip As we have set crossdefine to on, the above commands should automatically create library client definitions on the Library Manager. Check this with the QUERY SERVER command Define library and drives for library client See Chapter 3, Basic IBM tape setup for Windows on page 79, Chapter 4, Basic IBM tape setup for Linux on page 183, and Appendix 5, SAN considerations on page 223 for basic tape drive installation on the library clients. You will need to define the library definition at each library clients. The drive paths must be defined for each library client drive, but this definition is done at the Library Manager: DEFINE LIBRARY library_name LIBTYPE=shared PRIMARYLIBMANAGER=lib_manager_name Note the use of the LIBTYPE=shared parameter. You must use the same library_name as was defined on the library server. On the Library Manager, define each of the tape drive paths for each library client as: DEFINE PATH server_name drive_name SRCTYPE=SERVER DESTTYPE=DRIVE \ LIBRARY=library_name DEVICE=device_name For server_name, enter the name of the library client, and for device_name, specify the name of the device special file on the library client machine. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 293

322 Important: Keep in mind that the drives are not necessarily configured by the operating system in the same order as they are installed physically in the library, as described in 5.3, Persistent binding on page 237. Therefore, check carefully that the element address matches your drive configuration. You can check the result with the Q PATH command. Now you can define the device class and the storage pool using the library definitions, as described in 7.2.7, Defining the storage pool using the command line on page Administering shared libraries When using a shared LTO library, it is important to remember that the library clients cannot directly access the library robotics (medium changer) themselves. Any requests for tape movement must be requested through the Library Manager. While library clients do not directly access the library robotics, once a volume is mounted in a drive, the library clients can read or write data directly to the drive through the SAN data path. This means that certain commands give different output, or are not applicable in some circumstances. QUERY LIBVOLUME If you use the QUERY LIBVOLUME on the Library Manager, the output will now also display which Tivoli Storage Manager server is the owner of each volume, as shown in Example Example 7-13 Q LIBVOL on a Library Manager Library Name Volume Name Status Owner Last Use Home Element LTO_3584 ABA920 Private SICILY Data 4,114 LTO_3584 ABA922 Private SICILY Data 4,104 LTO_3584 ABA923 Scratch 4,106 LTO_3584 ABA924 Scratch 4,107 LTO_3584 ABA925 Private SICILY 4,130 LTO_3584 ABA926 Private SICILY 4,098 LTO_3584 ABA927 Private BRAZIL Data 4,102 LTO_3584 ABA928 Private BRAZIL Data 4,111 LTO_3584 ABA929 Private BRAZIL Data 4,112 LTO_3584 ABA990 Private BRAZIL Data 4,133 The library client is only using the drives, and has no knowledge of the library contents. Example 7-14 shows executing QUERY LIBVOLUME on a library client. Example 7-14 Q LIBVOL on a library client tsm: BRAZIL> QUERY LIBVOLUME ANR2017I Administrator ADMIN issued command: QUERY LIBV ANR2034E QUERY LIBVOLUME: No match found using this criteria. QUERY VOLUME Querying the volumes (QUERY VOLUME) on any attached server will report only those volumes that belong to that server (see Example 7-15 on page 295). 294 Implementing IBM Tape in Linux and Windows

323 Example 7-15 QUERY VOLUME on a shared library tsm: SICILY>q volume Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status (MB) ABA LTO_ST- 3580_DEVC- 95, Filling GPOOL LASS ABA LTO_ST- 3580_DEVC- 190, Filling GPOOL LASS AUDIT LIBRARY Performing an AUDIT LIBRARY command from a library client does not actually perform a physical audit on the shared library; instead, the library client s database is checked and synchronized against the Library Manager s database. No tape mounts are performed. Performing this command on the Library Manager mounts or inspects tapes in the library, the same as it does in non-shared configurations. CHECKIN and CHECKOUT LIBV Checking in or out of a volume from a shared library must be done from the Library Manager. If you try to execute the CHECKOUT LIBVOLUME command from a library client, the operation will fail with an error. LABEL LIBVOLUME When the IBM tape library is shared, tape labeling must be performed on the Library Manager. If you try to execute the LABEL LIBVOLUME command from a library client, the operation will fail with an error. You can share the scratch volumes between all the library clients. This is because the Library Manager serves as a central repository for information about all the volumes contained in the library. Since all media handling requests are handled by the Library Manager, it can keep track of which tape belongs to which library client, and which tapes are unallocated and available for use by any library client. There is no special configuration required to utilize this feature; simply make sure there is an adequate supply of labeled scratch tapes in the library. The Library Manager will allocate them as needed to the requesting library clients or to itself. Once a particular volume is assigned to a library client, the Library Manager flags that volume as used by that client, and prevents other clients from accessing it. Note: The Library Manager is itself a fully functional Tivoli Storage Manager server, that is, it typically supports its own backup client workload and can access and use the volumes just like a library client. However, it also has the particular function of overall management of the devices and tape inventory. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 295

324 7.7 LAN-free backup with Tivoli Storage Manager We will briefly discuss configuration parameters to consider for LAN-free backup. For in-depth discussion of this topic, see the redbook Get More Out of Your SAN with IBM Tivoli Storage Manager, SG LAN-free client data transfer is based on library sharing, as already discussed in 7.6, Sharing LTO libraries with Tivoli Storage Manager on page 292. Clients that will send their data using the LAN-free path need SAN access to the storage devices, for example, the LTO library. The Tivoli Storage Manager server also requires tape library access via the SAN. LAN-free backup is performed by separating the actual application data (the client data written to or read from the storage pools) from the meta or control data (information contained in the Tivoli Storage Manager database). The metadata is transmitted over the LAN from the Tivoli Storage Manager client to the Tivoli Storage Manager server while the application data is moved directly over the SAN from the Tivoli Storage Manager client to the storage device. Figure 7-3 on page 260 describes this process. A core component of LAN-free technology is the Storage Agent, which is a piece of code installed on each LAN-free client. Essentially, the Storage Agent can be viewed as a lightweight Tivoli Storage Manager server that has no database or storage hierarchy of its own. It behaves like a library client, which contacts the Tivoli Storage Manager server for volume access, and reads/writes data directly to SAN-attached devices LAN-free configuration setup Install and configure the LAN-free clients according to the detailed instructions in the Storage Agent s User Guides, for example, IBM Tivoli Storage Manager for SAN for AIX Storage Agent User's Guide V5.3, GC Before beginning, set up your Tivoli Storage Manager server as a Library Manager, as described in 7.6.1, Configuring the Library Manager to share libraries on page 292. Table 7-2 on page 297 is a summary of the tasks necessary to configure LAN-free backup-archive client data transfer. The detailed instructions are contained in the user s guides. 296 Implementing IBM Tape in Linux and Windows

325 Table 7-2 Configuring LAN-free backups Step On server On client 1)... Install tape drives according to above. 2)... Install Tivoli Storage Manager client code. 3)... Modify dsm.sys of backup-archive client with: ENABLELANFREE YES LANFREECommethod TCPIP LANFREETCPPort port_number 4)... Install the Storage Agent. 5)... Specify the DEVCONFIG option in the dsmsta.opt of Storage Agent: DEVCONFIG outputfile 6) Define each LAN-free client Storage Agent as though it was a server. Use the DEFINE SERVER command.... 7)... Set the installation data for the Storage Agent with: DSMSTA SETSTORAGESERVER 8) Register clients for LAN-free backup. If needed; define a separate domain. Also, register the license for LAN-free nodes.... 9)... Obtain Tape Device information (see Define path considerations). 10) Use the DEFINE PATH command to define paths from the Storage Agent to the drives that are available to the Tivoli Storage Manager server (see 7.7.2, Define path considerations on page 297) )... Test to see if the data transfer goes over the SAN. Note: Make sure TXNGROUPMAX in dsmsta.opt is set at the same value as that in dsmserv.opt. When using LTO or 3592 drives, it is recommended to set this value to 256 or higher for performance reason (see 7.3.1, Performance hints for Tivoli Storage Manager, LTO, and 3592 on page 288) Define path considerations Consider the following guidelines for mapping your SAN drives: Define paths to all drives. Problems can occur if you do not define paths from the server to each drive in a library. For example, during backup operations, all drives that have paths that can be used by the Storage Agent are backing up data. Backup operations will fail if you try to use other drives in a library that do not have defined paths. When paths are defined for each drive in a library, backup operations wait until the next drive is available for the transfer of data. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 297

326 If you want to limit the number of drives available to a node, you can use the MAXNUMMP parameter on the REGISTER NODE or UPDATE NODE command. This will limit the number of drives that are available for the Storage Agent to use on behalf of the client. Review tape device names. For the same tape device, the device name known to the server will probably not match the device name known to the Storage Agent, as described in 5.3, Persistent binding on page 237. Define paths on the server using the device names seen on the Storage Agent machine. Use the DEFINE PATH command: DEFINE PATH storageagent_name drive_name SRCTYPE=SERVER DESTTYPE=DRIVE \ LIBRARY=library_name DEVICE=dev_name_on_storageagent Where: storageagent_name is the name of the Storage Agent. drive_name is the tape drive name defined on the Tivoli Storage Manager server. library_name is the tape library name defined on the server. dev_name_on_storageagent is the device special file name of the tape drive on the Storage Agent machine (for example mt ). Important: Keep in mind that the drives are not necessarily configured by the operating system in the same order as they are installed physically in the library, as described in 5.3, Persistent binding on page 237. Therefore, check carefully that the element address matches your drive configuration. 7.8 NDMP backup with Tivoli Storage Manager Network Data Management Protocol (NDMP) is an open standard protocol developed to eliminate the issues centered around the decentralization of backup standards for file servers, and dedicated Network Attached Storage (NAS) file servers. NDMP backup is provided with IBM Tivoli Storage Manager Enterprise Edition. This is well documented in the Administration Guide for your Tivoli Storage Manager platform; for example, for a Windows server, refer to: IBM Tivoli Storage Manager for Windows Adminstrator's Guide V5.3, GC Also see the redbook: IBM Tivoli Storage Manager Implementation Guide, SG Network Attached Storage NAS stands for Network Attached Storage and is a way to make large amounts of disk storage available to many clients using standard file sharing protocols. An NAS box (sometimes also called an NAS appliance or file server) consists of a number of standard disks, one or more network adapters (NICs), and a controller that typically runs an embedded, specialized operating system, used to configure and administer the box. The NAS appliance exists as an entity in the network. The disks are divided up into volumes, which can then be accessed by other servers or workstations, using standard file-sharing protocols like NFS and CIFS. Network Attached Storage is, therefore, easy and relatively cheap to implement, since standard file sharing methods and normal network adapters are used to access the data. 298 Implementing IBM Tape in Linux and Windows

327 But the question arises, how do you back up the data in the NAS box? One way is to back up the mounted file systems from a client that is accessing it. However, this involves multiple network accesses and may or may not back up metadata, like access control lists, correctly. Or, you could write/modify a backup client to run directly on the NAS appliance itself. The issue here is that vendors use different operating systems (often specialized) for their appliances, which means multiple ports of the backup client would be necessary. A standard is really needed to make NAS backup easier. The need for NDMP NDMP is a standard protocol for backup applications to use to back up NAS servers. NDMP provides a high-performance backup solution by separating meta-data (control path) transfer over the LAN from raw backup data (data path), which can be transferred locally to a storage device. NDMP also solves the problem of interoperability of various NAS servers and backup software. NDMP backup with Tivoli Storage Manager is available for the following servers: A Tivoli Storage Manager V5.2 or later server for Windows, AIX, Sun Solaris, HP-UX, or Linux. For the most up to date support details, see: ml Overview of Tivoli Storage Manager NDMP backup Tivoli Storage Manager Enterprise Edition provides backup of supported NAS file servers. Tivoli Storage Manager controls the backup operation remotely, but the NAS file server transfers the backup data locally. Typically, this in a direct SCSI attached configuration between the NAS file server and a tape library. It is possible to configure NDMP operations with Tivoli Storage Manager using a SAN attached configuration. However, the library robotics must be logically but explicitly controlled by the Tivoli Storage Manager server, and the tape drives must be logically, but explicitly, controlled by the NAS file server. Tivoli Storage Manager Enterprise Edition NDMP support backs up and restores complete NAS file systems without having to use file access protocols like Common Internet File System (CIFS) and Network File System (NFS). The first backup performed is a full backup with every backup thereafter being a differential backup by default (a differential backup will back up all file system changes since the last full backup). When a restore is initiated, Tivoli Storage Manager will restore the full backup first, followed by the differential backup. Attention: A Tivoli Storage Manager V5.3 server is required for directory-level backup. See the latest Tivoli Storage Manager manuals, or the Redbook IBM Tivoli Storage Manager Implementation Guide, SG , for details Tivoli Storage Manager NDMP backup configurations The fundamental physical requirement for Tivoli Storage Manager NDMP backup is to have the tape devices connected to the NAS system. The library robotics may be controlled by either the NAS system or the Tivoli Storage Manager server. If the tape library does not have separate interfaces for the medium changer and tape devices, or if there is a large distance separating the Tivoli Storage Manager server and the NAS system, then the library must be directly connected to the NAS system. Below are the supported configurations. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 299

328 Library connected to NAS system In this configuration, the tape library and drives are directly connected to the NAS file server, as shown in Figure The Tivoli Storage Manager server sends commands to the library across the LAN to the NAS file server, which passes the commands onto the tape library. Any generated responses are sent back to the Tivoli Storage Manager server via the NAS file server. In this configuration, the NAS file server may be separated from the Tivoli Storage Manager server by a large distance, as TCP/IP connectivity is all that is required. Figure 7-24 Library connected to NAS system Library connected to Tivoli Storage Manager server In this configuration, the tape library is directly connected to the Tivoli Storage Manager server and the tape drives within the library are directly connected to the NAS file server, as shown in Figure The Tivoli Storage Manager server passes commands directly to the tape library, and the NAS file server pushes data directly to the tape devices at the request of the Tivoli Storage Manager server. This configuration is only possible within the physical connectivity limitations of SCSI or Fibre Channel. Figure 7-25 Library on Tivoli Storage Manager server: drives on NAS system 300 Implementing IBM Tape in Linux and Windows

329 Expiration and retention policies for NDMP backup When an NDMP backup is performed, the Tivoli Storage Manager server checks if a valid full image backup exists. If it does not, a full image backup is performed. The Tivoli Storage Manager server will also identify any older backup versions that exceed the allowed number of versions according to the management class policies. This is done from oldest to most recent without regard to whether the versions represent full or differential images. Any excess versions are marked for expiration. During expiration processing, if the server detects a full backup that is marked for expiration, it checks to see if that version has any dependent differentials. If so, the full backup version is not deleted even though it has been marked for expiration. An example should make this process clearer. Let us say we set VEREXISTS in the backup copy group to 3 and that we run a series of backups as follows: Day 1: Full backup Day 2: Differential backup Day 3: Full backup Day 4: Differential backup Day 5: Differential backup Each backup operation creates a version in the Tivoli Storage Manager database. After day 4 s differential backup, therefore, we have a total of four versions, but the policy settings allow us only three. Therefore, the day 1 backup, being the oldest, will be marked for expiration. However, the first backup cannot be physically expired because the day 2 differential backups depends on it. This is because in order to restore the day 2 backup, we would have to restore the day 1 full and then the day 2 differential. A full backup will never be expired as long as it has dependent differentials. However, after day 4 it is no longer possible to restore just the day 1 backup. In this case, day 4 represents the ACTIVE backup, with day 2 and day 3 being INACTIVE backup versions. On day 5 when another differential backup is made, both the day 1 and day 2 backups will be marked for expiration. At this stage, as shown in Figure 7-26 on page 302, the day 5 backup represents the ACTIVE backup, day 3 and day 4 backups are INACTIVE and the day 1 and day 2 backups are deleted. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 301

330 Versioning example: VEREX IST S=3 Day 1: full backup Expired Day 2: Day 3: differential full backup Expired Inactive Day 4: differential Inactive Day 5: differential Active Figure 7-26 How version control works for NDMP backups 7.9 Tivoli Storage Manager and redundant library control paths The IBM 3582, 3583, and 3584 allow you to enable multiple control paths to a single logical library. Support is provided under AIX, Linux, HP-UX, Windows, and Solaris for both SCSI and Fibre Channel attachments when the IBM tape device driver is used. This provides improved redundancy to the libraries. If there is only a single control path available, a failure in this path would result in loss of communication with the library. Therefore, multiple control paths eliminate this single point of failure. See also 3.4, Control Path Failover on page 103 and 4.4.4, Setting up control path failover on Linux on page 211 for further details in particular environments. Tivoli Storage Manager cannot automatically handle multiple control paths to one logical library on its own; however, it can work with automatic control path failover for the operating system. This feature provides an automatic failover to an alternate control path when the primary control path fails. An error on the control path would have no effect on your Tivoli Storage Manager server. Figure 7-27 on page 303 shows an IBM 3584 with two drives. Both drives have the control path enabled. 302 Implementing IBM Tape in Linux and Windows

331 Server FC Adapter FC Adapter SAN Switch 3584 Control path enabled Drive Drive Control path enabled Medium Changer Figure 7-27 IBM 3584 with multiple control paths enabled If you enable multiple control paths on your IBM 3582, 3583, or 3584, you will see several SCSI media changer devices with primary and alternate paths. For example, with Linux, as in this example, you can check if the IBMtape driver has recognized multiple control paths for your library by reading the /proc/scsi/ibmchanger file. If your library lists Primary or Alternate under the FO Path, as in Example 7-16, then you have successfully enabled the control path failover feature for your library. If NA is listed under the FO Path, then the control path failover is not enabled. When IBMtape is loaded into kernel memory, the first logical medium changer device that IBMtape sees in the system will be the primary path for that medium changer. The other logical medium changers that IBMtape attached for the same medium changer will be configured as alternate paths. The device driver supports up to 16 physical paths for a single device. Example 7-16 An example of /proc/scsi/ibmchanger file [root@saab root]# cat /proc/scsi/ibmchanger IBMtape version: IBMtape major number: 253 Attached Changer Devices: Number Model SN HBA FO Path 0 ULT3583-TL IBM QLogic Fibre Channel 2200 Primary 1 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate 2 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate Whether you use automatic control path failover or not, you should only configure one control path to the library in Tivoli Storage Manager. If you configure the second control path, then you will get a second library. If a failure occurs on the first control path (IBMchanger0), and we do not use automatic control path failover, we could switch to the second path (IBMchanger1) with: UPDATE PATH server_name library_name SRCTYPE=SERVER DESTTYPE=LIBRARY DEVICE=/dev/IBMchanger1 With automatic control path failover enabled, we would not need to perform the UPDATE PATH command, since failover happens automatically. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 303

332 7.10 Tivoli Storage Manager and data path failover The concept of control and data path failover is further discussed in the redbook Get More Out of Your SAN with IBM Tivoli Storage Manager, SG The IBM tape device driver for AIX, Linux, and Solaris allows you to configure and automatically failover between multiple data paths (single SAN fabric) to a single FC LTO, or two SAN fabrics to an IBM 3592 drive. See 4.4.5, Setting up data path failover on Linux on page 214 for details in the Linux environment. Note that the LTO drives have only one interface to the fabric, while IBM 3592 has two. Without the drivers alternate pathing support in the Linux environment, if an application opens IBMtape0 and a permanent path error occurs (because of an HBA or cable failure, for example), the application fails. It is possible to initiate manual failover by restarting the application on the alternate logical device (IBMtape1), but the application has to be restarted from the beginning. A long backup or restore operation may have been in progress when the path error occurred. Sometimes manual failover may require operator intervention to reset the drive because a SCSI Reservation can still exist on the failing HBA path. When the alternate pathing support is enabled on both IBMtape0 and IBMtape1, the device driver configures them internally as a single device with multiple paths. The application can still open and use only one logical device at a time (either IBMtape0 or IBMtape1). If an application opens IBMtape0 and a permanent path error occurs, the device driver initiates failover error recovery automatically on the alternate path (IBMtape1). If successful, the current operation continues on the alternate path without interrupting the application. The failover error recovery first restores the previous device state, SCSI Reservation, and tape position, then retries the failing operation. Figure 7-28 shows an IBM 3584 with 3592 drives. Server FC Adapter A 3584 SAN Switch 3592 Drive FC Adapter B Medium Changer Figure drive with multiple data paths configured You can check if the IBMtape driver has recognized multiple data paths for your library by reading the /proc/scsi/ibmtape file. If your library lists Primary or Alternate under the FO Path, as shown in Example 7-17 on page 305, then you have successfully enabled the data path failover feature for your library. If NA is listed under the FO Path, then the data path failover is not enabled. 304 Implementing IBM Tape in Linux and Windows

333 Example 7-17 An example of the /proc/scsi/ibmtape file IBMtape version: IBMtape major number: 253 Attached Tape Devices: Number Model SN HBA FO Path 0 ULT3583-TL IBM QLogic Fibre Channel 2200 Primary 1 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate 2 ULT3583-TL IBM QLogic Fibre Channel 2300 Alternate Whether you use automatic data path failover or not, you should only configure one data path to each of the drives defined to the Tivoli Storage Manager server. Defining a path to IBMtape0, if a failure occurs on this path, the IBM device driver will automatically and transparently to the application (for example, Tivoli Storage Manager) failover to the alternate path (/dev/ibmtape1) without interrupting the current Tivoli Storage Manager operation Tape alert support Tape alert messages are generated by tape and library devices to report hardware errors. A log page is created and can be retrieved at any given time or at a specific time, such as when a drive is dismounted. These messages help determine problems that are not related to the Tivoli Storage Manager server. There are three severity levels of tape alert messages: Informational For example, you may have tried to load a cartridge type that is not supported. These messages will log in as ANR8951I messages. Warning For example, a hardware failure is predicted. These messages will log in as ANR8950W messages. Critical For example, there is a problem with the tape and your data is at risk. These messages will log in as ANR8948S or ANR8949E messages. Tape alert messages are turned off by default. You may set tape alert messages to ON or OFF by using the SET TAPEALERTMSG command. The current setting of the tape alert can be checked with the QUERY TAPEALERTMSG command. The messages from the device are logged into the actlog, which can be checked with the QUERY ACTLOG command. Example 7-18 and Example 7-19 on page 306 are examples of the QUERY TAPEALERTMSG and QUERY ACTLOG commands in UNIX environments. Example 7-18 QUERY TAPEALERTMSG command output tsm: SERVER1>query tapealertmsg ANR8960I QUERY TAPEALERTMSG: The display of Tape Alerts from SCSI devices is Enabled. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 305

334 Example 7-19 QUERY ACTLOG command output tsm: SERVER1>query actlog begindate=-15 search=tapealert Date/Time Message /24/04 18:23:09 ANR8948S Device /dev/rmt/11smc, volume unknown has issued the following Critical TapeAlert: The library mechanism is having difficulty communicating with the drive: 1. Turn the library off then on. 2. Restart the operation. 3. If the problem persists, call the library supplier help line. (SESSION: 9) 03/24/04 18:23:09 ANR8950W Device /dev/rmt/11smc, volume unknown has issued the following Warning TapeAlert: There is a problem with the library mechanism. If problem persists, call the library supplier help line. (SESSION: 9) 03/24/04 18:23:09 ANR8950W Device /dev/rmt/11smc, volume unknown has issued the following Warning TapeAlert: There is a potential problem with the barcode label or the scanner hardware in the library mechanism. 1. No action needs to be taken at this time. 2. If the problem persists, call the library supplier help line. (SESSION: 9) 7.12 Device migration and coexistence Careful planning is recommended when introducing and mixing new generations of media technology with Tivoli Storage Manager. This is because new format generations cannot be read by older drives, and conversely the old formats cannot necessarily be read and written by the new drives. Tivoli Storage Manager controls the media through the library changer by using SCSI commands, and cannot detect the internal format of a cartridge. Tivoli Storage Manager has always taken the position that all media must be at least readable by all the drives in a given library. With Tivoli Storage Manager V5.2 and higher, you can operate with mixed media types when the library is able to distinguish the different media. This section provides information about migration and coexistence issues for LTO Ultrium 1, 2, and 3 drives in one library, and with Tivoli Storage Manager V5.1 and V5.2 or newer. First, we will define a few terms. Mixed media libraries Mixed media in a Tivoli Storage Manager server describes devices using different device types (in the devclass) in the same logical library. LTO and 3592 are examples of two devices that need different device classes, but can coexist in the same library. Mixed media is supported in Tivoli Storage Manager V5.2 and higher. Mixed generation devices A mixed generation device in a Tivoli Storage Manager server describes devices that use the same device types (from DEFINE DEVCLASS) despite capacity differences. In order to have mixed generation devices in the same device class, the media types must be distinguishable. Note: In mixed generation environments, the current generation device can generally read and write current and previous generation media. The previous generation device can only read and write previous generation media. LTO Ultrium devices are an example of mixed generation devices. 306 Implementing IBM Tape in Linux and Windows

335 The design specifications for Ultrium devices are: Ultrium 1 Can read and write Ultrium 1 cartridges Ultrium 2 Can read and write Ultrium 1 and Ultrium 2 cartridges Ultrium 3 Can read and write Ultrium 2 and 3 cartridges, and can read Ultrium 1 cartridges Note: Tivoli Storage Manager V or higher provides support for the Ultrium 3 drives, while support for Ultrium 2 is available as of V Scenarios In the lifetime of a Tivoli Storage Manager server, there will be times when new technology or client requirements will allow the expansion of storage capacity through new devices. This might occur through the addition of a new library to an existing Tivoli Storage Manager server, or through increased capacity of a new or upgraded tape drive in an existing library. In both these instances, you need to decide whether to install the new technology and retire the old technology, or operate both technologies in parallel. For Ultrium 1, Ultrium 2, and Ultrium 3 drives, Table 7-3 on page 308 describes some of the migration and coexistence possibilities in one physical library, and also the migration from an existing library to a new LTO library, relative to the version of Tivoli Storage Manager used. You may need to upgrade the library firmware for Ultrium 2 or Ultrium 3 device support and library partitioning support. We will discuss each scenario in more detail. The table and subsequent discussion will not attempt to show all migration possibilities, but will cover the most obvious scenarios. For several of the configuration scenarios, there are two identical discussions. In general, whatever applies to the coexistence and migration of Ultrium 2 and 3 is also valid for the coexistence and migration of the older Ultrium 1 and 2. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 307

336 Table 7-3 LTO migration and coexistence examples Scenario Configuration TSM V TSM V5.2 TSM or a) Ultrium drives Ultrium 2 Media b) Ultrium drives Ultrium 1 Media One logical library One devclass One logical library One devclass One logical library One devclass 2 a)ultrium drives Ultrium Media b)ultrium drives, Ultrium Media Two logical libraries Two devclass One logical library Two devclass One logical library Two devclass 3 Ultrium drives Ultrium Media One logical library Three devclass 4 a)migrate Ultrium 2 to 3 drives Ultrium Media b)migrate Ultrium 1 to 2 drives Ultrium Media One logical library One devclass One logical library One devclass One logical library One devclass 5 a)migrate Ultrium 2 to 3 drives Migrate media Ultrium 2 to b)migrate Ultrium 1 to 2 drives Migrate Media Ultrium 1 to One logical library One devclass One logical library One devclass One logical library One devclass 6 Migrate Ultrium 1 to 3 drives Migrate media Ultrium 1 to 3 One logical library One devclass 7 Migrate existing tape storage to LTO Ultrium Two libraries Two devclass Two libraries Two devclass Two libraries Two devclass Scenario 1 There are two similar scenarios: Install Ultrium 3 drives in addition to the current Ultrium 2 drives and media, or the equivalent scenario for the older generation, that is, install Ultrium 2 drives in addition to the current Ultrium 1 drives and media. We can install the new Ultrium 3 devices with existing Ultrium 2 devices into the same logical library and device class because of mixed generation support. The Ultrium 3 devices will be able to read and write the Ultrium 2 cartridges at the Ultrium 2 speed and capacity. Similarly, we can install the Ultrium 2 devices with existing Ultrium 1 devices into the same logical library and device class because of mixed generation support. The Ultrium 2 devices will be able to read and write the Ultrium 1 cartridges at the Ultrium 1 speed and capacity. Scenario 2 Install Ultrium 3 drives and Ultrium 3 media in addition to existing Ultrium 2 drives and Ultrium 2 media. As of Tivoli Storage Manager V5.2, mixed media types are supported in one library, and thus different generations of tape devices can coexist in the same logical library. However, two device classes are required because of the two media types. 308 Implementing IBM Tape in Linux and Windows

337 All of the tape devices are available to the Ultrium 2 device class, but only Ultrium 3 devices are available to the Ultrium 3 device class. Tivoli Storage Manager will ensure that Ultrium 3 media will only be loaded into Ultrium 3 devices for reading and writing. Ultrium 2 media will be read from or written to by all the Ultrium 2 and 3 devices. Tip: MOUNTLIMIT For read or write tape mounts, Tivoli Storage Manager will select Ultrium 2 drives for Ultrium 2 media first. If no Ultrium 2 devices are available, an available Ultrium 3 drive will be selected for the Ultrium 2 media. To prevent the case where all Ultrium 3 drives are loaded with Ultrium 2 media (leaving no drives available to read/write Ultrium 3 media), set the DEVCLASS parameter MOUNTLIMIT appropriately. For example: MOUNTLIMIT can be set to the number of Ultrium 2 drives in the library for the Ultrium 2 devclass, so it will not use Ultrium 3 drives at all. MOUNTLIMIT can be set to the number of Ultrium 2 drives plus half the number of Ultrium 3 drives. This is a compromise position to allow good drive utilization, but reserve some Ultrium 3 drives for Ultrium 3 media. You should define a suitable MOUNTLIMIT that works for your environment. In Tivoli Storage Manager V5.1, we would have to separate the physical Ultrium device types into separate logical libraries and device classes. Therefore, one Tivoli Storage Manager with both Ultrium 1 and 2 drives would have to define at least two logical libraries, and the physical library would have to support library partitioning. Again, Tivoli Storage Manager will ensure that only Ultrium 2 media are loaded in the Ultrium 2 drives, while Ultrium 1 media can be read and written by both Ultrium 1 and 2 drives. Scenario 3 As of Tivoli Storage Manager V5.2.4, Ultrium 3 drives are supported, and any combination of Ultrium 1, 2, and 3 drives and media can be used in one library. As discussed in scenario 2, Ultrium 3 drives can read and write Ultrium 2 media. Similarly, the Ultrium 2 drives can read and write Ultrium 1 media. Although Ultrium 3 drives can read the Ultrium 1 media (but cannot write to it), care should be taken to avoid attempted writing. Set the MOUNTLIMIT option for the Ultrium 1 devclass to less than the sum of Ultrium 1 and 2 drives (see tip above), thereby preventing the Ultrium 1 media from being loaded in the Ultrium 3 drives. The Ultrium 1 media will still be available for normal use by the Ultrium 1 and 2 drives. Alternatively, the migration path will be to have all Ultrium 1 media set to read-only for use by all drives, and the Ultrium 1 drives and media eventually phased out of the library Scenario 4 Replace all Ultrium 2 drives with Ultrium 3 drives, using the existing Ultrium 2 media and installing additional Ultrium 3 media: 1. Delete the existing Ultrium 2 device DRIVE and PATH entries and define new DRIVE and PATH entries for the Ultrium 3 devices. 2. The replacement of the Ultrium 2 drives with Ultrium 3 drives will also affect the Tivoli Storage Manager device class parameter format, which should now be set to ultrium3c. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 309

338 Tip: The devclass format parameter is used to pre-determine the capacity value of a storage pool. Because we now have media with varying amounts of capacity (200 GB and 400 GB native), the storage pool values will not be correct. If this is an issue, then use two device classes, as described in Scenario 2 on page 308. The same discussion applies using the older generation Ultrium 1 and Ultrium 2 media and drives. Scenario 5 Replace all Ultrium 2 drives with Ultrium 2 drives, and choose to migrate the existing Ultrium 2 media to Ultrium 3 media: 1. Delete the existing Ultrium 2 device DRIVE and PATH entries, and define new DRIVE and PATH entries for the Ultrium 3 devices. 2. Remove empty Ultrium 2 media and install Ultrium 3 media (label 1 in Figure 7-29 on page 311). 3. Over time, update the Ultrium 2 media ACCESS to READONLY. This ensures they will then not be written to any more by any Tivoli Storage Manager client or server operation (label 2 in Figure 7-29 on page 311). 4. You can leave the existing utilized Ultrium 2 cartridges as they are, and over time, expiration of old backups and reclamation will reduce the usage of the old cartridges. 5. However, if you want to drain the existing Ultrium 2 cartridges more quickly, you can execute a MOVE DATA volume_name LTO_storage_pool_name command, selecting each individual Ultrium 2 volume and targeting the LTO storage pool. 6. Once the old Ultrium 2 cartridges are emptied, the cartridges can be checked out of the library and new Ultrium 3 cartridges can be checked in to replace them (label 3 in Figure 7-29 on page 311). 7. The replacement of the Ultrium 2 drives and media with Ultrium 3 drives and media will also affect the device class parameter format, which should be set to DRIVE, ULTRIUM3 or ULTRIUM3C. If the format parameter is left at ULTRIUM2 or ULTRIUM2C, a write will still occur to the end of Ultrium 3 media, but the pre-determined capacity of the storage pool will only show Ultrium 2 capacity when the command query stgpool is used. 310 Implementing IBM Tape in Linux and Windows

339 1 checkout LTO2 LTO3 checkin LTO2 LTO3 LTO2 LTO3 checkin LTO3 LTO2 LTO3 TSM Server LTO Library 2 LTO3 LTO3 R/O LTO3 R/O LTO3 R/O LTO3 TSM Server LTO Library 3 checkout LTO3 LTO3 checkin LTO3 R/O LTO3 LTO3 LTO3 LTO3 LTO3 TSM Server LTO Library Figure 7-29 Migration scenario 5 The same discussion applies for migrating the older generations Ultrium 1 to Ultrium 2. Scenario 6 Ultrium 3 drives can read the Ultrium 1 media. The discussion in scenario 5 applies here, although in this scenario it is imperative that all Ultrium 1 media are updated to an ACCESS of READONLY. All new writes are to the new Ultrium 3 media, and all data on Ultrium 1 media is moved specifically, or phased out over time. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 311

340 Scenario 7 Replace an existing tape library and migrate the client data to a new LTO tape library. The steps are the same whether migrating to Ultrium 2 or Ultrium 3 drives and media. You are, however, encouraged always to migrate to the newest generation library. Various techniques can be used. We will describe migrating the data by using an existing management class. This only requires modifying the currently used storage pool to cascade to the new LTO storage pool. This has the advantage of being less disruptive, and has no affect on the client option files. We give two possibilities for storage pools, depending on whether the primary destination is a disk or tape (sequential) pool. Sequential storage pool as primary copy destination Your modification affects the storage pools only: 1. The new LTO library, library path, drives, drive paths, and device classes must first be defined. 2. An LTO sequential storage pool or copy storage pool must be created using the new LTO device class (label 1 in Figure 7-30 on page 313). 3. Modify the NEXTSTGPOOL parameter of the old storage pool to point to the new LTO storage pool (label 2 in Figure 7-30 on page 313). 4. You update the old storage pool ACCESS to READONLY. Note: This assumes that you want to move the entire storage pool content to the new LTO, as you cannot have the storage pool read-only for certain management classes and read-write for others. 5. You can leave the old storage pool as it is, and over time, expiration of old backups will reduce the usage of the old storage pool. 6. However, if you want to drain the old storage pool more quickly, you can simply set HIGHMIG and LOWMIG to zero. This starts a migration process that moves data from the old storage pool to the new LTO storage pool. To speed up the migration, you can increase the MIGPROCESS limit for the old storage pool to use more drives (remember this is a drive to drive process). 7. Alternatively, you can execute a MOVE DATA volume_name LTO_storage_pool_name command, selecting each individual volume from the old storage pool, and targeting the new LTO storage pool. 8. Once the old storage pool is emptied, modify the BACKUP and ARCHIVE COPY GROUP of each management class to point the DESTINATION to the new LTO Storage pool (label 3 in Figure 7-30 on page 313). 9. Delete the DRIVE and PATH, and also the LIBRARY and PATH entries for the old library and drives. 312 Implementing IBM Tape in Linux and Windows

341 1 Old Storage Old Mgmt Class LTO 2 R/O Old Storage Old Mgmt Class LTO 3 Old Storage LTO LTO Mgmt Class Figure 7-30 Migrating to LTO as sequential primary copy Disk storage pool as primary copy destination If you use a disk storage pool as your primary destination which, in turn, is cascaded to the old storage pool, your final modification affects the primary disk storage pool only: 1. The LTO library, library path, drives, drives paths, and device classes must first be defined. 2. An LTO sequential storage pool or copy storage pool must be created using the LTO device class. 3. After creating the new LTO storage pool (label 1 in Figure 7-31 on page 314), modify the NEXTSTGPOOL parameter of the old storage pool to point to the new LTO storage pool (label 2 in Figure 7-31 on page 314). 4. Update the old sequential storage pool ACCESS to READONLY. Note: This assumes that you want to move the entire storage pool content to the new LTO, as you cannot have the storage pool read-only for certain management classes and read-write for others. 5. You can leave the old storage pool as it is and, over time, expiration and migration will reduce the usage of the old storage pool. 6. However, if you want to drain the old storage pool more quickly, you can simply set HIGHMIG and LOWMIG to zero. This starts a migration process, which moves data from the old storage pool to the new LTO storage pool. To speed up the migration, you can increase the MIGPROCESS limit for the old storage pool to use more drives (remember this is a drive to drive process). 7. You can also run a MOVE DATA volume_name LTO_storage_pool_name command, selecting each individual volume from the old sequential storage pool, and targeting the new LTO storage pool. Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 313

342 8. Once the old sequential storage pool is emptied, modify the NEXTSTGPOOL parameter of the disk storage pool to point to the new LTO storage pool (label 3 in Figure 7-31). 9. Delete the DRIVE and PATH, and also the LIBRARY and PATH entries for the old library and drives. 1 Disk Storage Old Mgmt Class Old Storage LTO 2 Old Mgmt Class R/O Old Storage LTO 3 Disk Storage R/O Old Storage LTO Old Mgmt Class Figure 7-31 Migrating to LTO through disk primary copy 7.13 Tivoli Storage Manager V5.2 SAN device mapping In a SAN environment, device IDs can change dynamically due to device or cabling changes. Before V5.2, the Tivoli Storage Manager server used statically defined library and tape device IDs. If the device IDs were changed after a reboot or a re-scan of the SCSI bus, Tivoli Storage Manager could access a wrong target device and cause data integrity problems. Tivoli Storage Manager V5.2 introduced a new method to dynamically determine the correct device special file name and makes appropriate changes to the Tivoli Storage Manager server database by using the device s serial number. This function can replace persistent binding, which binds a device WWN to a specific target/lun ID (as described in 5.3, Persistent binding on page 237) in certain environments. SAN Discovery and Device Mapping are discussed in detail for the Tivoli Storage Manager environment in the redbook Get More Out of Your SAN with IBM Tivoli Storage Manager, SG SAN device mapping functions SAN device mapping has three basic functions: Serial number autodetection and validation Element number autodetection SAN discovery 314 Implementing IBM Tape in Linux and Windows

343 To enable these functions, the DEFINE LIBRARY and DEFINE DRIVE commands have been enhanced to allow manual entry or automatic detection of the serial and element numbers. Also, the DEFINE PATH command is enhanced to automatically update the serial number. This new syntax is described in 7.2.3, Defining the library and drives using the command line on page 269. Refer to the Tivoli Storage Manager documentation for further details. Serial number autodetection and validation Serial number autodetection enables Tivoli Storage Manager to automatically obtain a library or drive serial number by issuing a SCSI Inquiry command during the DEFINE PATH command. Serial number validation automatically validates the serial number if the serial number is provided with the DEFINE/UPDATE LIBRARY and DEFINE/UPDATE DRIVE commands by issuing a SCSI Inquiry command during the DEFINE PATH command. Device serial numbers are also automatically validated during every library or tape drive access. To avoid potential errors during device definitions or when SAN and device reconfiguration occurs, you can use the AUTODETECT function of the DEFINE PATH command. This function automatically updates the Tivoli Storage Manager server database with the correct device special file name by using the device s serial number. Element number autodetection Element number autodetection enables Tivoli Storage Manager to automatically obtain the drive element address by using the drive s serial number. This function automatically finds the matching element address in the serial number/element number map during the DEFINE PATH command. SAN discovery To avoid the need for manual modification, there is an accurate SAN device mapping feature available in Tivoli Storage Manager V5.3. This mapping process involves two steps: 1. Detecting that the device has changed. This detection is accomplished by recording the device s serial number, manufacturer, and World Wide Node Name (WWNN), if it exists, in the Tivoli Storage Manager database. Whenever a device is opened, its identity is verified. This feature is now available on Windows, AIX, Sun, and Linux servers as well as Storage Agents, and was implemented in Tivoli Storage Manager V5.2 for Windows. 2. Reconciling the device definitions (paths) dynamically when changes are detected. This reconciliation requires Tivoli Storage Manager to discover devices in the SAN environment. New commands are available in Tivoli Storage Manager V5.3. To activate SAN device mapping, set the SANDISCOVERY option to ON in the dsmserv.opt file: SANDISCOVERY ON This setting is the default for Windows platforms. For all other platforms, you must set this option in the server options file. To activate SAN discovery in a running Tivoli Storage Manager instance, use the following setting: SETOPT SANDISCOVERY ON Chapter 7. Configuring IBM Tivoli Storage Manager on Windows and Linux 315

344 316 Implementing IBM Tape in Linux and Windows

345 8 Chapter 8. Configuring EMC Legato NetWorker on Windows This chapter describes the steps that are necessary to configure EMC Legato NetWorker on Windows 2000 using an IBM LTO library. As examples, we describe implementing an IBM 3583 with LTO 1 drives with EMC Legato NetWorker 6 and implementing an IBM 3584 with LTO 2 FC drives in EMC Legato NetWorker 7. Note: Later versions of EMC Legato NetWorker are available that support IBM LTO3 and IBM 3592 products. The panels and command outputs may have changed from what is shown in this chapter; however, the information is included as a guide. Consult the product documentation and the compatibility Web sites listed in this chapter for the most up-to-date information. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 317

346 8.1 EMC Legato NetWorker overview EMC Legato NetWorker provides backup, recovery, and other storage management services. It is supported on many different client and server platforms as well as popular applications (for example, Oracle, Exchange, and so on). NetWorker products for different operating systems are interoperable, and provide flexibility in designing a storage management setup. For detailed product information, visit the NetWorker Web site: NetWorker uses a client/server architecture, organized around a data zone, and is comprised of three different functions: server, client, and storage node. A data zone is a single NetWorker server with one or more clients or storage nodes. NetWorker server The NetWorker Server software provides control and scheduling for NetWorker operations. The NetWorker Server defines the clients, devices, and media used by the NetWorker Server, defines the schedules for backups and other operations, and monitors all the NetWorker operations. NetWorker Client The NetWorker Client provides recover and on-demand backup functionality, and it communicates with the NetWorker Server. The NetWorker Client software is installed on all computers that will back up to the NetWorker Server. NetWorker Storage Node Data can be backed up to devices either directly attached to a server or to a storage node. A storage node controls storage devices, such as tape drivers, autochangers, and silos, but does not do the other configuration that a server performs EMC Legato NetWorker and IBM LTO interoperability Be sure that EMC Legato NetWorker is supported in your specific environment. You have to cross check on both the IBM and NetWorker Web sites to verify this: Special note: NetWorker and IBM 3584 The IBM 3584 is a SCSI Library with fixed tape drive SCSI element addresses for the tape drives. Because of the way that NetWorker configures tape libraries, special handling is required when installing with a multiframe 3584 where the drives are not installed in a contiguous sequence. Preferably, you should first install 12 drives in the first frame before installing additional drives in the second frame. If the IBM 3584 is not set up in this manner, the NetWorker commands sjirdtag, sjirelem, inquire, and jb_config will all return a list of drives that include tape devices where no physical devices are present. When configuring the tape library with jbconfig, you will have to define some dummy devices, as described in Configuring dummy devices (non-contiguous libraries only) on page Implementing IBM Tape in Linux and Windows

347 8.2 NetWorker installation on Windows 2000 In the following section, we describe NetWorker 6 installation for the Windows 2000 platform. For more details, see the official NetWorker documentation, at this Web site: In the following example, we show the installation of NetWorker with a SCSI point to point connection to an IBM 3583 with two drives. We installed NetWorker in the following environment, as shown in Figure 8-1: Pentium server (DIOMEDE) with Windows 2000 Advanced Server (2195). Adaptec LVD SCSI card. IBM 3583 library SCSI attached. A single SCSI bus supports both the library controller and the two 3580 tape drives. NetWorker Version 6.1. In 8.3, NetWorker library configuration on page 321, we will show two sample setups for NetWorker, with IBM 3583 and IBM 3584 libraries. SCSI Windows 2000 Intel server IBM 3583 Figure 8-1 SCSI attach configuration Installation preparation Before installing NetWorker, you should have installed the adapter card in Windows 2000 and loaded the IBM Ultrium drivers. These procedures are described in 3.2, Installing IBM tape device drivers for Windows 2000 on page 82. Disable the RSM service if it is running, as described in Disabling RSM on page Software installation To start the installation, run the autorun command from the product CD. You will see the start window shown in Figure 8-2 on page 320. Chapter 8. Configuring EMC Legato NetWorker on Windows 319

348 Figure 8-2 NetWorker installation start window We will install the Windows 2000 version and select the option to run the installation program directly from its current location, as shown in Figure 8-3. Figure 8-3 Install from the current location We can ignore the security warning about a missing authentication code signature and select both client and server for installation in the directory of our choice, as shown in Figure 8-4 on page Implementing IBM Tape in Linux and Windows

349 Figure 8-4 Select the NetWorker client and server software for installation As we are installing a single server environment, we do not need to specify additional servers to backup the data on this computer (see Figure 8-5). Figure 8-5 Selection of additional servers is not required You will be asked to confirm the selected parameters before proceeding with the installation. Installation time depends on the capacity of the server. When it is complete, you see a message that installation was successful. Click Finish to end the installation setup. 8.3 NetWorker library configuration Before we can use NetWorker with our LTO library, we have to configure our devices and library. We show one example of configuring an IBM 3583 with LTO 1 SCSI drive and one example of configuring an IBM 3584 with LTO 2 FC drives. You should have already installed and configured the tape drives as described in Chapter 3, Basic IBM tape setup for Windows on page 79. Also you should disable Removable Storage Manager (RSM). Chapter 8. Configuring EMC Legato NetWorker on Windows 321

350 8.3.1 NetWorker 6.1 library configuration of IBM 3583 We use the jbconfig tool to make the LTO Library available to NetWorker. Example 8-1 shows the procedure of defining the LTO library with jbconfig. The process automatically detects our hardware so that it can be configured. In our case, this is the IBM 3583, referred to as a SCSI Jukebox, and our two tape drives. Since we are using the IBM Ultrium drivers, we use the device names \\.\Tape0 and \\.\Tape1. Example 8-1 Library configuration via jbconfig D:\Program Files\nsr\bin>jbconfig 1) Install a SmartMedia Jukebox. 2) Install an Autodetected SCSI Jukebox. 3) Install an Autodetected NDMP SCSI Jukebox. 4) Install an SJI Jukebox. 5) Install an STL Silo. What kind of Jukebox are you installing? [1] 2 These are the SCSI Jukeboxes currently attached to your system: 1) [email protected]: Standard SCSI Jukebox, Vendor <IBM>, Product <ULT3583-TL> Which one do you want to install? 1 Installing an Standard SCSI Jukebox jukebox. Name you would like to assign to the jukebox device? LTO3583 A brief description of the jukebox device? [[email protected]: Standard SCSI Jukebox] Path name of the control port for the jukebox device? [[email protected]] Do you want automated device cleaning support enabled? (yes/no) no Will media drive 1 be shared by multiple device paths? (yes/no) no Enter host name that owns media drive 1:? [diomede] Enter path name of media drive 1:? [\\.\Tape0] using \\.\Tape0 as device name Should the drive be configured as a NDMP device? (yes/no) no This media device has not been configured yet. Please select a media device type for \\.\Tape0. 1) ) dlt8000 2) ) dst (NT) 3) ) dtf 4) ) file 5) 4mm 26) himt 6) 4mm 12GB 27) logical 7) 4mm 20GB 28) LTO Ultrium 8) 4mm 4GB 29) optical 9) 4mm 8GB 30) qic 10) 8mm 31) SD3 11) 8mm 20GB 32) sdlt 12) 8mm 5GB 33) Tivoli Performance Reporter for OS/390 13) 8mm AIT 34) tkz90 14) 8mm AIT-2 35) tz85 15) 8mm Mammoth-2 36) tz86 16) ) tz87 17) ) tz88 18) ) tz89 19) dlt 40) tzs20 20) dlt1 41) vhs 21) dlt ) VXA Choice? Choice? 28 Will media drive 2 be shared by multiple device paths? (yes/no) no 322 Implementing IBM Tape in Linux and Windows

351 Enter host name that owns media drive 2:? [diomede] Enter path name of media drive 2:? [\\.\Tape1] using \\.\Tape1 as device name Should the drive be configured as a NDMP device? (yes/no) no This media device has not been configured yet. Please select a media device type for \\.\Tape1. 1) ) dlt8000 2) ) dst (NT) 3) ) dtf 4) ) file 5) 4mm 26) himt 6) 4mm 12GB 27) logical 7) 4mm 20GB 28) LTO Ultrium 8) 4mm 4GB 29) optical 9) 4mm 8GB 30) qic 10) 8mm 31) SD3 11) 8mm 20GB 32) sdlt 12) 8mm 5GB 33) Tivoli Performance Reporter for OS/390 13) 8mm AIT 34) tkz90 14) 8mm AIT-2 35) tz85 15) 8mm Mammoth-2 36) tz86 16) ) tz87 17) ) tz88 18) ) tz89 19) dlt 40) tzs20 20) dlt1 41) vhs 21) dlt ) VXA Choice? 28 Your jukebox does not report that it has a bar code reader, but it does report that it can handle volume tags. Some jukeboxes that have barcode readers report this way. If your jukebox has a barcode reader, do you want bar code reader support enabled? (yes/no) yes Do you want volume labels to match bar code labels? (yes/no) yes Jukebox has been added successfully Would you like to configure another jukebox? (yes/no) no For our environment, we do not need special features like multiple device paths or NDMP support. We do activate barcode support and specify that volume labels should match the barcode labels NetWorker 7 library configuration of IBM 3584 Here we will configure an IBM 3584 with one LTO 2 FC drive and one LTO 2 SCSI drive connected via a SDG to a SAN. 1. Use the NetWorker inquire command to check the tape devices connected to the system. This gives you the output shown in Example 8-2 on page 324. Here you see the devices recognized as SCSI attached to the system and information about their SCSI identification. For example, for the SCSI Medium Changer, [email protected], the last two numbers indicate the target ID and the LUN number (tgt 4 and LUN 1). Note this information, as it will be used later in the autochanger configuration. You can also see the firmware microcode level (301v for the medium changer and 2CKH for the drives) and the serial number of the tape drives and the tape library. As you can see on the WWNN (WW Node Name) for the FC tape drive, this is the fifth tape drive in the first frame of the 3584 (see also Appendix 5, SAN considerations on page 223). For testing Chapter 8. Configuring EMC Legato NetWorker on Windows 323

352 purposes, we are using a library with just two tape drives available, one SCSI and one FC. The FC tape is installed in the fifth position. We cannot yet determine what position the SCSI tape drive is installed in. Before you start configuring the library you should know which tape special file name corresponds to which tape drive in the library. See also 5.3, Persistent binding on page 237, and Verifying device attachment with tapeutil or ntutil on page 426. In Example 8-2, you see, using inquire, the path (8.4.0) and the WWN. Example 8-2 inquire c:\inquire scsidev@ :emulex Utility Ifc Dev.EMU2 (Unknown Device Type b) [email protected]:ibm ULT3580-TD2 2CKH Tape, \\.\Tape0 S/N: ATNN:IBM ULT3580-TD [email protected]:crossrds10000 Router 02aw (Unknown Device Type c) [email protected]:ibm ULT3580-TD2 2CKH Tape, \\.\Tape1 S/N: ATNN:IBM ULT3580-TD WWNN: F005 [email protected]:ibm 03584L32 301v Autochanger (Jukebox) S/N: T ATNN:IBM 03584L T scsidev@ :emulex Utility Ifc Dev.EMU2 (Unknown Device Type b) 2. Use NTUTIL to determine the serial numbers of the installed tape drives. Use 14: Additional ioctls calls and then select 9: Extended drive inventory. As shown in Example 8-3, the \\.\Tape0 with the serial number is the sixth tape drive in the library. Note that NTUTIL reports the whole contents of the library, which has 6 tape drives. However, to our Windows system, only two drives are accessible (for example, because of cabling or zoning). Example 8-3 ntutil extended drive inventory Enter selection: 9 Displaying returned data: Number of Drives = 6 Drive # Serial Number: Serial Valid: 1 Element address = 257 Accessible = 1 Lun flag = 0 Lun = 0 Svalid = 0 Source Address= 0 SCSI flag = 1 SCSI ID = 10 Drive # Serial Number: Serial Valid: 1 Element address = 258 Accessible = 1 Lun flag = 0 Lun = 0 Svalid = Implementing IBM Tape in Linux and Windows

353 Source Address= 0 SCSI flag = 1 SCSI ID = 11 Drive # Serial Number: Serial Valid: 1 Element address = 259 Accessible = 1 Lun flag = 0 Lun = 0 Svalid = 0 Source Address= 0 SCSI flag = 1 SCSI ID = 11 Drive # Serial Number: Serial Valid: 1 Element address = 260 Accessible = 1 Lun flag = 0 Lun = 0 Svalid = 0 Source Address= 0 SCSI flag = 1 SCSI ID = 11 Drive # Serial Number: Serial Valid: 1 Element address = 261 Accessible = 1 Lun flag = 0 Lun = 0 Svalid = 0 Source Address= 0 SCSI flag = 1 SCSI ID = 11 Drive # Serial Number: Serial Valid: 1 Element address = 262 Accessible = 1 Lun flag = 0 Lun = 0 Svalid = 0 Source Address= 0 SCSI flag = 1 SCSI ID = 11 Chapter 8. Configuring EMC Legato NetWorker on Windows 325

354 Attention: Because Windows (unlike other operating systems) does not use the SCSI IDs to generate device names, you may not be sure that after a reboot of your server that you still have the same configuration available, even if you use persistent binding. Therefore, you should always check after a reboot if your tape device names are still mapped to the same devices. 3. The sjirjc command provides more information about the tape library. Use sjirjc and specify the library with the SCSI address given from the inquire output, as shown in Example 8-4. In our example, we used sjirjc Example 8-4 sjirjc c:\sjirjc Device: Number of Drives: 6 Number Drive Pairs: 1 Number of Import/Export Elements: 10 Number of Import/Export Pairs: 1 Number of Slots: 201 Number of Slot Pairs: 1 Number of Transport Elements: 1 Number of Transport Pairs: 1 Volume Tags Supported Initialize Element Status Supported As you see, sjirjc reports that the IBM 3584 has six tape drives installed. But to the operating system, there are just two tape drives visible. In the library, which we are using, the first four drives are switched off, inaccessible by cabling or zoning, or used by other tasks and therefore not visible to the operating system. Normally in a production, you would partition the 3584 into logical libraries to get consistency. In this example, we did not do this, in order to show the steps that are needed to get this configuration (using non-contiguously installed tape drives) working. This is the situation we discussed in Special note: NetWorker and IBM 3584 on page 318. Another situation where this could occur is in a multi-frame 3584, where a frame is not completely full with drives (typically to increase the number of cartridge slots available). For example, if two drives are installed in the first frame and two drives are installed in the second frame, sjirjc would report 14 drives, as it sees that the last available drive is in position 14. If you do have contiguously numbered devices (that is, the number of drives reported by sjirjc matches the number of drives visible to the operating system in the correct positions), you can skip the following steps and proceed. Otherwise, perform the steps in Configuring dummy devices (non-contiguous libraries only) on page 326. Configuring dummy devices (non-contiguous libraries only) In our example, we only have two tape drives available. But sjirjc reports six drives, so we have to create four dummy devices. Create a directory on your C: drive, such as mkdir c:\drive, and create four files, log1 to log 4 (for example, echo > c:\drive\log1). Check if all the dummy drive files are available, as in Example 8-5 on page 327. We will use these files in the next step. 326 Implementing IBM Tape in Linux and Windows

355 Example 8-5 Dummy drive files C:\>dir c:\drive Volume in drive C is C_DRIVE Volume Serial Number is 6C10-18AA Directory of c:\drive :26 <DIR> :26 <DIR> :26 13 log :26 13 log :26 13 log :26 13 log4 4. Example 8-6 shows how to define the LTO library with jbconfig. The process automatically detects our hardware so that it can be configured. In our case, this is the IBM 3584, referred to as a SCSI Jukebox, and our two tape drives, \\.\Tape0 and \\.\Tape1, (plus, if necessary, any dummy devices). As determined in Step 1 on page 323 and on Step 2 on page 324, \\.\Tape0 is the sixth tape drive and \\.\Tape1 is the fifth tape drive. Therefore, we use, for the first four tape drives, the dummy files log1 to log4 and the real drive devices for the fifth and sixth drives. For the dummy devices, we use the device type 31 logical, and for the real drives, we use device type 33 LTO Ultrium-2. Example 8-6 Library configuration via jbconfig jbconfig 1) Configure an AlphaStor/SmartMedia Jukebox. 2) Configure an Autodetected SCSI Jukebox. 3) Configure an Autodetected NDMP SCSI Jukebox. 4) Configure an SJI Jukebox. 5) Configure an STL Silo. 6) Configure a Microsoft Removable Storage Jukebox. What kind of Jukebox are you configuring? [1] 2 Installing 'Standard SCSI Jukebox' jukebox - scsidev@ What name do you want to assign to this jukebox device? IBM3584fc Turn NetWorker auto-cleaning on (yes / no) [yes]? n The drives in this jukebox cannot be auto-configured with the available information. You will need to provide the path for the drives. Is (any path of) any drive intended for NDMP use? (yes / no) [no] Is any drive going to have more than one path defined? (yes / no) [no] Please enter the device path information in one of the following formats: \\.\Tape0 --for local path or host:device-path --for remote node or host:drive-letter:directory path --for Windows disk file Drive 1, element 257 Drive path? s6-dev-nt2:c:\drive\log1 Drive 2, element 258 Drive path? s6-dev-nt2:c:\drive\log2 Drive 3, element 259 Drive path? s6-dev-nt2:c:\drive\log3 Chapter 8. Configuring EMC Legato NetWorker on Windows 327

356 Drive 4, element 260 Drive path? s6-dev-nt2:c:\drive\log4 Drive 5, element 261 Drive path? \\.\Tape0 Drive 6, element 262 Drive path? \\.\Tape1 Please select the appropriate drive type number: 1) ) ) optical 2) ) 9840b 35) qic 3) ) ) SD3 4) ) adv_file 37) sdlt 5) 4mm 22) dlt 38) sdlt320 6) 4mm 12GB 23) dlt1 39) Tivoli Performance Reporter for OS/390 7) 4mm 20GB 24) dlt ) tkz90 8) 4mm 4GB 25) dlt ) travan10 9) 4mm 8GB 26) dst (NT) 42) tz85 10) 8mm 27) dtf 43) tz86 11) 8mm 20GB 28) dtf2 44) tz87 12) 8mm 5GB 29) file 45) tz88 13) 8mm AIT 30) himt 46) tz89 14) 8mm AIT-2 31) logical 47) tz90 15) 8mm AIT-3 32) LTO Ultrium 48) tzs20 16) 8mm Mammoth-2 33) LTO Ultrium-2 49) VXA 17) 9490 Enter the drive type of drive 1? 31 Are all the drives the same model? (yes / no) [yes] n Enter the drive type of drive 2? 31 Enter the drive type of drive 3? 31 Enter the drive type of drive 4? 31 Enter the drive type of drive 5? 33 Enter the drive type of drive 6? 33 Jukebox has been added successfully The following configuration options have been set: > Jukebox description to the control port and model. > Autochanger control port to the port at which we found it. > Autocleaning off. > At least once during device path definition, you used a "host" value that evaluated to the name of this host, but was not the same text. All the references to this host in the RAP database will use the text string: > Barcode reading to on. Your jukebox does not report that it has a bar code reader, but it does report that it can handle volume tags. Some jukeboxes that have barcode readers report this way. > Volume labels that match the barcodes. > Slot intended to hold cleaning cartridge to 201. Please insure that a cleaning cartridge is in that slot > Number of times we will use a new cleaning cartridge to Implementing IBM Tape in Linux and Windows

357 You can review and change the characteristics of the autochanger and its associated devices using nwadmin. Would you like to configure another jukebox? (yes/no) [no]n In our example, our library is non-shared, and will not be used for NDMP, so we answer No to those questions. We do activate barcode support and specify that volume labels should match the barcode labels. Disabling dummy devices The dummy devices (if required) are just needed to complete the jbconfig stage. After this task is complete, you should disable them using the following procedure before continuing. If you did not have to create dummy devices, then you can continue with the installation, as described in 8.4, Labeling cartridges on page To disable the configured dummy devices, start the NetWorker Admin GUI and select Autochanger. As you see in Figure 8-6, the library currently shows six drives. Figure 8-6 Library view To see more information about the drives and the library, you should set the options to also see hidden attributes. Select Options Customize and enable Display Hidden Attributes, as in Figure 8-7 on page 330. Chapter 8. Configuring EMC Legato NetWorker on Windows 329

358 Figure 8-7 Display hidden attributes Because of the dummy drives, we have to match the number of real drives to the maximum tape mounts allowed (max parallelism) on this autochanger. Select the tape library (autochanger) and right-click it. Select Preferences and set the max parallelism to 2 (or to the number of actual drives used), as in Figure 8-8 on page Implementing IBM Tape in Linux and Windows

359 Figure 8-8 Set max parallelism Now go to the Devices view, select one of the dummy devices, right-click and select Edit (Figure 8-9 on page 332). Chapter 8. Configuring EMC Legato NetWorker on Windows 331

360 Figure 8-9 Device View: Edit dummy device On the Devices Edit panel, disable the dummy device by selecting No on the Enabled field (Figure 8-10 on page 333). 332 Implementing IBM Tape in Linux and Windows

361 Figure 8-10 Edit Device: Disable dummy drive Repeat this step for all dummy devices. Now your Device view should look like Figure 8-11 on page 334, with all dummy devices disabled. Chapter 8. Configuring EMC Legato NetWorker on Windows 333

362 Figure 8-11 Device view with disabled dummy devices 8.4 Labeling cartridges Now we are ready to work with the LTO Library and to make the tape cartridges available to NetWorker. When initializing a new library or/and labeling a lot of new tapes, set Max consecutive errors to a higher value (such as 20, as every unlabeled cartridge will generate an error). Therefore, set the max consecutive errors higher than the number of cartridges you are labeling. Go to the device view and select a drive. Right-click and select Edit. Select the Configuration tab and set the max consecutive errors, as in Figure 8-12 on page 335. Perform this step for each drive. After labeling, you should re-set it to the previous value. 334 Implementing IBM Tape in Linux and Windows

363 Figure 8-12 Device configuration Now go to the library view, select the library, and right-click Select Operations and the Autochanger Operations panel will appear. Click the Label button and select the cartridge slots you want to use for labeling (Figure 8-13 on page 336). Tip: Use the Fast/Silent option for the Operation Type for faster labeling. Chapter 8. Configuring EMC Legato NetWorker on Windows 335

364 Figure 8-13 Labeling cartridges After entering your selection, click OK and the labeling will start. Figure 8-14 shows the progress of the labeling. Figure 8-14 Labeling in progress When the labeling process has finished, the Autochanger Operations dialog box shows the cartridges with their label names, as in Figure 8-15 on page 337. As you see, not all cartridges are labeled yet. The unlabeled cartridges appear as <unlabeled>. 336 Implementing IBM Tape in Linux and Windows

365 Figure 8-15 Display of cartridges after labeling 8.5 Inventory Sometimes a manual inventory is required, for example, if you need to open the IBM 3583 or 3584 library door and move the cartridges, or extract them for maintenance or other reasons. Remember to start an inventory of the library from the NetWorker administration interface after you put the library online. Select Inventory from the Autochanger Operations panel (Figure 8-15). 8.6 Some additional settings The default values for the library are suitable for most environments. But if you have load and unload problems, then review and adjust the following settings. Unload Sleep Specifies the number of seconds an autochanger sleeps between unloading a volume and moving the volume from the device to a slot. The NetWorker software uses this attribute for all autochangers when a volume is unloaded. IBM LTO 1 Drives have a nominal unload time of 18 seconds. Therefore, it may be necessary to increase the unload sleep to 18 seconds or more. IBM LTO 2 Drives have a nominal unload time of 15 seconds. Therefore, it may be necessary to increase the unload sleep to 15 seconds. Chapter 8. Configuring EMC Legato NetWorker on Windows 337

366 Load Sleep Specifies the number of seconds the NetWorker software sleeps between loading a volume and trying to access that volume s data. IBM LTO 1 Drives have a nominal unload time of 20 seconds. Therefore, it may be necessary to increase the unload sleep to 20 seconds or more. IBM LTO 2 Drives have a nominal unload time of 15 seconds. Therefore, it may be necessary to increase the unload sleep to 15 seconds or more. To access and set the sleep-related Jukebox resource attributes, go to the autochanger view, select your library, and right-click. Select Edit and go to the Timers tab (see Figure 8-16). Tip: Display Hidden Attributes, as seen in Figure 8-7 on page 330, must be enabled to set these values. Figure 8-16 Autochanger edit menu: Adjust the timer values 8.7 NetWorker client backup At the beginning of our installation, we decided to install the NetWorker Client and Server on our system. Therefore, we can immediately start the NetWorker Client to create a backup of our system. Select Start Programs NetWorker Group NetWorker User. From the main window (Figure 8-17 on page 339), click the Backup icon. 338 Implementing IBM Tape in Linux and Windows

367 Figure 8-17 Backup main window The NetWorker client backup interface appears. Select the files for backup by highlighting them and clicking the blue check box, as shown in Figure Figure 8-18 NetWorker client window with file selections for backup We selected the Start traffic light button, and after a short period of time, a tape will be mounted in our LTO Ultrium library to receive the backup. The NetWorker Client shows the status of the backup operation (Figure 8-19). Figure 8-19 NetWorker Client during backup operation The NetWorker documentation provides additional information about configuration and optimization tasks. Chapter 8. Configuring EMC Legato NetWorker on Windows 339

368 340 Implementing IBM Tape in Linux and Windows

369 9 Chapter 9. Configuring BakBone NetVault on Windows and Linux This chapter describes the steps needed to configure NetVault Version 6 by BakBone in the Windows 2000 and Linux environments. We show how to set up a basic tape library connection and then how to use the BakBone NDMP Client on the Linux server. Note: Later versions of BakBone NetVault are available, which support IBM LTO3 and IBM 3592 products. The panels and command outputs may have changed from what is shown in this chapter; however, the information is included as a guide. Consult the product documentation and the compatibility Web sites listed below for the most up-to-date information. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 341

370 9.1 NetVault by BakBone NetVault by BakBone is an easy-to-use, fully functional, high-performance, and scalable backup and recovery storage management product. NetVault supports a broad range of server and client operating systems in LAN, SAN, and NAS environments. NetVault also supports a wide range of media and devices, including the IBM LTO and 3592 products. NetVault uses industry standard, non-proprietary formats for writing to tape. These are cpio for UNIX and Microsoft Tape Format (MTF) for Windows. For easy data interchange and disaster recovery protection, NetVault-produced tapes can be read by any UNIX- or Windows-based system supporting the standard. In the event of a problem with the library, server hardware, or applications, NetVault tapes can be restored to any machine, regardless of whether the NetVault application is present. The latest device, library, and operating system-specific information can be obtained from the BakBone Web site at: We will first describe the basic installation of the NetVault application onto Linux and Windows 2000, as the actual configuration of the product is almost identical on both systems. 9.2 Installing NetVault on Windows 2000 In this section, we show the steps to configure NetVault Version 6.03 on Windows 2000 using an IBM We tested for both SCSI direct attach and SAN attach. For SCSI direct access connection, we used the following hardware, as shown in Figure 9-1: Pentium II server with Windows 2000 Advanced Server (build 2195). Adaptec LVD SCSI card. IBM 3583 SCSI attached. A single SCSI bus supports both the library controller and the two 3580 tape drives. SCSI Windows 2000 Intel server IBM 3583 Figure 9-1 Windows 2000 direct SCSI configuration For the SAN environment, we used the following hardware, as shown in Figure 9-2 on page 343: A Pentium II server with Windows 2000 Advanced Server (build 2195). QLogic 2200F FC HBA. IBM 2109 Fibre Channel switch. IBM 2108 SAN Data Gateway (SDG). 342 Implementing IBM Tape in Linux and Windows

371 IBM 3583 attached via SCSI port to the SAN Data Gateway. A single SCSI bus supports both the library controller and the two IBM 3580 drives. Intel server Windows 2000 Ethernet LAN Fiber SAN IBM 2109 FC Switch Fiber SCSI IBM 2108 LTO 3583 Figure 9-2 Windows 2000 SAN configuration Installation preparation The preparation for installing NetVault depends on whether your tape library is already installed. Existing LTO installation If your LTO drive was already installed on your server, check to see if the IBM drivers are being used. The IBM Ultrium drivers are not required for the NetVault software. If you have already installed these, disable them, as described in 3.5.5, Deleting LTO devices on page 134. New LTO installation If this is a brand new installation, first install the adapter card to Windows 2000 and load the drivers. This procedure is given in 3.6, Windows 200x SCSI adapter installation on page 137, and 3.7, Windows 200x Fibre Channel HBA driver installation on page 142, for the FC card. Disable the RSM service if required, as described in Disabling RSM on page 134. Shut down the server, physically cable the tape library, and reboot the system. All LTO installations Your drive and libraries should now show up as unknown devices using the native Windows driver. Check in Windows Device Manager. The drives should appear similar to Figure 3-19 on page 91, and the changer (if present) as in Figure 3-12 on page 88. Chapter 9. Configuring BakBone NetVault on Windows and Linux 343

372 9.2.2 Installing NetVault The NetVault application code is available on diskette, CD-ROM or zip package. Both the CD-ROM and zip packages are built from the diskette images. To start the installation, execute setup.exe. You will see an introductory window (Figure 9-3) and then the licensing agreement (Figure 9-4). Figure 9-3 Initial NetVault installation window Figure 9-4 License agreement You are prompted to enter your name and your company and then to specify where to install NetVault (Figure 9-5 on page 345). 344 Implementing IBM Tape in Linux and Windows

373 Figure 9-5 Destination folder Next, specify where you want NetVault to install its database (Figure 9-6). Refer to the NetVault documentation for guidance on sizing the database to help decide where to locate it. For our simple testing, we accepted the default location. Figure 9-6 Database location Next, choose which type of NetVault installation you want (Figure 9-7 on page 346). We selected NetVault Server System. Chapter 9. Configuring BakBone NetVault on Windows and Linux 345

374 Figure 9-7 Setup type In the next panel (Figure 9-8), enter your machine name. We installed on a system called DIOMEDE. Figure 9-8 Enter machine name Next, you will need to create a password for access to your NetVault domain (Figure 9-9 on page 347). 346 Implementing IBM Tape in Linux and Windows

375 Figure 9-9 NetVault password The installation now takes place. When it has finished, you will be prompted to reboot the system to allow the NetVault service to start. You can now configure your LTO device into NetVault, as shown in 9.4, Configuring NetVault on page Installing NetVault on Linux In this section, we show the steps to configure NetVault Version 6.03 on Linux with an IBM We use the following hardware (Figure 9-10): Intel server with Red Hat Linux 7.1 Server (Red Hat , Kernel UP). Adaptec LVD SCSI card. IBM 3583 SCSI attached. A single SCSI bus supports both the library controller and the two 3580 tape drives. SCSI Red Hat Linux Intel server IBM LTO 3583 Figure 9-10 Linux lab environment Chapter 9. Configuring BakBone NetVault on Windows and Linux 347

376 9.3.1 Installation preparation The preparation for installing NetVault depends on whether your tape library is already installed. Existing LTO installation If your LTO drive was already installed on your server, check to see if the IBM drivers are being used. The IBM Ultrium drivers are not required for the NetVault software. If you have already installed these, disable them, as described in 4.4.3, Uninstalling the Ultrium device drivers and utilities on page 211. New LTO installation If this is a brand new installation, first install the adapter card to Linux and load the drivers. This procedure is given in 4.3.1, Identifying and activating the SCSI controller on page 188. Shut down the server, physically cable the tape library, and reboot the system. Check the configuration of the devices using the procedures in 4.3.2, Kernel compilation and installation checklist on page 191 and the following sections. All LTO installations Your drive and medium changer should now be available to the operating system Installing NetVault The NetVault application code is available on CD-ROM or in a compressed tar package. We downloaded the image from the BakBone Web site, which arrived as a compressed tar file. Uncompress the file, then unpack the tar image into a temporary directory in preparation for installation, as shown in Example 9-1. Example 9-1 Unpacking NetVault Image [root@diomede tmp]# uncompress 6linux60_ tar [root@diomede tmp]# tar -xvf 6linux60_ tar NetVaultDistribution/ NetVaultDistribution/readme.txt NetVaultDistribution/install NetVaultDistribution/relnotes.txt NetVaultDistribution/nvdist [root@diomede tmp]# Make sure to review the files readme.txt and relnotes.txt before installing. These files contain up to date information about the product and installation issues. Change the directory to NetVaultDistribution and execute./install (see Example 9-2 on page 349). 348 Implementing IBM Tape in Linux and Windows

377 Example 9-2 Installing NetVault tmp]# cd NetVaultDistribution NetVaultDistribution]#./install NetVault 6 - Release V603_R (C) NetVault Ltd Unix Installation/Removal Utility Shutting down NetVault services... Accept the license agreement (see Example 9-3). Example 9-3 License agreement v2 Do you accept all the terms of the preceding license agreement If you choose No this setup will close. To install NetVault you must accept this agreement Press y to accept, n otherwise (y/n)y You will be prompted to enter an installation directory, NetVault database location, preferred installation type (server, client, or custom), server components, host name, and password. We accepted the defaults for the directory; however, you should consult the NetVault documentation for guidance on sizing the database to help decide where to locate it. We select a server type installation and all components (see Example 9-4). Example 9-4 Server configuration This program will install NetVault 6 V603_R Are you sure you want to continue? (y/n): y Please enter the path where you would like the NetVault directory to be created (The NetVault database directory will be specified separately) Installation Directory ('/usr'): Please enter the path for the NetVault database directory Database Directory: (/usr/netvault6/nvdb): Please select the type of installation to perform: 1) Server 2) Client 3) Custom Please select (1-3): 3 Available Components: 1) Data Plugin files 2) Device control files 3) GUI files 4) Online help files 5) Server files Chapter 9. Configuring BakBone NetVault on Windows and Linux 349

378 Please select components to install, separated by commas, eg 1,2,5: 1,2,3,4,5 You have chosen to install: - Data Plugin files - Device control files - GUI files - Online help files - Server files Is this correct? (y/n): y Enter a name that this machine will be known as by the other NetVault machines on your network NetVault Machine Name ('diomede.almaden.ibm.com'): Enter the password that will be required to access this system from other NetVault nodes on your network Password: Confirm Password: The installation now completes using the options entered (see Example 9-5). Example 9-5 Software installation Please wait while the software is installed... Copying 'Core files': copied Copying 'Data Plugin files': copied Copying 'Device control files': copied Copying 'GUI files': copied Copying 'Online help files': copied Copying 'Server files': copied Creating symbolic links: done Successfully installed '/usr/netvault6/packages/con1110.npk' Successfully installed '/usr/netvault6/packages/cpy1110.npk' Successfully installed '/usr/netvault6/packages/nvd1210.npk' Successfully installed '/usr/netvault6/packages/nvf1610.npk' Successfully installed '/usr/netvault6/packages/raw1410.npk' installed: 'TRUE' Will link to '/usr/netvault6/etc/startup.sh' Installed NetVault services Restarting NetVault services... ok Installation completed successfully. [root@diomede NetVaultDistribution]# \Key After successfully completing the installation, the product is ready to be configured and started. 350 Implementing IBM Tape in Linux and Windows

379 9.4 Configuring NetVault In this section, we will describe how to configure the IBM Other LTO models use a similar configuration method. Refer to the NetVault Administrator s Guide for general operational information. There are very few differences in the NetVault configuration between Linux and Windows These will be highlighted where necessary. The NetVault Configurator needs to be executed initially to verify the base NetVault configuration. In Windows 2000, select Start Programs NetVault6 to start the NetVault Configurator. In Linux, the NetVault configurator is started from the command line in Linux and requires a running X display. The command is: /usr/netvault6/bin/nvconfigurator You will see the panel in Figure Figure 9-11 NetVault Configurator We did not need to make any changes to any of the fields in the configurator; however, we did download the latest patch from the BakBone Web site: Chapter 9. Configuring BakBone NetVault on Windows and Linux 351

380 This patch included the latest library/device support and was distributed as a zip file, which we unpacked into a temporary directory. To load the patch, click the Install Software button. Figure 9-12 shows the beginning of the installation program. Figure 9-12 Update/plug-in installation program Enter the file name of the downloaded patch file, as in Figure Figure 9-13 Enter install file name The patch will be identified before installation, as in Figure 9-14 on page 353. Click Next to install the patch. 352 Implementing IBM Tape in Linux and Windows

381 Figure 9-14 Software identification window Configuring the IBM 3583 The library now needs to be identified to the NetVault server. For Windows, start the NetVault GUI by selecting Start Programs NetVault6 NetVault. For Linux, run the command /usr/netvault6/bin/nvgui. You will see the main administration panel for NetVault (Figure 9-15). Figure 9-15 Primary NetVault interface (NetVault GUI) Select the Device Management icon to open up the display in Figure 9-16 on page 354. The panel is empty, because we have not configured any devices yet. Select Add and then Add Library from the drop-down menu. Chapter 9. Configuring BakBone NetVault on Windows and Linux 353

382 Figure 9-16 Device Management The Device Management window will now be started (Figure 9-17 on page 355) with a list of all the discovered servers and clients. The servers and clients listed are those machines that are running the NetVault service. They will be listed as candidate machines that could potentially have a library. Select the server or client with the library to be added (DIOMEDE in our case), right-click, and select Open. 354 Implementing IBM Tape in Linux and Windows

383 Figure 9-17 Select library server The panel will then display any candidate libraries the server has detected (Figure 9-18 on page 356). We can see that the IBM 3583 displays as a Robotic Library, but is as yet unrecognized by the NetVault application. Now we need to select the compatible NetVault device. Right-click the library device and select it. Chapter 9. Configuring BakBone NetVault on Windows and Linux 355

384 Figure 9-18 Selecting the library device The NetVault application will now determine if the device exists as a supported library and will display a picture and type name for the device. Note the picture of the IBM 3583, as shown in Figure 9-19 on page Implementing IBM Tape in Linux and Windows

385 Figure 9-19 Displaying library device Ensure that the correct library device type is selected. We will now configure the appropriate tape devices. Select the Drive Selection tab (Figure 9-20 on page 358). You will notice that the library name is displayed in the Library Name field and two tape drive bays are already determined to exist in the library (in the Selected Drives panel). We will now identify these two tape drives. Right-click the server name and select Open. Chapter 9. Configuring BakBone NetVault on Windows and Linux 357

386 Figure 9-20 Selecting library devices The library entry will now be displayed with two unknown tape devices, indicated by the fact that no photo appears (Figure 9-21 on page 359). Right-click the first tape device and click Select. 358 Implementing IBM Tape in Linux and Windows

387 Figure 9-21 Selecting first device The NetVault application will now determine if the device exists as a supported tape device, and will display a picture and type name for the device (Figure 9-22 on page 360). Chapter 9. Configuring BakBone NetVault on Windows and Linux 359

388 Figure 9-22 Identifying the tape device If the drive is correctly identified and displayed (3580 in our case), select the second device for identification. To do this, increment the Select for drive bay counter on the right-hand side (see Figure 9-23 on page 361). 360 Implementing IBM Tape in Linux and Windows

389 Figure 9-23 Selecting another drive bay Identify the second drive using the same select process. We will now verify selections by selecting the Configure tab. Note that the library and drives now show up as configured devices. If the listing is correct, save the configuration and make it available to NetVault by clicking the Save icon in the top left-hand corner (Figure 9-24 on page 362). Chapter 9. Configuring BakBone NetVault on Windows and Linux 361

390 Figure 9-24 Verify library and tape selections Figure 9-25 on page 363 shows that the configuration has been successful and the library is now available to NetVault. 362 Implementing IBM Tape in Linux and Windows

391 Figure 9-25 Completion of library addition Now that the library is available, NetVault determines the status of the library and discovers the media. The results are displayed in the Device Management window (Figure 9-26). We can see that cartridges have been detected, including their barcode labels in Slots 2 and 7. Figure 9-26 Library status Chapter 9. Configuring BakBone NetVault on Windows and Linux 363

392 This ends the NetVault installation. You can now use the library for client backups. Refer to the NetVault documentation for information about how to set up clients. 9.5 NetVault NDMP plug-in The NetVault application includes support for the NDMP protocol. The NDMP protocol provides a mechanism for backing up and restoring data to Network Attached Storage (NAS) devices. By using an open network protocol (TCP/IP) and providing a well-documented API, this has allowed backup vendors to implement NDMP solutions for NAS devices. NDMP uses a client/server model to access library and tape devices managed by backup applications. The NAS device acts as an NDMP server, while the backup vendor provides an NDMP Client Plug-in. For the NetVault application, an NAS device is managed as a client, allowing the NAS device to access NetVault managed drives and libraries both locally and remotely Installation of NDMP Client We used the following hardware (Figure 9-27): Pentium server running Linux 7.1, Kernel 2.4 with BakBone NetVault V6.03 installed QLogic 2200F FC HBA Brocade SilkWorm Fibre Channel switch NetApps F760 filer running ONTAP 6.0.1R3/NDMP V3 IBM 3584 library with two Fibre Channel 3580 drives Linux NetVault Server with NDMP NAS Plugin NetApp F760 Ethernet LAN Fibre SAN Fibre IBM 2109 FC Switch LTO 3584 Fibre Figure 9-27 SAN lab environment The first step is to see if the NDMP plug-in is installed on the library server (the Pentium system with host name X342). Select Client Management from the Management Console (shown in Figure 9-15 on page 353). 364 Implementing IBM Tape in Linux and Windows

393 The Client Management window (Figure 9-28) displays the managed clients (on the left-hand side) and other machines available to become clients (on the right-hand side). Right-click the desired client (X342) and select Properties. Figure 9-28 Client Management Figure 9-29 shows that the NDMP Client Plug-in has already been installed. If it has not, then return to the Client Management window and select Install Software. Figure 9-29 Client Properties We can now identify the NetApp filer to the NDMP Client and commence doing backups. From the NetVault main window (Figure 9-15 on page 353), select Backup. The list of managed clients and servers displays, as in Figure 9-30 on page 366. Chapter 9. Configuring BakBone NetVault on Windows and Linux 365

394 Figure 9-30 NetVault Backup Double-click the x342 NetVault server and the backup properties will be displayed (Figure 9-31). Figure 9-31 Display backup properties Double-click the NDMP Client entry to display the NDMP Server configuration window (Figure 9-32 on page 367). Add the appropriate details for your NetApp filer. For the Name field, choose an arbitrary name for your NDMP system (for example, the host name). Enter the TCP/IP address in the Address field. You should leave the port at the default and enter in a user ID and password, which is valid on the box. The other fields can be left at the defaults. 366 Implementing IBM Tape in Linux and Windows

395 Figure 9-32 Configuring NDMP server After configuring the NDMP server, it will now be displayed under the NDMP Client entry (Figure 9-33). Figure 9-33 NetVault NDMP client The NDMP server NetApp has now been added and client backups and restores can be tested. To run a test backup, double-click the NDMP Client (Netapp). This displays the NDMP Backup Request window, as shown in Figure 9-34 on page 368. Enter the volume to be backed up, the dump level (0 in our example, as we are taking a full backup), and accept the default Data Block Size of 64 KB. All the other fields can use the default values. Click the OK button, then submit the job by clicking the traffic light icon, as shown in Figure Chapter 9. Configuring BakBone NetVault on Windows and Linux 367

396 Figure 9-34 NDMP backup request The data will now be backed up to a specified backup device using BakBone. 368 Implementing IBM Tape in Linux and Windows

397 10 Chapter 10. Configuring Arkeia on Linux This chapter describes the steps to configure Arkeia from Knox on Linux, using an IBM LTO library. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 369

398 10.1 Arkeia from Knox Software Arkeia greatly simplifies data protection by providing automated backup and recovery. It supports a wide variety of computers, operating systems, and storage devices. Arkeia is easy to install, quick to configure, and conveniently scalable from a simple network to a complex enterprise. Arkeia accommodates full and incremental backups, scheduled or on demand, and preserves directory structure, registry, symbolic links and special attributes. The system manages file system data, and with extension modules, provides online backup for Oracle databases. Arkeia uses multi-flow technology and client side compression, making it capable of backup speeds that could exceed the network's rated speed. Its unique transaction engine allows multiple backups and restores to be performed simultaneously with total reliability. In the case of network and system errors, Arkeia is designed to restart, recover, and survive. Arkeia's systems management facility allows prioritization of other processing activities while a backup is in progress, and leverages standard TCP/IP protocol to intelligently monitor network errors. Should a network error occur, Arkeia restarts the backup procedure from the point of interruption. Arkeia's centralized catalog keeps a full record of all data and metadata managed by the system. It appends the relevant part of the catalog onto each tape. In the event of complete backup server failure, the catalog can be rebuilt and the data recovered by using the fail-safe restore utility. For more information about the Arkeia product, go to their Web site: Arkeia supports both Ultrium 1 and Ultrium 2 generation drives Installing Arkeia In this section, we show the steps to configure Arkeia Version 4.2 on Linux with an IBM We used the following hardware (Figure 10-1): Intel server with Red Hat Linux 7.1 Server (Red Hat , Kernel UP). Adaptec LVD SCSI card. IBM 3583 SCSI attached. A single SCSI bus supported both the library controller and the two 3580 tape drives. SCSI Red Hat Linux Intel server IBM 3583 Figure 10-1 Linux Arkeia environment 370 Implementing IBM Tape in Linux and Windows

399 Installation preparation The preparation for installing Arkeia depends on whether your tape library is already installed. Existing LTO installation If your LTO drive was already installed on your server, check to see if the IBM drivers are being used. The IBM Ultrium drivers are not required for Arkeia. If you have already installed these, disable them, as described in 4.4.3, Uninstalling the Ultrium device drivers and utilities on page 211. New LTO installation If this is a brand new installation, first install the adapter card to Linux and load the drivers. This procedure is given in 4.3.1, Identifying and activating the SCSI controller on page 188. Shut down the server, physically cable the tape library, and reboot the system. Check the configuration of the devices, using the procedures in 4.3.2, Kernel compilation and installation checklist on page 191, and the following sections. All LTO installations Your drive and medium changer should now be available to the operating system using Linux native device drivers Package installation The following section gives the steps to install the Arkeia RPM (Red Hat Package Format) packages. Refer to the Arkeia Installation Manuals for specific information about disk and resource requirements. We are installing on a system called DIOMEDE. The Arkeia Red Hat 7.0 Linux Version 4.2 code level RPM package contains the following code (Example 10-1). Example 10-1 Package listing total rwxr-xr-x 1 root root Oct 16 17:41 arkeia-arkc i386.rpm -rwxr-xr-x 1 root root Oct 16 17:42 arkeia-client i386.rpm -rwxr-xr-x 1 root root Oct 16 17:43 arkeia-gui i386.rpm -rwxr-xr-x 1 root root Oct 16 17:43 arkeia-server i386.rpm The RPM packages can now be installed. The order of installation is client, server, and GUI. We installed the client, then server, then command line, then GUI packages (see Example 10-2). Example 10-2 Installing RPM packages [root@diomede Arkeia]# rpm -Uvh arkeia-client i386.rpm Preparing... ########################################### [100%] 1:arkeia-client ########################################### [100%] [root@diomede Arkeia]# rpm -Uvh arkeia-server i386.rpm Preparing... ########################################### [100%] 1:arkeia-server ########################################### [100%] [root@diomede Arkeia]# rpm -Uvh arkeia-arkc i386.rpm Preparing... ########################################### [100%] 1:arkeia-arkc ########################################### [100%] [root@diomede Arkeia]# rpm -Uvh arkeia-gui i386.rpm Preparing... ########################################### [100%] 1:arkeia-gui ########################################### [100%] [root@diomede Arkeia]# Chapter 10. Configuring Arkeia on Linux 371

400 The product is installed in the /usr/knox directory. The product is essentially self configuring using already defined system information for Arkeia default values, such as the server name. Verify that /usr/knox/nlp/admin.cfg has the correct server name (replace the entry with your own host name if required) and restart the NLSERVD daemon if necessary. Then start the Arkeia GUI. These steps are shown in Example Example 10-3 Arkeia configuration knox]# cd nlp nlp]# cat admin.cfg diomede.almaden.ibm.com nlp]# NLSERVD Another Nlservd is already running. Restarting it... nlp]# ARKEIA The GUI welcome window displays, as shown in Figure Authenticate with the Arkeia server by entering a valid Linux ID and password. Figure 10-2 Server authentication The main administration window displays (Figure 10-3 on page 373). 372 Implementing IBM Tape in Linux and Windows

401 Figure 10-3 Server administration window 10.3 Configuring the LTO library To define the LTO library to Arkeia, do the following: Install licenses. Define library. Define drives. Associate the drives with the library. First, install the product licenses. From the Server administration window, select Utilities License Management. The window in Figure 10-4 on page 374 displays. Fill in the license details for the server as provided from the vendor. The license values have been intentionally left blank. Chapter 10. Configuring Arkeia on Linux 373

402 Figure 10-4 Server license Install the license for the library (Figure 10-5). Figure 10-5 Tape library license After the license details have been added, the library, tape devices, and drive packs can now be configured. Select Devices Libraries Management from the Server administration window (Figure 10-3 on page 373). In the Libraries management window (Figure 10-6 on page 375), select New and fill in the appropriate details for the new library. The Library name field is arbitrary (we choose LTO), but the type and control device fields must correspond to the correct library type (IBM3583) in our case, and the Linux device name for the library changer (/dev/sg2). Use the Type drop-down to select the library type. 374 Implementing IBM Tape in Linux and Windows

403 Figure 10-6 Adding a new library We used the commands and utilities documented in 4.3.3, Identifying and accessing the LTO device on page 192 to determine the exact Linux device name. Click the green check mark box to add the library. It now appears in the panel on the right-hand side, and the log message shows it was successfully added (Figure 10-7). Figure 10-7 Library added The tape devices can now be added and associated with the library device. Select Devices Drives management from the Server Administration window (Figure 10-3 on page 373). Select New in the Drives management window (Figure 10-8 on page 376). Chapter 10. Configuring Arkeia on Linux 375

404 Figure 10-8 Drives management Enter an arbitrary name for the tape device name (we chose LTO_DRIVE1). Select the tape type from the Type drop-down list, as in Figure Figure 10-9 Drive type selection 376 Implementing IBM Tape in Linux and Windows

405 The rewind device corresponds to the Linux rewind device name for the drive, which is /dev/st0. We determined the device names by examining the dmesg boot message output (as described in 4.3.3, Identifying and accessing the LTO device on page 192). Enter this, as shown in Figure Figure Rewind device name Click the green check box to add the drive. It now appears in the panel on the right-hand side and the log message shows it was successfully added (Figure on page 378). Chapter 10. Configuring Arkeia on Linux 377

406 Figure Drive added Now select New to add additional drives or close the window to complete the task. We added our second drive, /dev/st1, and called it LTO_DRIVE2. Once all drives have been added, they need to be associated with the library. From the Server administration window, select Devices Libraries management. The library device should be displayed (LTO in our example, shown in Figure on page 379). You can use the graphics at the bottom of the window or right-click the library name to get a list of options for the library. We have used the pop-up menu and selected Drive options. 378 Implementing IBM Tape in Linux and Windows

407 Figure Library drive associations The window will contain a list of empty drive entries (Figure 10-13). We will now associate the drives we have added with the drive slots in the library. Figure Library drives Right-click the Drive number (1 first) and select Attach drive, as shown in Figure on page 380. Chapter 10. Configuring Arkeia on Linux 379

408 Figure Attaching drive A list of available drives will be shown for attachment (Figure 10-15). Select the drive LTO_DRIVE1 and click the green check mark box to associate the drive. Figure Drive selection The library and drive association has now been made and is displayed in Figure on page Implementing IBM Tape in Linux and Windows

409 Figure Library drive association Repeat the same process to associate the second drive LTO_DRIVE2 to Drive Number 2. This completes the basic configuration of the LTO drive for Arkeia. There are additional steps that will need to be performed to allow backups to occur: 1. Define drive packs. 2. Create pools. 3. Create tape labels. 4. Create save packs. The specific requirements for these tasks will be determined by the design requirements. Consult the Arkeia manuals for more details of these tasks and design considerations. Chapter 10. Configuring Arkeia on Linux 381

410 382 Implementing IBM Tape in Linux and Windows

411 Part 3 Part 3 Appendixes Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 383

412 384 Implementing IBM Tape in Linux and Windows

413 A Appendix A. IBM SAN Data Gateway Note: The IBM SAN Data Gateway (SDG) Router models 2108-R03 and 2108-G07 were withdrawn from marketing in September The SAN Data Gateway Integrated Module is no longer available as a feature in a new IBM The SAN Data Gateway features were withdrawn from marketing in October The information is this section is a reference for any client still using the SDG or an IBM 3583 with the integrated SDG. The IBM 2108 Storage Area Network (SAN) Data Gateway is a family of connectivity products that enable Fibre Channel connections to Ultra SCSI or SCSI-based storage or host systems. The IBM 2108 Model G07 SAN Data Gateway is a protocol convertor available with up to six short wave or two long wave Fibre Channel ports and has four Ultra SCSI Differential ports for device attachment. It supports attachment of the IBM LTO Tape Drives to Fibre Channel-capable IBM System p5, IBM ^ xseries, and other Intel-based servers running Microsoft Windows, and Sun UNIX servers. With the Virtual Private SAN capability, the SAN Data Gateway provides access control between host systems and storage devices across a SAN. The IBM 2108 Storage Area Network (SAN) Data Gateway Router connects Ultra SCSI and SCSI tape libraries to Fibre Channel environments. New or existing SCSI-based tape libraries can be attached to SANs or directly to host systems using an industry-standard Fibre Channel interface. The SAN Router is an easy-to-manage protocol converter that provides a single Fibre Channel port and two Ultra SCSI ports, either single-ended or differential. It supports Fibre Channel attachment of the IBM Netfinity and other Intel-based servers running Microsoft's Windows NT to IBM LTO Libraries. The SAN Data Gateway Integrated Module is a chargeable library feature that was available for the IBM it is functionally equivalent to the separate SAN Data Gateway models. For the rest of this section, we will use SDG to refer to any of these products interchangeably unless otherwise indicated. The SDG provides the ability for SCSI devices in the library to connect into a SAN. The SDG can run at either 1 Gbps or 2 Gbps port speeds, providing compatibility for older (1 Gbps) devices, as well as support for higher speed devices. Two Fibre Channel ports make multiple Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 385

414 attachments easy and support failover redundancy. The SDG has two Fibre Channel ports and four SCSI ports. The Fibre Channel ports have 2 Gigabit, SC-style shortwave multimode Gigabit Interface Converter (GBIC) modules. The Fibre Channel ports can communicate reliably at distances of up to 300 m, over 50 µm multimode-optical fiber cables. The four SCSI ports are Ultra2, low voltage differential (LVD), with VHDCI-style connectors (Very High Density Cable Interconnect). The IBM 3583 with Ultrium 1 drives allows a mixture of up to six direct attached SCSI LVD or HVD drives. If you are using the integrated SAN Data Gateway to enable FC connectivity, then up to six LVD or HVD drives can be installed. The SAN Data Gateway Integrated Module cannot support a mixture of HVD and LVD drives. 386 Implementing IBM Tape in Linux and Windows

415 Connecting tape drives to a SDG The data transfer throughput for an IBM SAN Data Gateway 2108 G07 is 100 MB/sec. For a SAN Data Gateway 2108 R03, the data transfer throughput is about 50 MB/sec. Although it is possible to connect LTO Ultrium 2 SCSI tape drives to a SAN Data Gateway, it makes more sense to use native Fibre Channel tape drives. Our suggestions for achieving the best effective data rate with LTO Ultrium 1 tape drives on the SDG are: Avoid daisy-chaining drives. If this is necessary (for example, if there are more than three drives to be connected), then do not connect more than two drives per SCSI Bus. If possible, do not install more than two drives on a 2108 R03, or four drives on a 2108 G07. Figure A-1 shows an example of a connection with SDG and a The 3583 contains six LTO drives. Each SCSI connection has two LTO drives. The SCSI medium changer is attached to its own SCSI bus. The server is connected to the SDG using two HBAs and FC ports. If you have more drives to attach, you can move the SCSI medium changer to share any of the SCSI ports on the SDG Lxx Server Medium Changer F E Fibre Channel Aapter SDG Module D C B Tape Library with 6 drives A Figure A-1 Example of a connection with SDG WWN of SDG Since it is a SAN device, each SDG has its own World-Wide Name (WWN). Getting the WWN of the SDG Telnet to the SDG and use the command fcshownames (Example A-1). Example: A-1 WWN of SDG Router > fcshownames Ctlr : PCI Addr : ISP : Node : Port Id : Bs Dv Fn : Type : Name : Name : : 2200 : ff5 : ff Appendix A. IBM SAN Data Gateway 387

416 You can also use the SAN Data Gateway Specialist (Figure A-2) to display this information. See Install and use the SDG Specialist on page 391 for more information about the SAN Data Gateway StorWatch Specialist. Figure A-2 WWN of the SDG SAN Data Gateway setup The SDG maps addresses across and among the different interfaces and preserves the persistency of the address maps across startups of systems, devices, and the SDG. Attention: Sharing the gateway between disk and tape products is not supported. You can connect more than one host to an SDG. By default, all hosts can access all target devices. In practice, you want to restrict this access, unless you are sure that the different host operating systems and applications will correctly handle simultaneous access to the same device by multiple servers. Otherwise, device operation failures and potential data integrity problems can occur. To avoid these, you can use zoning (as discussed in 5.2, Zoning on page 232), use intelligent applications that can handle the device sharing (such as tape library sharing with IBM Tivoli Storage Manager), or use these options available with the SDG: Channel zoning option: You can set the desired access between SAN connections and individual SCSI channels. Virtual Private SAN (VPS) or LUN masking: You can set the desired access permissions between hosts on the SAN connections and individual LUNs. Note: VPS is only available as an option for the IBM 2108 G07, and not for the IBM 2108 R03 or the Integrated SAN Data Gateway Module for the Special software is also required. 388 Implementing IBM Tape in Linux and Windows

417 Basic setup In the following section, we give an overview of: The basic setup of the SDG The installation and usage of the StorWatch SDG Specialist How LUN mapping works How to use channel zoning The Virtual Private SAN For more information about the SAN Data Gateway, refer to these publications: 2108 Model G07 Installation and User's Guide, SC Model R03 Installation and User's Guide, SC We briefly summarize the main steps for setting up the SDG; detailed information is provided in the installation and user guides listed in the previous section: 1. After installing the hardware, set up a connection between the SDG s serial port and a serial port on a PC, using the supplied null modem cable and a PC terminal program, such as Netterm or Hyperterm. Use the following parameters to configure the terminal session: Bits per second: Data bits: 8 Parity: None Stop bits: 1 Flow Control: Xon/Xoff If you are connected, press Enter and you will get a response from the SDG, as shown in Figure A-3. Figure A-3 Connected to the SDG 2. We suggest the following basic commands sequence to install a new or an already used SDG: a. initializebox This restores the factory defaults by deleting all configuration files, including persistent address map and VPS databases, and then a restart is needed. b. ethaddrset Use the ethaddrset command to set or change the IP address and network mask (if required) of the SAN Data Gateway: Router > ethaddrset Appendix A. IBM SAN Data Gateway 389

418 c. ethenable The ethenable command alters the start parameters of the SDG Router, enabling the Ethernet port. This command does not take effect until the SDG Router is restarted. d. useradd "admin", password This adds a user and password to the password file. The user name variable must be three to 80 characters. The password variable must be eight to 40 characters. Here you create your own user ID: Router > useradd nancy, password e. sethost X,YYY (where port X can be 1,4,2,5,3,6 and YYY can be solaris, nt, hpux, aix, as400, and so on) The sethost command sets the operating system type for the specified SAN interface. This provides some customization in the way the SDG is presented to the particular operating system. If the port is 0, the change applies to all SAN connections; otherwise, the host type is applied only to the SAN connection on the specified interface. The default setting is NT. Currently, the operating system can be specified as NT, AIX, NetWare, HP-UX, AS/400, or Solaris. You have to put the host type in double quotes, as shown in Example A-2. Example: A-2 sethost for FC 4 to AIX Router > sethost 4,"aix" value = 0 = 0x0 Note: Ports 1 and 4 belong to first FC Card, ports 2 and 5 to the second FC Card, and ports 3 and 6 to the third FC Card inside the SDG. 3. reboot A reboot makes the above changes effective. You can now connect to the SDG via a telnet session, using the Ethernet address you defined. 4. fcshowdevs and fcshownames The fcshowdevs command displays information about the devices that are accessible from each Fibre Channel interface. The display shows the LUN that the SDG has assigned to each device, the SCSI Channel that the device is attached to, the actual SCSI ID and LUN of the device, and the vendor, product, revision, and serial number of the device. The fcshownames command displays the node and port names (addresses) of the Fibre Channels. If the output does not meet your physical installed devices then execute scsirescan and reboot. Collect the output from fcshowdevs and fcshownames for further use (fcshownames shows you the WWN, the assigned LUN, and the serial number of the tape drives; see Example A-3 on page 391). 390 Implementing IBM Tape in Linux and Windows

419 Example: A-3 Output of fcshowdevs and fcshownames Router > fcshowdevs FC 1: LUN Chan Id Lun Vendor Product Rev SN PATHLGHT SAN Router 32aC IBM ULT3583-TL 2.50 IBM IBM ULT3580-TD1 16E IBM ULT3580-TD1 16E value = 6 = 0x6 Router > fcshownames Ctlr : PCI Addr : ISP : Node : Port Id : Bs Dv Fn : Type : Name : Name : : 2200 : ff5 : ff5 Install and use the SDG Specialist With the IBM SAN Data Gateway Specialist, you can manage multiple SDGs from any location on your network. The Specialist consists of two Java applications, but it is a client-server application, not Web-based like the TotalStorage Specialist for the IBM 2109 Switch. You can install the server on a single system on your network and manage connections between multiple clients and multiple SDGs. Also, you can install the server and client on one single system. The installation program allows you to install the appropriate components on your target host system. The Java runtime environment is also installed when you install the application components. The server does not need to be used as a client, but it can be. The sever needs network access to the SDGs to be managed. The client system can be located anywhere as long as it can connect to the server system using TCP/IP. The SDG StorWatch Specialist is available for AIX, HP-UX, Windows, and Sun Solaris. One installation image is provided for each operating system, containing both the server and the client code. During installation, you can choose which of them you want to install. The client and server do not need to be on the same operating system. This means that you can install the server, for example, on AIX, HP-UX, or Sun Solaris, and use the client on Windows 2000 or on Windows NT. You can download the latest version of the SDG Specialist from: ftp://ftp.software.ibm.com/storage/san/2108/ Install on Windows Download the latest version and the readme file for Windows from the FTP site above. Execute the downloaded file to start the installation. During installation, you can choose to install the server or the client (see Figure A-4 on page 392). Appendix A. IBM SAN Data Gateway 391

420 Figure A-4 Install of the SDG StorWatch Specialist As always, check the readme file for the latest information. Start the server In order to connect to a SDG, you must first start the server application. To start the server on Windows, select Start Programs IBM StorWatch SAN Data Gateway Specialist Server. This opens a DOS-window (Figure A-4). Note that when starting the Specialist for the first time, you will see additional messages to subsequent invocations. Example: A-4 SDG Specialist: Server application IBM StorWatch SAN Data Gateway Specialist Server Version Build 0003 Server Start Copyright 2001 Advanced Digital Information Corporation All rights reserved. Centralized error handling initiated Log Filename = SanmgrServerLog00002.txt SNMP Initialized NetSessionManager instantiated Trying to start RMI Registry on Port in Range (1099,1109) RMI registry started from within server, Host , Port 1099 Checking for other applications bound with URL rmi:// :1099/starfish No other Server URL bound in registry, OK to proceed Trap receiver started on UDP Port 162 Server logging on Server-to-Gateway heartbeat started Server-to-Client heartbeat started Ready. Waiting for commands rmi:// :1099/starfish : Next, you can start the client. 392 Implementing IBM Tape in Linux and Windows

421 Start the client To start the client on Windows, select Start Programs IBM StorWatch SAN Data Gateway Specialist Client. Enter the TCP/IP address of the server where the SDG Specialist Server application is running (Figure A-5). Note that if you are running the server on the same system as the client, you will not receive this prompt, as the client automatically attempts to connect to a local server. Figure A-5 SDG StorWatch connect to server Now you will be asked for a user name and password (Figure A-6). The default entries are: User name: StorWatch Password: StorWatch Both values are case sensitive (see Figure A-6). Figure A-6 SDG StorWatch logon Enter the TCP/IP address or host name of the SDG that you want to manage (Figure A-7). Figure A-7 Connect to SDG Install firmware on the SDG After you are connected to the SDG, you should check the firmware level, which is printed in the right-side window. Check this FTP site in the Downloads section to see if there is a newer version available: ftp://ftp.software.ibm.com/storage/san/2108/ If so, download the file the package client system and update the firmware on the SDG. Appendix A. IBM SAN Data Gateway 393

422 Attention: All I/O must be halted while updating the firmware. Select the SDG to be updated in the left-side window. Then select, from the menu, Controls Update Firmware (Figure A-8). You will be asked for the file name of the new firmware. After you have selected the downloaded file, you are asked to confirm that you want to update now. Answer with OK if all I/O activity to the SDG is stopped. Figure A-8 Install firmware on the SDG SCSI settings If you want to view or change the SCSI settings, first select the desired SCSI Channel on the left side of the client display. Then select Controls SCSI Channel from the menu (see Figure A-9 on page 395). 394 Implementing IBM Tape in Linux and Windows

423 Figure A-9 Select the SCSI option If you update the SCSI device firmware, the Specialist does not display the new firmware version until the SDG Router has issued a SCSI inquiry. The SCSI inquiry occurs when it rescans the SCSI buses. If you want to rescan the SCSI bus, select the button Re-scan SCSI Bus (Figure A-10). Figure A-10 SCSI Channel parameters FC settings If you want to view or change the FC options, first select the desired FC Channel on the left side of the client display. Then select Controls Fibre Channel (see Figure A-11 on page 396). Appendix A. IBM SAN Data Gateway 395

424 Figure A-11 Select the Fibre Channel options On the Fibre Channel Parameter window, you can change to settings that are valid for the selected FC port. You can change the host type to match it for your configuration. The connection options should be point-to-point or point-to-point preferred if the SDG is connected to a switch. If the SDG is directly connected to a server, both server HBA and SDG need to have the same connection options (see Figure A-12). Figure A-12 Fibre Channel parameters 396 Implementing IBM Tape in Linux and Windows

425 SDG LUN mapping In SCSI terminology, a tape drive or a disk drive is attached to a bus and has a unique address on that bus. There are three parts of the address in a conventional SCSI ID: Bus (or channel) Target ID LUN A simple case of two tape drives attached to a single bus is shown in Figure A-13. Server SCSI Aapter SCSI Drive 0 SCSI ID 0 LUN 0 Drive 1 SCSI ID 1 LUN Lxx Control path enabled smc A SCSI ID 0 LUN 1 B Medium Changer Figure A-13 Basic SCSI connection to a system This configuration has a device map (from the host point of view) that looks as shown in Table A-1. Some tape library devices, such as the 3584, support LUNs for the devices; the tape drive is addressed as LUN 0; the SCSI Medium Changer (smc) is available as LUN 1. Table A-1 Target ID and device mapping - Native SCSI Target ID LUN Device 0 0 Drive smc 1 0 Drive 1 If a product like an SDG is placed between the system and target devices, the addressing has another layer. This is because the targets (the tape drives) are not directly attached to the host, but are connected to a SCSI adapter installed in the gateway instead. Figure A-14 on page 398 shows the device mapping with the additional layer due to the SDG. Appendix A. IBM SAN Data Gateway 397

426 Server FC Aapter FC SCSI Drive 0 SCSI ID 0 LUN 2 Drive 1 SCSI ID 0 LUN 4 SDG SCSI Id 0 LUN Lxx Control path enabled B smc SCSI ID 0 A LUN 3 Medium Changer Figure A-14 SDG attached through Fibre Channel - Host view The system now only has a single target ID (target 0 in this case) directly attached to the SAN Data Gateway. The gateway forwards commands to and from its targets, the tape drives. However, there is a need to map the devices (tapes) so the host system can use them. This is achieved by using another layer of mapping (LUNs). The device map might now look like Table A-2 from the host perspective. Table A-2 Device map from host perspective with SDG Target ID LUN Device 0 0 SAN Data Gateway 0 2 Drive smc 0 4 Drive 1 Note that LUN 0 points to the SDG. This allows you to send commands to control the gateway. This is referred to as the Command and Control Interface. Tape drives are always assigned an even LUN number. If a control path is enabled for this drive, its LUN is one higher than the drives. The odd-assigned LUN number that follows the tape-drive even number is reserved for the medium changer. This algorithm has been chosen for the best compatibility with existing applications and operating systems. The medium changer in a 3583 has its own SCSI ID, but will still be assigned an odd LUN number. If the resulting map is not suitable for your environment, you can edit the mapping done by the SDG with the Specialist. First select your desired SDG, then select Controls Device Mapping, as shown in Figure A-15 on page Implementing IBM Tape in Linux and Windows

427 Figure A-15 Select Device Mapping The current device mapping displays, as in Figure A-16. Devices that have already been entered into the persistent device map or devices that were automatically assigned by the SDG are shown in black type on the left. The assigned LUN for each device is shown in the left-most column. On the left side, you see devices that are currently not assigned. You can delete a drive from the right side by dragging it to the Recycle Bin icon. Figure A-16 Device Mapping You can easily change this configuration by dragging and dropping. Select the device that you want to move to a different LUN. Hold your left mouse button and move the device to an empty LUN. After you have made any changes, you need to reboot the SDG for the changes to take effect. Appendix A. IBM SAN Data Gateway 399

428 Access control by channel zoning Select Controls Access Options Channel Zoning (see Figure A-17) to configure zones to restrict access between SAN connections and SCSI channels. The default settings allow all SAN connections to access all SCSI channels. Figure A-17 Select Channel Zoning When you select this menu option, a pop-up window displays the current channel zoning settings. Figure A-18 shows the settings for a gateway that has two SAN connections and four SCSI channels. Currently only SCSI Channel 3 and SCSI Channel 4 are assigned to FC 1 and FC 2. Clear the check marks or put in additional check marks by clicking in the boxes to create restricted access zones for the desired SAN connections and SCSI channels. All combinations are possible. Figure A-18 Channel Zoning Settings Access control by Virtual Private SAN (VPS) Channel zoning provides access control between ports. While channel zoning provides control of paths between host adapters and SCSI storage ports, it does not limit access to specific devices (LUNs) within the storage system. Virtual Private SAN (VP SAN) provides LUN masking to limit access between host adapters and LUNs attached to SAN Data Gateway SCSI ports. The SDG Specialist provides the tools to define SDG channel zoning, 400 Implementing IBM Tape in Linux and Windows

429 the VP SAN LUN-masking, and control that host systems have access to specific storage devices. VPS is applicable mainly in disk environments, so we do not discuss it further here. It is also not available for the Integrated SAN Data Gateway Module for the You can find more information about VPS in IBM TotalStorage: Implementing an Open IBM SAN, SG Appendix A. IBM SAN Data Gateway 401

430 402 Implementing IBM Tape in Linux and Windows

431 B Appendix B. SNMP setup This appendix describes setting up SNMP on the IBM TotalStorage 3582 Tape Library, IBM TotalStorage 3583 Tape Library, and IBM TotalStorage 3584 Tape Library. Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 403

432 Simple Network Management Protocol (SNMP) alerts Occasionally, the LTO library may encounter a situation that you want to know more about, such as an open door that causes the library to stop. The IBM U, 3582, 3583, and 3584 libraries provide a standard TCP/IP protocol called Simple Network Management Protocol (SNMP) to send alerts about conditions (such as an opened door) over a TCP/IP LAN network to an SNMP manager. These alerts are called SNMP traps. Using the information supplied in each SNMP trap, the monitoring server (together with client-supplied software) can alert operations staff of possible problems or operator interventions that occur. Many monitoring servers (like Tivoli NetView ) can be used to send or pager notifications when they receive an SNMP alert (for more information, see your Tivoli NetView documentation or the manuals for your network management application). The monitoring server must be loaded with system management software that can receive and process the trap, or the trap is discarded. SNMP supports a get/get-response mechanism for an operator to gather more information about a problem or query the library about its current status. A get is a request for information about the library that the operator issues through a monitoring server and that is transmitted by SNMP. A get-response is the information that is provided in response to the get. This type of support generally requires an up-to-date library Management Information Base (MIB). The library s MIB contains units of information that specifically describe an aspect of a system, such as the system name, hardware number, or communications configuration. The SNMP connection requires an Ethernet port; therefore, your library must have the RMU feature (for IBM 3581, 3582 and 3583) or Ethernet port (for IBM 3584) installed. SNMP is itself a sub-protocol of TCP/IP and is based on a hierarchical structure represented by strings of object identifiers or OIDs. Much of the data required by network managers is mapped to instances of the OIDs. Standard values are included in higher levels of the structure, providing a standard for identifying those data. Brand-specific extensions are provided by the manufacturers. These standard and proprietary OID collections are called Management Information Bases (MIBs). The specification for SNMP, contained in RFC 1157, is available at: ftp://ftp.isi.edu/in-notes/rfc1157.txt The IBM 3581, IBM 3582, and IBM 3583 have the SNMP monitoring function included in the RMU module. The RMU supports SNMP Version 2.0, and can act as an SNMP server, responding to SNMP requests and generating SNMP traps. An internal library serial interface enables the RMU to acquire TapeAlert 3.0 compatibility information from the drives and to send this information to an SNMP server. In the event of a power loss, the RMU will detect the loss and generate an SNMP trap for notification. The IBM 3584 has the SNMP support included in the FCA (frame controller assembly, which is required for at least the L-Frame). The FCA must have Ethernet Support (FC #1660) for using the SNMP function. For redundancy reasons, the SNMP function uses all FCAs with Ethernet support. Up to five different SNMP managers can be configured to receive trap events. The 3584 also support the get/get-response mechanism. For all SNMP-capable LTO tape libraries, you need an Ethernet LAN connection to the SNMP manager to trap SNMP events. We described how to configure the LAN connection for these libraries in 3.8.1, IBM U Tape Library Specialist on page 151; 3.8.2, IBM 3582 Tape Library Specialist on page 154, 3.8.3, IBM 3583 Tape Library Specialist on page 157, and 3.8.4, IBM 3584 Tape Library Specialist on page Implementing IBM Tape in Linux and Windows

433 Configuring SNMP for the IBM 3582 To configure and activate SNMP event monitoring for the IBM 3582, use the Ultrium Tape Library Specialist panels. You cannot use the Operator panel to configure this function. From the main specialist in the black column at the left hand side of the panel, select SNMP MIB. The window shown in Figure B-1 appears. Figure B-1 IBM 3582 Tape Library Specialist: SNMP MIB download As described in the text of the window, the MIB file is a specific configuration file for the SNMP environment with the information for the IBM Download the file to the SNMP management server. If you are running Tivoli NetView on this server, you should store the file in the directory \usr\ov\snmp_mibs. You will then load this file to your SNMP manager, using the specific application s process. Go to the Specialist Configuration panel. In the SNMP Configuration section at the lower left side of the panel, enter the TCP/IP address and other related parameters for the SNMP server, and make sure the Alerts Enabled drop-down is set to ON, as shown in Figure B-2 on page 406. Appendix B. SNMP setup 405

434 Figure B-2 IBM 3582 Ultrium Tape Library Specialist: Configuring SNMP Click the Submit button to apply the changes. A confirmation panel appears. Click ENTER to confirm the updates. After you have configured the RMU to send SNMP alerts to the SNMP server, configure your SNMP monitoring product (like Tivoli NetView) to use the MIB-supplied file and to monitor the events. Configuring SNMP for the IBM 3583 To configure and activate SNMP event monitoring for the IBM 3583, use the Ultrium Tape Library Specialist panels. You cannot use the Operator panel to configure this function. From the main specialist panel (Figure on page 160), in the black column on the left-hand side of the panel, select SNMP MIB. The window shown in Figure B-3 on page 407 appears. 406 Implementing IBM Tape in Linux and Windows

435 Figure B-3 IBM 3583 Ultrium Tape Library Specialist: SNMP MIB download As described in the text of the panel, the MIB file is a specific configuration file for the SNMP environment with the information for the IBM Download the file to the SNMP management server. If you are running Tivoli NetView on this server, you should store the file in the directory \usr\ov\snmp_mibs. You will then load this file to your SNMP manager using the specific application s process. Go to the Specialist Configuration panel. In the SNMP Configuration section on the lower left side of the panel, enter the TCP/IP address and other related parameters for the SNMP server, and make sure the Alerts Enabled drop-down is set to ON, as shown in Figure B-4. Figure B-4 IBM 3583 Ultrium Tape Library Specialist: Configuring SNMP Appendix B. SNMP setup 407

436 Click the Submit button to apply the changes. A confirmation panel appears. Click ENTER to confirm the updates. After you have configured the RMU to send SNMP alerts to the SNMP server, configure your SNMP monitoring product (like Tivoli NetView) to use the MIB-supplied file and to monitor the events. An example of the Tivoli NetView panel is shown in Figure B-5. We can see our tape drive BAVARIA discovered as a node. Figure B-5 Tivoli NetView SNMP monitoring Tip: For more information about NetView, see the redbook Tivoli NetView 6.01 and Friends, SG Configuring SNMP for the IBM 3584 In general, the IBM 3584 library generates SNMP traps when it detects TapeAlert error conditions. Additionally, the library also generates SNMP traps under certain non-error conditions. They are generated under the following non-error conditions: The I/O station is full for over an hour. The logical library is full for over an hour and contains no empty storage slots. The I/O station door is open for an extended period of time. There are no LTO Ultrium or 3592 Cleaning Cartridges in the library (0 cleanings remain on the LTO Ultrium Cleaning Cartridges in library). An LTO Ultrium or 3592 Cleaning Cartridge has expired (the number of cleanings that remain on the cartridge has decreased to 0). 408 Implementing IBM Tape in Linux and Windows

437 You can enable SNMP and change the settings on the 3584 Operator panel dialog or by using the IBM 3584 TotalStorage Specialist. The IBM 3584 sends the SNMP traps over all configured Ethernet ports. If using more than one Ethernet port, then you will also receive more than one SNMP trap for one single failure. Enable SNMP traps using the Operator panel From the library s Activity Operator panel, click MENU, then Settings Network SNMP. To enable or disable SNMP Traps, click up or down to highlight Enable/Disable SNMP Traps and press ENTER. The Enable/Disable SNMP Traps panel displays with the current state of SNMP Traps (Figure B-6). Click the up or down arrow keys to specify ENABLED or DISABLED for SNMP Traps. The SNMP Traps panel redisplays the new setting. To accept the new setting, press ENTER. To return to the previous panel, press BACK. Figure B Operator panel: Enable/disable SNMP Traps Some SNMP monitoring applications only support Version 1 SNMP traps, while others only support Version 2 traps. The IBM 3584 supports both Version 1 and Version 2c. To send a different version of traps, select V1 /V2 on the SNMP Menu. The V1 / V2 Traps screen displays the version of the traps that were last sent by the SNMP agent. To change the setting press up or down to specify the version of the trap (Figure B-7), then press ENTER. The screen redisplays with the new version of the trap. To accept the new setting and return to the previous panel, click BACK. Figure B Operator panel: V1/V2 traps Appendix B. SNMP setup 409

438 To view or change the destination IP address of a monitoring station to which SNMP alerts are sent, choose Destination IP Addresses from the SNMP menu. Then press UP or DOWN to specify the destination IP address that you want to view or change (Figure B-8), then press ENTER. You can have the library send the SNMP traps to up to five different monitoring station. Figure B-8 IBM 3584 Operator panel: Destination IP address The Set Destination IP Address panel displays with the current value of the destination IP address you specified (Figure B-9). Click UP or DOWN to change to the value that you want, then click ENTER. The panel redisplays with the new destination IP address. To accept the new setting and return to the previous panel, click BACK. Figure B-9 IBM 3584 Operator panel: Set destination IP address To view or change the community name, on the SNMP Menu, click UP or DOWN to highlight Community Name and click ENTER. The Community Name panel displays with the current password (Figure B-10 on page 411). To change the password, click UP or DOWN to specify the character that you want and click ENTER. Repeat this operation for the following characters. When you are done, the library displays the message Updating Community Name and the update of the password begins. When the update is finished, Community Name change displays. Click ENTER to display the new password. To accept the new setting and return to the previous panel, click BACK. 410 Implementing IBM Tape in Linux and Windows

439 Figure B-10 IBM 3584 Operator panel: Set community name To use the Operator panel to send a test SNMP trap and ensure proper connection of the IBM 3584, do the following: From the library s touchscreen, select MENU Settings Network SNMP Send a Test Trap ENTER. The library displays the message A test trap with the text This is a test SNMP trap. has been sent to all defined target hosts. Click ENTER to continue. The library sends an SNMP trap to all SNMP IP addresses at the remote port that you specified. The trap contains the machine type, model number, and serial number of the library, as well as other fields. For more information about SNMP traps, see the IBM TotalStorage UltraScalable Tape Library 3584 Introduction and Planning Guide, GA Enable SNMP traps using Tape Library Specialist From the Web Specialist, select Manage Access SNMP Settings. Select the trap version (either SNMP V1 or SNMP V2c; see Figure B-11 on page 412). Some SNMP monitoring applications only support V1 SNMP traps, while others only support V2 traps. The IBM 3584 supports both V1 and V2c. Appendix B. SNMP setup 411

440 Figure B-11 IBM 3584 Specialist: Enabling SNMP Next, enter the destination SNMP monitoring server. Up to five SNMP monitoring servers can be defined. Select SNMP Destinations at the Specialist and enter the IP address(es) and port(s) of any SNMP monitoring server(s) to which you want to send SNMP alerts. Click Apply to accept the information (see Figure B-12). Figure B-12 IBM 3584 Specialist: SNMP destinations 412 Implementing IBM Tape in Linux and Windows

441 After you have configured the IBM 3584 to send SNMP alerts to the SNMP server, configure your SNMP monitoring product (like Tivoli NetView) to monitor the events. The SNMP monitoring product needs the library Management Information Base (MIB) for interpreting the SNMP traps; otherwise, you have to interpret the SNMP traps manually. information about how to interpret the SNMP traps manually is in the IBM Total Storage UltraScalable Tape Library 3584 Operator Guide, GA The MIB contains units of information that specifically describe an aspect of a system, such as the system name, hardware number, or communications configuration. To obtain the MIB for the IBM 3584, visit this URL: ftp://ftp.software.ibm.com/storage/358x/3584/ For Windows, select 3584mib.zip; for UNIX, select 3584mib.tar. Download the MIB and load it into your management application. Follow the information provided by your SNMP monitoring product to receive SNMP traps from the IBM As an example, we show how to configure IBM Tivoli NetView to receive SNMP traps from the IBM First, create a new object on your NetView console. Enter an object name and a label name (see Figure B-13). Figure B-13 Tivoli NetView: Create new object Next, select the Other tab and specify the host name, the IP address of the IBM 3584, and the subnet mask (see Figure B-14 on page 414). Before you can create this new object, you have to verify the connection. Click the Verify icon for that purpose. Appendix B. SNMP setup 413

442 Figure B-14 NetView: Create new object On the NetView console, you can browse the network segment to which your library belongs. The color of the icon indicates the status of the library. See Figure B-15 for an illustration of several libraries with different statuses. Figure B-15 NetView: Browse network segment 414 Implementing IBM Tape in Linux and Windows

443 By choosing the properties of one object (one library) and selecting the event tab you can see all SNMP traps received by NetView (see Figure B-16). Figure B-16 NetView: SNMP traps If you double-click one of these SNMP traps, you will see a detailed description of the reason why the library sent an SNMP trap. In most cases, depending on the failure, you also get suggestions as to what to do to resolve the failure (see Figure B-17). Figure B-17 NetView: Detail description of 3584 SNMP trap Appendix B. SNMP setup 415

444 Enabling or disabling SNMP requests SNMP supports a get and get-response mechanism for an operator to gather more information about a problem or to query the library about its current status. A get is a request for information about the library that the operator issues through a monitoring server and that is transmitted by SNMP. A get-response is the information that is provided in response to the get request. This type of support generally requires an up-to-date library Management Information Base (MIB). The library s MIB contains units of information that specifically describe an aspect of a system, such as the system name, hardware number, or communications configuration. In addition to the IBM 3584 MIB, you also have to load the Storage Networking Industry Association-Storage Media Library (SNIA-SML) MIB into your SNMP monitoring product. To obtain the MIB for the IBM 3584, visit this URL: ftp://ftp.software.ibm.com/storage/358x/3584/ To enable SNMP requests, use the Operator panel or use the IBM 3584 Tape Library Specialist. From the Web Specialist, select Settings SNMP Settings and enable SNMP Requests, as shown in Figure B-18. Figure B-18 Enable SNMP request with IBM 3584 Specialist You can now use SNMP to monitor your library. Here are some examples created with Tivoli NetView: To know how many drives are present in the library, use your monitoring server to issue an SNMP get request on the object numberofmediaaccessdevices.0. To get a list showing the status of all of the drives in the library ordered by element address, issue an SNMP get request on the objects mediaaccessdevice-availability Implementing IBM Tape in Linux and Windows

445 through mediaaccessdevice-availability.n, where n is the number returned by numberofmediaaccessdevices.0 (see Figure B-19). Figure B-19 SNMP Request: Drive status To obtain a list of all cartridges in the library, issue an SNMP get request on the object numberofphysicalmedias. This indicates how many cartridges are present in the library (see Figure B-20 on page 418). Issue an SNMP get request on the objects physicalmedia-physicallabel.1 through physicalmedia-physicallabel.n, where n is the number returned by numberofphysicalmedias. This gives a list of the physical label (VOLSER) of all cartridges in the library. You may also use, depending on your SNMP monitor product, the subtitle physicalmediaentry (see Figure B-21 on page 419) to get the status and the VOLSER of all cartridges. Appendix B. SNMP setup 417

446 Figure B-20 SNMP request: Number of all physical cartridges 418 Implementing IBM Tape in Linux and Windows

447 Figure B-21 SNMP request: List of all physical media Note: As of the time of writing, a few SNMP requests were implemented. More SNMP requests will be implemented in the future. Check for updates on the IBM 3584 library firmware and MIB files on: ftp://ftp.software.ibm.com/storage/358x/3584/ Appendix B. SNMP setup 419

448 420 Implementing IBM Tape in Linux and Windows

449 C Appendix C. Additional information This appendix provides some additional information that is useful when implementing IBM LTO tape drives and libraries. The topics are: Guidelines for booting SAN Data Gateway and FC hosts Some performance considerations for tape devices Tivoli Storage Manager tape drive and library commonly used commands EMC Legato NetWorker autochanger maintenance commands Using ntutil and IBMtapeutil to verify correct device attachment Troubleshooting considerations Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 421

450 Rules for booting SAN Data Gateway and FC hosts Device access problems sometimes occur when it is necessary to shut down the IBM SAN Data Gateway. To avoid losing access to your FC devices when a shutdown is required, the SAN Data Gateway and its attached devices must be booted in a specific order. Rebooting is required after updating firmware and when adding or removing SCSI devices. The following procedure describes the recommended boot order, and is also applicable to the SAN Data Gateway Router. Attention: You must stop all I/O between the host and SCSI devices before rebooting the SAN Data Gateway. 1. SCSI devices Turn on the SCSI devices first. All SCSI devices attached to the SAN Data Gateway (SDG) must be turned on before turning on or rebooting the SDG. 2. SAN Data Gateway (SDG) The SDG scans the SCSI buses when it is booting. If you add or remove SCSI devices after the SDG has booted, it will not automatically detect the changes. You can reboot the SDG using the StorWatch SAN Data Gateway Specialist client, from a telnet session or a serial terminal session. You can also use the scsirescan command to scan the SCSI channels. 3. Fibre Channel hosts Before turning on or restarting hosts that are connected via Fibre Channel to the SDG, you must wait until the SDG has finished booting, as indicated by the Ready light on the front panel blinking at a rate of about once per second. Although some operating systems may provide software methods that allow SCSI devices to be dynamically added or removed after the host has booted, we highly recommend that you reboot the host to ensure reliable operation. If you update SDG firmware, you must reboot the SDG to use the new firmware. We highly recommended that you also reboot the host to ensure compatibility with any new firmware features or functions. If you update SCSI device firmware, the SDG Explorer application will not display the new firmware version until the SDG has issued a SCSI inquiry, which occurs when it rescans the SCSI buses. The same is true for the StorWatch SAN Data Gateway Specialist client application and the service terminal. Performance considerations Performance analysis is approached by determining which component of the data path impacts performance. Typically, a performance problem can be isolated by looking at one aspect of the data path at a time. The data path mainly consists of: Client file system Client server hardware Network Application server hardware Application server file system Application itself (for example, database) 422 Implementing IBM Tape in Linux and Windows

451 Connection to the tape drives Type of HBAs: 1 GBit or 2 Gbit. What are the HBAs connected to? Which type of PCI Bus? What else is on the same PCI Bus? Size of files that you are backing up If you think you have a performance problem, then you have to determine which link of your chain is causing the problem, that is, where does the bottleneck occur? Therefore, look at each link separately. Attention: The numbers presented here are not intended to reflect any real performance that might be achieved. The tests were run without particular attention to optimizing performance and are intended to be used for comparative results only. Linux The Linux command dd can be used to get a baseline performance level. You may test the performance of your disk subsystem first by writing and reading from the disk to /dev/zero. Then you may want to test the performance from the server to the tape by writing and reading from tape to /dev/zero. Finally, you write files from the disk to the tape. The dd command has the following syntax: dd if=input_file/device of=output_file/device bs=blocksize count=amount_of block_reading/writing You may use dd in conjunction with time to measure the time. We suggest that you write/read at least 1 GB; therefore, use bs= count=4096. First, test the file system performance with: time dd if=<filename> of=/dev/null bs= Substitute <filename> with a large file that you have created or that is already available. Then test the tape performance with: time dd if=/dev/zero of=/dev/ibmtapex bs= And with: time dd if=filename of=/dev/ibmtape0 bs= Windows With NTUTIL in batch mode, you can test native performance of the tape drives. For this task, you have to generate a batch file with the content shown in Example C-1. Example: C-1 Sample NTUTIL batch file to test tape drive performance command open RW command set_device_parameters compression = 0 command set_media_parameters block_size = set block_size = command write records = 4096 command write_filemark 2 Appendix C. Additional information 423

452 With this example, we are writing 1 GB data (4096 x 256 KB) from the cache to the tape using blocksize 256 k. Compression is set to off. We are using an Ultrium 1 drive. Save this file as ntutil.in in the directory where you open NTUTIL. Set the device special file, as described in 3.5.1, Testing the library with NTUTIL on page 122. Load a scratch tape to the tape drives that you want to test (use NTUTIL, StorWatch, or do it manually). Then go back to the main menu (see Example C-2) and select 2. Example: C-2 NTUTIL main menu NTutil - Copyright (c) IBM Corporation Main Menu: Microsoft Windows 2000 version ========== 1: Manual test 2: Batch test 9: Exit ntutil Enter selection:2 This runs the batch job in the file ntutil.in and generates output in ntutil.out. In our case, the batch job opens the tape drive, disables compression, and writes 4096 times 256 KB random blocks to the drive. After the job is finished, view the output file ntutil.out. At the end of the file, you see the calculated performance (see Example C-3). Example: C-3 ntutil.out Batch test begin at time Sat Mar 22 20:48: Test tool version command line library mode off 20:48:44 Line 1 >>> command open RW special file (\\.\tape1) will be opened 20:48:44 Line 2 >>> command set_device_parameters compression = 0 execute set_device_parameters compression = OFF 20:48:44 Line 3 >>> command set_media_parameters block_size = execute set_media_parameters block_size = :48:44 Line 4 >>> set block_size = :48:44 Line 5 >>> command write records = 4096 attempt write , actual write bytes, data = attempt write , actual write bytes, data = attempt write , actual write bytes, data = attempt write , actual write bytes, data = attempt write , actual write bytes, data = attempt write , actual write bytes, data = attempt write , actual write bytes, data = attempt write , actual write bytes, data = attempt write , actual write bytes, data = :49:20 Line 6 >>> command write_filemark 2 20:49:21 Line 7 >>> Total elapsed time in seconds = Bytes transferred = Data rate = bytes/second Batch test end rc=0 at time Sat Mar 22 20:49: Implementing IBM Tape in Linux and Windows

453 During this test, it may be helpful to monitor the real-time performance values on your SAN Switch (if FC Drives). You can use either the switch GUI or command line interfaces. For IBM 2109 (Brocade) switches, you can use the portperfshow command to show the performance of the attached devices. Example C-4 shows the portperfshow output from an IBM 2109-F16 Switch. The tape is connected on port 7 and the HBA is connected on port 5. Performance varies between 35 and 36 MB/second, with the values updated automatically every second. Example: C-4 IBM 2109 SAN Switch: portperfshow portperfshow m 0 35m m 0 36m m 0 36m m 0 36m m 0 35m m 0 36m m 0 35m m 0 36m m 0 36m m 0 36m m 0 36m m 0 36m m 0 35m m 0 36m m 0 36m Tivoli Storage Manager tape and tape library commands These commands, as seen in Table C-1, are commonly used Tivoli Storage Manager tape and tape library commands. Table C-1 Commonly used Tivoli Storage Manager tape commands Command QUERY LIBRARY QUERY DRIVE QUERY DEVCLASS QUERY LIBVOLUME QUERY VOLUME QUERY VOLUME ACCESS=READONLY CHECKIN LIBVOLUME CHECKOUT LIBVOLUME LABEL LIBVOLUME AUDIT LIBRARY REPLY nnn QUERY PATH Description Information about the library Information about tape drives Information about device classes Find volumes (scratch and private) Find private volumes Find volumes in read only status Check in volumes to the library Check out volumes to the library Write TSM labels on cartridges Check consistency of library inventory Reply to console request Information about library and device paths Appendix C. Additional information 425

454 EMC Legato NetWorker autochanger maintenance commands NetWorker device driver software provides the following maintenance commands for diagnosing problems on tape devices and medium changers (Table C-2). Table C-2 NetWorker autochangers maintenance commands Command lusbinfo lusdebug lrescan lreset changers inquire ldunld msense pmode tur writebuf sjirjc Description Prints out SCSI information Sets the library debugging level Rescans for devices Resets the SCSI bus Lists the SCSI autochangers attached to the system Lists the devices available Loads or unloads a tape device Retrieves mode sense data Prints mode sense data Tests whether the unit is ready Writes a device buffer Tests the jukebox Verifying device attachment with tapeutil or ntutil Before you start to use your devices for production work with your applications, or if you encounter difficulties with your devices, you may want to verify that the hardware, connections, and device drivers are working together properly. Before you can do this, you should have already installed your LTO according to Chapter 3, Basic IBM tape setup for Windows on page 79 and Chapter 4, Basic IBM tape setup for Linux on page 183. Also, you should have already determined which operating system device name corresponds to which tape drive in the library. You could create a list like Table C-3. Table C-3 Library device table Device name WWN Tape drive in the library SCSI element address \\.\tape Drive \\.\tape Drive \\.\tape Drive If your list is incorrect, or you have not made one yet, the procedures here will show you how to correct it. You should run this test for every attached tape drive. 426 Implementing IBM Tape in Linux and Windows

455 Linux tape and medium changer device attachment test The following procedure tests the attachment of a medium changer device and a tape drive to a Linux system. The procedure assumes that the medium changer is attached at /dev/ibmchanger0 and the tape device is attached at /dev/ibmtape0 and that there is no cartridge in the drive. You also need an unassigned cartridge available for loading in at least one of the slots. 1. List all your tape drives using ls /dev/ibm* (Example C-5). Example: C-5 List tape drives # ls /dev/ibm* /dev/ibmchanger0 /dev/ibmtape0 /dev/ibmtape0n /dev/ibmtape1 /dev/ibmtape1n 2. Start IBMtapeutil. The main menu will be displayed (Example C-6). Example: C-6 IBMtapeutil for Linux IBMtapeutil for Linux, Version 1.2., Sept 19, 2003 ========================================= 1. Tape 2. Changer 3. Quit ========================================= 3. Select 2: Changer. 4. Select 1: Open a Device. 5. Enter /dev/ibmchanger0 for the device name (Example C-7). Example: C-7 tapeutil changer menu Enter device name (<enter> for /dev/ibmchanger0): /dev/ibmchanger0 Opening device... Hit <enter> to continue General Commands: Open a Device 7. Request Sense 2. Close a Device 8. Log Sense Page 3. Inquiry 9. Mode Sense Page 4. Test Unit Ready 10. Switch Tape/Changer Device 5. Reserve Device 11. Create Special Files 6. Release Device 12. Query Driver Version Q. Quit IBMtapeutil Medium Changer Commands: Element Information 65. Load/Unload Medium 61. Position To Element 66. Initialize Element Status 62. Element Inventory 67. Prevent/Allow Medium Removal 63. Exchange Medium 68. Initialize Element Status Range 64. Move Medium 69. Read Device Identifiers Service Aid Commands: Dump Device 72. Load Ucode 71. Force Dump 73. Reset Drive Back To Main Menu 6. Select 3: Inquiry. Press Enter when prompted for an inquiry page. This concludes a very basic test of the device, SCSI connection, and the device driver. You may stop the test here or continue to perform a more complete test. Appendix C. Additional information 427

456 7. Select 62: Element Inventory. 8. From the output of the previous step, select a writable, scratch cartridge and determine its element ID (see also Using tapeutil element inventory (Linux) on page 431). Also, select the element ID of the tape drive who your are working with; refer to Table C-3 on page Select 64: Move Medium, then supply the address of the cartridge, followed by the address of the tape drive that you want to test. Use the element address from Table C-3 on page 426. Verify that the cartridge moved. 10.Close the medium changer (option 2) and return to the main menu (99). 11.Select 1: Tape from the main menu. Example: C-8 tapeutil tape main menu General Commands: Open a Device 7. Request Sense 2. Close a Device 8. Log Sense Page 3. Inquiry 9. Mode Sense Page 4. Test Unit Ready 10. Switch Tape/Changer Device 5. Reserve Device 11. Create Special Files 6. Release Device 12. Query Driver Version Q. Quit IBMtapeutil Tape Commands: Rewind 33. Set Block Size 21. Forward Space Filemarks 34. Retension Tape 22. Backward Space Filemarks 35. Query/Set Tape Position 23. Forward Space Records 36. Query Tape Status 24. Backward Space Records 37. Load Tape 25. FSFM 38. Unload Tape 26. BSFM 39. Lock Tape Drive Door 27. Space to End of Data 40. Unlock Tape Drive Door 28. Read and Write Tests 41. Take Tape Offline 29. Write Filemarks 42. Enable/Disable Compression 30. Read or Write Files 43. Flush Driver's Buffer 31. Erase 44. Self Test 32. Reset Drive 45. Display Message IBMtape Commands: Query Sense 52. Locate Tape Position 47. Query Inquiry 53. Read Tape Position 48. Query/Set Tape Parameters 54. Query Mtdevice Number 49. Query/Set Tape Position 55. Synchronize Buffers 50. Query/Set MT/ST Mode 56. List Tape Filemarks 51. Report Density Support Service Aid Commands: Dump Device 72. Load Ucode 71. Force Dump 73. Reset Drive Back To Main Menu 12.On the Tape menu, select 1: Open a device. 13.Enter /dev/ibmtape0 (or the device name of the drive you want to test referring to Table C-3 on page 426) when prompted for the device name. 14.Select 1: Read/Write. 15.Select 4: Test Unit Ready and wait until no error occurs and the tape drive is ready (see Example C-9 on page 429). 428 Implementing IBM Tape in Linux and Windows

457 Example: C-9 Test unit ready Enter Selection for /dev/ibmtape0: 4 Issuing test unit ready... Unit ready. Hit <enter> to continue... If your drive is not ready after one minute, then do a visual check to see if the cartridge is loaded on the right drive. If not, then your library device table (Table C-3 on page 426) may be wrong and you will have to figure out it by iteration. Close your device by selecting 2, try to open a different device name, and start again at step 12. Repeat steps 12 to 15 until you find a device that is ready, then update your library device table (Table C-3 on page 426). 16.Select 28: Read and Write Tests. 17.Select 1: Read/Write. Press the Enter key three times to accept the defaults and run the test. 18.Select 38: Unload Tape. Wait until the medium is unloaded. 19.Then close the tape device with option 2 and go back to the main menu with Select 2: Changer 21.Select 1: Open a Device. 22.Select /dev/ibmchanger0 for the device name. 23.Select 62: Move Medium, then supply the address of the tape drive, followed by the address of the cartridge slot where it was before. Verify that the cartridge moved. 24.Select 2: Close a Device. 25.Select Q: Quit Program. Windows tape and medium changer device attachment test The following procedure tests the attachment of a medium changer device and a tape device to a Windows system. The procedure assumes that your media changer is configured at Changer0, and the tape drive is attached at Tape0. It also assumes that there is no cartridge in any drive. You also need an unassigned cartridge available for loading in at least one of the slots. 1. Open a terminal session. 2. Start ntutil. The ntutil menu will be displayed (as in Example 3-1 on page 122). 3. Select 1: Manual test. 4. Select 8: Library Mode 5. List all available devices with 88: List registered devices, as shown in Table C-10. Example: C-10 List registered devices enter selection: 88 Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 1" Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 2" Device found: Port 3\Scsi Bus 1\Target Id 0\Logical Unit Id 4" Total elapsed time in seconds = 0.00 Appendix C. Additional information 429

458 Return to continue: 6. Select 1: Set device special file (Example C-11). Enter the special file name for the tape (tape0). Enter the special file name for the changer (changer0). Example: C-11 ntutil: Set special file name enter selection: 1 Enter device special file (tape path) name or return for no change: tape0 Enter device special file (changer path) name, or "def" for default lun1 changer or return for no change: changer0 Total elapsed time in seconds = Return to continue: If you are testing other tape drives, then you have to enter the appropriate special file name. 7. Select 20: Open to open the tape and the changer. 8. Select 14: Additional ioctls calls and then 2: Library Inventory. 9. From the output of the previous step, select a writable, scratch cartridge and determine its element ID. Also, select the element ID of the tape drive that you are working with (refer to Table C-3 on page 426). 10.Select 11: Move Medium, then select 2 (SE = Storage Element) or 3 (IEE = Import / Export Element), depending on where your cartridge is stored. Supply the address of the cartridge. As the destination type, select 4 (DTE = Data Transfer Element = Tape Drive), followed by the address of the tape drive, as seen in Example C-12. Verify that the cartridge moved. Example: C-12 Move medium enter selection: 11 source type [moving from]: 2 = SE, 3 = IEE, 4 = DTE:2 source address moving from: 4120 destination type [moving to]: 2 = SE, 3 = IEE, 4 = DTE:4 destination address moving to: Select 39: Test Unit Ready until no error occurs. If your drive is not ready after one minute, check to see if the cartridge actually loaded in the right drive. If not, then your library device table (Table C-3 on page 426) may be wrong and you will have to figure out it by iteration. Close your device by selecting 2 and try to open a different device name by selecting a different device special file name. Open it and try it again with 39: Test Unit Ready. Repeat these steps until you find a device that is ready, then update your library device table (Table C-3 on page 426). 12.Select 87: Read and Write Tests. 13.Select 33: Unload Tape. Wait until the medium is unloaded. 14.Select 11: Move Medium, then supply the address of the tape drive, followed by the address of the cartridge slot where it was before. Verify that the cartridge moved. 15.Select 2: Close a Device. 16.Select Q: Quit Program or start again at step 6 with a different tape drive. 430 Implementing IBM Tape in Linux and Windows

459 Using tapeutil element inventory (Linux) When you select option 62 in tapeutil, you will receive a list of each element in the library and its status. First, the robot itself is listed, followed by each of the slots in the Import/Export station, as shown in Example C-13. Example: C-13 Tapeutil element inventory: import/export station Enter Selection for /dev/ibmchanger0: 62 Reading element status... Robot Address 1 Robot State... Normal ASC/ASCQ Media Present... No Source Element Address Valid... No Media Inverted... No Volume Tag, Length A B C D E F ABCDEF [...] [...] [... ] Import/Export Station Address 16 Import/Export State... Abnormal ASC/ASCQ Media Present... No Import Enabled... Yes Export Enabled... Yes Robot Access Allowed... No Source Element Address Valid... No Media Inverted... No Volume Tag, Length A B C D E F ABCDEF [...] [...] [... ] Hit <enter> to continue... Import/Export Station Address 17 Import/Export State... Abnormal ASC/ASCQ Media Present... No Import Enabled... Yes Export Enabled... Yes Robot Access Allowed... No Source Element Address Valid... No Media Inverted... No Volume Tag, Length A B C D E F ABCDEF [...] Appendix C. Additional information 431

460 [...] [... ] Scroll down to continue the listing of the rest of the import/export slots. Next, the drives are listed (Example C-14). Example: C-14 Tapeutil element inventory: drives Drive Address 256 Drive State... Normal ASC/ASCQ Media Present... No Robot Access Allowed... Yes Source Element Address Valid... No Media Inverted... No Same Bus as Medium Changer... Yes SCSI Bus Address... 0 Logical Unit Number Valid... No Volume Tag, Length A B C D E F ABCDEF [...] [...] [... ] Drive Address 257 Drive State... Normal ASC/ASCQ Media Present... No Robot Access Allowed... Yes Source Element Address Valid... No Media Inverted... No Same Bus as Medium Changer... Yes SCSI Bus Address... 1 Logical Unit Number Valid... No Volume Tag, Length A B C D E F ABCDEF [...] [...] [... ] Finally, the individual storage slots are listed (Example C-15). Example: C-15 Tapeutil element inventory: storage slots Slot Address 4097 Slot State... Abnormal ASC/ASCQ Media Present... No Robot Access Allowed... No Source Element Address Valid... No Media Inverted... No Volume Tag, Length Implementing IBM Tape in Linux and Windows

461 A B C D E F ABCDEF [...] [...] [... ] Slot Address 4102 Slot State... Normal ASC/ASCQ Media Present... Yes Robot Access Allowed... Yes Source Element Address Media Inverted... No Volume Tag, Length A B C D E F ABCDEF C [ABA920L1...] [...] [... ] You can see that slot 4102 is occupied, since Media Present is set to Yes and the Volume Tag (Barcode label) contains ABA9201L1, indicating that this tape cartridge is located in this slot. Slot 4097 is empty, since Media Present is set to No. Therefore, when selecting option 1: Move Medium, assuming we knew the tape in slot 4102 was not already used by an application, we could specify source address 4102 and destination address 256. This would load that tape into the tape drive. To unload the media (after selecting 33: Unload Tape), we would move the medium from 256 back to Using NTUTIL element inventory (Windows) When you select option 14: Additional ioctls calls and then 2: Library Inventory in NTUTIL, you will receive a list of each element in the library and its status. First, the drives are listed, followed by each of the slots in the storages cells and the import/export station, as shown in Example C-16. Some of the listing has been deleted for brevity. Example: C-16 NTUTIL element inventory DATA TRANSFER ELEMENTS -- DRIVES Element address = 258 Accessible = 1 Lun flag = 0 Lun = 0 Full = 0 Svalid = 0 Source Address= 0 SCSI flag = 1 SCSI ID = 10 Barcode = Barcode length = 0 Element address = 259 Accessible = 1 Lun flag = 0 Lun = 0 Appendix C. Additional information 433

462 Full = 0 Svalid = 0 Source Address= 0 SCSI flag = 1 SCSI ID = 11 Barcode = Barcode length = 0 STORAGE ELEMENTS Element address = 4120 Accessible = 1 Full = 0 Svalid = 0 Source Address= 0 Barcode = Barcode length = 0 Element address = 4121 Accessible = 1 Full = 0 Svalid = 0 Source Address= 0 Barcode = Barcode length = 0... Storage element output deleted IMPORT/EXPORT ELEMENTS Element address = 16 Accessible = 1 Full = 0 Svalid = 0 Source Address= 0 Barcode = Barcode length = 0 Element address = 17 Accessible = 1 Full = 1 Svalid = 0 Source Address= 0 Barcode = H00512L1 Barcode length = Import/Export element output deleted You can see that slot 17 is occupied, since Full is set to 1 and the Barcode contains H00512L1, indicating that this tape cartridge is located in this slot. All other slots are empty, since Full is set to 0. Therefore, when selecting option 11: Move Medium, assuming we knew the tape in slot 17 was not already used by an application, we could specify source address 17 and destination address 258. This would load that tape into the tape drive. To unload the media (after selecting 33: Unload Tape), we would move the medium from 258 back to Implementing IBM Tape in Linux and Windows

463 Troubleshooting In this section, we present an approach to troubleshooting problems with LTO drives and libraries. Collect real-time failure information If you encounter a problem, it is helpful to save all available error information as soon possible to provide it to the IBM Support Center for failure analysis. Here are the elements to save; the following are details of how to save each element. Save the Library logs. Save the Drive logs (Drive dump). Force a Drive dump and save the Drive dump again. Save your application log. Save the operating system error log. Save the Library logs on Windows with ntutil To save the Library logs on Windows with ntutil: 1. Start NTUTIL. 2. Select 1: Manual test. 3. Select 8: Library Mode. 4. Select 1: Set device special file. 5. Open the device with Option Select 81: Read Dump and choose 1 for library. 7. Save the dump to local disk (Example C-17). Example: C-17 NTUTIL save library logs enter selection: 81 Drive = 0, Library = 1: 1 Enter dump name (1 to 8 characters) or return for default dump0001: libdump analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = Return to continue: Save the Library logs on LINUX with tapeutil To save the Library logs on LINUX with tapeutil: Start IBMtapeutil. Select 2: Changer. Select 1: Open a Device. Enter the changer device name. Select 70: Dump Device. Save the dump to local disk (Example C-18). Example: C-18 Tapeutil save library logs Enter Selection for /dev/ibmchanger0: 70 Enter destination filename (<enter> for dump0001.dmp): lib_dump.dmp Issuing read dump... Total dump data length is Total number of transfers is 1. Transfering dump data... Current transfer number is 1. Appendix C. Additional information 435

464 Wrote 3840 bytes. Total dump data length is Total number of transfers is 1. Transfering dump data... Current transfer number is 1. Wrote 3840 bytes. Hit <enter> to continue... Save the Library logs with the IBM Ultrium Tape Library Specialist You may also use the IBM Ultrium Tape Library Specialist to download the library logs. If you are using a backup application that uses its own device driver for the medium changer, you cannot use NTUTIL or IBMtapeutil; you have to use the IBM Ultrium Tape Library Specialist. Compared to IBMtapeutil, where you just download one log for the whole library, if you use the IBM Ultrium Tape Library Specialist, you have to download several logs. For the IBM U, you can save the logs from the autoloader and the drive. Go to option Logs in the IBM Ultrium Tape Library Specialist, where you upload the logs to your host. For the IBM 3582 and 3583, you have to download four logs from the Diagnostics File section (Library Command Log, Library Error Log, RMU Support Log, and RMU Error Log) (see Figure C-1). Figure C-1 IBM 3582 Ultrium Tape Library Specialist: Download logs For the IBM 3584, you have to download several logs under Service Download Logs, of which the Error Log of Accessor Controller Card is the most important (see Example C-2 on page 437). 436 Implementing IBM Tape in Linux and Windows

465 Figure C-2 IBM 3584 Ultrium Tape Library Specialist: Download logs Save the drive logs on Windows with NTUTIL To save the drive logs on Windows with NTUTIL: 1. Start NTUTIL. 2. Select 1: Manual test. 3. Enter 1: Set device special file. 4. Open the device with option Select 81: Read Dump and choose 0 for drive. 6. Save the dump to local disk (Example C-19). Example: C-19 ntutil save drive logs enter selection: 81 Drive = 0, Library = 1: 0 Enter dump name (1 to 8 characters) or return for default dump0001: before_drive 0 execute_command_read_dump, invalid dump_name statement at (dump_name = before_dr ive0 device = 0 result rc!= -1) batch file syntax error, line 0 NTUTIL error unable to execute_command Total elapsed time in seconds = Return to continue: Save the drive logs on Linux with tapeutil To save the drive logs on Linux with tapeutil: 1. Start IBMtapeutil. 2. Select 1: Tape. 3. Select 1: Open a Device. 4. Enter a tape device name. 5. Select 70: Dump Device. 6. Save the dump to local disk (Example C-20 on page 438). Appendix C. Additional information 437

466 Example: C-20 tapeutil save drive logs Enter Selection for /dev/ibmtape0: 70 Enter destination filename (<enter> for dump0001.dmp): tape_before.dmp Issuing read dump... Querying tape parameters... Total dump data length is Total number of transfers is 5. Transfering dump data... Current transfer number is 1. Wrote bytes. Current transfer number is 2. Wrote bytes. Current transfer number is 3. Wrote bytes. Current transfer number is 4. Wrote bytes. Current transfer number is 5. Wrote bytes. Hit <enter> to continue... Force a drive dump and save the dump again on Windows To force a drive dump and save the dump again on Windows: 1. Use NTUTIL. 2. Select 80: Force Dump (Example C-21). Example: C-21 ntutil force dump enter selection: 80 analyze() called with rc 1 err 0 (ERROR_SUCCESS) data 0 Total elapsed time in seconds = 0.00 Return to continue: 3. Select 81: Read Dump and choose 0 for Drive. 4. Save the dump to local disk (for example, after_drivex). Force a drive dump and save the dump again on Linux To force a drive dump and save the dump again on Linux: 1. Use tapeutil. 2. Select 71: Force Dump (Example C-22). Example: C-22 tapeutilforce dump Enter Selection for /dev/ibmtape0: 71 Issuing force dump... Hit <enter> to continue Select 70: Dump Device. 4. Save the dump to local disk (for example, after_drivex). 438 Implementing IBM Tape in Linux and Windows

467 Save your application logs To save your application logs: For Tivoli Storage Manager, save the server activity log. For NetWorker, save the Daemon logs in /nsr/log/daemon.log. Save the operating system error log To save the operating system error log: Copy the Event log for Windows machines. For Linux, copy the messages and IBMtape.errorlog logs. Both are located on /var/log. Provide all those logs to the IBM Support Center. You should also provide general information about your system, such as: Exact machine type Exact operating system version Installed adapter (SCSI/FC, Adaptec, Emulex, and so on) Adapter microcode, firmware level, bios level, and configuration Hints Finally, here are some miscellaneous operational hints. Library inventory and application inventory If you open the library door, the library will automatically update its inventory. But this does not mean that the backup application will also update inventory. If the library has been opened, it is possible that cartridges have been moved, added, or removed. Therefore, you should always have your application audit the library after it has been opened. Refer to your application documentation for details on how to do this. In Tivoli Storage Manager, use the command: AUDIT LIBRARY library_name checklabel=barcode The IBM Ultrium Tape Library Specialist If you have problems connecting to your library using the IBM Ultrium Tape Library Specialist, try changing the library network settings to 10 Mbit / Halfduplex. Appendix C. Additional information 439

468 440 Implementing IBM Tape in Linux and Windows

469 Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. IBM Redbooks For information about ordering these publications, see How to get IBM Redbooks on page 446. Note that some of the documents referenced here may be available in softcopy only. Designing an IBM Storage Area Network, SG Designing and Optimizing an IBM Storage Area Network, SG Get More Out of Your SAN with IBM Tivoli Storage Manager, SG Getting Started with zseries Fibre Channel Protocol, REDP0205 IBM SAN Survival Guide, SG IBM Tivoli Storage Management Concepts, SG IBM Tivoli Storage Manager: Implementation Guide, SG IBM Tivoli Storage Manager Version 5.3 Technical Guide, SG IBM TotalStorage Enterprise Tape 3592: Presentation Guide, REDP3749 IBM TotalStorage: Implementing an Open IBM SAN, SG IBM TotalStorage Tape Libraries Guide for Open Systems, SG Implementing IBM Tape in UNIX Systems, SG Introduction to Storage Area Networks, SG Tivoli NetView 6.01 and Friends, SG Other publications These publications are also relevant as further information sources: IBM SAN Data Gateway Router 2108 Model R03 Installation and User's Guide, SC IBM Storage Area Network Data Gateway Installation and User's Guide, SC IBM Storage Area Network Data Gateway Module Setup, Operator and Service Guide, GA IBM Tivoli Storage Manager for Linux Administrator's Guide V5.3, GC IBM Tivoli Storage Manager for Linux Administrator's Reference Guide v5.3, GC IBM Tivoli Storage Manager for Linux Installation Guide V5.3, GC IBM Tivoli Storage Manager for Linux Quick Start V5.2, GC IBM Tivoli Storage Manager for Linux Storage Agent Users Guide V5.3, GC IBM Tivoli Storage Manager for SAN for AIX Storage Agent User's Guide V5.3, GC Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 441

470 IBM Tivoli Storage Manager for Windows Adminstrator's Guide V5.3, GC IBM Tivoli Storage Manager for Windows Quick Start V5.2, GC IBM Tivoli Storage Manager for Windows Storage Agent Users Guide V5.3, GC IBM Tivoli Storage Manager for Windows Installation Guide V5.3, GC IBM TotalStorage 3580 Tape Drive Setup, Operator, and Service Guide, GC IBM TotalStorage 3581 Tape Autoloader Models L28/L38/L3H and F28/F38/F3H Setup, Operator and Service Guide, GA IBM TotalStorage 3582 Tape Library Setup, Operator, and Service Guide, GA IBM TotalStorage 3583 Tape Library 3583 Setup and Operator Guide for Multi-Path Libraries, GA IBM TotalStorage 3953 Tape Frame Model F05 and Library Manager Model L05 Introduction and Planning Guide, GA IBM TotalStorage Enterprise Tape System 3592 Introduction and Planning Guide, GA IBM TotalStorage SMI-S Agent for Tape Installation Guide, GC NOT FOUND IBM TotalStorage Tape Device Drivers Installation and User s Guide, GC IBM TotalStorage Tape Device Drivers Programming Reference, GC IBM TotalStorage UltraScalable Tape Library 3584 Introduction and Planning Guide, GA IBM Total Storage UltraScalable Tape Library 3584 Operator Guide, GA IBM TotalStorage UltraScalable Tape Library 3584 SCSI Reference, GA IBM TotalStorage Ultrium Device Drivers Programming Reference, GC IBM TotalStorage Ultrium Tape Autoloader 3581 Setup, Operator and Service Guide, GA IBM Ultrium Device Drivers Installation and User s Guide, GA Online resources These Web sites and URLs are also relevant as further information sources: Adaptec Adaptec - Support echnology%2fscsi+host+adapters Arkeia home page BakBone home page Devfs (Device File System) FAQ EMC 2 External Doc Archive Implementing IBM Tape in Linux and Windows

471 EMC 2 Legato - Compatibility Guides Emulex home page IBM 3580 Tape Drive: Interoperability matrix- IBM TotalStorage Tape Storage Systems IBM 3581 Tape Autoloader: Interoperability matrix - IBM TotalStorage Tape Storage Systems IBM 3582 Interoperability Matrix IBM 3582 Tape Library: Interoperability matrix - IBM TotalStorage Tape Storage Systems IBM 3583 Interoperability Matrix IBM 3583 Tape Library: Interoperability matrix - IBM TotalStorage Tape Storage Systems IBM 3584 drive and library firmware ftp://ftp.software.ibm.com/storage/358x/3584 IBM 3584 Interoperability Matrix IBM 3584 Tape Library: Interoperability matrix - IBM TotalStorage Tape Storage Systems IBM ^: I/O connectivity on zseries mainframe servers IBM HBA and SAN Interoperability Matrix IBM LTO Linear Tape-Open: Overview - IBM TotalStorage Tape Storage Systems IBM LTO products Web site IBM ServerProven compatibility for hardware, applications, and middleware: IBM Software - IBM Tivoli Storage Manager - Support IBM Software Support : Tivoli : IBM Tivoli Storage Manager Supported Devices for AIX HPUX SUN WIN IXHPSUNWIN.html IBM Storage Media: Overview - IBM TotalStorage Related publications 443

472 IBM Support & downloads - United States IBM Tape Storage Systems: Independent Software Vendor (ISV) matrix for LTO - IBM TotalStorage IBM Tape Storage Systems: Resource Library - IBM TotalStorage IBM Tivoli Storage Manager - NDMP backup for Network Attached Storage ml IBM Tivoli Storage Manager - Product overview IBM Tivoli Storage Manager - Related products IBM Tivoli Storage Manager SAN device support IBM Tivoli Storage Manager for Storage Area Networks - Product overview IBM TotalStorage support: 3583 Ultrium Scalable Tape Library Downloading IBM TotalStorage support: 3584 UltraScalable Tape Library Downloading IBM TotalStorage support: Search for host bus adapters, firmware and drivers IBM TotalStorage support: Tape & optical storage IBM TotalStorage UltraScalable Tape Library 3584 Advanced Library Management System Technology White Paper, found at: stem.pdf Index of ftp://index.storsys.ibm.com/358x/3581 ftp://index.storsys.ibm.com/358x/3581 Index of ftp://ftp.software.ibm.com/storage/358x/3583 ftp://ftp.software.ibm.com/storage/358x/3583 Index of ftp://ftp.software.ibm.com/storage/devdrvr/doc ftp://ftp.software.ibm.com/storage/devdrvr/doc Index of ftp://ftp.software.ibm.com/storage/devdrvr/linux ftp://ftp.software.ibm.com/storage/devdrvr/linux Index of ftp://ftp.software.ibm.com/storage/devdrvr/windows/win2000 ftp://ftp.software.ibm.com/storage/devdrvr/windows/win Implementing IBM Tape in Linux and Windows

473 Index of ftp://ftp.software.ibm.com/storage/devdrvr/windows/win2003 ftp://ftp.software.ibm.com/storage/devdrvr/windows/win2003 Index of ftp://ftp.software.ibm.com/storage/san/2108 ftp://ftp.software.ibm.com/storage/san/2108 Index of ftp://metalab.unc.edu/pub/linux/system/backup ftp://metalab.unc.edu/pub/linux/system/backup ISV Support Matrix for LTO java.com Kernel Rebuild Guide Legato home page The Linear Tape-Open Technology Organization Web site provides information about the technology, formats, and licensing Linear Tape-Open Web site The Linux SCSI Generic (sg) Driver Linux for zseries and S/390Device Drivers, Features, and Commands November 30, 2004 Linux Kernel April 2004 stream, found at: LTO devices update drive firmware Network Appliances home page The PCI Utilities QLogic home page QLogic Support QLogic Support: OEM Download driver RFC 1157: A Simple Network Management Protocol (SNMP) ftp://ftp.isi.edu/in-notes/rfc1157.txt rscan-scsi-bus.sh script Related publications 445

474 SANBlade Manager User s Guide Management Application for SANblade Host Bus Adapters for your specific HBA, found at: scsidev utility for Linux SCSI Media Changer and Backup Device Control System Solaris documentation Tivoli - Support - Information Center Ultrium 3580 Drive firmware information Ultrium device driver downloads ftp://ftp.software.ibm.com/storage/devdrvr VERITAS home page This Web site describes the media available from IBM How to get IBM Redbooks You can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft publications and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at this Web site: ibm.com/redbooks Help from IBM IBM Support and downloads ibm.com/support IBM Global Services ibm.com/services 446 Implementing IBM Tape in Linux and Windows

475 Index Symbols /etc/lilo.conf 191, 197 /etc/modules.conf 190, 220 Numerics , 21 WORM 22, 291 A ACSLS 38 Adaptec 138, 187 Adaptec HBA and Linux 190 Advanced Library Management System. See ALMS AIX multiple control path 115 allocate media 130 ALMS 20, 25, 40, assign drives 70 cartridge assignment policy 62, 67 configuration 63 create logical library 65 migration 75 move media 76 shared drive assignment 60 storage slot pooling 61 using 76 alternate pathing support 211 API 129 Arbitrated Loop 224 Arkeia 370 installation 371 installation preparation 371 library configuration 373 NLSERVD 372 server daemon 372 assign drives 70 Atape alternate pathing support 115 control paths 115 Atape alternate pathing support 115 autochanger maintenance commands 426 automatic control path failover 302 automation 12 B BakBone NetVault 342 configuration 351 database 345 installation 344, 348 installation preparation 343, 348 media identification 363 NDMP backup 365 NDMP plugin 364 NDMP plugin installation 364 patch installation 351 block ID 132 block size 32, 133, 194, 198, booting FC hosts 422 booting SAN Data Gateway 422 C cables 34 cabling 34 CAP 62 Capacity Expansion Feature 24 Capacity On Demand 25 cartridge assignment policy 62, 67 cartridge I/O station 19 cartridge labeling 274 cartridge memory 7 cartridge policy 67 cartridges mounting 127 catridge 291 CD-ROM 140 Changer Bus Enumerator 103, 107 channel calibration 21 channel zoning 388, 400 cleaning tape drives 280 Command and Control Interface 398 compression 133, 199, 224 configuration discovery 51 configuring SNMP 406 configuring the Library Client 293 configuring the Library Manager 292 connecting tape drives to a SDG 387 connectivity 30 control path failover 12, 16, 25, 82, 91, 107, 211 control paths 115 CPF 103 cpio 342 create logical library 65 Customer Element Exchange 9 D daisy-chaining 31 32, 387 data expansion 21 data path failover 12, 17, 25, 214 data streaming 228 Data Transfer Element 59, 195 debugging 81 devfs 203 device attachment with tapeutil 426 device configuration 132 device driver 32, 187 Copyright IBM Corp. 2002, 2003, 2004, All rights reserved. 447

476 digital certification 120 download 81, 203 Emulex HBA 148 generic 187 medium changer 83, 93, 188 QLogic 217 removing 135 SCSI adapter 138 Ultrium 203 device driver selection 80, 184 device drivers 33 device files no rewind 187 Device Manager 82, 91, 119, 134, 150 device reconfiguration 133 device special file 173, 185 device special name 124, 200 device_strs 193 DHCP 151, 161 diagnostics 156, 160 discovery 51 disk device files 187 dismount 80 DLT expansion frame 3584-D42 23 dmesg 192, 198, 217 downtime 61 drive 133 blocksize 265 check firmware 170 compression 133, 199, 224, 271, 284 daisy-chaining deleting 134 device special name 124 element address 315 element numbers 268 firmware download 175 Linux kernel parameters 197 LUN assignment 397 maximum number 31 microcode download 169 multidrop 34 properties 120 SCSI inquiry 206 serial number 324 update firmware 171, 175, 178 Windows 2000 configuration 132 drive sharing 40 Driver Details tab 121 drives daisy-chaining 387 maximum connections 224 medium changer 387 multiple paths 227 DTE 126 dual pathing 233 duplicate drive definitions 227 dynamic device attachment 221 dynamic partitioning 25 E element addresses 267 element numbers 268 element type 126 elxcfg 148, 239 EMC Legato NetWorker see Legato NetWorker Emulex 30 elxcfg 239 Emulex HBA elxcfg 148 install driver 218 installation 148 persistent binding 239 remove driver 150 ethaddrset 389 ethenable 390 expansion frame 22 F failover 25 FCA 404 FC-AL 224 fcshowdevs 390 fcshownames 387, 390 Fibre Channel mix disk and tape 229 FICON zseries Linux 218 filesize and tape performance 224 firmware 169, 171, 175, 235, 393 drive 178 IBM SAN Data Gateway 393 LTO-TDX 179 RMU 177 FLOGI 241 FMR 171 for 168 G GBIC 16, 386 generic device driver 187 H hardware zoning 235 HBA 32, 80 Emulex 148 firmware 235 number of drives 31 using multiple 227 Windows 2000 support 142 HD68 34 Hewlett-Packard 4 hexadecimal 126 Hierarchical Storage Management 246 high availability via control paths 118 hot-plug 82, 91 HVD 9, 18, Implementing IBM Tape in Linux and Windows

477 HVD and LVD characteristics 34 HVD model 8 I IBM 20 IBM 2109 StorWatch Specialist 225 IBM library sharing 38 IBM check installed firmware 169 firmware 169 HVD model 8 installed firmware 169 LVD model 8 IBM check firmware drive firmware 178 firmware installed firmware Library Specialist 151 Library Specialist menu 153 set IP address 151 update drive firmware 178 IBM U RMU 11 SNMP 11 Tape Library Specialist 11 IBM access mode 116 alternate control path 116 check firmware 170 configure SNMP 405 control path failove 12 control path failover 116 data path failover 12 diagnostic logs 436 drive firmware 178 firmware 170 general information 11 I/O station 12 Import/Export station 12 installed firmware 170 Library Specialist 154 Library Specialist diagnostics 156 Library Specialist logs 156 Library Specialist menus 155 Library Specialist users 155 load balancing 12 logs 156 multi-path architecture 12 operator panel 157 partitioning 12, 44 RMU 13, 151, 154, 404 set IP address 154 SNMP 13, 156 Tape Library Specialist 13, 151, 154 update drive firmware 178 IBM , 168 alternate control path 116 check firmware 170 configure SNMP 406 control path failover 16, 116 data path failover 17 diagnostic logs 436 diagnostics 160 drive firmware 178 firmware 170 installed firmware 170 Library Specialist menu 158 Library Specialist SNMP 159 Library Specialist users 158 load balancing 17 logs 160 multi-path support 16 operator panel 160 partitioning 44 partitioning setup 46 RMU 17, 404 SAN Data Gateway Integrated Module 15, 385 set IP address 158 SNMP 17, 159 StorWatch logs 160 Tape Library Specialist 17, 157 Ultrium 2 16 Ultrium 3 16 update drive firmware 178 update firmware 172 IBM drives expansion frame 21 ALMS 20, 25, 58 alternate control path 116 and Legato NetWorker 318 assign drives 70 base frame base library 22 Capacity Expansion Feature 24 Capacity On Demand 25 cartridge assignment policy 62, 67 cartridge I/O station 19 check firmware 170 control path failover 25, 116 create logical library 65 data path failover 25 diagnostic logs 436 drive firmware 178 dynamic partitioning 25 Ethernet 404 expansion frame 20, 22 FCA 404 firmware 170 frame for high availability 118 high availability frame 20 I/O station 22 IEE 62 insert notification 62 installed firmware 170 L32 22 Index 449

478 library accessor 20 Library Specialist 50, 161 Library Specialist menus 162 Library Specialist password 167 Linux zseries 28 load balancing 25 logical libraries 48 logical library 24 logs 436 MAC address 161 MCP 161 Model D22 21 Model D32 22 Model D52 20 Model HA1 20 Model L22 20 Model L52 19 mtlib 27 multi-path architecture 24 partition with labels 50 partitioning 48, 50 service bays 20 set IP address 161 SMI-S agent 27 StE 63 storage element 63 storage slot pooling 25 tape library specialist 19 Ultrium 1 22 update drive firmware 178 VIEE 62 virtual I/O 62 zseries attach 21 IBM scaling 290 segmentation 290 IBM SAN Data Gateway 7, 29 data transfer rate 387 fcshownames 387 get WWN 387 install firmware 393 rebooting 422 setup 389 Specialist 388, 391 StorWatch Specialist 390 IBM SAN Data Gateway commands ethaddrset 389 ethenable 390 fcshowdevs 390 fcshownames 390 initializebox 389 reboot 390, 422 scsirescan 390, 422 sethost 390 useradd 390 IBM SAN Fibre Channel Switch 225 IBM Support 81 IBM Tape Library Specialist 19 IBM TotalStorage 3580 Tape Drive see IBM 3580 IBM TotalStorage U Tape Autoloader see IBM U IBM TotalStorage 3581 Tape Autoloader see IBM 3581 IBM TotalStorage 3582 Tape Library see IBM 3582 IBM TotalStorage 3583 Tape Library see IBM 3583 IBM TotalStorage 3584 Tape Library see IBM 3584 IBM TotalStorage 3588 Tape Drive Model F3A 20 IBM TotalStorage Virtual Tape Server 27 IBM3584 MCP 150 IBMtapeutil 203 SCSI inquiry IEE 26, 62, 126 Import/Export station 12 information 329 initializebox 389 inquiry 128 Insert Notification 62 inserting unlabeled data cartridges 279 install StorWatch SDG Specialist 391 Integrated SAN Data Gateway Module 15, 385 inventory 431, 433 ioctl 126 ISV applications 28 device driver selection 80 ITSM device driver (tsmscsi) 282 J Java 150 K kernel 189 L labeling data cartridges 278 LAN-free backup 41, 164, 259 LAN-free data transfer 296 LCD 157 Legato NetWorker and IBM autorun 319 backup operations 338 configuration 321 data zone 318 dummy devices 318 element addresses 318 installation 319 installation preparation 319 interoperability 318 inventory 337 jbconfig 322 library operations 334 tape labeling 334 Legato NetWorker commands 426 inquire 318, 323 jb_config 318 sjirdtag 318 sjirelem 318 sjirjc Implementing IBM Tape in Linux and Windows

479 libraries 306 library check firmware 170 firmware download 172 inventory 126 inventory with Linux 195 Windows 2000 configuration 132 library accessor 20 library client 293 library management 38 Library Manager 292 library sharing definitions 38 TSM 292 Library Specialist 151, 154, diagnostics 156, 160 operator panel 157, 160 update drive firmware 178 update RMU firmware 177 users 155, 158 library-centric WWN 238 lilo 192 Linear Tape-Open initiative 4 Linux /etc/lilo.conf 191, 197 /etc/modules.conf 190, /etc/zfcp.conf activate Adaptec HBA 190 alternative device names 200 basic LTO setup 183 block size 194, 198 boot messages 192, 217 booting 192 compile kernel 189, 191 control path failover 211 data path failover 214 devfs 203 device attachment test 427 device driver READMEs 185 device driver selection 184 device drivers 187 device map 220 device mapping 221 device special file 185 device_strs 193 disable alternate path 213 dmesg 192, 198 drive compression 199 drive status 198 dynamic device attachment 221 enable control path failover 212 generic device drivers 188, 218 generic device file 187 generic device utilities 188 IBMtapeutil 203 identifying LTO devices 192 install Emulex driver 218 install QLogic driver 217 installing device drivers 184 installing tapeutil 203 Intel 184 kernel 185 kernel modules 185 kernel parameters 197 labelling TSM volumes 287 library element inventory 431 library inventory 195 lilo 192 load tape 195 loaderinfo 196 low level drivers 190 lspci 188 LTO connectivity 30, 184 LUN support 190 max_scsi_luns 190 microcode updates 205 modprobe zfcp 219 mt 196 mtx 199 mtx driver utilities 194 mtx status 195 native device drivers 192 persistent binding 218 probe LUNs 190 Red Hat 28, 185 SCSI support scsidev 188, 201 scsiinfo 193 sg_scan 188, 193, 218 SuSE 28, 185 tape buffer 198 tape device control 196 tape parameters 198 tapeinfo 199 tar 199 TSM configuration steps 281 Ultrium device driver 203 Ultrium driver download 203 uninstalling Ultrium driver 211 unload tape 196 xconfig 189 zseries 28, 184 zseries FICON enablement 218 Linux commands dd 423 time 423 Linux kernel load balancing 12, 17, 25 loaderinfo 196 logical library 16, 24, 39 logs 436 look 217 lspci 188 LTO 4, 79, 183 alternate pathing support 211 API 129 automation 12 basic setup 80 block size 32 Index 451

480 buying media 274 cartridge memory 7 compression 133, 224 compression with Linux 199 data path failover 214 delete device 134 destination address 127 device configuration 132 device drivers 33, 80 device inquiry 128 device special file 185 device special name 124 disabling in Windows element type 126 FC attachment 29 firmware 169 generic device drivers 218 ISV software 28 Linux connectivity 30 Linux device identification 192 Linux device special names 200 Linux device utilities 188 Linux drivers 203 Linux installation 184 Linux setup 183 logical library 16 logs LTO-TDX 171 media compatibility 6 mixed media with TSM 306 multi-path architecture 43 partitioning 39 read/write test 128 roadmap 4 SCSI attachment 29 source address 127 supported operating systems 28 supported servers 28 technology migration with TSM 306 test basic operations 122 troubleshooting 435 update firmware 171 Vital Product Data selection 170 Windows 2000 connectivity 29 Windows 2000 requirements 80 WORM 7, 289 LTO 1 tape capacity 5 LTO 2 tape capacity 5 LTO drive display devices in Windows LTO Ultrium 4 LTO-DC 22 LTO-TDX 171, 179 LUN assignment with SAN Data Gateway 133 Linux 190 LUN mapping 239, 397 LUN masking 400 LVD 18, 33, 138 LVD model 8 M MAC address 161 magazine 45 make xconfig 189 Management Information Base (MIB) 404, 413 max_scsi_luns 190 Maximum Number of Cartridges 59 MCP 150, 161 media compatibility 6 media suppliers 274 medium changer 39 40, 119 device attachment test 427 device driver 83, 93, 188 device special name 124 LUN mapping 397 microcode 32, 205 Microsoft digital certification 120 Microsoft Management Console 246 Microsoft Tape Format 342 migration of LTO 306 mixed media 306 mount 80 move media 76 mt 196 data compression 200 status 198 MTE 126 mtlib 27, 38 mt-st 196 mtx 194, 199 inventory 195 load 195 status 195 unload 196 multidrop 34 multi-path architecture 12, 24, 39, 43 multi-path support 16 multiple tape paths 227 N NAS 298 NDMP backup with Tivoli Storage Manager 299 BakBone NetVault plugin 364 metadata 299 network 298 Network Attached Storage see NAS NetWorker Client 318 NetWorker server 318 NetWorker Storage Node 318 NTBACKUP 130 allocate media 130 and SAN 132 backup directory 131 restore Implementing IBM Tape in Linux and Windows

481 with SAN 132 NTUTIL , 132, 264, 324, 423, 435 base mode 123 basic functions 122 device inquiry 128 device special file 173 dismount cartridge 128 enable compression 133 inquiry 174 interactive mode 122 ioctl 126 library element inventory 433 library mode 123 list registered devices 133 list registered devices. 124 manual test 123 mount cartridge 127 move medium 126 operating modes 122 read/write test 128 set block size 133 test basic operations 122 test medium changer 125 update drive firmware 175 update library firmware 172 view installed devices 124 view library inventory 126 ntutil 429 O On-Demand Express Portfolio 8, 11 P partitioning 12 password protection 167 performance block size 32 performance considerations 422 persistent binding 218, 223, 228, 237 Emulex HBA 239 PLOGI 241 point-to-point 224 Q QLConfig 143 QLogic 30 install device driver 142 persistent binding 237 SANBlade Manager 143 SANSurfer 143, 236 QLogic HBA configuration 143 install driver 217 R RAID 138 read/write test 128 reboot 390 Red Hat 30, 185 Redbooks Web site 446 Contact us xxiii redundant library control paths 302, 304 registry 132 Remote Management Unit (RMU) 11, 13, 17 Remote Storage Server 247 Removable Storage Manager see RSM rescan-scsi-bus 202 RMU 17, , 154, 404 firmware download 177 update firmware 177 roadmap 4 RSM 89, 100, 102, 122, 130, 261, 319, 321, 343 and SAN 252 disabling 134 pools 247 prepare media 251 service properties 248 RSMConfg 132, 253 S SAN and NTBACKUP 132 bandwidth 224 channel zoning 400 fabric 80, 224 performance 224 performance statistics 226 Simple Name Server 235 switch 233 tapes and libraries 223 TSM device mapping 314 with NTBACKUP 132 WWN 235 WWNN 235 WWPN 235 zoning 228, 232 SAN Data Gateway 15, 132, 142, 385 LUN assignment 133 SAN discovery 315 SANBlade 143 SANergy 257 SANSurfer 143, 236 QLogic SANSurfer 237 SCALECAPACITY 290 scratch pool 42 SCSI attach with Linux 30 cable limitations 34 cables 34 commands 122 device driver 138 enable in Linux 190 hot-plug 82, 91 inquiry LTO with Linux 30 LTO with Windows LUNs in Linux 190 Index 453

482 mix disk and tape 228 Read ElementStatus 132 target ID 133 Ultra Ultra2 34 SCSI adapter Adaptec 138, 190 install in Linux 188 install in Windows SCSI Commands reserve 164 SCSI commands release 164 reserve 164 SCSI element address 58 SCSI Medium Changer 387 SCSI storage element address 58 scsidev 188, 201 scsiinfo 193 scsirescan 390, 422 SDG install firmware 393 SCSI LUN mapping 397 setup 389 WWN 387 SDLC 21 SE 126 Seagate 4 sense data 122 service bays 20 set commands 132 sethost 390 sg_scan 188, 193, 218 Simple Name Server 235 slot pooling 58 SMI-S 27 SNIA 241 SNMP 11, 13, 17, 78, 156, 159, Community Name 410 Set Destination IP Address 410 test trap 411 traps 409, 411 SNMP alerts 404 software zoning 235 StE 63 storage element 63 storage slot pooling 25 StorWatch Specialist IBM SAN Data Gateway 422 Streaming Lossless Data Compression (SLDC) 21 SuSE 185 switch commands portperfshow 425 T tape barcode reader 276 blocksize 198, compression 264 element number 267 target IDs 133 tape alert 305 tape buffers modifying 198 tape categories 39 tape device files 187 tape directory 21 tape drive serial number 324 tape library partitioning 37 sharing 37 tape library commands 425 Tape Library Specialist 11, 13, 17, , 154 IBM , 154 tape management system 80 tape parameters displaying 198 TapeAlert 305 tapeinfo tapeutil 142, 203 device attachment tests 427 library element inventory 431 update drive firmware 175 tapeutil element inventory 431, 433 tar 199 The 63 Tivoli NetView 405, 407 Tivoli Storage Manager see TSM troubleshooting 435 TSM automatic control path failover 302 browser interface 269 checkin volumes 277 client 257 client compression 272, 286 command line interface 269 data migration 307 define storage pool 273, 286 defining devices 264 device class 268, 270 device coexistence 307 Device Configuration Wizard 265 device driver 263 device mapping 314 device mapping - new functions 314 dsm.opt 289 dsm.sys 289 dsmserv.opt 288 element autodetection 314 element number autodetection initial configuration 262 insert cleaner cartridge 280 insert data cartridges 278 labeling cartridges 274 LAN-free backup 259 library client 259, 293 Library Manager 258, 292 Library Manager Server 292 library sharing 258, 292 Linux LTO configuration Implementing IBM Tape in Linux and Windows

483 LTO migration 306 Management Console 262, 265, 275 metadata 296 migration and coexistence 307 mixed generation device 306 mixed media 306 mixed media libraries 306 MOUNTLIMIT 272, 286 mountlimit 309 multiple control paths 302 performance hints 288 RSM 261 SAN device mapping 314 SAN discovery SCALECAPACITY 290 scratch volumes 295 serial number autodetection server 257 server-to-server communication 293 server-to-server communications 259 Storage Agent 296 storage pools 268, 273, 286 supported platforms 256 tape alert 305 tape cleaning 270, 284 tape library 257 TXNBytelimit 289 TXNGroupmax 288 unlabeled cartridges 279 Windows installation 260 TSM commands 425 AUDIT LIBRARY 439 CHECKIN LIBVOLUME 280 DEFINE DEVCLASS , 284, 286 DEFINE DRIVE , , 293, 315 DEFINE LIBRARY 269, 283, 293, 315 DEFINE PATH 269, 283, 298, 315 DEFINE STGPOOL 273, 286 LABEL LIBVOLUME , 287 QUERY ACTLOG 279 QUERY LIBVOLUME 278, 294 QUERY PATH 294 QUERY REQUEST 279 REPLY 279 SET CROSSDEFINE 293 SET SERVERHLADDRESS 293 SET SERVERLLADDRESS 293 SET SERVERNAME 293 SET SERVERPASSWORD 293 SET TAPEALERTMSG 305 TSM devclass 3592 format 272, c format 272, 285 Ultrium format 271, 285 Ultrium2 format 271, 285 Ultrium2c format 271, 285 Ultriumc format 271, 285 TSM for NDMP 299 configurations 299 expiration and retention policies 301 requirements 299 U Ultra Ultra160 SCSI 34 Ultra2 SCSI 34 Ultrium 4 device drivers 33, 80 roadmap 4 tape pool 131 Ultrium 1 5 Ultrium 2 5 Ultrium device driver 228, 233 debug version 81 Driver Details tab 121 install in Linux 203 install in Windows , 98 installing 82, 92 NTUTIL 122 properties 120 removing 135 tapeutil 203 uninstall in Linux 211 update firmware NTUTIL 172 upgrade firmware 168 use StorWatch SDG Specialist 391 useradd 390 using the Tape Library Specialist 50 V VHDCI 16, 34, 386 VIEE 26, 62 virtual I.O 62 Virtual Private SAN 388, 400 Vital Product Data selection 170 VOLSER 58, 62, 78 VTS 27 W WHQL 97, 106, 113 Windows device attachment test 429 install SDG StorWatch Specialist 391 Install Shield 136 library element inventory 433 Plug and Play Device Manager 90 RSM 89 tape drive serial number 324 TSM installation 260 Windows 2000 backup and restore 130 basic LTO setup 79 compression 133 delete LTO device 134 Device Manager 82, 119, 134, 150, 228 device special name 124 disabling LTO device 134 Index 455

484 drive block size 133 Driver Details tab 121 Driver Installation Wizard 82 Emulex HBA install 148 install SCSI adapter 137 install tape driver 82 install Ultrium driver 82, 86, 98 library inventory 126 LTO configuration 132 LTO connectivity 29 LTO requirements 80 NTBACKUP 130 QLogic HBA configuration 143 QLogic HBA installation 142 registry 132 remove Emulex driver 150 removing Ultrium driver 135 resource kit utility 132 RSM 122, 130 SANSurfer 143 supported HBAs 142 test basic LTO operations 122 Ultrium device driver 81 unknown device 83 Windows 2003 Device Manager 91 disabling LTO device 134 Driver Installation Wizard 91 install Ultrium driver 92 NTBACKUP 130 removing Ultrium driver 135 RSM 122 Ultrium device driver 81, 91 unknown device 93 WORM 5, 7, 22, 289, 291 write_threshold_kbs 198 WWN 145, 233, 235, 237, 387 library-centric 238 of SDG 387 WWNN 235 WWPN 145, 235 Z zoning 223, 228, 232 and dual pathing 234 hardware 235 SNS 235 software 235 zseries and IBM connectivity information 218 Linux 184 zfcp.conf 220 zseries Linux FICON enablement 218 Ultrium driver download Implementing IBM Tape in Linux and Windows

485 Implementing IBM Tape in Linux and Windows Implementing IBM Tape in Linux and Windows Implementing IBM Tape in Linux and Windows Implementing IBM Tape in Linux and Windows (1.0 spine) <-> <-> 788 pages

486 Implementing IBM Tape in Linux and Windows Implementing IBM Tape in Linux and Windows

487

488 Back cover Implementing IBM Tape in Linux and Windows How to set up tape drives and libraries New: Ultrium3 and WORM features Integration with popular backup products This IBM Redbook follows IBM TotalStorage Tape Libraries Guide for Open Systems, SG , and will help you plan, install, and configure IBM Ultrium LTO tape drives, as well as the IBM 3592 tape drive and libraries with servers running Linux and Windows 2000/2003. This redbook focuses on the setup and customization of these drives and libraries in both direct-attached SCSI and SAN configurations. Part 1 describes how to attach and configure the drives and libraries, and covers basic installation and administration. It also covers the sharing and partitioning of libraries and explains the concept and usage of the Advanced Library Management System (ALMS) and virtual I/O with the IBM TotalStorage 3584 Tape Library. Part 2 documents how to use these products with popular data backup applications, including IBM Tivoli Storage Manager, BakBone NetVault, Arkeia, and EMC Legato NetWorker. This redbook will help IBM personnel, Business Partners, and clients to better understand and implement the IBM Ultrium LTO product line and also the IBM 3592 tape drive in Windows and Linux environments. INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment. For more information: ibm.com/redbooks SG ISBN