Netfinity tape solutions sg245218

Netfinity Tape Solutions

Wim Feyants, Steve Russell

International Technical Support Organization

SG24-5218-01

www.redbooks.ibm.com

http://www.redbooks.ibm.com

International Technical Support Organization SG24-5218-01

Netfinity Tape Solutions

March 2000

© Copyright International Business Machines Corporation 1998 2000. All rights reserved.Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictionsset forth in GSA ADP Schedule Contract with IBM Corp.

Second Edition (March 2000)

This redbook applies to IBM’s current line of tape products for use with Netfinity servers. At the time of writing, thesewere:

IBM 40/80 GB DLT tape driveIBM 35/70 GB DLT tape driveIBM 20/40 GB DLT tape driveIBM 20/40 GB 8 mm tape driveIBM 20/40 GB DDS-4 4 mm tape driveIBM 12/24 GB DDS-3 4 mm tape driveIBM 10/20 GB NS tape driveIBM 490/980 GB DLT tape libraryIBM 280/560 GB DLT tape autoloaderIBM 3447 DLT tape libraryIBM 3449 8 mm tape libraryIBM 3570 Magstar MP tape libraryIBM 3575 Magstar MP tape library

Comments may be addressed to:IBM Corporation, International Technical Support OrganizationDept. HZ8 Building 678P.O. Box 12195Research Triangle Park, NC 27709-2195

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any wayit believes appropriate without incurring any obligation to you.

Before using this information and the product it supports, be sure to read the general information in Appendix E,“Special notices” on page 289.

Take Note!

© Copyright IBM Corp. 1998 2000 iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe team that wrote this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixComments welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Chapter 2. Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32.1 Why are backups necessary? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32.2 Backup methodologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

2.2.1 When will a file be backed up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42.2.2 Backup patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

2.3 System and storage topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.3.1 Direct tape connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.3.2 Single server model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.3.3 Two-tier model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.3.4 Multi-tier model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

2.4 Storage area network implementations . . . . . . . . . . . . . . . . . . . . . . . . . . .142.4.1 Why use SAN for tape storage? . . . . . . . . . . . . . . . . . . . . . . . . . . . .152.4.2 Fibre Channel attached tape storage. . . . . . . . . . . . . . . . . . . . . . . . .172.4.3 Tape pooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

2.5 Performance considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192.5.1 Scheduling backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192.5.2 Network bandwidth considerations . . . . . . . . . . . . . . . . . . . . . . . . . .202.5.3 Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212.5.4 Hierarchical storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

2.6 Database server backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232.7 Selecting a tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

2.7.1 Tape capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272.7.2 Single tape devices and libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . .272.7.3 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

2.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Chapter 3. Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333.1 Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

3.1.1 Digital Linear Tape (DLT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363.1.2 8 mm tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393.1.3 4 mm Digital Audio Tape (DAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403.1.4 Travan Quarter-Inch Cartridge (QIC) . . . . . . . . . . . . . . . . . . . . . . . . .423.1.5 Magstar 3570 MP Fast Access Linear tape cartridge. . . . . . . . . . . . .433.1.6 Linear Tape Open (LTO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .453.1.7 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

3.2 40/80 GB DLT tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .473.2.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49



3.5 20/40 GB 8 mm tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .583.5.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .593.5.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

3.6 20/40 GB DDS-4 4 mm tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

iv Netfinity Tape Solutions

3.6.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.7 12/24 GB DDS-3 4 mm tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

3.7.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653.8 10/20 GB NS tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3.8.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.9 490/980 GB DLT library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

3.9.1 Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.9.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.9.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3.10 280/560 GB DLT autoloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.10.1 Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.10.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.10.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

3.11 3447 DLT Tape Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773.11.1 Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.11.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.11.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

3.12 3449 8 mm tape library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.12.1 Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.12.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.12.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

3.13 3570 Magstar MP tape library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.13.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.13.2 SCSI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

3.14 3575 Magstar MP tape library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.14.1 Design highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.14.2 The multi-path feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003.14.3 Bulk I/O slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.14.4 High performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.14.5 High reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.14.6 3575 models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023.14.7 Magstar MP tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Chapter 4. SAN equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054.1 Netfinity Fibre Channel PCI adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054.2 IBM SAN Fibre Channel switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054.3 IBM SAN Data Gateway Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074.4 Netfinity Fibre Channel hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094.5 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114.6 Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

4.6.1 Fibre Channel attached tape storage . . . . . . . . . . . . . . . . . . . . . . . 1134.6.2 Netfinity server consolidation with tape pooling . . . . . . . . . . . . . . . 1144.6.3 Sample SAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Chapter 5. Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235.1 Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

5.1.1 Products and base components . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255.1.2 Server data management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1275.1.3 Automating client operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1325.1.4 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

5.2 Tivoli Data Protection for Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . 1355.2.1 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355.2.2 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

v

5.2.3 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1375.3 VERITAS NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137

5.3.1 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1385.3.2 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

5.4 Legato NetWorker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1415.4.1 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1415.4.2 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

5.5 Computer Associates ARCserveIT for Windows NT . . . . . . . . . . . . . . . .1435.5.1 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1455.5.2 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146

5.6 Computer Associates ARCserveIT for NetWare . . . . . . . . . . . . . . . . . . .1475.6.1 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1485.6.2 Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

5.7 VERITAS Backup Exec for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . .1495.7.1 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1515.7.2 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

5.8 VERITAS Backup Exec for Novell NetWare . . . . . . . . . . . . . . . . . . . . . .1555.8.1 Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1565.8.2 Job types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1575.8.3 Supported devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

Chapter 6. Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . .1596.1 Tivoli Storage Manager for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . .159

6.1.1 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1596.1.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1646.1.3 Configuring the IBM tapes and libraries . . . . . . . . . . . . . . . . . . . . . .186

6.2 Tivoli Storage Manager Server V2.1 for OS/2 . . . . . . . . . . . . . . . . . . . . .1946.2.1 Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

6.3 Tivoli Data Protection for Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . .2046.3.1 Configuration and use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2066.3.2 Configuring IBM tape devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

6.4 Legato NetWorker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2106.4.1 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212

6.5 Computer Associates ARCserveIT for Windows NT . . . . . . . . . . . . . . . .2176.5.1 Preparing to install ARCserveIT . . . . . . . . . . . . . . . . . . . . . . . . . . .2176.5.2 Installing ARCserveIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2176.5.3 Configuring ARCserveIT on Windows NT Server . . . . . . . . . . . . . . .221

6.6 Computer Associates ARCserve Version 6.1 for NetWare. . . . . . . . . . . .2246.6.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2246.6.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2286.6.3 Managing ARCserve for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . .2336.6.4 The ARCserve changer option . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

6.7 VERITAS Backup Exec for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . .2426.7.1 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2426.7.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2446.7.3 Configuring IBM tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252

6.8 Veritas Backup Exec for Novell NetWare . . . . . . . . . . . . . . . . . . . . . . . .2546.8.1 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2546.8.2 Software configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

6.9 Seagate Sytos Premium for OS/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2626.9.1 Installing Sytos Premium Version 2.2 . . . . . . . . . . . . . . . . . . . . . . .263

vi Netfinity Tape Solutions

Appendix A. Sources of information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Appendix B. Hardware part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269

Appendix C. Storage area networks and Fibre Channel . . . . . . . . . . . . . . .275C.1 Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

C.1.1 Lower layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275C.1.2 Upper layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

C.2 Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276C.3 Classes of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276C.4 SAN components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277

C.4.1 SAN servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277C.4.2 SAN storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277

C.5 SAN interconnects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277C.5.1 Cables and connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278C.5.2 Gigabit link model (GLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278C.5.3 Gigabit interface converters (GBIC). . . . . . . . . . . . . . . . . . . . . . . . . . . .278C.5.4 Media interface adapters (MIA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278C.5.5 Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279C.5.6 Extenders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279C.5.7 Multiplexors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279C.5.8 Hubs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279C.5.9 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279C.5.10 Bridges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280C.5.11 Gateways. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280C.5.12 Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280C.5.13 Directors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280

Appendix D. TSM element addresses and worksheets . . . . . . . . . . . . . . . .283D.1 Device names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283D.2 Single tape devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283D.3 Tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

D.3.1 IBM 3502-108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284D.3.2 IBM 3502-x14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284D.3.3 IBM 3447 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285D.3.4 IBM 3449 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285D.3.5 IBM 3570 C2x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286D.3.6 IBM 3575 L06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286D.3.7 IBM 3575 L12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287D.3.8 IBM 3575 L18, L24, and L32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287

Appendix E. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289

Appendix F. Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291F.1 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291F.2 IBM Redbooks collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291F.3 Other resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291F.4 Referenced Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292

How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295IBM Redbooks fax order form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296

vii

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299

IBM Redbooks review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305

viii Netfinity Tape Solutions

© Copyright IBM Corp. 1998 2000 ix

Preface

This redbook discusses IBM’s range of tape drives currently available for Netfinityservers. The book starts with a discussion of tape backup strategies and whatconcepts you should consider when designing a backup configuration. Each ofthe tape drives currently available from IBM is then described, listing itsspecifications and connectivity options. It also includes Storage Area Networkimplementations of tape devices. The redbook then examines the backupsoftware that is most commonly used by customers in the Intel processorenvironment. Finally the book explains how to configure the tape drives andsoftware so that they function correctly together.

This redbook gives a broad understanding of data backup and how important it isto day-to-day operations of networked servers. It will help anyone who has toselect, configure or support servers and tape subsystems involving software fromIBM and other leading backup solution providers and IBM tape hardware.

The team that wrote this redbook

This redbook was produced by a team of specialists from around the worldworking at the International Technical Support Organization, Raleigh Center.

Wim Feyants is a Support Engineer in Belgium. He has four years of experiencein supporting PCs and related software, and one year in OS/390 support. Heholds a degree in Electromechanical Engineering. His areas of expertise includeTivoli Storage Manager on S/390 and Netfinity, Netfinity Servers, OS/2 and NovellNetWare. His previous publications include the redbook IBM Netfinity and PCServer Technology and Selection Reference and the first edition of this redbook.Wim can be reached at [email protected].

Steve Russell is a Senior IT Specialist at the International Technical SupportOrganization, Raleigh Center. Before joining the ITSO in January 1999, Steveworked in a Technical Marketing role in IBM’s Netfinity organization in EMEA.Prior to that, he spent nearly 15 years managing and developing PC-basedhardware and software projects. He holds a BSc in Electrical and ElectronicEngineering and is a member of the Institution of Electrical Engineers and aChartered Engineer.

This is the second edition of this redbook. The authors of the first edition were:

David WattsWim FeyantsMike SanchezDilbagh Singh

Thanks to the following people from the ITSO for their help:

David Watts, RaleighMatthias Werner, San JosePat Randall, San JoseMargaret Ticknor, RaleighShawn Walsh, RaleighGail Christensen, Raleigh

x Netfinity Tape Solutions

Linda Robinson, RaleighThanks also to the following IBMers for their invaluable contributions to thisproject:

John Gates, Tape Product Manager, RaleighLee Pisarek, Netfinity Technology Lab, RaleighDan Watanabe, Tape and Optics Business Development, Tuscon

Comments welcome

Your comments are important to us!

We want our Redbooks to be as helpful as possible. Please send us your commentsabout this or other Redbooks in one of the following ways:

• Fax the evaluation form found in “IBM Redbooks review” on page 305 to the faxnumber shown on the form.

• Use the online evaluation form found at http://www.redbooks.ibm.com/

• Send your comments in an Internet note to [email protected]

http://www.redbooks.ibm.com/contacts.html


© Copyright IBM Corp. 1998 2000 1

Chapter 1. Introduction

IBM has a long heritage in the development and production of digital datastorage. As Netfinity servers take on more work in the enterprise, the need forrobust storage management solutions and support programs becomes a basicrequirement.

IBM provides industry leading tape technology in 4 mm, 8 mm, Quarter InchCartridge (QIC), Digital Linear Tape (DLT), and Magstar. IBM’s tape offerings aremanufactured and tested to IBM’s standards and specifications and are backedby its worldwide service and support. IBM can provide a total storage solutionend-to-end, from the hardware to financing.

Before selecting a tape solution, you first need to determine your own specificrequirements both in terms of the data to protect and the time it takes to back upand recover those files. Once you have determined the strategy you wish to use,you need to select the drive technology, then the hardware and software productsthat best meet those strategic requirements.

This redbook leads you through the points you need to consider whendetermining a backup strategy, describes the hardware and software available toyou and finally provides guidance about how to configure the hardware andsoftware so that they work well together.

This edition adds descriptions of hardware and software introduced since the firstedition was published. In addition, we have included a chapter about storage areanetworks (Chapter 4, “SAN equipment” on page 105), which discusses tapeimplementations using a SAN fabric in particular.

As well as providing an overview of newly announced SAN components, includingFibre Channel hubs, gateways, and routers, we examine configurations of thesecomponents supported in combination with tape hardware. Examples we exploreinclude remotely attached tapes and tape library sharing solutions. Finally, theadvantages of SAN attached tape devices in comparison with direct SCSIattached tape devices are discussed.

This books only covers SAN solutions in a backup environment. Otherimplementations, such as remotely attached direct access storage devices, arenot dicussed.

2 Netfinity Tape Solutions


Chapter 2. Strategy

When designing a backup solution, you will start by looking at your specificneeds, and then at the possibilities different products (hardware and software)have to offer. This chapter is meant to help you determine those needs, byexplaining some common backup terminology. We won’t be referring to specifichardware or software. For specific information, see Chapter 3, “Hardware” onpage 33 and Chapter 5, “Software” on page 123.

2.1 Why are backups necessary?

In today’s server environments, there is great emphasis on high availabilitysolutions. Examples include RAID disk subsystems, redundant power supplies,ECC memory and clustering solutions. These new technologies reduce the risk ofserver downtime and data loss. Some people could see this as a reason not toimplement a backup solution, since data is already secured. Unfortunately,hardware failures are only responsible for a small percentage of incidentsinvolving data loss.

Among other causes of data loss, one of the most common is operator errors, thatis, user errors. Users may inadvertently save a file that contains erroneousinformation, or they may erase a critical file by mistake. Besides hardware anduser errors, software errors and virus attacks can also cause data loss or datacorruption.

When thinking about backups, you should consider that your backup is not onlynecessary for disaster recovery. Being able to provide a stable storageenvironment for keeping earlier versions of user files is as important. You shouldthink about your backup environment as being a storage management solution.

Storage management (when discussed in a backup/archive context) embodiesmore than just disaster recovery. The possibility of keeping several versions of aparticular file, including ways to maintain these multiple versions, is just asimportant. If a user or application corrupts data, and saves it, the above functionwill allow you to roll back changes and get back to a previous version. Backup filemaintenance is also an important factor. It is fairly easy to create a backup of afile each hour. However, if there is no way to set the period for which theseversions should be kept, or the number of different versions to be kept, yourstorage utilization will be very high (and costly). Another factor that is important isthe degree of automation a backup product delivers. This is the differentiatorbetween simple backup/restore applications and storage management tools. Ifthe operator has to do everything manually, the chances of errors and the cost ofoperation will go up.

Where backup data is meant to be used as a recovery resource in case of dataloss, another possible use of low-cost mass storage media is archiving. Thecurrent trend of producing data in an electronic form, rather than on paper, callsfor a need to have a valid archiving solution. Documents such as contracts,payroll records, employee records, etc. will need to be stored in a permanent way,without losing the advantages of the electronic form they exist in. A typicaldifference between backup data and archive data is their lifetime and rate ofchange. While backup data changes very fast and becomes obsolete in a shortterm period, archive data typically is static and stays current for a long time (up to


several years, depending on legal standards). As a result, backup productsshould be able to differentiate between these two types of data, since storagepolicies will differ.

Besides a difference in handling this data, the storage device and media will havespecific needs. Since data will be kept for a long time, media lifetime must be veryhigh, which means you might need tape devices that are backward compatible.Physical storage is as important. It should be an environmentally controlled,secured area.

Finally, availability of this data should be very high. That is why some sourcessuggest keeping a second backup server, entirely identical to the production system,on standby in a remote location, together with an extra copy of the media.

2.2 Backup methodologies

This section explains the different ways our data will be backed up, what will bebacked up, and where will it go. Different methods exist, each having itsadvantages and disadvantages. We will discuss three common ways in whichdata is approached by backup programs. When an approach is decided upon, thenext step is to set the backup pattern that will be used. The backup pattern can beseen as the way the backup program determines how data will be handled over acertain time period. This leads us to another important factor in backupoperations: continuity. There is a start point, and from then on, reliable backupsmust be maintained. This is why backup implementation should be very wellplanned before starting.

2.2.1 When will a file be backed up?

2.2.1.1 Full backupA full backup is simply that: a complete backup of every single file.

It is the start point for every backup implementation. Every file that needs to bebacked up, will have to be backed up at least once.

The advantage of such a backup is that files are easily found when needed. Sincefull backups include all data on your hard drive, you do not have to search throughseveral tapes to find the files you need to restore. If you should need to restorethe entire system, all of the most current information can be found on the lastbackup tape (or set of tapes).

The disadvantage is that doing nothing but full backups leads to redundancywhich wastes both media and time. A backup strategy would normally include acombination of full, incremental and/or differential backups.

2.2.1.2 Incremental backupIncremental backups include files that were created or changed since the lastbackup (that is, the last full or incremental backup). To achieve this, the status ofeach file must be recorded either within the backup software or through the use ofthe archive attribute of the files. If no previous backup was made, an incrementalbackup is equivalent to a full backup.

Chapter 2. Strategy 5

Incremental backups make better use of media compared to full backups. Onlyfiles that were created or changed since the last backup are included, so lessbackup space is used and less time is required.

The disadvantage is that multiple tapes are needed to restore a set of files. Thefiles can be spread over all the tapes in use since the last full backup. You mayhave to search several tapes to find the file you wish to restore. The backupsoftware can minimize this by remembering where files are located; however arestoration may still require access to all incremental backups.

2.2.1.3 Differential backupA differential backup includes all files that were created or modified since the lastfull backup. Note the difference between incremental and differential: incrementalbackups save files changed since the last (incremental or full) backup, whereasdifferential backups save files changed since the last full backup. In somepublications, a differential backup is also called a cumulative incremental backup.

The advantages over full backups are that they are quicker and use less media.The advantage over an incremental backup is that the restore process is moreefficient — at worst, the restore will require only the latest differential backup setand the latest full backup set, whereas an incremental backup could require allincremental backup sets and the full backup set.

The disadvantage of differential backups is that longer and longer time is neededto perform them as the amount of changed data grows. Compared to incrementalbackups, differential backups use more time and media — each backup wouldstore much of the same information plus the latest information added or createdsince the last full backup.

2.2.2 Backup patternsA backup pattern is the way we will back up our data. Now that we have definedthe different types of backups, the question is how should we combine them?Tape usage and reusage are important factors, because tape management willget complicated when dealing with a large numbers of tapes, and media costs willrise if we do not reuse tapes.

2.2.2.1 Full/Incremental patternThe most common way of performing backups is to take full backups on a regularbasis, with incremental backups in between.

To avoid the management of too many tapes, the number of incremental backupsshould be as few as possible. The average frequency is one full backup everyweek, plus five or six incremental backups (one per day) in between. This isshown graphically in Figure 1 on page 6.

The definition of a file change can differ between backup applications. Somecriteria used for marking a file as changed include:

• Data changes• Location changes• Attribute changes (last modification or access date, archive bit)• Security changes

Note


This way of performing backups implies:

• One tape (or set of tapes) per day• Very little data on each tape (except the full backup tapes)• When performing the second full backup, you ignore all of the previous full

backups, erase the tapes, and send them back to the scratch pool.

The administration of the tapes, inventory and tracking, tape labeling, andarchiving must be done manually in most cases. In addition, each time you do afull backup, you send all of the data again.

When doing a full restore, you will need to start by restoring the full backup, thenrestore the changes using every incremental backup.

Figure 1. Tape usage in full/incremental backup pattern

An important factor within each backup pattern is tape usage and reutilization. Inthe example above (Figure 1), if in week 2, you need to restore a file that wasbacked up in week 1, you will need to have these tapes still available. This meansthat the number of tapes needed increases significantly. That is why rotationschedules are a very important part of tape management. Tape rotationschedules will provide you with different versions of files, without having a largenumber of tapes.

A commonly used tape rotation strategy is the “grandfather-father-son” schedule.This name reflects the use of three generations of backup tapes: grandfathertapes, father tapes and son tapes. To explain, let us start our backups.

On Sunday, a full backup is taken to a tape labeled “Week_1”. From Monday toSaturday, backups are taken to tapes labeled “Monday”, “Tuesday”, etc. The nextSunday, a full backup is taken to a tape “Week_2”. On Monday, we reuse thetapes labeled with the names of the week (the same tapes as used in week 1).These tapes are called the son tapes. For the next two weeks, we take weekly fullbackups to separate tapes, and store daily backups on the son tapes. At the endof the month, this leaves us with four father tapes, labeled “Week_1”, “Week_2”,“Week_3”, “Week_4”. This gives us the possibility to restore a version of a file thatis one month in age. The last day of the month, a backup is taken to a grandfathertape, labeled “Month_1”. After this, the “Week_1” through “Week_4” tapes can bereused to do the weekly full backup.

Week 1

Week 2

Sun TueMon Wed Thu Fri Sat

I IIIII

I IIIII

F

F

F Full backupI Incremental backup


So, you will have a set of 5 son tapes reused weekly, a set of 4 father tapesreused monthly, and a set of 4 or 12 grandfather tapes (depending on the amountof time you want to cover).

Figure 2. Grandfather-Father-Son media rotation schedule

2.2.2.2 Full/differential patternAnother way of performing backups is to take full backups and differentialbackups, with incremental backups in between.

In this pattern:

• A full backup saves every file.

• A differential backup saves the files that have changed since the previous fullbackup.

• An incremental backup saves the files that have changed since the previousincremental backup (or the previous differential backup if no previousincremental backups exist, or the previous full if no previous differentialsexist).

This process reduces the number of tapes to manage because you can discardyour incremental tapes once you have done a differential. You still have tomanage the incremental tapes prior to the differential backup, however.

This way of performing backups implies:

• One tape (or set of tapes) per day• Very little data on each tape (except the full backup tape)• More tapes to manage, because you have to keep the full backup tapes, the

differential tapes, and the incremental tapes

Week_1

Week_2

Week_3

Wednesday Thursday Friday Saturday Week_4

Monday Tuesday Month_1

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Daily Backup (Son backup set)

Weekly Full Backup (Father backup set)

Monthly Full Backup (Grandfather backup set)


Figure 3. Tape usage in full/differential backup patterns

The advantage of the full/differential pattern over a full/incremental pattern is that arestore will use full, differential and incremental backups which require fewer tapes.(See 2.2.2.4, “Example” on page 9.)

As in the full/incremental pattern, tape rotation can be implemented to limit thenumber of tapes used, while keeping a certain number of versions of each fileover a certain time period

2.2.2.3 Incremental forever patternSince one of the critical factors in any backup is the amount of data that has to bemoved, a way of limiting this amount should be pursued. The best way to do thisis to back up changes only. Using the incremental forever pattern, onlyincremental backups are performed. This means that there is no need for regularfull or differential backups. Though the first backup will be an incremental that willback up everything (so, essentially the same as a full backup), only incrementalbackups need to be taken afterwards.

It is clear that this pattern will limit the amount of backed up data, but turns tapemanagement and usage into a very complex process. That is why you will need abackup application that is capable of managing these tapes.

A good example of this is tape reusage. Since there is no determined point intime when tapes can be reused (as we had in the previous two patterns), thenumber of tapes can increase dramatically. Therefore, the application should beable to check tapes and clean them if necessary. This cleanup (or tapereclamation) should occur when a tape holds backup data that will no longer beused, since newer versions have been backed up.

Another point is that, when backing up data from different machines, their datacan be dispersed over a multitude of different tapes. Since mounting a tape is aslow process, this should be avoided. That is why some applications have amechanism that is called collocation. Collocation will try to maintain the data ofone machine on the fewest number of tapes possible. This should mean aperformance gain when restoring, but will slow down the backup in cases wheremultiple machines need to back up their data to a single tape drive. Instead ofmoving the backup data of both clients to the same tape, the backup program willtry to put the data of both clients on separate tapes. Therefore, the second clientwill have to wait until the backup of the first one completes before it can start its

Sun TueMon Wed Thu Fri Sat

F

New/changed data since last incremental backup

Data from previous days' incremental backups

I DD III

F Full backupI Incremental backupD Differential backup


backup. Again, applications have been provided to limit the impact of this (see2.5.4, “Hierarchical storage” on page 22).

2.2.2.4 ExampleTo make things a bit clearer, let’s look at an example. We have a machine with20 GB of data, and each day about 5% of this data changes. This means we willhave to back up about 1 GB of data for each incremental backup. The network willbe the determining factor for the data transfer rate (we will assume a 16 Mbpstoken-ring network), and backup and restore throughput is equal.

Table 1 shows times needed for backup operations and the type of backups:

Table 1. Backup operation: time required using specific backup patterns

If we look at the restore operation, we will need to determine the number of tapesthat are required and the time needed to restore the data. Let’s assume that wehave to do a full restore (that is, 20 MB) on Friday (restoring from Thursday’sbackups).

Table 2. Restore operation: total number of tapes and total amount of time required

From this we conclude:

• A full restore is faster when using incremental strategies, but the number oftapes needed is hard to predict.

• The number of tapes is the least when using the differential pattern.

Pattern Sun Mon Tue Wed Thu Fri Sat

Full/incremental (Figure 1 onpage 6)

Type Full Incr Incr Incr Incr Incr Incr

Time (sec) 10240 512 512 512 512 512 512

Full/differential(Figure 3 onpage 8)

Type Full Incr Incr Diff Incr Incr Diff

Time (sec) 10240 512 512 1536 512 512 1536

Incremental Type Incr Incr Incr Incr Incr Incr Incr

Time (sec) 5121 512 512 512 512 512 512

1.The first incremental backup will take 10240 seconds but here we assumethat Sunday’s backup is not the first backup.

Type Number of tapes Time (seconds)

Full/incremental 5Sun, Mon, Tue, Wed, Thu

6000(10240 + 4 x 512= 12288)

Full/differential 3Sun, Wed, Thu

6000(10240 +1536 + 512 =12288)

Incremental Unknown 10240


2.3 System and storage topologies

When implementing a backup solution, the first thing to look at is how you aregoing to set up your site. Different possibilities exist, each giving someadvantages and disadvantages. For SAN implementations, refer to 2.4, “Storagearea network implementations” on page 14.

The following topology models will be discussed:

• Direct connection• Single server site• Two-tier site• Multi-tier site or branch office model

There is no one “best” solution applicable to every situation. Factors to beconsidered when deciding on a backup solution include:

• The network bandwidth available• The period available for backup activity• The capabilities of the backup software• The size and number of machines to be backed up

2.3.1 Direct tape connectionThe most easy topology to understand, is the one where we connect our tapedevice directly to the machine we are going to back up (see Figure 4). Oneadvantage of this setup is the speed of the link between data and backup device(typically SCSI) versus the network connection used in other models.

The disadvantages of this model are limited scalability, manageability andhardware cost (one tape device needed for every machine that requires backup).

This setup can be suited for sites with a limited number of machines that need tobe backed up, or for emergency restores.

Figure 4. Direct tape connection

2.3.2 Single server modelAs opposed to the direct connection model, this type of setup is based on abackup server, connected through a network to the machines that will need totake a backup. These machines are often referred to as clients, nodes or agents.The tape device (or other storage media) will be connected to this backup server(see Figure 5). The advantages of this design are that centralized storageadministration is possible and the number of storage devices is reduced (andprobably the cost).

StorageDevice


However, one of the problems here could be the network bandwidth. Since alldata that is backed up needs to go over the network, the throughput is smallerthan what we have using a direct tape connection. Every client that is added willneed some of this bandwidth (see 2.5.2, “Network bandwidth considerations” onpage 20). This bandwidth issue becomes even more important when dealing witha distributed site. Let’s imagine that one of the machines that needs to be backedup is located in a different location than the backup server, with only a very slowlink between these two sites. Throughput could diminish in such a way that itwould take longer than 24 hours to back up the remote system. In this case, atwo-tier solution would be better (as discussed in 2.3.3, “Two-tier model” on page11).

Although not required, it is advised that the machine used as backup servershould be a dedicated machine. The reason for this is that backup and restoreoperations would have an impact on this server’s performance. If you included itin your regular server pool, acting as a file or application server, it could slowdown all operations on the network servers.

Figure 5. Single server model

This design is well suited for sites with a limited number of machines. There aremultiple reasons for this. For example, network bandwidth is not unlimited.Another reason for the limit on clients that a single server will support is that eachsession will use resources (processor, memory) on the backup server.

2.3.3 Two-tier modelAs discussed in 2.3.2, “Single server model” on page 10, scalability and networkbandwidth are limited when working with a single server site. In a two-tier model,an intermediate backup server is used as a staging platform (see Figure 6 onpage 12). The advantages are twofold:

1. The backup is done to the first backup server (or source server), which resideslocally (and has a LAN connection), and only then forwarded to the central

Machines thatneed to bebacked up.

Backup server


backup server (or target server). This can be done asynchronously, so thatcommunication performance between the first and second-level backupservers is not critical.

2. The backup completes in a much shorter time as data transmission is notslowed down by tape drive write speeds. This leads to much shorter backupwindows.

You could also load balance large sites by adding additional source servers.

Figure 6. Two-tier model

Figure 7 shows what happens with the data that needs to be backed up. In thefirst stage, data is moved to the source server. This happens during the period oftime that we have to take our backups (referred to as backup window; see 2.5.1,“Scheduling backups” on page 19).

Source Servers with local backupsforwarded asynchronously to...

Target or CentralServer


Figure 7. Data movement in a two-tier model

The specifications of the storage device connected to this source server shouldbe sufficient to store all the data that is backed up. Typically, it will also be a fastdevice (probably a disk drive). In the second stage, data on this storage device ismoved across the network to a second backup server. This normally happensafter stage 1 completes (but not necessarily, however), and can be done outsideof the normal backup window. The only rule here is that all data from the sourceservers must be moved to the target server before the backup window restarts.

This setup gives advantages with regard to scalability, since you can add as manysource servers as you want. However, more intelligent software is required tomanage the transfer of backed up data both in backup mode and in restore mode.In the case of a restore operation, the user should not need to know on whichbackup server the data is.

Another advantage of this server storage hierarchy is that in case of a sitedisaster at the source server location, the backups still reside on the targetserver. Of course, this advantage will only be true if the target and source serversare geographically separated, and all backup data has been moved to the centralserver.

2.3.4 Multi-tier modelThe multi-tier or branch office model is an extension of the two-tier model, butwith another stage added (and you can add even more stages if you wish). Thesame advantages and disadvantages can be observed. Scalability goes up, butso does complexity.

DATA

Storage 1

Storage 2

Stage 1: Data is backed up to thefirst backup server. This operationshould complete during the normalbackup window.

Stage 2: Data is moved fromStorage 1 to Storage 2. Thiscan happen outside of thebackup window.


Figure 8. Multi-tier model

2.4 Storage area network implementations

In this section, we will introduce some tape storage implementations using astorage area network architecture. This is not intended to be an introduction toSAN itself. It is limited to currently supported and tested configurations. For moreinformation please refer to the following redbooks: Introduction to Storage AreaNetworks, SG24-5470 and Storage Area Networks: Tape Future in Fabrics,SG24-5474.

The IBM definition of a storage area network, or SAN, is a dedicated, centrallymanaged, secure information infrastructure, which enables any-to-anyinterconnection of servers and storage systems.

A SAN is made up of the following components:

• A Fibre Channel topology

• One or more host nodes

• One or more storage nodes

• Management software

Central Server

Branches

Regional Offices


The SAN topology is a combination of components, which can be compared tothose used in local area networks. Examples of such components are hubs,gateways, switches and routers. The transport media used is Fibre Channel,which is defined in several ANSI standards. Although the name, Fibre Channel,assumes the usage of fiber connections, copper wiring is also supported. Thistopology is used to interconnect nodes. The two types of nodes are host nodes,such as the FC adapter of a server, and storage nodes. Storage nodes can beany devices that connect to a SAN.

When looking at the above description, it is clear that many configurations can becreated. However, only a limited number of implementations of the SANarchitecture are currently supported for Netfinity backup solutions. This numberwill certainly rise in the future.

2.4.1 Why use SAN for tape storage?There can be several reasons to use SAN, and the importance of these reasonswill depend on your requirements, such as availability, cost and performance. Onething that should be noted is that current Netfinity SAN implementations arelimited to tape libraries, and not single tape drives. Besides the lack of testedimplementations using single drives, another important fact is responsible for thislack of support: the main reason for implementing SAN solutions is tape drive andmedia sharing. Both concepts are possible when a media pool is available, andthe tape devices have enough intelligence to share this media between them.Neither of these concepts is applicable to single tape drives.

When talking about the availability of tape storage, two separate points can bediscussed. The first one is availability of the hardware, meaning the tape libraryitself. The second one is the availability of the data backed up to tape. In currenthigh availability implementations, this data is backed up and stored off-site.Although this way of working is generally accepted, it also might be a good thingto automate this. By doing so, a copy of local tapes would be sent to a remote sitewithout human intervention. Retrieving these copies would also be transparent.This technique, which is sometimes referred to as automatic vaulting, can beachieved by using the SAN architecture.

Performance issues can also be addressed using SAN architectures. When usinga client/server backup model (the client backs up the data to the backup server),all the backup data must pass through the network (LAN or WAN). In some cases,for example, if the backup client is a big database server, the network can nolonger deliver the throughput that is needed to complete the backup in a certaintime frame. Current solutions would consist of putting a local tape device on thebackup client. Besides the extra cost of additional tape devices, decentralizingbackup management can be difficult to maintain. SAN provides a solution by atechnique called “LAN-free backup”. Here, only the meta data (labeled controldata in Figure 9 on page 16) flows over the LAN, while the actual backup datamoves directly from the client to the storage device connected to the SAN.


Figure 9. SAN-based LAN-free backup

Even though this solution is still in an early phase, the next step towardsperformance improvement has already been architected. This will be called“server-free backup”. Here, client-attached SAN storage moves data immediatelyto the tape storage. Besides having the advantage that most of the data no longerneeds to be backed up through the network, you get an additional performancegain by bypassing the SCSI interface. Both connections (SCSI and network) havea lower throughput than the SAN interface. Its nominal throughput is rated at1 Gbps. Future implementations will allow this figure to extend to 4 Gbps. See2.5.2, “Network bandwidth considerations” on page 20 for network throughputfigures. Compared to SCSI, operating at 40 MBps, FC-AL operates at 100 MBps.Since FC-AL supports full-duplex communications, the total throughput can go upto 200 MBps.

Figure 10. SAN Server-free backup

SAN

BackupClient

BackupServer

Data

Tape StorageNode

Backup Data Control Data

Control Data

SAN

BackupClient

BackupServer

ClientData Tape Storage

Node

Backup Data

Control Data

Control Data


Finally, cost reduction can be an important factor in deciding to move tapestorage from traditional SCSI attachments to SAN attachments. Here, using thesharing capability of a SAN-connected tape library, two or more systems can useone library. This limits the investment in expensive hardware, and enables the useof cheaper storage media (as compared to disk). So, where a traditionalimplementation of a tape library would probably cost more than the equivalent indisk storage, sharing of the library increases the utilization factor and decreasesthe cost per amount of storage.

Figure 11. Storage cost

Figure 11 is a graph of Cost versus Amount of Data for both tape and diskstorage. As you can see, if the amount of data that needs to be stored is lowerthan x, disk storage is cheaper than tape. However, by increasing the amount ofdata stored, the total cost goes below that of disk storage. In order to get past thispoint, you should increase the volume of data that is stored on tape. One way ofdoing this is by sharing the library between different systems.

2.4.2 Fibre Channel attached tape storageProbably the most straightforward type of SAN implementation of a tape device iswhere a tape library is connected to one backup server using fiber. The reasonwhy this can be done is the fact that fiber connections, using long-wavetechnology, can have a length up to 10 kilometers. This means that you canphysically separate your tape library from your backup server, which might proveefficient for disaster recovery or automatic vaulting.

Figure 12 shows the logical setup of such a configuration:

Cost

Amount of Data

Disk

Tape

x

Tape

Libr

ary

Cos

t


Figure 12. Fibre Channel attached tape storage

The above diagram is only a representation of a logical configuration. Forinformation on the actual hardware and software that can be used to implementthis, see Chapter 4, “SAN equipment” on page 105.

This still leaves the question of how to implement the remote vaulting. Since thisis typically done by using tape copies, a second library should be added. Here, forexample, we could use a local SCSI-connected library.

2.4.3 Tape poolingA configuration that comes closer to the general idea of storage area networks,sharing storage across multiple machines, is the tape pooling configuration. Here,one (or more) tape libraries are connected to several backup servers. This isdone by using a Fibre Channel SAN switch. The main advantage of this type ofinstallation is the ability to share a (costly) tape library between two or morebackup servers. Although this might look like something that could already beaccomplished in the past, using a library setup in split configuration (the library islogically split in two, each part using one tape device connected to one backupsystem), there are some differences.

The split configuration was a static setup. This means that you connected onetape drive to one system, the other tape drive to another. If you had a library withtwo tape devices, the split setup meant that you created two smaller, independentlibraries. Also the cartridges were assigned to one part of the split library.

In a tape pooling configuration, there is no physical or logical split of the tapehardware. The entire library is available to both systems. This means that whenone server needs two tape drives for a certain configuration, it will be able to getthem (if they are not being used by another system). Also, the free tapes, orscratch pool, can be accessed by both systems.

However, the physical media that are in use (meaning that they do not belong tothe scratch pool) cannot be shared. A tape used by one system cannot be read byanother.

Figure 13 shows a tape pooling configuration:

Host Node Tape StorageNode

SANFibreChannel

SCSI


Figure 13. Tape pooling

Again, this configuration is just a logical layout. The exact physical layout, and thenecessary hardware and software will be discussed later.

2.5 Performance considerations

When talking to people who are using backup software intensively, one of theirmajor problems is performance. The reason for that is as follows: while theamount of data increases steadily, the time that a machine is available for backup(which has a performance impact on the machine, and sometimes requiresapplications to be quiesced) often gets shorter. That is, more data has to bemoved in a shorter time period. Although hardware and software manufacturersare continually improving their products to cope with this trend, some parametersaffecting performance are related to the way the backup solution is implemented.The following topics discuss some of the techniques you can use, as well assome considerations that might help you determine what performance issuesshould be addressed.

2.5.1 Scheduling backupsWhen thinking about which machines you are going to back up, you will probablythink about file or application servers. Unfortunately, these machines get updatesduring the day, and the only time it makes sense to back up these systems is afterhours. The reason for this is that backup products need to access files and backup valid copies of them. If these files are in use and modified during a backup, thebackup version you have would not be very helpful when restored.

That is why you should determine a period of time in which operations on themachine that you will back up are minimal, and use this period of time to run yourbackup. This period is often referred to as the backup window. You will soon seethat this backup window usually starts sometime late at night, and ends early inthe morning, not exactly the time you or someone else wants to sit beside themachine starting or stopping backup operations. Luckily, backup programs makegood use of scheduling mechanisms. These schedulers allow you to start abackup at a certain point in time.

The following points are important when automating your backup processes usingschedulers:

• What will my backup application do in case of errors? Will it continue or stop?The worst case would be if the application stops and asks for userintervention. It would be better for the backup application to make every effortto work around problems, backing up as much of your data as possible.

Host Node

Tape StorageNode

SAN

Host Node

FibreChannel

SCSI

FibreChannel


• Will operations and errors be logged somewhere, so I can check if thebackups were successful?

• If the backup operation takes longer than the defined backup window, will itcontinue or stop?

There are different scheduling mechanisms, each with its own advantages anddisadvantages. For more details, please refer to Chapter 5, “Software” on page123.

2.5.2 Network bandwidth considerationsWhen implementing a backup solution that backs up data to a backup server overthe network, an important factor is network bandwidth. The reason for this is thatall the data must go over the network. This becomes even more important whendifferent machines are trying to back up to one server at the same time, since theamount of data increases. That is why network bandwidth will be one of thefactors when deciding how many machines will be backed up to one backupserver, and which backup window will be needed.

To calculate the time needed for a backup, the following points must beconsidered:

• The amount of data that will be backed up

Unfortunately, this number can differ from backup system to backup system.Let’s say you have a file server with 20 GB of data. When you do a full backupof this system, it will indeed send 20 GB. But most backup programs also workwith incremental or differential backup algorithms, which only back upchanged data. So, to figure out the amount of data that is backed up in suchan operation, we will have to consider the following points:

• How much data changes between two backups?• What does “changed” mean to my backup program?

Backup programs will normally also compress data. Unfortunately, thecompression rate is strongly dependent on the type of file you are backing up,and therefore hard to define. For initial calculations, you could take the worstcase scenario, where no compression would take place.

• Nominal network speed (commonly expressed in Mbps)

This is the published speed of your network. Token-ring for example will have anominal network speed of 4 or 16 Mbps.

• The practical network speed

Since a communication protocol typically adds headers, control data andacknowledgments to network frames, not all of it will be available for ourbackup data. As a rule of thumb, the practical capacity is 50-60% fortoken-ring, FDDI or ATM networks, and 35% for Ethernet networks.


• Bandwidth available to the protocol we are using.

For simplicity, we will suppose that we have the entire bandwidth for theprotocol.

This brings us to the following formulas:

• For token-ring, FDDI or ATM:

• For Ethernet:

2.5.3 CompressionWhen defining tape device capacities, you will often see two values for capacityand transfer rate. The first is referred to as native rate and the second as rateusing compression. The compression rate used will often be 2:1. What do thesecompression rates mean? Are there differences between hardware and softwarecompression? Which should you use?

The first thing to consider is that your tape device will only be able to use onerecording density — it cannot record one piece of data at one density and anotherat a higher density. Secondly, hardware compression uses a softwarecompression algorithm, running in the firmware of the tape device. This meansthat all the rules applicable to software compression, are valid for hardwarecompression. Let’s list some of these rules:

• Compression ratio is strongly dependent of the type of file. This means thatthe published 2:1 ratio is an average and can differ.

• Files should only be compressed once. Compressing an already compressedfile will typically make the file bigger.

The above values are only used as indicative values. Actual figures mightdiffer, since they are influenced by numerous factors. These factors includenetwork topology, number of concurrent network connections and theprotocol that is used.

If more exact values are necessary, we suggest that you trace your network,and get average values for data throughput.

Note

Time (seconds) Amount of Data (MB)Nominal Network Speed (Mbps)------------------------------------------------------------------------------------- 4×=

Time (seconds)Amount of Data (MB)

Nominal Network Speed (Mbps)------------------------------------------------------------------------------------- 2.8×=

When calculating backup throughput, factors other than network speed willmatter. For example, processing on a backup server and tape mounting willalso play an important factor. See performance reports from specific productsto get an idea of application capabilities.

Note


• Reading a compressed file takes longer than reading a non-compressed file,and needs more processing to decompress it.

We can conclude from the above that you should not use hardware compressionand software compression at the same time.

Software compression will be done by your backup software. In most cases it ismore advanced than hardware compression, but also slower. Some backupapplications could for example distinguish between compressed anduncompressed files, and not compress them again. Hardware compression willnot do this.

The advantage of software compression should become more apparent when youare using a client/server environment, where all backup data is moved over thenetwork. If your backup client is able to compress files before sending them overthe network, network traffic will decrease. The disadvantage is that clientprocessing will become higher, and you could run out of processing power.

So what should you use now? Unfortunately, there is no one answer. It is verymuch dependent on your environment and the capabilities of your software. Ingeneral, the following rules should be observed:

• When using the direct SCSI-attached setup, hardware compression will be thebetter solution.

• When storage space is important, use software compression that is able todistinguish compressed files from uncompressed files. This means that it willnot attempt to re-compress the compressed files, and won’t use extra spacedoing this.

• When backing up over a network, and using clients that have enoughprocessing power, use software compression on the clients.

• When backing up a file system that is mostly used for storing compressed files(code servers for example), turn compression off.

2.5.4 Hierarchical storageWhen looking at the data flow when doing a backup, the data passes through acollection of components, each with its own throughput. Looking at Figure 14, wesee that the data moves from the hard disk to the tape over many different typesof components. The slowest one is the tape drive, at 400 KBps. This means that abottleneck often occurs here.

Figure 14. Component speed

SCSI

Token-Ring

Hard Disk10 MBps

DDS-2 Tape0.4 MBps

40 MBps 40 MBps

PCI132 MBps

PCI132 MBps

1 MBps SCSI

TR AdapterTR Adapter


Using newer tape technologies improves transfer rates, but unfortunately, this isnot the only factor that makes the tape device slow. Tape mounts, for example,can take up to several minutes, or even more when human intervention isrequired.

To solve this bottleneck, we could include a buffer mechanism just before the tapedrive. This can be done by inserting a fast storage mechanism, for example ahard disk. This hard disk will then serve as an intermediate storage place, beforetransferring the data to the tape drive. This is what we call a hierarchical storagemechanism.

What will happen now when we take a backup? The backup data is backed up tothe hard disk. Since its transfer rate is much higher, and no mounts arenecessary, the bottleneck effect disappears. At one point, though, data must bemoved (or migrated) to the next storage device, in our case the tape. This datamovement can occur in two ways:

• System triggered• User initiated

An automated, system-triggered, approach is usually preferred. One way to dothis would be to define a high and low threshold. When the amount of data on thehard disk to which we are backing up reaches the high threshold, a process isstarted that migrates data to the tape. This process stops when the low thresholdis reached.

Hierarchical storage can also be used to minimize tape mounts during backupwhen tape collocation (see 2.2.2.3, “Incremental forever pattern” on page 8) isused.

2.6 Database server backup

When using a backup application, you are basically “copying” files to your backupserver or tape device. This is perfectly fine when backing up a file server, where afile is the smallest entity you are working with. But what about applicationservers? Let’s say you have a database server running Lotus Domino, IBM DB2or Microsoft SQL Server. In these types of systems, files are just containers ofrecords in your database (for example, a Lotus Notes NSF file). This file consistsof all notes in your database. It also means that if you change one character inone note, the entire NSF file is flagged as having changed. Normally, this wouldmean your backup program would send the entire file to the backup server. Sincethis way of working is inefficient, another solution should be found.

Most backup applications have add-ons, which allow you to back up applicationdata (for example databases) on a lower level than the entire database containeror file. If we continue the above example, it would mean that changing one note inthe entire Notes database would result in a backup of only this note.

When an application server needs to be backed up, check the availability ofbackup agents for your application. Since they are application dependent, it couldlimit your choice of backup software.

To elaborate on this topic, let’s look in detail at how Relational DatabaseManagement Systems, or RDBMSs, store data, and how backup products caninteract with this data. Non-relational databases, such as Lotus Domino, will have


slightly different ways of handling data, but the concepts for how backups shouldbe performed are the same.

It is important to understand the basic structure of RDBMSs so that you can putan effective backup and recovery strategy in place. You need to back up morethan the database itself to ensure a successful recovery.

RDBMSs share a common set of principles and similar logical and physicalstructures. These fundamental structures include tables, table spaces, log files,and control files.

Tables are used to store data. These two-dimensional tables are the entitieswithin which the database manager will manipulate data. To keep these logicaldata structures separated from the physical, disk structures, many databaseapplications use table spaces. A table space holds one or more tables, and is aphysical entity on the hard disk (a file or raw partition). As explained above,backup operations could be limited to the physical part, meaning the tablespaces. However, besides the fact that this could lead to a huge overhead bybacking up unchanged data, there are other considerations, such as the log files.

Log files are used by the database manager to keep track of changes. Whenevera transaction modifies data, all the changes are kept in these log files. Thereason for that is that a transaction might start changing data in one table, andthen fail later on when updating a second table. In order to maintain data integrity,that transaction must be undone. The database manager will use these logs toroll back, or undo, incomplete transactions. The use of log files in a backupenvironment is slightly different. Since all transactions are kept in these log files,they can be used to replay the transactions performed. This technique iscommonly known as roll-forward recovery. Practically, this means that you couldrestore a database backup that has a certain age, and then roll forward therestored database using the log files, to end with a database that has the currentchanges included. This also means that if you are implementing a databasebackup and recovery scheme, you should pay attention to backing up log files.

Finally, the control files play an important role. Control files are used to map thelogical structure of the database to its physical structure. In other words, theyhold information like which table is placed in which table space and which log fileis currently used. Control files are very important when recovering an entiredatabase. Some database applications will have separate files containing thisinformation, while others will store it in the database itself. Besides the abovedatabase-related components, you should also think about the configuration filesof your database manager itself.

Having explained the structure and major components, we can now look atdifferent backup techniques that are available.

Please note that although all RDBMS products are based on the same set ofprinciples, they do not all use the same terminology or structures. For example,a table space in Informix is called a dbspace, and there is no table spaceconcept in Sybase or Microsoft SQL Server. Log files in Oracle are called redologs, while in Sybase they are called transaction logs.

Note


One method of classifying database backups, is by explaining the physicaltechniques. There are four major ways of maintaining availability of yourdatabases:

• Database mirroring• Database export• Offline backup• Online backup

MirroringDisk or database mirroring is probably the solution which provides the highestavailability in case of media failure. Databases are mirrored on two or moreseparate hard disks. Although this is a good solution for high-availabilityimplementations, it does not take away the need for real database backups. Asalready explained, disk mirroring will not help you in case of data corruption dueto user errors. Also, in case of a disaster, the chance that all disk volumes havebeen damaged is real.

An advantage of disk mirroring is the fact that the mirror can be broken. Althoughthis normally should not happen, there is a valid reason for doing it. As we willexplain later, a full backup of a database should occur when the database isoffline. Offline means that no transactions occur, and that no users have accessto the database. With a mirrored solution, you can stop the mirroring process andtake an offline backup of the nonfunctional database while the original copy is stillonline. This technique can be called a simulated offline backup. After the backup,the mirrored disks can be resynchronized. You must, however, consider theimpact of working like this. You will be taking a physical backup of the tablespaces, and not a logical backup of the tables. This has the disadvantages oflarge backup size, as well as the fact that you will need to back up log files andcontrol files separately. Furthermore, resynchronization can be difficult, and havea serious performance impact.

ExportingA second technique that can be used is database export. Using database exportfunctions, you will create a physical file that can be used to import the data backinto a database. The advantage over just backing up the physical database files isthat export and import utilities will function against the logical databasecomponents (tables). Again, the disadvantage is that you will need to get the logfiles backed up to provide serious recovery scenarios. This technique might be agood solution to make archive copies of your database for longer storage.

Offline backupA third technique is an offline backup of the database. The advantage over thetwo previous methods is the fact that you will use the database manager toorganize the backup. In most cases, this means that the database manager willtake into account the control files, as well as the log file. Simplified, this meansthat the database manager will record the fact that a database backup has beentaken, and will deactivate the log files that exist, since all changes are reflected inthe database itself. The disadvantage of this technique is that you must quiescethe database, limiting access to users and batch programs. Some databaseproducts have partially solved this issue by queueing transactions during thebackup. This means that all transactions performed will be stored, and releasedwhen the database comes back online.


Online backupFinally, there is the online backup technique. The online backup makes a backupof the database, while it is in use. The problem with this technique is that thebackup taken is fuzzy. Transactions made during the backup will not be reflectedin certain tables, while they might be in others. Therefore, it is mandatory that youmaintain log files when using this technique. Solutions exist where parts of thedatabase will be stopped during backup, leaving other tables online. It isimportant to understand that the backup process will be controlled by theRDBMS. The backup product you are using will interface with this RDBMS, andprovide data management and placement. However, it will not include any logicon what is backed up, or how it is organized.

This completes the first classification of database backups. A second approachfocuses on what you will back up. The following ways exist:

• Full database backup• Partial database backup• Log file backup

The full database backup makes backups of all data files, log files and controlfiles. Depending on the RDBMS you are using, you can either do this online,offline or both. Some database products let you take an incremental backup,which will only include changed database pages. This is also called trueincremental backup (as opposed to simulated incremental backup, which will beexplained below).

Partial database backups let you make backups of certain database parts, suchas a single table space. Although faster than a full database backup, it is oftenmore difficult to maintain a consistent backup when using this method.

Log file backups are used to create a simulated incremental backup. Whathappens is that, at some point in time, a full database backup is taken and, fromthen on, only the log files are backed up (on a daily basis for example). Recoveryconsists of restoring the full database backup and the log files, and then using theroll-forward technique to get an up-to-date restore of the database. Theadvantage is the smaller amount of data that needs to be backed up on a dailybasis, but the roll-forward recovery can be a slow process.

With all the techniques explained, one question is still unanswered: which backuptechnique should be used? This all depends on the daily change in yourdatabase. This change is typically around 15%, which clearly indicates that adaily full backup might give a huge overhead. Therefore, for large databases, itmight be a good idea to make a weekly full backup, with daily or hourly(depending on the recovery level you need) log file backups. As explained above,this makes recovery more complicated, but could save you time in backups. Also,in some cases, the size of the database could be too large to complete its backupover a one-day period. In that case, daily full backups are impossible. When adatabase changes almost entirely, or if the size is very small, the daily full backupis a good practice. In the first case (high change rate), the size of the log files willbe comparable or even larger than the original database. In the case of a smalldatabase, the simplicity of working with daily full backups is an advantage.

As explained above, true incremental backups might help you in the case of smalldatabase change rates. However, this is only possible for some RDBMSs (and


non-relational databases, such as Lotus Domino). Two things should be kept inmind however:

• True incremental backups are based on the incremental backup paradigm (see2.2.1.2, “Incremental backup” on page 4), which means you will need aperiodic full backup. Therefore, incremental forever techniques provided bysome backup applications (like Tivoli Storage Manager) are not exploited.

• True incremental does not mean that you cannot take log file backups betweenincremental backups. This enhances the incremental pattern, and can giveyou a more up-to-date database when restored.

This completes the section on database backups. With the above information, youshould now have an idea of what is possible, and what is necessary. It is a goodidea to check with the database administrators about availability requirements,and the backup possibilities of your database product.

2.7 Selecting a tape drive

When designing your backup solution, one important question is: which tapesolution is the best for my environment? Different factors will affect your choice.The following factors should be taken into account:

• Capacity• Manual tape load or a library• Speed• Reliability• Cost

2.7.1 Tape capacityA primary factor in determining which tape device you will use is the capacity youneed. Although this looks unimportant at first sight because you can have asmany tapes as you want, it will become clear that large numbers of tapescontribute to performance, manageability and reliability problems. The neededcapacity all depends on one question: will it be possible to change mediamanually during your backup operation? If the answer is no, you will need a tapedrive that is capable of backing up the amount of data passed to it in one backupsession on one tape. Keep in mind that the amount of data can grow. Current tapemedia capacity ranges from 4 to 80 GB (for details, please refer to Chapter 3,“Hardware” on page 33). If more space is needed, tape libraries might be a bettersolution.

2.7.2 Single tape devices and librariesYou will also need to make a choice between single tape devices and tapelibraries. A manual device requires the operator to insert and remove tapesmanually. A tape library can hold a certain number of tapes, and load themautomatically. Libraries may also make use of more than one tape device,increasing throughput and functionality.

It is quite simple to determine your needs in this case. When automating yourbackups to run at night, you should be able to do this without manual intervention(unless you have operators who can mount tapes). This means that your backupshould be contained on one tape. This can easily be determined if you are usinga full backup pattern (see 2.2.2.1, “Full/Incremental pattern” on page 5 and


2.2.2.2, “Full/differential pattern” on page 7), but could get difficult if you’re usingthe incremental pattern (because you do not have a clear view of tapeusage/reusage).

Besides the enlarged capacity, libraries can also be used to install a lowmaintenance backup solution. This could mean that you can hold a series ofbackups in your libraries, reducing the need for operator intervention.

Another point to consider is the total number of backup copies which should bestored (in other words, the expiration time of a backup). For several reasons it is awise decision to keep more than one backup generation:

• Any backup may fail. Even so-called verify options (if provided by the backupsoftware) cannot detect all types of failures and inconsistencies. For example,for most databases there is no way to compare byte for byte the tape contentswith the database files because the database is permanently modified in thebackground, and the special database backup agents can ensure a “frozenpicture” only during a small time window.

• The reason for a restore may be a software or human error which wasdetected some days after the last full backup. If this is the only completebackup copy available then the situation becomes difficult to correct.

• A larger disaster in the data center may damage some or all cartridges there,or they may not be accessible for disaster recovery at a remote site. Thusthere are rules established for moving backup copies of business-critical datato separate and safe locations. This leads to a dilemma: such copies are in avery safe place, but it may not be acceptable that to restore a deleteddocument you need to visit a bank safe. Working with multiple backupgenerations gives a way to balance the requirements.

Using single tape drives, the solution is simple: buy enough cartridges. Do not tryto save money here — even multiplying the cartridge stock is much cheaper thanthe financial loss in critical situations.

For tape libraries, you have to decide how many backup generations will be keptin the library itself. This may change the choice of the library model dramatically,since you will need to add these copies to the storage capacity needed.

2.7.3 ReliabilityWhen discussing the reliability of a tape system, the following distinction has tobe made:

• Device reliability• Media reliability

When searching for reliability figures, the mean time between failure (MTBF)value is a metric commonly used. So, what is the relation to the life expectancy ofyour device? Unfortunately, none. MTBF and life expectancy have no directrelationship. The reason for this lies in the way MTBF is calculated. If you look atFigure 15, you see a curve expressing the relationship between the number offailures over time for a population of devices. As you can see, the largest numberof failures will occur in the beginning (called early life failures) and after a certainamount of time has passed (wear-out failures). In between these two periods,there is a phase where failures are rare and rather constant. This is called theuseful life. MTBF values are based on failure rates during this useful life. So no


early life and no wear-out failures are taken into account. This means that themean time between failure will be much higher than the life expectancy, sincefailures are more likely to occur during the two phases that are not taken intoaccount.

Figure 15. Failure rate bathtub curve

So what can you do with an MTBF value? One way to use this value is byintroducing it into the Poisson formula to make a quantitative estimation ofreliability. To do this, we need to convert the MTBF to a new value: failure rate.Failure rate will be expressed as a probability of failure during one machinemonth (MM). One machine month is rounded to 730 hours. This means that thefailure rate will be equal to the inverse of the MTBF (expressed in hours) timesthe hours per machine month. If we have, for example, an MTBF value of 100,000hours, the failure rate will be 1/100,000 failures per machine hours, or730/100,000 failures per machine month. So, the failure rate expresses theprobability (p) of a single event occurring in a selected time period. Table 3 showsan overview of the MTBF and this probability.

Table 3. Relationship of failure probability to MTBF

What is usually of interest however, is an estimate for the probability of a certainnumber of failures during a defined time period. To do this, we will use thePoisson distribution function.

MTBF (khrs) 100 200 300 400 500 600 700

p (Fails/MM) 0.0073 0.00365 0.00243 0.00183 0.00146 0.00122 0.00104

Num

ber

OfF

ailu

res

Time

EarlyLife

Useful Life Wear-OutPeriod

This table is based on an MTBF calculated with a 100% duty cycle. Somepublications will show an MTBF with a lower duty cycle. To convert these,multiply the published MTBF with the duty cycle percentage used and divide by100.

Note


Where:

n Number of trialsp Probability of a single event during a selected time period (Fails/MM)x Number of eventsP(x) Probability of x events occurring in n trials

How can we use this formula now? Let’s say we have 10 devices, and we want tocheck them over a time period of 12 months. This means that the number of trialswill be 120 (one trial is defined as one machine during one machine month).Thevalue p can be obtained from Table 3. We can now calculate the probability of anumber of failures occurring during one year on these 10 devices.

Table 4. Probability of an Error Occurring on 10 Devices during 12 Months

Another item that is mostly unpublished in MTBF claims is the preventive andscheduled maintenance that is done. This could significantly extend MTBF. Themain thing to remember is that when comparing MTBFs, extreme caution shouldbe used.

A second factor in overall reliability is media reliability. Again, published figurestend to get confusing and are hard to compare.

The following terminology is commonly used:

Error rate: Average number of errors that can be expected per one unitof information processed, and this on the entire population oftapes.

Data reliability: Number of units processed per one error, or the inverse ofthe error rate.

When looking at these figures, you should ask yourself the following questionsbefore actually comparing them:

MTBF(Khrs.)

Probability of nofailures (x=0)

P(0)

Probability of onefailure (x=1)

P(1)

Probability of two ormore failures (x>1)

P(>1)

100 .416 .365 .219

200 .645 .283 .072

300 .747 .218 .035

400 .803 .176 .021

500 .839 .147 .014

600 .864 .126 .010

700 .882 .110 .008

n=120 trials

P x( ) Exp-np

np( )x

x!-------------------------------= for x=0,1,2,3,... ; np > 0


• Are these calculated or measured values?

• If calculated, what are the underlying assumptions?

• If measured, is it the average over the entire population?

• Who performed the tests or calculations?

• What do they mean by an error?

Most bit or byte level errors could go undetected, because an ECC mechanismin tapes can correct them. An error that would fail the system would probablybe an error on an entire block of data.

Another published figure in media reliability is life expectancies. The problemhowever is that this value is highly dependent on external factors, liketemperature and humidity.

As a general rule, DLT and Travan technologies have a better reliability than4 mm or 8 mm tapes.

2.8 Summary

After reading the previous topics, it should be clear that choosing a backupsolution is a process of many steps, involving a lot of different parameters. Itshould also be clear that there is no “best” solution. All solutions have theiradvantages and disadvantages. The trick is to make the choice based on yourcurrent and future needs. Questions that you should ask are:

• What is the purpose of my backups?• Are they limited to one location, or do I have to secure different locations?• How much data will be backed up?• What performance level is required?• What kind of network do I have available?• How much will it cost?• What is the expected growth of my environment?

After answering these questions, using the descriptions we have provided in thischapter, you should be able to decide on what backup strategy is best for yourenvironment. The following chapters will explain the industry standard backupapplications, and describe the current IBM tape hardware that is available forNetfinity systems. With these chapters, you should be able to select hardwareand software to match your strategy.

© Copyright IBM Corp. 2000 33

Chapter 3. Hardware

This chapter describes each of the tape products currently available from IBM forNetfinity servers. Specifically, we cover the following tape drives:

• IBM 40/80 GB DLT tape drive (see page 47)• IBM 35/70 GB DLT tape drive (see page 51)• IBM 20/40 GB DLT tape drive (see page 54)• IBM 20/40 GB 8 mm tape drive (see page 58)• IBM 20/40 GB DDS-4 4 mm tape drive (see page 62)• IBM 12/24 GB DDS-3 4 mm tape drive (see page 64)• IBM 10/20 GB NS tape drive (see page 66)

and these libraries:

• IBM 490/980 GB DLT tape library (see page 69)• IBM 280/560 GB DLT tape autoloader (see page 74)• IBM 3447 DLT tape library (see page 77)• IBM 3449 8 mm tape library (see page 83)• IBM 3570 Magstar MP tape library (see page 93)• IBM 3575 Magstar MP tape library (see page 98)

The part numbers for the different models and related options are convenientlygrouped in Appendix B, “Hardware part numbers” on page 269.

For each tape drive, we describe:

• Specifications• Connectivity requirements• Performance information

The following tables show tape drive support for IBM Netfinity systems andbackup applications. Table 5 and Table 6 list the Netfinity systems that supporteach of the individual tape drives and tape libraries discussed respectively. Table7 and Table 8 list the major backup software that supports the tape drives andtape libraries covered here.

Note: Since this information is subject to change, check the softwaremanufacturers and the following IBM Web site for up-to-date information:

http://www.pc.ibm.com/us/compat/storage/matrix.shtml#tape



Table 5. Supported internal tape drives on IBM Netfinity models

Netfinity servers also support the following tape library systems:

Table 6. Supported libraries on IBM Netfinity models

40/80 GBDLT

35/70 GBDLT

20/40 GBDLT

20/40 GB8 mm

20/40 GB4 mmDDS-4

12/24 GB4 mmDDS-3

IBM NS20

Netfinity1000

√ √ √

Netfinity3000

√ √ √

Netfinity3500 M10

√2,3 √4 √4

Netfinity5000

√2,3 √2,3 √2,3 √4 √4 √4 √4

Netfinity5500

√ √ √ √ √ √

Netfinity5500 M10

√ √ √ √ √ √

Netfinity5500 M20

√ √ √ √ √

Netfinity5600

√5 √5 √5 √5

Netfinity7000 M10

√2,3 √2,3 √2,3 √1,3 √1 √1,3

Netfinity8500R

√2,3 √2,3 √2,3 √1,3

√: Supported by IBM, Blank: Not supported

1. Externally connected to the IBM External SCSI half-height enclosure2. Externally connected to the IBM DLT External SCSI Enclosure3. Externally connected to the IBM NetMEDIA storage expansion unit EL4. If a RAID adapter is used, add an internal cable, part 36L96365. No free SCSI connections. Add RAID adapter to free internal connector, or add SCSI adapter.

490/980GB DLT Library

280/560GB DLT Loader

IBM 3447 IBM 3449 IBM 3570 C21,C22

Netfinity 5000 √ √ √

Netfinity 5500 √ √ √ √ √

Netfinity 5500 M10 √ √ √ √ √

Netfinity 5500 M20 √ √ √ √ √

Netfinity 5600 √ √

Netfinity 7000 M10 √ √ √ √ √

Netfinity 8500R √

√: Supported by IBM, Blank: Not supported


Chapter 3. Hardware 35

A variety of software to support single tape drives is available. At the time ofwriting, the supported software is as follows:

Table 7. Supported software

40/80 GBDLT

35/70 GBDLT

20/40 GBDLT

20/40 GB8 mm

20/40 GB4 mmDDS-4

12/24 GB4 mmDDS-3

IBM NS20

TSM NT V3.7.1 S S S S S S

TSM OS/2V2R1L15

S S S S

TDP forWorkgroups

S1 S1 S1 S1 S1

VeritasNetbackup

NetWorker NTV5.5.1

S1,3 S1 S1 S1 S

NetWorkerNetWare

S2 S1 S1

ARCServeITV6.6x

S1 S S S S1 S1 S1

ARCServeITNetWare V6.6

S1 S S S S1 S1

BackupExec NT I I I I I I I

BackupExecNetWare

I I I I I I I

Sytos PremiumV2.2a for OS/2

S S S

I: Supported by IBMS: Supported by software manufacturerBlank: Not supportedNotes:1.Support for generic Quantum, Exabyte and HP devices.2.Only supported on NetWare 4.123.Currently supported as DLT 7000 type


Finally, software to support tape libraries on Netfinity servers is shown in thefollowing table:

Table 8. Software support for libraries

3.1 Technology

There is a continuing proliferation of incompatible tape formats appearingconstantly, not from newcomers, but from some of the biggest names in the tapetechnology world, such as IBM, Seagate, Exabyte, Quantum to name but a few.There are several sizes of tape, 4 mm Digital Audio Tape (DAT), 8 mm,Quarter-Inch Cartridge (QIC), and half-inch such as Digital Linear Tape (DLT),and each has several formats. For example, there are four different types of 4 mmDAT tape: DDS-1, DDS-2, DDS-3 and DDS-4. Fortunately, DDS-4 tape drives arebackward compatible with the earlier versions.

Each of these formats is normally used in particular environments; for example,QIC and 4 mm products are designed for low-end applications in PC and smallnetwork backup environments, while the 8 mm and DLT half-inch products arepopular in the mid and high-end for their capacity to store vast amounts of data.

Let’s take a closer look at each technology and discuss the merits of each.

3.1.1 Digital Linear Tape (DLT)The Digital Linear Tape (DLT) technology conforms to both ANSI and ECMAformat standards, and greatly improves data storage capacity and data transferrates over other media formats. The DLT technology is owned, developed, andmanufactured by Quantum Corporation who bought it from Digital Equipment

IBM 3502Library

IBM 3502Loader

IBM 3447 IBM 3449 IBM 3570C2x

IBM 3575


TSM OS/2 V2R1L15 S S S S

TDP for Workgroups S S S

Veritas Netbackup S S S S

NetWorker NT V5.5.1 S S S S

NetWorker NetWare

ARCServeIT NTV6.6x

S S S S

ARCServeIT NetWareV6.6

S S S

BackupExec NT S S S

BackupExec NetWare S S S S

Sytos Premium V2.2afor OS/2

I: Supported by IBMS: Supported by software manufacturerBlank: Not supported


Corporation in 1994 along with a number of patents associated with DLTtechnology. Any drive that uses the name “DLT” is manufactured by QuantumCorporation. While Quantum is the only company that manufactures DLT drives,the company licenses the rights to manufacture DLT tape cartridges to othercompanies such as Hewlett-Packard and IBM, who must follow the Quantummodel-naming standards.

What distinguishes DLT technology from other tape storage technologies arespeed, capacity, and reliability.

Table 9. DLT characteristics

DLT technology uses linear recording and writes each data track on the entirelength of the tape (about 1,800 feet for DLTtape IV media). Data is first writtenonto a track along the entire length of the tape, and when the end is reached theheads are repositioned to record a new track again, along the entire length of thetape, now travelling in the opposite direction. This continues back and forth untilthe tape is full. Current DLT drives record either 128 tracks (DLT 2000XT and DLT4000 drives) or 208 tracks (DLT 7000 and DLT 8000) on half-inch tape.

Figure 16 on page 38 illustrates the direction in which data is recorded on the DLT4000 and DLT 7000 drives. The DLT 4000 drive records data in avertically-oriented pattern along the entire length of the tape on each track,whereas the DLT 7000 recording head is slightly angled and therefore the data isrecorded at angles on adjacent tracks. As a result, a gap or “guard band”between each track is not required on the DLT 7000 which allows for greater datastorage capacity.

The DLT 7000 tape drive provides backward compatibility with the DLT 4000 driveas it can automatically position the read/write head to a vertical orientation.

Media Cartridges CapacityGB

SpeedMB/sec

Durability(head passes)1

DLTtape III DLT 2000 10 GB 1.25 500,000

DLTtape III XT DLT 2000XT 15 GB 1.25 1,000,000

DLTtape IV DLT 4000 20 GB 1.5 1,000,000

DLT 7000 35 GB 5.0 1,000,000

DLT8000 35 GB 6.0 1,000,000

1. 1,000,000 passes are equal to about 15,000 uses.

For more information about DLT technology, look at Quantum’s DLT UniversityHandbook at the following URL:

http://www.dlttape.com/resource/university/home.html

DLT University

http://www.dlttape.com/resource/university/home.html


Figure 16. Recording data on DLT 4000 versus DLT 7000

3.1.1.1 Tape pathAnother characteristic of the DLT drive is the head guide assembly (HGA) whichis different from technologies found in 4 mm and 8 mm. These latter formats usea helical scan system where the head guide systems are designed to move, asillustrated in Figure 17. By contrast, the DLT head drive system assembly nevermoves. Instead of the tape being wrapped around a rotating read/write drum, theDLT drive guide system guides the tape around the head guide assembly andwraps it around the take-up reel in the drive.

Figure 17. Tape path of a conventional two-reel cassette versus DLT tape path using HGA

A conventional two-reel 8 mm or 4 mm DAT cassette contains a take-up reelleaving less space for the tape. In contrast a DLT tape cartridge contains onlytape because the take-up reel is inside the tape drive.

3.1.1.2 Self-cleaning headsAnother characteristic of a DLT tape drive is the use of self-cleaning heads whichcontain fixed “outriggers” that wipe any debris from the tape, thereby reducinghead wear and helping to maintain the longevity of the tape.

Tape Edge Tape Edge

DLT 4000 DLT 7000

Track 0

Track 1

Track 2

Track 0Track 1Track 2Track 3Track 4

Tape Direction Tape Direction


Figure 18. Recording head on DLT drive showing the position of the outriggers

A next step in the DLT tape technology will be the release of Quantum’sSuperDLT tape technology. This will bring capacity per cartridge up to 100 GB(500 GB compressed), with transfer rates going from 10 MBps up to 40 MBps.

3.1.2 8 mm tape8 mm tape technology was originally designed for the video industry for thepurpose of transferring high-quality color images to tape for storage and retrieval.Now, 8 mm technology has been adopted by the computer industry as a reliableway to store large amounts of computer data.

Reliability has improved considerably over earlier models with the introduction ofadvanced metal evaporated (AME) media and the Mammoth tape drive.

3.1.2.1 Advanced metal evaporated mediaCurrent generations of 8 mm media have been manufactured using metal particle(MP) technology. As for most tape products, MP media comprises several layers:a substrate that provides the base for other layers, the magnetic layer where datais stored and a back coat that controls the media’s frictional characteristics. Insome cases, an additional surface treatment, such as lubrication, burnishing, orother conditioning may be added to enhance media and tape-head contact forbetter performance and durability of both components.

The magnetic layer of AME media is applied by evaporating the magnetic materialonto the base layers in a vacuum chamber. An electron beam evaporates thematerial. With AME, this process creates a much thinner, pure magnetic layer thatdoesn’t contain any binders or lubricants. These qualities give AME tape greaterpotential data density so that more information can be stored, as well as improvedperformance and durability.

The AME magnetic layer is 100% cobalt which enhances the magnetic qualitiesof the media.

3.1.2.2 Mammoth technologyMammoth technology, introduced in 1996, incorporates fast transfer rates, highcapacity, fast SCSI response, gentle tape handling, extensive error recovery andhigh-performance AME media.

Mammoth uses a capstanless design which eliminates the part of the tape drivethat creates unpredictable wear and exerts the most pressure on the media. With

Outriggers

WriteHeads

ReadHeads

WriteHeads


a capstanless drive, damage to the edge of the tape is prevented duringrepositioning. The gentle tape path supports the thinner AME media. Thecombination of Mammoth technology and AME media have helped to improvehead-life to 35,000 hours. Mammoth drives calibrate themselves regularly, searchfor and report errors.

Mammoth supports up to 64 variable-length partitions. A partition is a segment oftape that is used as an entity unto itself. Data within a predefined partition can beerased and new data written in its place.

Preserving data is of paramount importance in a tape storage product. Mammothuses two-level Reed-Solomon error checking and correction (ECC) whichcorrects errors on the fly by rewriting the blocks within the same track.

The design of Mammoth drives enables them to achieve a 250,000 hour meantime between failure (MTBF) specification.

8 mm hardware features data compression and a Read-While-Write standard. Ithas high capacity and transfer rate for a relatively small 5.25” half-high formfactor, and provides faster drive performance than 4 mm and quarter-inch tapedrive offerings. Data cartridge costs are low and the drives have downward readcompatibility with older 8 mm formats. Data storage capacity and performanceare lower than DLTtape technology.

Mammoth has better price/performance than DLT.

3.1.3 4 mm Digital Audio Tape (DAT)DAT is an acronym for Digital Audio Tape, and was originally used for consumeraudio recording technology based on 3.81 mm (0.15 inch) wide tape used in ahelical scan recorder compatible with the DAT Conference Standard.

DDSDDS is short for Digital Data Storage, and is a data storage format developed byHewlett-Packard and Sony to allow DAT drives to be used for reliably storingcomputer data. The use of the DDS logo on media must be approved through aprocess managed by Sony, and on tape drives from manufacturers that arelicensed by HP and Sony which meet the specifications set out in the ISO/EIC10777 (for 60 meter DAT) or 12247 (for 90 meter DAT).

DDS-SCDDS-SC is a complementary format with several extensions which allow datacompression to be used on DDS. DDS-SC drives may use normal DDS media.DDS-SC uses a data compression algorithm known as DCLZ (data compressionLempel-Ziv) which is the industry standard for hardware-compressed (DDS-DC)tapes.

DDS-2, DDS-3, DDS-4DDS-2, DDS-3, and DDS-4 are new formats providing higher capacity formatsbased on DDS. DDS-2, DDS-3, and DDS-4 media are different from DDS mediaand will only work in drives which support these new formats.

Media Recognition SystemThe Media Recognition System allows a DDS drive to distinguish DAT media fromDDS media. In relation to DDS drives and DDS media, there is a logo for Media


Recognition System which has four vertical bars after the DDS logo representingthe recognition stripes that distinguish a Media Recognition System tape from atape without these features. It is not appropriate to use the four bar logo inrelation to DDS-2, DDS-3 and DDS-4 formats.

DDS is the first generation 4 mm drive and media with a native storage capacityof 2.0 GB and a sustained transfer rate of 183 KBps. DDS-1 tape drives supportthe 60 meter DAT tape with a capacity of 1.3 GB and the 90 meter DDS tape witha capacity of 2.0 GB. The drives have a single-ended SCSI-2 interface.

DDS-DC uses the industry standard data compression giving a typical storagecapacity of 4.0 GB of data on a 90 meter cartridge, and a sustained transfer rateof 366 KBps. DDS-DC drives typically support 60 meter, 90 meter DDS and DDSMedia Recognition System cartridges. The drives have a single-ended SCSIinterface.

DDS-2 drives provide 4.0 GB native storage capacity, and a maximum storagecapacity of 8.0 GB with data compression (DCLZ) on a DDS-2 (120 meter)cartridge, with a transfer rate of 500 KBps (native), 1.0 MBps (compressed).Read and write compatibility is provided with DDS format (60 meter and 90meter) and DDS-2 format (120 meter), and Media Recognition System cartridges,allowing for interchange of data with existing DDS drives. The DDS-2 drive has asingle-ended, narrow SCSI-2 interface.

DDS-3 drives provide three times the capacity of DDS-2 using linear bit densitywhich is twice as great and track format efficiency which is 1.5 times as great,yielding 12.0 GB of native storage capacity and 24.0 GB with data compressionon a DDS-3 (125 meter) cartridge, with a sustained transfer rate of 1.0 MBps(native), 2.0 MBps (compressed). DDS-3 drives are read and write compatiblewith DDS format (60 meter and 90 meter) and DDS-2 (120 meter), and MediaRecognition System cartridges. Data integrity is ensured with read after writeverification without requiring a time consuming verification pass. DDS-3 driveshave a single-ended, narrow SCSI-2 interface.

DDS-4 offers yet more expanded capacity and performance than DDS-3. At20 GB native capacity (40 GB with compression) and transfer rates of up to4 MBps. These drives also offer read/write compatibility with older DDS-2 andDDS-3 tapes.

Table 10. Evolution of the DDS tape format

The advantages of 4 mm DAT are its popularity in the midrange Netfinity servermarket, and its large installed base. 4 mm DAT is a mid-capacity andmid-performance solution, in a compact 3.5-inch half-high form factor. It issignificantly lower priced than DLT and 8 mm. The data cartridges are also

Capacity (native) Transfer Rate

DDS 1.3 GB 183 KBps

DDS-DC (DDS-1) 2.0 GB 183 KBps

DDS-2 4.0 GB 360 KBps to 750 KBps

DDS-3 12.0 GB 1 MBps to 1.5 MBps

DDS-4 20.0 GB 2 MBps to 4 MBps


relatively low priced. Downward read/write compatibility is maintained with older4 mm DAT formats.

3.1.4 Travan Quarter-Inch Cartridge (QIC)Quarter-Inch Cartridge (QIC) technology, also known as DC6000, developed fordata storage applications, includes the following characteristics:

• Single capstan drive units containing magnetic read/write heads andelectronics for read/write, motion control, and system interface functions.

• Data cartridges containing up to 1,500 feet of quarter-inch magnetic tape, withintegral tape motion and guidance mechanisms.

• Data is recorded on up to 144 tracks along the length of the tape in serial,serpentine fashion, with storage capacities currently ranging up to 13 GB(uncompressed).

Travan technology is one implementation of the QIC format using shorter lengthtape. The Travan Quarter-Inch Cartridge (mini-QIC) has grown from the desktopmarket. Early products had floppy interface drives with limited server features.Early mini-QIC drives had capacities of 100-200 MB.

The initial Travan class mini-QIC drives allowed use of a larger capacity datacartridge, and extended capacities to 400 MB and more.

TR1, TR2, and TR3 drives use a diskette drive interface. The TR1 has a 400 MBcapacity, the TR2 capacity is doubled to 800 MB, and the TR3 capacity is doubledagain to 1.6 GB.

A TR3 drive has a data storage capacity of 1.3 GB native and 3.2 GB usingsoftware data compression, using the QIC-3020 tape format cartridges, and atypical transfer rate of 250 KBps. TR3 drives have a 3.5-inch form factor andtypically have a floppy interface for connection to a spare floppy disk connectorwhich can be found in most servers. Read and write compatibility is provided withthe QIC-3010, and QIC-80 tape format.

A TR4 drive has a data storage capacity of 4.0 GB native and 8.0 GB withsoftware controlled data compression using TR4 tape cartridges from 3M in theQIC-3095 tape format, and a sustained transfer rate of 600 KBps. TR4 drives aretypically available in 3.5-inch form factor, and have both SCSI and ATAPI (EIDE)interfaces. The TR4 provides read and write compatibility with the QIC-3080 tapeformat.

The TR5 drives (renamed NS20) offer a 10 GB native data storage capacity, withsustained transfer rates of 1 MBps, and added Netfinity server features(read-while-write and hardware data compression) which helps it to bridge thegap from being a desktop device to a true server class backup option.

The advantages of the Travan mini-QIC drives are that they are low cost, and areavailable in a compact (3.5-inch slimline) form factor. However, the data cartridgecosts can be higher than 4 mm and 8 mm tape. Another disadvantage is thatevery time the cartridge is inserted, all ¼-inch drives read the tape header, andsearch to the beginning of the tape to check if any data is written on the tape.This process can take a minute or two.


Compatibility between QIC formats varies by tape drive model and manufacturer.The minimum acceptable compatibility is 1 level downward read only. This allowsthe customer to upgrade to the next level of capacity without losing backup data.For a quick comparison of IBM’s Travan technology tape drives and the QICformat compatibility see Table 11.

Table 11. QIC formats supported by IBM tape drives (N/S not supported)

Capacity is stated in normal and compressed mode, for example 10/20. The first,or lower, figure is the capacity of the cartridge when the data is written in normalmode. The second figure is the maximum expected storage capacity when usingdata compression.

3.1.5 Magstar 3570 MP Fast Access Linear tape cartridgeBecause the Magstar MP Fast Access Linear tape cartridge has been speciallydesigned for repeated handling, it is ideal for use in automated libraries. The tapemedium is protected from outside environmental factors as it is enclosed in thecartridge at all times. Two tape spools inside the cartridge hold the tape. The tapepath, unique in design, also eliminates tape thread time, creates a simplified tapepath, and provides higher reliability.

Load point is established at the tape mid-point for fastest loading and access todata. The tape itself is a metal particle tape, developed for durability and capacity.Data write is provided by an exclusive thin-film write module that is designed forextremely accurate recording. Data read is provided by IBM's leading MR headbased on Magstar 3590 technology.

The 8-track head of the Magstar MP Model C tape drive also provides dataredundancy and servo tracking to ensure superior data integrity in the mid-rangetape marketplace.

The B-Format cartridge is designed to be read and written in the 3570-B1A tapedrive, and the C-Format cartridge is designed for the Magstar MP Model C tapedrive. However, to preserve compatibility between the 3570-B1A tape drive andMagstar MP Model C tape drive, the Magstar MP Model C tape drive can read thecartridges written by the 3570-B1A tape drive and write to B-Format cartridgesthat can then be read by a 3570-B1A tape drive. The 3570-B1A tape drive rejectsC-Format cartridges as “invalid media”.

Figure 19 shows two views of the Magstar MP tape cartridge:

Tape Formats Capacity IBM TR3 TapeDrive

IBM TR4 TapeDrive

IBM 10/20 GBNS Tape Drive

QIC 3020 1.3/3.2 GB Read and Write N/S N/S

QIC 3080 1.6 GB N/S Read and Write N/S

QIC 3095 4/8 GB N/S Read and Write Read Only

QIC 3220 10/20 GB N/S N/S Read and Write


Figure 19. Magstar MP Fast Access Linear Tape cartridge

3.1.5.1 B-Format data cartridgeData is written on or read from metal particle tape enclosed in a tape cartridge.Each tape cartridge includes a file-protect selector that, when placed in theupward position write-protects the tape.

A B-Format data cartridge is identified by a blue file-protect selector.

The automatic cartridge loader in the drive opens the cartridge door and allowsthe read/write element to access the tape path. The cartridge door remainsclosed during storage and handling to protect the medium and tape path fromcontamination.

Each data cartridge is identified by a factory-applied volume serial number(volser) and bar code. Another label is placed on the cartridge along the bottomof the plastic face. The label reads IBM Magstar MP Fast Access Linear Tape inblue lettering.

The capacity of a B-Format cartridge is 5 GB in uncompressed, or native, mode.The B-Format cartridge can be used in both Model B and Model C tape drives.

3.1.5.2 C-Format data cartridgeA C-Format cartridge has the same external format and can be described in thesame way as a B-Format cartridge. A C-Format cartridge is identified by a greenfile-protect selector. The label reads IBM Magstar MP Fast Access Linear Tape,C-Format in green lettering.

The capacity of a C-Format cartridge is 5 GB in uncompressed, or native, mode,the same capacity as the B-Format cartridge.

The C-Format cartridge is supported only by the Magstar MP Model C tape drive.If a C-Format cartridge is mounted in a 3570-B1A tape drive, the tape driverejects it with an error message.

Head Contact

Cartridge DoorTwin Reels

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAA

AAAAAA



AAAAAAAAAAAAA



AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

AAAAAAAAAAAAAAA

AAAAAA

ch1f03


3.1.5.3 C-XL format data cartridgeThe C-XL format is an extended version of the C format cartridge, which providesa larger capacity. The C-XL can hold up to 7 GB uncompressed data.

3.1.6 Linear Tape Open (LTO)LTO (Linear Tape Open) is a joint IBM, HP and Seagate initiative to create new defacto tape standards in the Open System markets. The group developed theformats to serve multiple market areas and to be supported by multiple suppliers.These formats provide customers with a clear and straightforward technologyroad map, destined to have broad industry support.

Licenses are available to all manufacturers for the two formats based on thetechnology: Ultrium, a single-reel implementation, optimized for high-capacity,that offers up to 200 GB of capacity assuming a 2:1 compression ratio (100 GBnative) and Accelis, a dual-reel implementation, designed for fast access, thatoffers smaller capacity, at 25 GB, but with data retrieval in under 10 seconds.Magstar technologies are at the foundation of the LTO specifications. Thisincludes the extension of the Magstar method of writing data, the linearserpentine Magstar track recording, an enhanced servo tracking mechanismbased on the Magstar MP servo system, a compression scheme derived from thesame algorithm as the Magstar LZ1 algorithm, error correction code based on theMagstar architecture, magnetically sensitive highly stable metal particle mediaused in Magstar today, and the implied use of MR heads already in the Magstarproducts.

An important fact regarding SAN solutions is the provision of a nativefibre-channel interface that will be available on products of the LTO format. Thisenhances configurations and it is not necessary to use a Gateway. The devicecan be directly attached to switches for easier fan-out.

Figure 20. LTO cartridge formats

ACCELIS ULTRIUM


3.1.6.1 UltriumThe Ultrium tape format is the implementation of LTO technology optimized forhigh capacity and performance with outstanding reliability, in either a stand-aloneor an automated environment. The Ultrium tape format uses a single reelcartridge to maximize capacity. It is ideally suited for backup, restore, and archivalapplications. They will load in a manner similar to DLT and will fit in DLTautomation slots. Here are the basic specifications of the Ultrium tape format:

• The first generation of Ultrium allows for 100 GB native capacity in a singlecompact cartridge. The cartridge is smaller than existing single-reel tapecartridges.

• Ultrium provides for data transfer rates of 10-20 MBps with the 8-channel headversion and 5-10 MBps with the 4-channel head version.

• Ultrium provides for 4 different cartridge capacities (10, 30, 50, and 100 GB).

• LTO-CM (Cartridge Memory) enhances functionality by providing a redundantfile log as well as user-defined information. A non-contacting passive RFinterface embedded in the cartridge allows remote reading of the contentswithout having to insert the cartridge into a drive.

3.1.6.2 AccelisThe Accelis tape format is the implementation of LTO technology optimized forfast access to data, with exceptional reliability and performance characteristics. Ituses a two-reel cartridge that loads at the middle of the tape to minimize accesstime. The Accelis tape format is targeted at automated environments and canenable a wide range of online data inquiry and retrieval applications.

• The first generation of Accelis allows 25 GB native capacity. Aself-enclosedtape path in the cartridge eliminates tape threading, which greatly improvestime to first data byte.

• Cartridges are loaded in the middle of the tape rather than at the beginning,reducing average search time for random files.

• Accelis provides for data transfer rates of 10-20 MBps with the 8-channel headversion or 5-10 with MBps with the 4-channel head version in the firstgeneration.

• Accelis is ideal for library use, with high-speed access to relatively short files.Accelis is suited for applications like data mining and image retrieval, as wellas traditional backup/restore.

• LTO-CM (Cartridge Memory) enhances functionality by providing a redundantfile log as well as user-defined information. A non-contacting passive RFinterface embedded in the cartridge allows remote reading of the contentswithout having to insert the cartridge into a drive.

For more information, see:

http://www.storage.ibm.com/hardsoft/tape/lto/lto.htm



3.1.7 SummaryTable 12 shows an overview of all currently used tape technologies and whichtape drives use them. Actual capacity and transfer rates depend on many factors,and are often less than stated.

Table 12. Tape drive standards overview

3.2 40/80 GB DLT tape drive

The IBM 40/80 GB DLT tape drive is a SCSI-2 Fast/Wide LVDS/SE tape device,using a 68-pin SCSI connector, that functions according to DLT8000 standards(see 3.1.1, “Digital Linear Tape (DLT)” on page 36). The tape drive has a capacityup to 40 GB, with a sustained transfer rate of 6 MBps (20 MBps burst transferrate). If hardware compression is used, capacity and transfer rate typicallydouble. These numbers can be obtained by using DLT IV 1700 foot datacartridges. The tape drive is also downward read compatible with DLT III and DLTIII xt cartridges (see 3.1.1, “Digital Linear Tape (DLT)” on page 36).

Changes in mechanical and electrical design have improved reliability comparedto earlier DLT devices. The current MTBF is rated at 250 000 hours with a 100%duty cycle.

One model is available from IBM with a black front bezel that matches with thecurrent Netfinity servers. It is an internal device, but also can be used as an

Technology Tape Drive Capacity (native) Native TransferRate

TR5 IBM 10/20 GB NS 10 GB 1 MBps

DDS-3 IBM 12/24 DDS-3 DAT 12 GB 1 MBps

DDS-4 IBM 20/40 DDS-3 DAT 20 GB 2.75

Mammoth IBM 20/40 GB 8 mmIBM 3449 8 mm Tape Library

20 GB 3 MBps

DLT 4000 IBM 20/40 GB DLT 20 GB 1.5 MBps

DLT 7000 IBM 35/70 GBIBM 3447 DLT Tape LibraryIBM 3502 machines

35 GB 5 MBps

DLT8000 IBM 40/80 GB 40 GB 6 MBps

3570 TapesC-XL-Format

IBM Magstar MP 3570 and3575 libraries

6 GB 7 MBps

LTO UltriumStage 1

100 GB 5 MBps

LTO AccelisStage 1

25 GB 5 MBps

Low voltage differential SCSI, or LVDS, is an implementation of differentialSCSI using the Single-Ended (SE) interface.

Note



external device. For this, you can use one of the following two externalenclosures:

1. The IBM DLT External SCSI Enclosure

When using this external enclosure, make sure to add a terminator, which isnot included in with the enclosure.

2. The IBM NetMEDIA storage expansion unit EL

The NetMEDIA enclosure features two 5.25-inch full-height bays, housing anycombination of up to four half-height or two full-height tape drives and isdesigned to fit into a Netfinity NetBAY3 Stackable Enclosure or the NetfinityRack Cabinet, or an equivalent EIA standard 19-inch rack.

Figure 21. NetMEDIA drive installation overview

The following machines support this tape device:

• Netfinity 3500 M10• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 5600• Netfinity 7000 M10• Netfinity 8500R

Support information is updated at the ServerProven URL whenever newmachines are announced and become available:

http://www.pc.ibm.com/us/compat/storage/matrix.shtml



The tape drive is shipped with the following items:

• User manual

• Trial version backup/restore software CD-ROMs, containing:

• Seagate Backup Exec

• CA ArcserveIT

These trial versions typically expire within 90 days after installation. Forinformation on getting permanent copies, please refer to the IBM tape Website at:

http://www.ibm.com/pc/us/solutions/accessories/tapedrives.html

• Data cartridge

Note: A SCSI terminator is not included with the tape drive.

3.2.1 InstallationInstalling the tape drive will require three main steps:

1. Installing the hardware2. Installing SCSI cables and SCSI setup3. Installing power cables

The tape device fits into two adjacent half-high 5.25-inch bays. For each of thesupported servers where the drive is supported internally, the drive fits in specificinternal bays.

• Netfinity 3500 M10

The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 3500-M10 has a standard 68-pinexternal SCSI connector, to which the external enclosure can be connected.

• Netfinity 5500 (including M10 and M20)

The drive will be installed in bays A and B, combining these two half-heightbays to one full height. The tape can be connected to the internal two-dropSCSI cable, which is self-terminating. Therefore, no additional SCSIterminator is needed. The SCSI cable itself should be connected to thesecond RAID channel connector.

• Netfinity 5600

The drive will be installed in bays A and B, combining these two half-heightbays to one full-height. The tape can be connected to the supplied internalSCSI cable, which is self-terminating. Therefore, no additional SCSIterminator is needed. When the internal SCSI onboard channel is used for thehard disks, an additional SCSI adapter (for example, the IBM PCI Fast/WideUltra SCSI Adapter) should be installed. When an optional RAID adapter isinstalled, connected to the hot-swap disk backplane, the onboard SCSIadapter can be used to connect the tape drive.


The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 7000-M10 has an external 0.8 mm veryhigh density connector, to which the external enclosure can be connected.


http://www.ibm.com/pc/us/solutions/accessories/tapedrives.html


• Netfinity 8500R

The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 7000-M10 has an external 0.8 mm veryhigh density connector, to which the external box can be connected.

• IBM DLT External SCSI Enclosure

When installing the tape drive into this external enclosure, be sure to add anactive terminator to the rear of the enclosure. The 68-pin connector of theenclosure, can be connected to an external SCSI connector on the Netfinitysystem. An external cable is not included, so it should be ordered separately.Internally, connect the tape drive to the 68-pin cable, connect power, andconnect the SCSI ID cable to the SCSI jumpers on the device. Remove allother jumpers before doing this.

• IBM NetMEDIA SCSI Expansion unit EL

The NetMEDIA enclosure can hold up to two DLT drives. The internal cablingis terminated, so the device itself must not be. You will have to set the requiredSCSI ID on the tape drive. Attach the 68-pin internal SCSI cable and power tothe tape device. The external SCSI connection on the NetMEDIA enclosureconsists of a 0.8 mm VHD connector.

The 40/80 GB DLT tape drive uses a single-ended low voltage differentialFast/Wide Ultra-2 interface. To connect the tape device to the SCSI adapter, youwill need a cable providing a 68-pin connector. The first step is to set the SCSI IDso that it does not conflict with any other devices on the bus. SCSI IDs can be setfrom 0 to 15. The factory default is SCSI ID 5.

Next, you will have to check if termination is necessary. If your tape device is thelast device on the SCSI bus, you will need to terminate it using a 16-bit activeterminator. The tape device itself cannot be used as a terminator. You also needto provide termination power, which is enabled by setting the correct jumper onthe left side of the tape device, and shown as 5 in Figure 22.

Figure 22. 40/80 GB DLT SCSI switch blocks

Assign the drive to one of the higher priority IDs available (0-6). Assign thelower IDs to faster, more accessed devices. Do not assign SCSI ID 7, which isusually the SCSI adapter ID.

Note

1 Right side view2 Left side view3 SCSI ID jumper block4 SCSI termination jumper block5 SCSI termination power jumper6 SCSI parity jumper block7 SCSI parity jumper


When SCSI-2 or higher adapters and devices are used each adapter and devicecan supply termination power. As a general rule, only the adapter should supplytermination power. If the SCSI cable is longer than 1.2 meters, termination powershould also be supplied from the last device on this cable, but no other devices insuch a chain should have termination power enabled.

If you are planning to connect the tape to a bus that already has other devicesconnected, adhere to the following guidelines:

• Connect the tape after fast 16-bit devices (like hard disks).• Ensure that all 8-bit devices (for example CD-ROMs) are connected after the

tape device.


The IBM 35/70 GB DLT tape drive is a SCSI-2 Fast/Wide tape device, using a68-pin SCSI connector, that functions according to DLT7000 standards (see3.1.1, “Digital Linear Tape (DLT)” on page 36). The tape drive has a capacity up to35 GB, with a sustained transfer rate of 5 MBps (20 MBps burst transfer rate). Ifhardware compression is used, capacity and transfer rate typically double. Thesenumbers can be obtained by using DLT IV 1700 foot data cartridges. The tapedrive is also downward read compatible to DLT III and DLT III xt cartridges (see3.1.1, “Digital Linear Tape (DLT)” on page 36).

The IBM 35/70 GB DLT Tape Drive was withdrawn from marketing at the end of1999. This section was kept in this edition for reference.

Withdrawn from marketing

DLT tape drives use the LZ-1 compression algorithm, a variant of theLempel-Ziv compression algorithm. Actual compression ratios can differ fromthe published 2 to 1 ratio. Binary files will typically compress to a 1.5 to 1 ratio,and image files up to a 4 to 1 ratio. Files that have been previously compressedhowever, will typically increase 5% in size. That is why combining software andhardware compression is inadvisable.

Note


Figure 23. 35/70 GB DLT tape drive

One model is available from IBM with a black front bezel that matches the currentNetfinity servers. It is an internal device. In addition, it can be used as an externaldevice. For this, you can use one of the following two external enclosures:

1. The IBM DLT External SCSI Enclosure. When using this external enclosure,be sure to add an active terminator.

2. The IBM NetMEDIA storage expansion unit EL.


• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 7000 M10



The tape drive is shipped with the following items:

• User’s guide• Data cartridge• Internal 4-drop 68-pin SCSI cable

The DLT drive included in the IBM 3447 library and its optional second driveare not compatible with the IBM 35/70 GB DLT Tape Drive. They are the samedrive but have different firmware. Consequently they cannot be interchanged.

Note



• Application software CD-ROM, containing:• Seagate Backup Exec Version 7.0 or later for Windows NT• Seagate Backup Exec Version 7.5 or later for Novell NetWare• Sytos Premium for OS/2 Version 2.2a

Note: A 16-bit active SCSI terminator is not included with the tape drive.


1. Installing the hardware2. Installing SCSI cables and SCSI setup3. Installing power cables

The tape device fits into two adjacent half-high 5.25-inch bays. For each of thesupported servers, the drive fits in specific internal bays:

• Netfinity 5000

The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 5000 has a standard 68-pin externalSCSI connector, to which the external enclosure can be connected.


The drive will be installed in bays A and B, combining these two half-heightbays to one full-height. The tape can be connected to the internal two-dropSCSI cable, which is self-terminating. Therefore, no additional SCSIterminator is needed. The SCSI cable itself should be connected to thesecond RAID channel connector.


The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 7000 M10 has an external 0.8 mm veryhigh density connector, to which the external enclosure can be connected.


When installing the tape drive in this external enclosure, be sure to add anactive terminator to the rear of the enclosure. The 68-pin connector of theenclosure can be connected to an external SCSI connector on the Netfinitysystem. An external cable is not included, so it should be ordered separately.Internally, connect the tape drive to the 68-pin cable, connect power, andconnect the SCSI ID cable to the SCSI jumpers on the device. Remove allother jumpers before doing this.

• IBM NetMEDIA SCSI expansion unit EL

The NetMEDIA enclosure can hold up to two DLT drives. The internal cablingis terminated, so the devices must not be. You will have to set the requiredSCSI ID on the tape drive. Attach the 68-pin internal SCSI cable and power tothe tape device. The external SCSI connection on the NetMEDIA enclosureconsists of a 0.8 mm very high density (VHD) connector.

Note: For each of these servers, if the tape drive is the last (or only) device on theSCSI channel, a 16-bit terminator should be connected to the end of the cable toensure proper termination of the SCSI bus.


The 35/70 GB DLT tape drive uses a single-ended SCSI-2 Fast/Wide interface. Toconnect the tape device to the SCSI adapter, you will need a cable providing a68-pin connector. The first step is to set the SCSI ID so that it does not conflictwith any other devices on the bus. SCSI IDs can be set from 0 to 15. The factorydefault is SCSI ID 5.

Next, you will have to check if termination is necessary. If your tape device is thelast device on the SCSI bus, you will need to terminate it using a 16-bit activeterminator. You also need to provide termination power, which is enabled bysetting the correct jumper on the left side of the tape device, and shown as 5 inFigure 24.

Figure 24. 35/70 GB DLT SCSI switch blocks

When SCSI-2 or higher adapters and devices are used each adapter and devicecan supply termination power. As a general rule, only the adapter should supplytermination power. If the SCSI cable is longer than 1.2 meters, termination powershould also be supplied from the last device on this cable, but no other devices inthe chain should have termination power enabled.

If you are planning to connect the tape drive to a bus that already has otherdevices connected, adhere to the following guidelines:

• Connect the tape after fast 16-bit devices (like hard disks).• Ensure that all 8-bit devices (for example CD-ROMs) are connected after the

tape device.


The IBM 20/40 GB DLT Tape Drive is a SCSI-2 Fast tape device, using a 50-pinSCSI connector, that functions according to DLT4000 standards (see 3.1.1,“Digital Linear Tape (DLT)” on page 36). The tape drive has a capacity up to 20GB, with a sustained transfer rate of 1.5 MBps (10 MBps burst transfer rate). Ifhardware compression is used, capacity and transfer rate typically double. Thesenumbers can be obtained by using DLT IV 1700 foot data cartridges. The tapedrive is also downward read compatible with DLT III and DLT III xt cartridges (see3.1.1, “Digital Linear Tape (DLT)” on page 36).

1 Right side view2 Left side view3 SCSI ID jumper block4 SCSI termination jumper block5 SCSI termination power jumper6 SCSI parity jumper block7 SCSI parity jumper


Figure 25. 20/40 GB DLT tape drive

The IBM 20/40 GB DLT tape drive is an internal device. However, you can install itin an external enclosure. The following two external enclosures are available:

1. The IBM DLT External SCSI Enclosure. When using this external enclosure,make sure to add a terminator.

2. The IBM NetMEDIA storage expansion unit EL.


• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 5600• Netfinity 7000 M10• Netfinity 8500R



The shipment group contains the following items:

• Base drive• Manual

DLT tape drives use the LZ-1 compression algorithm, a variant of theLempel-Ziv compression algorithm. Actual compression ratios can differ fromthe published 2 to 1 ratio. Binary files will typically compress to a 1.5 to 1 ratio,and image files up to a 4 to 1 ratio. Files that have been previously compressedhowever, will typically increase 5% in size. That is why combining software andhardware compression is inadvisable.

Note



• Application software CD-ROM, containing:• Seagate Backup Exec Version 7.0 or later for Windows NT• Seagate Backup Exec Version 7.5 or later for Novell NetWare• Sytos Premium for OS/2 Version 2.2a

• One data cartridge• SCSI wide-to-narrow (68-pin to 50-pin) converter• Internal SCSI fast/wide cable• SCSI terminator


• Installing the hardware• Installing SCSI cables and SCSI setup• Installing power cables

The tape device fits into two adjacent half-high 5.25-inch bays. For each of thesupported servers where the drive is supported internally, the drive fits in specificinternal bays.

• Netfinity 5000

The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 5000 has a standard 68-pin externalSCSI connector, to which the external enclosure can be connected.


The drive will be installed in bays A and B, combining these two half-heightbays to one full-height. The tape can be connected to the internal two-dropSCSI cable using the supplied 68-50 pin converter. Since this cable isself-terminating, you should not enable termination on the device. The SCSIcable itself should be connected to the second RAID channel connector.

• Netfinity 5600

The drive will be installed in bays A and B, combining these two half-heightbays to one full-height. The tape can be connected to the supplied internalSCSI cable using the supplied 68-50 pin converter. Since this cable isself-terminating, you should not enable termination on the device. When theinternal SCSI onboard channel is used for the hard disks, an additional SCSIadapter (for example the PCI Fast/Wide Ultra SCSI Adapter) should beinstalled. When an optional RAID adapter is installed, connected to thehot-swap disk backplane, the onboard SCSI adapter can be used to connectthe tape drive.



• Netfinity 8500R

The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 8500R has an external 0.8 mm veryhigh density connector, to which the external enclosure can be connected.



When installing the tape drive into this external enclosure, be sure to add anactive terminator to the rear of the enclosure. The 68-pin connector of theenclosure can be connected to an external SCSI connector on the Netfinitysystem. An external cable is not included, so it should be ordered separately.Internally, connect the tape drive to the 68-pin cable using the supplied 68-50pin converter, connect power, and connect the SCSI ID cable to the SCSIjumpers on the device. Remove all other jumpers before doing this.


The NetMEDIA enclosure can hold up to two DLT drives. The internal cablingis terminated, so the devices must not be. You will have to set the requiredSCSI ID on the tape drive. Attach the 68-pin internal SCSI cable, using the68-50 pin convertor, and power to the tape device. The external SCSIconnection on the NetMEDIA enclosure consists of a 0.8 mm VHD connector.

Note: For each of these servers, if the tape drive is the last (or only) device on theSCSI channel, a 16-bit terminator should be connected to the end of the cable toensure proper termination of the SCSI bus. A terminator is supplied with the tapedrive.

The 20/40 GB DLT tape drive uses a single-ended SCSI-2 Fast interface. Toconnect the tape device to the SCSI adapter, you will need a cable providing a68-pin connector, and a wide-to-narrow convertor, which converts the 68-pinconnector on the cable to a 50-pin connector, as found on the device.

The first step is to set the SCSI ID so that it does not conflict with any otherdevices on the bus. SCSI IDs can be set from 0 to 7. The factory default is SCSIID 5. Next, you will have to check if termination is necessary.

If your tape device is the last device on the SCSI bus, you will need to terminate itusing a 16-bit active terminator. The tape device itself cannot be used as aterminator. That is why you will need to install the included terminator. You alsoneed to provide termination power, which is enabled by setting the correct jumperon the tape device.

Figure 26. SCSI ID jumpers (left side view)

1 SCSI ID Jumper Block


Figure 27. SCSI termination jumper block (right side view)

When SCSI-2 or higher adapters and devices are used each adapter and devicecan supply termination power. As a general rule, only the adapter should supplytermination power. If the SCSI cable is longer than 1.2 meters, termination powershould also be supplied from the last device on this cable, but no other devices inthe chain should have termination power enabled.

If you are planning to connect the tape to a bus that already has other devicesconnected, ensure that you connect the tape device after all 16-bit devices. Thiswill allow the 16-bit devices to work at their nominal speed.

3.5 20/40 GB 8 mm tape drive

The 20/40 GB 8 mm internal SCSI tape drive uses the Mammoth tape technology,providing a 20 GB native (uncompressed) data storage capacity, with a sustainedtransfer rate of 3 MBps (uncompressed). These figures are doubled with the useof the hardware controlled data compression, allowing 20 GB of critical data to bebacked up in just about two hours. The 20/40 GB 8 mm tape drive uses the 170meter Advanced Metal Evaporated (AME) cartridge from Exabyte, IBM and Sony.The tape drive is black in color and matches the IBM Netfinity servers.

Figure 28. The 20/40 GB 8 mm tape drive

The tape drive has a SCSI-2 fast/wide interface. The tape drive is designed to beinstalled in a half-high, 5.25-inch drive bay. It has a black front bezel.

This tape drive is read compatible with Exabyte formats.

2 Jumper Block3 Parity Jumper4 Power Termination Jumper



• Netfinity 3500 M10• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 5600• Netfinity 7000 M10• Netfinity 8500R



The IBM 20/40 GB 8 mm tape drive is an internal device. However, you can installit in an external enclosure. The following two external enclosures are available:

1. The IBM external half-height SCSI storage enclosure


The 20/40 8 mm tape drive is shipped with the following components:

• IBM 20/40 GB 8 mm Tape Drive• One data cartridge• One cleaning cartridge• Multi-lingual manual• Four mounting screws• Application software CD-ROM

The physical specifications of the device are as follows:

• Height: 42.9 mm (1.69 inches)• Width: 208.3 mm (8.2 inches)• Depth: 149.1 mm (5.87 inches)

3.5.1 InstallationInstalling the tape drive is comprised of three main steps:


The tape fits in a single half-height 5.25-inch drive bay. It has a standard 68-pinSCSI connector and standard internal power connector, as shown in Figure 29 onpage 61. For each of the supported servers where the drive is supportedinternally, the drive fits in specific internal bays.

The tape drive can also read data from metal particle (MP) tape when it iswritten in 8500c, 8500, or 8200 formats. The drive cannot write to an MPtape or read data written in 8200c format. Before using an AME cartridgeafter reading an MP tape, clean the tape drive.

Tape Compatibility




The drive should be installed in bay 2. It connects to the internalself-terminating cable. Therefore, no additional termination is required. Sincethis cable is also used to connect the disk backplane, it cannot be used toconnect the tape drive when a RAID adapter is added to the system. In thatcase, an additional internal two-drop cable is needed.

• Netfinity 5000

The drive should be installed in bay A. It connects to the internalself-terminating cable. Therefore, no additional termination is required. Sincethis cable is also used to connect the disk backplane, it cannot be used toconnect the tape drive when a RAID adapter is added to the system. In thatcase, an additional internal two-drop cable is needed.


The drive can be installed in bay A or B. The tape can be connected to theinternal two-drop SCSI cable using the supplied 68-50 pin converter. Sincethis cable is self-terminating, you should not enable termination on the device.The SCSI cable itself should be connected to the second RAID channelconnector.

• Netfinity 5600

The drive can be installed in bay A or B. The tape can be connected to thesupplied internal SCSI cable. Since this cable is self-terminating, you shouldnot enable termination on the device. When the internal SCSI onboardchannel is used for the hard disks, an additional SCSI adapter (for examplethe IBM PCI Fast/Wide Ultra SCSI Adapter) should be installed. When anoptional RAID adapter is installed, connected to the hot-swap disk backplane,the onboard SCSI adapter can be used to connect the tape drive.



• Netfinity 8500R

The drive is not supported as an internal device. Therefore, it should beinstalled in an external enclosure. The 8500R has an external 0.8-mm veryhigh density connector, to which the external enclosure can be connected.

• IBM External SCSI half-height enclosure

Since the standard cabling of this enclosure follows the narrow (50-pin)standards, you need to replace this with the provided 68-pin wide cabling.When installing the tape drive into this external enclosure, be sure to add anactive terminator to the rear of the enclosure. The 68-pin connector of theenclosure, can be connected to an external SCSI connector on the Netfinitysystem. An external cable is not included, so it should be ordered separately.Internally, connect the tape drive to the 68-pin cable, connect power, andconnect the SCSI ID cable to the SCSI jumpers on the device. Remove allother jumpers before doing this.


The NetMEDIA enclosure can hold up to four 8 mm drives. The internalcabling is terminated, so the devices must not be. You will have to set the


required SCSI ID on the tape drive. Attach the 68-pin internal SCSI cable andpower to the tape device. The external SCSI connection on the NetMEDIAenclosure consists of a 0.8 mm VHD connector.

Figure 29. Rear view of 20/40 GB 8 mm tape drive

When setting the SCSI ID on the tape drive ensure that it does not conflict withany other devices on the same SCSI bus. SCSI IDs can be set from 0 to 15. Thefactory default for this tape drive is SCSI ID 5. Do not use ID 7 as this is usuallyassigned to the SCSI host adapter. It is best to assign the tape drive to the lowestpriority ID available (that is the biggest number), and leave higher prioritynumbers to those devices that are most often used or are faster than otherdevices in the chain.

If the tape drive is the last device on the SCSI bus, the chain must be terminatedat the drive using a 16-bit SCSI terminator.

3.5.2 ConfigurationWhen the server is switched on, the tape drive performs a power-on self-test(POST) within 30 seconds and performs a drive reset. It is important to not inserta tape cartridge into the tape drive during POST, as the tape drive will simplyeject it.

The LCD on the front of the tape drive, as shown in Figure 30 on page 62, iscapable of displaying messages in a number of languages. To change thelanguage, press and hold the Unload button. After the Reset message appearson the LCD, the LCD cycles through the available languages: English, German,French, Spanish, Italian, Portuguese. When the desired language is displayed,release the Unload button.

During the reset sequence, the tape drive rewinds the tape in the unit andrestores the drive to its initial state. When the tape drive is ready to accept acartridge, the indicator lights on the front panel of the tape drive turn off. Once acartridge is inserted into the tape drive, it will take approximately 20 seconds forthe tape drive to load it before the middle indicator lights show it is ready for readand write operations.

1 Ground hole2 Grounding tab3 Pin 1 of the SCSI connector4 Service port (reserved)5 Power connector6 SCSI ID jumper block7 SCSI connector


Figure 30. Front view of 20/40 GB 8 mm tape drive

3.6 20/40 GB DDS-4 4 mm tape drive

The IBM 20/40 GB DDS-4 4 mm tape drive is an internal Ultra-2 SCSI low voltagedifferential device. The drive can store up to 20 GB in native capacity, and up to40 GB via hardware data compression, on an industry standard DDS-4 datacartridge. The tape drive is downward read/write compatible with the IBM 4/10GB DDS-2 and 12/24 GB DDS-3 drives.

The drive has a 68-pin SCSI connector at the rear of the unit. The native transferrate is 2.75 MBps. This figure is typically doubled when hardware compression isused.

The following servers support this tape drive:

• Netfinity 1000• Netfinity 3000• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5600



The IBM 20/40 GB DDS-4 4 mm tape drive is an internal device. However, youcan install it in an external enclosure. The following two external enclosures areavailable:



1 Indicator lights2 LCD display3 Unload button

1 Indicator lights:•Top light (amber): Flashes when error has occurred. When lit, tape driveneeds cleaning.

•Middle light: (green): When lit, tape cartridge is loaded and tape drive isoperational.

•Bottom light (green): Flashes when tape is in motion.2 LCD shows information about the operational status of the tape drive.

3

When announcing this device, IBM gave a statement of direction that anautoloader based upon DDS-4 tape drives would be announced in the year2000.

Note



The tape drive includes the following components:

• User’s guide (multilingual)• Application software CD-ROM containing Seagate Backup Exec and Arcserve

trial software• Data cartridge• Cleaning cartridge• Black 5.25 and 3.5-inch faceplates



The tape fits in a single half-height 5.25-inch or 3.5-inch bay. It has a standard68-pin SCSI connector and standard internal power connector. For each of thesupported servers where the drive is supported internally, the drive fits in specificinternal bays.

• Netfinity 3000

The drive should be installed in bay 2. It connects to the internalself-terminating cable. Therefore, no additional termination is required.

• Netfinity 5000

The drive should be installed in bay A. It connects to the internalself-terminating cable. Therefore, no additional termination is required. Sincethis cable is also used to connect the disk backplane, it cannot be used toconnect the tape drive when a RAID adapter is added to the system. In thatcase, an additional internal two-drop cable is needed.


The drive cna be installed in bay A or B. The tape can be connected to theinternal two-drop SCSI cable. Since this cable is self-terminating, you shouldnot enable termination on the device. The SCSI cable itself should beconnected to the second RAID channel connector.

• Netfinity 5600

The drive can be installed in bay A or B. The tape can be connected to thesupplied internal SCSI cable. Since this cable is self-terminating, you shouldnot enable termination on the device. When the internal SCSI onboardchannel is used for the hard disks, an additional SCSI adapter (for example,the IBM PCI Fast/Wide Ultra SCSI Adapter) should be installed. When anoptional RAID adapter is installed, connected to the hot-swap disk backplane,the onboard SCSI adapter can be used to connect the tape drive.


Since the standard cabling of this enclosure follows the narrow (50-pin)standards, you need to replace this with 68-pin wide cabling. When installingthe tape drive into this external enclosure, be sure to add an active terminatorto the rear of the enclosure. The 68-pin connector of the enclosure can beconnected to an external SCSI connector on the Netfinity system. An externalcable is not included, so it should be ordered separately. Internally, connectthe tape drive to the 68-pin cable, connect power, and connect the SCSI ID


cable to the SCSI jumpers on the device. Remove all other jumpers beforedoing this.


The NetMEDIA enclosure can hold up to four 4 mm drives. The internalcabling is terminated, so the device itself must not be. You will have to set therequired SCSI ID on the tape drive. Attach the 68-pin internal SCSI cable andpower to the tape device. The external SCSI connection on the NetMEDIAenclosure consists of a 0.8 mm VHD connector.

3.7 12/24 GB DDS-3 4 mm tape drive

The IBM 12/24 GB DDS-3 4 mm tape drive is an internal SCSI-2 Fast device. Thedrive can store up to 12 GB in native capacity, and up to 24 GB via hardware datacompression, on an industry standard 125 meter DDS-3 data cartridge. The tapedrive is downward read/write compatible with the IBM 4/10 GB DDS-2 drive.

The drive has a SCSI-2 Fast interface and a 50-pin SCSI connector at the rear ofthe unit. The native transfer rate is 1.1 MBps. This figure is typically doubledwhen hardware compression is used.

Figure 31. 12/24 GB DDS-3 4 mm internal drive (with 5.25-inch black bezel)


• Netfinity 3000• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5500 M10• Netfinity 7000 M10



The IBM 12/24 GB DDS-3 4 mm tape drive is an internal device. However, youcan install it in an external enclosure. The following two external enclosures areavailable:





The drive includes the following components:

• User’s guide• Application software CD-ROM containing Seagate Backup Exec and Sytos

software• Data cartridge• Cleaning cartridge• Bezel kit• 68-50 pin SCSI converter

The drive is shipped with a 5.25-inch white bezel and mounting brackets alreadyinstalled, similar to Figure 31. The bezel kit contains the following additionalbezels:

• 5.25-inch black bezel• 3.5-inch black and white bezels



The tape fits in a single half-height 5.25-inch or 3.5-inch bay. It has a standard50-pin SCSI connector and standard internal power connector. For each of thesupported servers where the drive is supported internally, the drive fits in specificinternal bays.

• Netfinity 3000

The drive should be installed in bay 2. It connects to the internal SCSI cableusing the provided 68-50 pin converter. Since the internal cable isself-terminating, no additional termination is required. Due to the fact that thisdevice is an 8-bit SCSI device, be sure to add it as the last device on the SCSIchain.

• Netfinity 5000

The drive should be installed in bay A. It connects to the internal SCSI cable,using the provided 68-50 pin converter. Since the internal cable isself-terminating, no additional termination is required. Due to the fact that thisdevice is an 8-bit SCSI device, be sure to add it as the last device on the SCSIchain. Since this cable is also used to connect the disk backplane, it cannot beused to connect the tape drive when a RAID adapter is added to the system.In that case, an additional internal two-drop cable is needed.


The drive can be installed in bay A or B. The tape can be connected to theinternal two-drop SCSI cable, using the 68-50 pin converter. Since this cable isself-terminating, you should not enable termination on the device. The SCSIcable itself should be connected to the second RAID channel connector.





Since the standard cabling of this enclosure follows the narrow (50-pin)standards, you need to replace this with 68-pin wide cabling. This might lookunnecessary, due to the fact that the DDS-3 tape is a narrow device, but it willbe the only way to properly terminate the external 16-bit SCSI bus. Wheninstalling the tape drive into this external enclosure, add an active terminatorto the rear of the enclosure. The 68-pin connector of the enclosure can beconnected to an external SCSI connector on the Netfinity system. An externalcable is not included, so it should be ordered separately. Internally, connectthe tape drive to the 68-pin cable using the provided 68-50 pin converter,connect power, and connect the SCSI ID cable to the SCSI jumpers on thedevice. Remove all other jumpers before doing this.


The NetMEDIA enclosure can hold up to four 4 mm drives. The internalcabling is terminated, so the device itself should not be. You will have to setthe required SCSI ID on the tape drive. Attach the 68-pin internal SCSI cable,using the 68-50 pin converter and connect power to the tape device. Theexternal SCSI connection on the NetMEDIA enclosure consists of a 0.8 mmVHD connector.

3.8 10/20 GB NS tape drive

The IBM 10/20 GB NS (Network Series) tape drive is a Travan technology drivesuitable for many mid-range servers. It is designed for users who need higherperformance and capacity than the IBM 4/8 GB TR4 tape drive can provide butcannot yet justify the cost of a DLT solution for their backup strategy.

Figure 32. The 10/20 GB NS tape drive

Using the QIC 3220 format this drive can store up to 10 GB of data in normalmode and up to 20 GB in compressed mode. The recording media is packaged ina Travan TR5 cartridge or an NS20 cartridge. Both are functionally equivalent.The drive is downward compatible (read mode only) with the TR4 cartridge in QIC


3095 format. This allows administrators to restore data from the older backuptapes created on 4/8 GB TR4 tape drives.

The maximum data transfer rate is up to 2 MBps when using the drive’s hardwarecompression feature. Reading and writing is done in a precisely controlledcontinuous tape motion to get the most efficient use of resources. The streamingtape and serpentine recording technique combine to increase the capacity andspeed of backing up and restoring data. There is no time lost starting andstopping the tape, no space lost to inter-record gaps, and no stretching orcrimping of the tape due to intermittent tape movement.

The 10/20 GB NS tape drive has a 50-pin connector at the back of the unit. Theconnector is a SCSI-2 interface. The tape drive can be attached to a 68-pin cableby inserting a 50-pin to 68-pin converter shipped with the tape drive. If the tapedrive is the last device in the SCSI chain it must be terminated.


• Netfinity 3000• Netfinity 3500 M10• Netfinity 5000• Netfinity 7000 M10



The IBM 10/20 GB NS tape drive is an internal device. However, you can install itin an external enclosure. The following two external enclosures are available:



The following items are supplied with the tape drive:

• User’s guide• Data cartridge• Four M3 x 5 screws• Recess bezel kit• SCSI 68-50 pin SCSI converter• 5.25-inch mounting kit• Software CD-ROM containing Seagate software



The tape fits in a single half-height 5.25-inch or SL 3.5-inch bay. It has a standard50-pin SCSI connector and standard internal power connector. For each of thesupported servers where the drive is supported internally, the drive fits in specificinternal bays.



• Netfinity 3000

The drive should be installed in bay 2. It connects to the internal SCSI cableusing the provided 68-50 pin converter. Since the internal cable isself-terminating, no additional termination is required. Due to the fact that thisdevice is an 8-bit SCSI device, be sure to add it as the last device on the SCSIchain.


The drive should be installed in bay 2. It connects to the internalself-terminating cable. Therefore, no additional termination is required. Sincethis cable is also used to connect the disk backplane, it cannot be used toconnect the tape drive when a RAID adapter is added to the system. In thatcase, an additional internal two-drop cable is needed.

• Netfinity 5000

The drive should be installed in bay A. It connects to the internal SCSI cable,using the provided 68-50 pin converter. Since the internal cable isself-terminating, no additional termination is required. Due to the fact that thisdevice is an 8-bit SCSI device, be sure to add it as the last device on the SCSIchain. Since this cable is also used to connect the disk backplane, it cannot beused to connect the tape drive when a RAID adapter is added to the system.In that case, an additional internal two-drop cable is needed.




Since the standard cabling of this enclosure follows the narrow (50-pin)standards, you need to replace this with 68-pin wide cabling. This might lookunnecessary, due to the fact that the NS-20 tape is a narrow device, but it willbe the only way to properly terminate the external 16-bit SCSI bus. Wheninstalling the tape drive into this external enclosure, add an active terminatorto the rear of the enclosure. The 68-pin connector of the enclosure can beconnected to an external SCSI connector on the Netfinity system. An externalcable is not included, so it should be ordered separately. Internally, connectthe tape drive to the 68-pin cable using the provided 68-50 pin converter,connect power, and connect the SCSI ID cable to the SCSI jumpers on thedevice. Remove all other jumpers before doing this.


The NetMEDIA enclosure can hold up to four NS-20 drives. The internalcabling is terminated, so the device must not be. You will have to set therequired SCSI ID on the tape drive. Attach the 68-pin internal SCSI cable,using the 68-50 pin converter and connect power to the tape device. Theexternal SCSI connection on the NetMEDIA enclosure consists of a 0.8 mmVHD connector.


Figure 33. SCSI ID and termination jumpers

3.9 490/980 GB DLT library

The IBM 490/980 GB DLT library is a 14-cartridge library, using the DLT 7000tape drives. The library is available in both a tower model (machine type 3502,Model 314) and a rack mountable model (machine type 3502, Model R14). It isequipped with one DLT 7000 tape drive, but can be upgraded to hold up to threedrives, using the drive upgrade option. The cartridges are grouped in two,7-cartridge removable magazines.

The library functions according to the SCSI-2 single ended standard. It isequipped with 68-pin external connectors.

15 13 11 9 7 5 3 116 141210 8 6 4 2

1 Jumpered2 Not Jumpered


Figure 34. The IBM 490/980 DLT library (3502-314)

The shipment group contains the following:

• 3502-314 or 3502-R14 library• User’s guide• SCSI jumper cable• Adaptec 2940U2B SCSI host adapter• SCSI terminator• 3 meter SCSI fast/wide cable• DLT IV data cartridge• Cleaning cartridge

The drive upgrade option contains the following products:

• A DLT 7000 tape drive• SCSI jumper cable, used to complete the SCSI chain.

The library is supported on the following Netfinity systems:

• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 5600• Netfinity 7000 M10• Netfinity 8500R


3.9.1 OperationThe library can be configured to operate fully automatically, under control of asoftware application, or can be used to access tapes in a sequential mode. Thefollowing modes can be used:

• Random mode, where the host will request a specific tape to be mounted. Theloader will locate the requested tape and load it in the DLT drive.

• Sequential mode, where the loader will load all cartridges sequentially. It willstart with the cartridge in the lowest available slot (an available slot is a slot inwhich a data cartridge is loaded), and end with the last one. After this, thesequential command must be issued to restart this cycle. Cartridges areautomatically loaded when this function is enabled (see 3.9.3, “Configuration”on page 72).

• Circular sequential mode, where the loader acts the same as in sequentialmode, but automatically restarts the cycle after using the last availablecartridge.

• Autoclean mode, where the autoloader automatically loads the cleaningcartridge when a cleaning operation is necessary. When this mode is selected,one slot is reserved for a cleaning cartridge. This means that only 13 slots areavailable for data cartridges, thus reducing the maximum capacity of theautoloader.

3.9.2 InstallationThe main work in installing the library will consist of connecting the SCSI cables.Since the ship group contains all necessary material when one drive is installed,no additional options are necessary. To start, install the supplied SCSI hostadapter in the Netfinity server. Connect the 3 meter SCSI cable to the connector 8at the far right on the rear of the library. This connector connects to the SCSIinterface of the library robotic arm. Next, complete the SCSI chain by connectingthe pre-installed DLT 7000 drive (far left) using the SCSI jumper cable (1 and 7). Ifthis is the last device on the chain, install the SCSI terminator on the secondconnector 2 of the tape drive.

Figure 35. 490/980 GB DLT library rear view


To install additional tape drives, remove the metal plates. Next, slide in the tapedrive and connect internal cables (see Figure 36). These consist of power supplycables for fan 3 and tape drive 1, SCSI ID cable 2 and tape information cable 4.Next, secure the tape by inserting the panel screws. Finally, use additional SCSIjumper cables to complete the SCSI chain, again terminating the last device onthe SCSI chain.

Figure 36. Adding an additional DLT 7000 tape drive

3.9.3 ConfigurationAfter installing, the library needs to be configured. The configuration will consistof the following steps:

The above method of connecting is just an example that provides a clean,logical manner of connecting the cables. However, since this is a normal SCSIbus, you can connect each device in any order you prefer. The main concernshould be that the bus is terminated properly, and that SCSI cable lengthlimitations are not exceeded.

Note


1. Setting the SCSI ID2. Setting the mode of operation

The setup of the library is done by using the operator control panel (OCP), shownin Figure 37.

Figure 37. 490/980 GB DLT library operator control panel

As a first step, it might be necessary to change the SCSI IDs of both theautoloader controller and the DLT 7000 tape drives. By default, the SCSI ID of thecontroller is set to 0, while the pre-installed DLT 7000 tape drive is set to 1. Tochange the SCSI ID, follow the next steps:

1. Press the Select button on the OCP repeatedly until it displays the SCSI ID? selection prompt.

2. Press the Enter button. The View ID? selection for the library is shown. Bypressing the Next button, you will get the Set ID? function. Use the Enterbutton to scroll through the different devices, until you reach the Librarysetting. After pressing Enter, the current ID of the controller is shown. Pressthe Down button until it reaches the required SCSI ID. Press the Enter buttonto confirm the change.

3. By pressing Enter again, you will arrive in the set ID section for the first drive.Repeat the same procedure as for changing the ID of the controller.

4. By pressing Enter again, you will arrive in the set ID section for the next drive.Repeat the same procedure as for changing the ID of the first drive.

5. Restart the autoloader for the new SCSI IDs to take affect.

As explained in 3.9.1, “Operation” on page 71, the autoloader can function indifferent modes. As with setting the SCSI ID, the operational mode can be set byusing the operator panel. To set the mode, press the Select button on the OCPrepeatedly until it displays the MODE? selection prompt. By pressing the Downbutton, you can circulate through the different modes. Press Enter to set one ofthe modes.

In addition, you will encounter the following two modes of operation:

1. The autoload cartridge mode, which will only function when one of thesequential base modes is selected. This function enables the machine toautomatically load tapes in the drive when they are needed.

2. The enable barcode function. This function will scan the barcodes wheninitializing the autoloader. This happens when the loader is turned on, or thedoor has been opened and then closed.

This completes the setup and configuration part of the autoloader. If you needmore information, please refer to the 490/980 GB DLT Autoloader User’s Guide.

1 Display2 Previous3 Select4 Enter5 Next


3.10 280/560 GB DLT autoloader

The IBM 280/560 GB DLT autoloader is a robotic tape handling system, based onthe DLT 7000 technology (see 3.3, “35/70 GB DLT tape drive” on page 51). Itcombines one 35/70 GB DLT drive, with 8 cartridge slots. Two of those slots arefixed, while the six others are grouped in a removable magazine.

The library functions according to the SCSI-2 single ended standard. It isequipped with 68-pin external connectors.

Although the library is intended to be used as an external desktop device, it canbe mounted in a Netfinity 9306 Model 300 rack using a fixed shelf.

Figure 38. The IBM 280/560 DLT autoloader

The shipment group contains the following:

• 3502-108 library• User’s guide• SCSI jumper cable• SCSI 0.8 mm to 68-pin converter• Adaptec 2940U2B SCSI host adapter• SCSI terminator• 3 meter SCSI fast/wide cable• DLT IV data cartridge• Cleaning cartridge

The library is supported on the following Netfinity systems:

• Netfinity 5000• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 5600• Netfinity 7000 M10• Netfinity 8500R


3.10.1 OperationThe autoloader can be configured to operate fully automatically, under control ofa software application, or can be used to access tapes in a sequential mode. Thefollowing modes can be used:

• Random mode, where the host will request a specific tape to be mounted. Theloader will locate the requested tape and load it in the DLT drive.

• Sequential mode, where the loader will load all cartridges sequentially. It willstart with the cartridge in the lowest available slot (an available slot is a slot inwhich a data cartridge is loaded), and end with the last one. After this, thesequential command must be issued to restart this cycle. Cartridges areautomatically loaded when this function is enabled (see.3.10.3,“Configuration” on page 75).

• Circular sequential mode, where the loader acts the same as in sequentialmode, but automatically restarts the cycle after using the last availablecartridge.

• Autoclean mode, where the autoloader automatically loads the cleaningcartridge when a cleaning operation is necessary. When this mode is selected,one slot is reserved for a cleaning cartridge. This means that only seven slotsare available for data cartridges, thus reducing the maximum capacity of theautoloader.

3.10.2 InstallationSince the ship group of the autoloader contains all needed equipment, installationis fairly easy. To start, install the SCSI host adapter in the Netfinity system. Next,attach the SCSI fast/wide cable to the adapter and to the first connector of theautoloader. This is the SCSI interface of the autoloader controller. Next, continuethe SCSI chain to the tape drive, by connecting the SCSI jumper cable. Since oneof the connectors has a 0.8 mm SCSI connector, you will need to add the 0.8 mmto 68-pin convertor to one side of the cable. Finally, terminate the SCSI chain byadding the provided terminator.

To install the autoloader in a rack, use a fixed shelf. Refer to the IBM NetfinityRack Planning and Installation Guide for details.

3.10.3 ConfigurationAfter installation, the library will need to be configured. The configuration willconsist of the following steps:

1. Set the SCSI ID.2. Set the mode of operation.

The setup of the library is done by using the operator control panel (OCP), shownin Figure 39:


Figure 39. 260/560 GB DLT autoloader operator control panel

As a first step, it might be necessary to change the SCSI IDs of both theautoloader controller and the DLT 7000 tape drive. By default, the SCSI ID of thecontroller is set to 0, while the DLT 7000 tape drive is set to 1. To change theSCSI ID, follow the next steps:

1. Press the Select button on the operator control panel repeatedly until itdisplays the SCSI ID? selection prompt.

2. Press the Enter button. The View ID? selection for the library is shown. Bypressing the Next button, you will get the Set ID? function. Use the Enterbutton to scroll through the different devices, until you reach the Librarysetting. After pressing Enter, the current ID of the controller is shown. Pressthe Down button until it reaches the required SCSI ID. Press the Enter buttonto confirm the change.

3. By pressing Enter again, you will arrive in the set ID section for the drive.Repeat the same procedure as for changing the ID of the controller.

4. Restart the autoloader for the new SCSI IDs to take affect.

As explained in 3.10.1, “Operation” on page 75, the autoloader can function indifferent modes. As with setting the SCSI ID, the operational mode can be set byusing the operator panel. To set the mode, Press the Select button on the OCPrepeatedly until it displays the MODE? selection prompt. By pressing the Downbutton, you can circulate through the different modes. Press Enter to set one ofthe modes.

In addition, you will encounter the following two modes of operation:

1. The autoload cartridge mode, which will only function when one of thesequential base modes is selected. This function enables the machine toautomatically load tapes in the drive when they are needed.

2. The enable barcode function. This function will scan the barcodes wheninitializing the autoloader. This happens when the loader is turned on, or thedoor has been opened and then closed.

This completes the setup and configuration part of the autoloader. If you needmore information, please refer to the 280/560 GB DLT Autoloader User’s Guide.

1 Display2 Previous3 Select4 Enter5 Next


3.11 3447 DLT Tape Library

The 3447 digital linear tape (DLT) library is a robotic tape handling systemcontaining one or two DLT 7000 tape drives. These provide a native data transferrate up to 5 MBps and a data storage capacity 35 GB. If hardware compression isused, the transfer rate can go up to 10 MBps and 70 GB of storage capacity. Theentire library provides up to 525 GB (or 1050 GB if hardware compression isused) of data storage capacity.

Figure 40. The 3447 DLT tape library

The total amount of data depends on the type of tape cartridges (see 3.1.1,“Digital Linear Tape (DLT)” on page 36) and the number of storage cells definedfor data tape cartridges. The tape library can hold a maximum of 15 tapecartridges. Up to 10 cartridges can be held in a removable magazine and up to 5cartridges in fixed cells located inside the library.

Two models are available:

• Model 105: desktop unit

• Model 106: rack-mountable unit. This 5U model can be installed in an industrystandard EIA-310-D 19-inch rack (such as the Netfinity rack).

The IBM 3447 DLT Tape Library was withdrawn from marketing at the end of1999. This section was kept in this edition for reference.

Withdrawn from marketing

DLT tape drives will use the LZ-1 compression algorithm, a variant of theLempel-Ziv compression algorithm. Actual compression ratios can differ fromthe published 2 to 1 ratio. Binary files will typically compress to a 1.5 to 1 ratio,and image files up to a 4 to 1 ratio. Files that have been previously compressedhowever, will typically increase 5% in size. That is why combining software andhardware compression is inadvisable.

Note


Figure 41. Major components

The tape library is designed for unattended operation. However, an operatorpanel on the front enables an operator to monitor activity, suspend operations,load and unload tape devices and run diagnostics. Additionally, the library has aRS-232 connector enabling remote diagnostics. The remote diagnostics optionsenable you to send diagnostic and information retrieval commands to the librarythrough an RS-232 interface. This can be done through a modem, or by using anull modem cable locally. For more information, see 3.11.3, “Configuration” onpage 80.

The tape library communicates with the host computer through a SCSI-2single-ended interface. The tape library can be attached to the IBM Fast/WideUltra SCSI Adapter or to an onboard SCSI interface. For performance reasons, itis recommended to attach the library to a dedicated SCSI host adapter.

• A barcode reader allowing tape cartridge configuration and inventory areincluded. Bar code labels can be attached to the tape cartridges, and canhave up to eight characters. For more information about barcodespecifications, see 3447 and 7337 Digital Linear Tape Library Setup andOperation Guide, GA32-0399.


The shipment group contains the following items:

• 3447 DLT library• One power cord• One 4.5 meter SCSI cable• One SCSI terminator• One removable cartridge magazine• One DLT format data cartridge, a cleaning cartridge and a test cartridge• Setup and operator guide• Service guide

In addition, an additional drive kit and a removable 10-cartridge magazine can beordered.

3.11.1 OperationThe 3447 has three modes of operation:

• Manual mode, which is controlled by the operator panel switches, allowingcomplete operator control.

• Autoloader mode, where the library automatically loads the cartridges into thedrives sequentially for reading and writing. The backup software has nocontrol over the robotic shuttle.

• Random mode, which allows tapes to be selected randomly by the backupsoftware for reading or writing. The backup software has full control over therobotic shuttle.

The tape library can be configured either in base library configuration or splitlibrary configuration

3.11.1.1 Base configurationIn base configuration, the tape library is connected to a single SCSI adapterwhich is installed in a server. The server is in complete control of the entire libraryand all tape drives. The tape library may be installed with a one or two tapedrives, both accessible from a single server.

3.11.1.2 Split configurationWith this configuration, the 3447 can be split into two halves, each controlled by aseparate server, connected by separate SCSI cables.

However, the library does not contain firmware to support random mode in a splitconfiguration. As a result, each half can only be used in autoloader mode unlessthe backup software on both servers provides the necessary managementsupport to allow the two servers to access the cartridges in random mode withoutdata corruption. If the backup software does not support this, random modecannot be used in a split configuration.

3.11.2 InstallationThe installation of the IBM 3447 library basically consists of connecting thecorrect cables. For the rack mounted device, IBM recommends that the procedurebe performed by trained service personnel. Information about installation can befound in 3447 and 7337 Digital Linear Tape Library Service Guide, GA32-0400.The desktop model must be placed in such a way that the front door can be


opened, and that there is enough clearance in the back so that cooling fans arenot blocked and SCSI and power cables can be easily connected.

3.11.2.1 Installing cables and terminator

Figure 42. 3447 SCSI cable attachment

The main SCSI cable connects the SCSI host adapter with the library’s roboticSCSI interface. The cable must be a 68-pin SCSI-2 Fast/Wide cable. The SCSIbus then further continues to the first tape drive, and eventually to the second. Allthese connections are made using external short 68-pin cables (see Figure 42).Since no internal termination is installed, an external terminator must be installedat the end of the SCSI chain.

Since the IBM 3447 is also available for our RS/6000 range of machines (asmachine type 7337), two versions of this terminator exist. The reason for this isthat the RS/6000 library uses differential SCSI, while the Netfinity library usessingle-ended SCSI. To differentiate between the two, labels have been installedon both the terminator and the SCSI connectors of the library. Figure 43 showsthese two labels.

Figure 43. SCSI labels

3.11.3 ConfigurationOnce all the cables are installed, the configuration can start. The first step will beto set SCSI IDs in such a way that they don’t conflict. The IBM 3447 will use up tothree SCSI IDs: one ID for each tape device installed, and one ID for the library’srobotics. The SCSI IDs of the tape devices can be set by using toggle switches onthe back of the library (see Figure 44). The SCSI ID of the library can be setthrough the operator panel.

SCSI DIFFSCSI SE


Some backup applications require the SCSI IDs to be sequential. The loadershould be assigned the highest ID, and the two tape devices the descending nexttwo (for example, loader: ID 6, tape 1: ID 5 and tape 2: ID 4).

Figure 44. 3447 back panel

To access the setup information, press the three control keys (Menu, Cycle andSelect key) simultaneously, and keep them depressed for approximately 6seconds. This will begin the initialization of the SCSI library. When initializing,press any of the three keys to enter setup (this might take a while). After enteringsetup, the first parameter that can be set is the SCSI ID. To keep the setting,press the Menu key. To change to the value specified in the second line of thedisplay, press the Select key. To change the value in the second line of thedisplay, press the Cycle key. By using the Menu key, you can scroll through everysetting. It is advised not to change anything in here, since factory settings meetmost customers’ needs. The initial setup of the SCSI IDs is as follows:

Tape Drive A: SCSI ID 4Tape Drive B: SCSI ID 5Robotics: SCSI ID 6


Figure 45. 3447 operator panel

The operations that can be further performed using the operator panel (seeFigure 45) are shown in Table 13 and Table 14.

Table 13. Control key function

Table 14. Menu operations

Key Scrolling Presentation Menu/Cycle Presentation

Menu Toggles between library statusscreen and diagnostic screen.

Moves arrow up.

Pressing this key changes from thecurrent operational menu to thenext. The current operational menuis shown on row 1 of the display.

Cycle Moves arrow down. Pressing this key switchesbetween alternate actions of theoperational menus.

Select Pressing this key causes the tapelibrary to perform the operationchosen.

Menu Operations Prerequisite Mode Description

Change Mode None Changes the tape library operationalmode. Operational modes are:ONLINEOFFLINEDIAGNOSTIC OFFLINE

Move Cartridge Diagnostic Offline Moves a cartridge from one location toanother.

DLT Diagnostics Diagnostic Offline Performs basic DLT 7000 tests. Data onthe tape cartridge will be destroyed.

Confidence Tests Diagnostic Offline Moves cartridge randomly throughoutstorage locations.


Additional diagnostics can be run using a remote diagnostics mode. This modewill enable an operator to run diagnostics and get information from the librarythrough an RS-232 connection using a VT-100 terminal (available in the WindowsNT hyperterminal utility). This can be done locally (using a null modem cable) orremotely by using a modem. When using the null modem solution, please beadvised that the DB-9 connector on the library is a female connection. Becausenull modem cables typically have two female connectors, a DB-9 gender changermight be necessary.

The following list shows a subset of information and commands that can beaccessed using the remote diagnostics facility:

• IPL the library• Upload new firmware• Temperature of controller card and both tape devices• Voltages• Shuttle movement• Diagnostics• Drive load and unload tests• Bar code scans• Inventory• Traces

For more information, please refer to 3447 and 7337 Digital Linear Tape LibraryService Guide, GA32-0400.

3.12 3449 8 mm tape library

This section describes the IBM 3449 8 mm Tape Library Models 355 and 356.The 3449 is an automated tape library using the latest 8 mm Mammoth tape drivetechnology. It uses the 170 meter Advanced Metal Evaporated (AME) tapecartridges from Exabyte, IBM and Sony, which provides a native storage capacityof 20 GB and up to 40 GB with 2:1 hardware-controlled data compression. A fullyconfigured tape library with 22 data cartridges has a maximum storage capacityof up to 880 GB with compression.

Remote Diagnostics Diagnostic Offline Enables communication through theRS-232 interface.

DRVLDULD Diagnostic Offline DLT 7000 load and unload test. Alsore-calibrates heads.

COMM Test Diagnostic Offline Verifies SCSI communications betweentape library and host.

Maintenance Menu Diagnostic Offline Provides service information. Data onthe tape cartridge will be destroyed.

Menu Operations Prerequisite Mode Description


Figure 46. The 3449 8 mm tape library

The tape library contains two removable 10-cartridge magazines and two fixedcartridge slots for a total capacity of 22 cartridges. The fixed slots (referred to asbonus slots in the product manuals) can be used for a cleaning cartridge, drivediagnostic cartridge, test tape, or data cartridges. The tape library can beconfigured with one or two cartridge magazines, and one or two 8 mm Mammothtape drives. Full interchangeability of data is provided with the IBM 20/40 GB 8mm Tape Drive and read compatibility with previous 8 mm media format.

The IBM 3449 8 mm tape library is available in two models:

• Model 355 — a stand-alone desk-side unit.

• Model 356 — a rack-mountable unit which can be installed in an IBM Netfinityrack or any industry standard EIA-310-D 19-inch rack.

Each model can have up to two drives installed, which provide additionalenhanced features such as: faster transfer of data, simultaneous backup,concurrent read-write operations and fault tolerance. A bar code reader allowspositive tape cartridge identification and inventory, and an operator display is alsoincluded.

The 3449 has a sustainable data transfer rate of 3 MBps without compression.Using an implementation of IBM’s Improved Data Recording Capability (IRDC) upto 40 GB may be stored on a single cartridge with a data transfer rate of up to 6MBps on a one-drive model. With a split-dual server two-drive modelconfiguration, the backup capability of the IBM 3449 8 mm Tape Library increasesup to 43.2 GB per hour with compression.


The 8 mm tape library has the following features:

• Available as stand-alone tower or rack mountable.• One or two internally mounted tape drives.• A picker (transport mechanism) that moves tape cartridges between the

magazine slots and the tape drive(s).• Two removable 10-cartridge magazines, located internally above the tape

drives.• Two fixed slots (referred to as bonus slots in product manuals):

• One cleaning cartridge slot.• One customer slot for either a second cleaning cartridge, drive diagnostic

cartridge, drive test cartridge, data cartridge, or special user applicationcartridge.

• A front door provides access to the tape magazines and tape drives. Two lockson the door, a key lock and a software controlled lock, provide security andsafety.

• A barcode reader for cartridge identification and inventory.• An operator control panel with an operator key pad and a graphical LCD.

The tape library is primarily designed for unattended operation and has threemodes of operation:

• Manual mode is controlled by the operator panel switches, allowing completeoperator control.

• Sequential mode automatically loads the cartridges into the drivessequentially for reading and writing.

• Random mode allows tapes to be selected randomly by the host for reading orwriting.

Each mode will operate in each configuration. In split library configuration, eachhalf of the library can operate in random or sequential mode independently.

The library has support for two different configurations:

1. Base-Single Server Library Configuration (Single or Dual Drives)

In this configuration the tape library is attached to a single SCSI adapterinstalled in a server as shown in Figure 47 on page 87, and is under completecontrol of the server which has access to all installed tape drives and allinstalled data cartridges.

2. Split-Dual Server Library Configuration

In this configuration the tape library is shared between two SCSI adaptersconnected to two servers as shown in Figure 48 on page 88. Each server hasaccess to a specific tape drive, all data cartridges in a specificcartridge-magazine, and to cartridges in both fixed slots.

A barcode reader allows positive tape cartridge identification and inventory.Barcode labels, having up to 8 characters, may be attached to the tape cartridge.For information on barcode specifications see IBM 3449 8 mm Tape LibraryOperator Guide, GA32-0376.

The tape library is shipped with the following items:

• IBM 3449 8 mm tape library, Model 355 or 356• SCSI-2 F/W differential adapter (Adaptec AHA-2944)• One power cord (the rack-mounted model ships with two power cords)


• One 4.5 meter SCSI cable• One SCSI terminator• Two removable cartridge magazines• One 20 GB 8 mm AME data cartridge• Cleaning cartridge• Test cartridge• Installation guide• Operator guide• Service guide

In addition, the following parts may be ordered:

• IBM 3449 20 GB Drive• IBM 3449 10-Cartridge Media Magazine• IBM 3449 SCSI F/W Differential Adapter and Cable Kit

Note: The SCSI differential adapter kit includes a 4.5 meter SCSI-2 F/W cableand a 16-bit terminator for attachment of the second tape drive to a secondserver. This part should be ordered if the second tape drive is installed and youwant to operate the library in a split library configuration.

3.12.1 Operation

3.12.1.1 Base library configurationThe tape library can be configured either in base library configuration or splitlibrary configuration (see 3.12.1.2, “Split library configuration” on page 88).

In base configuration the tape library is connected to a single SCSI adapter whichis installed in a server. The server is in complete control of the entire library andall tape drives. The tape library may be installed with a one or two tape drives,both accessible from a single server. Figure 47 shows how the SCSI cable isconnected from the server to the tape library.


Figure 47. Base library configuration

This cabling is the same regardless of whether a single drive or two drives areinstalled in the tape library.

Modes of operationThe 8 mm tape library base configuration supports the following three modes ofoperation that are selected using the operator control panel:

• Manual mode (offline)• Sequential mode (selectable)• Random mode (selectable)

When the library is not in random or sequential mode it is in manual mode andconsidered offline. In manual mode, the operator uses the control panel tomanually move cartridges, load drives, or perform maintenance and service.

Sequential mode is selected on the tape library from the operator panel.Sequential mode is used with operating systems that do not support mediachangers but still want library automation. In this mode of operation, the servercontrols drive functions and the unloading of the tape cartridge from the tapedrive. The library rejects any motion commands issued by the server.

When in sequential mode, the library picks the first tape cartridge (the cartridgethat is in the lowest slot of the magazine) and places it into tape drive 1. When thecartridge is ejected from the tape drive, it is returned to the same magazine slotfrom which it was removed. The library automatically picks the next cartridge (thecartridge above the returned tape cartridge), and places it into tape drive 1. Thiscycle continues until all cartridges from both magazines have been processed.

System Unit

TerminatorT

T

1

2

3

4

SystemAdapter

SCSI Jumper

Tape LibraryBackpanel

System-to-DeviceSCSI Cable

A B

C

RSCSI02-00


After all cartridges have been processed (picked, loaded in a drive, unloaded,and returned to the magazine slot from which they were removed) the operatorcontrol panel displays a message indicating that all tape cartridges have beenprocessed.

Random mode allows the library to function as a self-contained library systemcomposed of 20 cartridges and two bonus slots, controlled by a server. Theserver uses commands to select a cartridge in a given slot or drive and move it toa destination slot or drive. The source and destination are controlled by theserver.

Random mode is selected from the control panel or through the Mode Selectcommand issued by the host system. Random mode continues until anothermode is selected.

3.12.1.2 Split library configurationIn split configuration the library has the ability to be shared between servers. Splitlibrary configuration allows for a single tape library to be used by multiple servers.This is accomplished by having the library appear as two separate libraries on theSCSI bus as shown in Figure 48.

Figure 48. Split library configuration

Split configuration allows the library to function as two self-contained librarysystems composed of 10 cartridges each and two fixed slots, controlled by aserver. The server uses commands to select a cartridge in a given slot or driveand moves it to a destination slot or drive. The source and destination arecontrolled by the server.

T

T

T

Terminator

1

2

3

4

A B

C

SystemAdapter

System Unit

SystemAdapter

Tape LibraryBackpanel

2

1

System-to-DeviceSCSI Cable

RSCSI03-00

System Unit


Server 1 has access to the following components through the primary port (port 1on the tape library backplane in Figure 48)

• Tape cartridges in magazine 1• Tape drive 1• The bonus slots

Server 2 has access to the following components:

• Tape cartridges in magazine 2• Tape drive 2• The bonus slots

Note: The bonus slots are available to both servers.

Modes of OperationThe 8 mm tape library in split configuration supports the same modes as in baselibrary configuration plus two additional ones:

• Manual mode (offline)• Sequential mode (selectable)• Random mode (selectable)• Sequential/random mode (available only in split configuration)• Random/sequential mode (available only in split configuration)

When the library is not in random mode or sequential mode it is in manual modeand considered offline. Manual mode operation in split configuration is identical tomanual mode in base configuration. See, “Modes of operation” on page 87 formore information.

Sequential mode may be selected from the operator panel. Sequential mode isavailable for use with operating systems that do not support media changers butwhich must, nevertheless, support library automation. Sequential modecontinually feeds both tape drives 1 and 2 with tape cartridges from themagazines. During sequential mode operation, the server controls drive functionsand the unloading of the tape cartridge from the tape drive. The library rejectsany motion commands issued by the server.

When in sequential mode, the library picks the first tape cartridge in the lowermagazine (the cartridge that is in the lowest slot of the magazine) and places itinto drive 1. The picker then picks the first tape cartridge in the upper magazine(the cartridge that is in the lowest slot of the magazine) and places it into drive 2.

Using the bonus slots in a split library configuration can result in a tapecartridge being moved to a slot in either half of the split library. Since eachhost has access to only half the library, the tape cartridge may becomeinaccessible to one of the hosts after the move.

Using the bonus slots

The bonus slots are not used in sequential mode except when required forcleaning.

Bonus slots


When a tape cartridge is ejected from either drive, it is returned to the magazineslot from which it was removed. The picker automatically gets the next cartridgeabove the returned tape cartridge, and places it into the appropriate drive.

This cycle continues until the top most cartridge in each magazine is processed.

After all cartridges have been processed (picked, loaded into a drive, unloaded,and returned to the magazine slot from which they were removed) the operatorcontrol panel displays a message indicating that all of the tape cartridges havebeen processed.

Random mode is selected from the control panel or through the Mode Selectcommand issued by the server. Random mode continues until another mode isselected.

The sequential/random mode splits the tape library so that drive 1 and the lowermagazine are operating in sequential mode while drive 2 and the upper magazineare operating in random mode.

The random/sequential mode of operation splits the tape library so that drive 1and the lower magazine are operating in random mode while drive 2 and theupper magazine are operating in sequential mode.

3.12.2 InstallationInstallation of the IBM 3449 8 mm Tape Library is fairly straightforward. The rackmountable model must be installed in an IBM Netfinity Rack, or any industrystandard EIA-310-D 19-inch EIA using the supplied support rails and base plate,and must be installed in a gap of no less than 15U (EIA units). The stand-alonemodel must be placed in such a way that the front door can be opened, and thereis enough clearance behind the device to allow for cooling. For additionalinformation on installing the tape library see IBM 7331 and 3449 8 mm TapeLibrary Installation, GA32-0375.

Once installed and after the picker lock has been released, the tape library shouldbe cabled as a base configuration or a split configuration as described in3.12.1.1, “Base library configuration” on page 86 and 3.12.1.2, “Split libraryconfiguration” on page 88.

3.12.3 ConfigurationWhen all the cables and terminators have been installed, the configuration of theIBM 3449 8 mm Tape Library can start. The tape library has a control panel whichis located behind the small access door on the front of the library as shown inFigure 49. The control panel will be used to perform most configuration actions.


Figure 49. Control panel

When the tape library is operating in manual mode, that is, offline, and the frontdoor is open, the tape picker mechanism may be operated by using the movepicker buttons located on the inside of the front door as shown in Figure 50.

Figure 50. Move picker buttons inside library front door

Power switch and power-on indicatorThe power switch located on the control panel controls power to the tape library.The switch does not provide a visual indication of its On or Off state. When theswitch is On the library cooling fan operates and DC power is distributed to thecomponents in the library and the power-on indicator illuminates.

The power-on indicator is a green LED located on the front panel and is softwarecontrolled. During initial power-on the power-on indicator is illuminated, indicatingthe start of Power-On Self Test (POST). If no errors are detected during POST,the power-on indicator remains lit continuously. If an error is detected during

Down Button

Power Switch

Power-On Indicator

Door LockIndicator

Key Lock

Door Unlock Button

Select Button

Display Panel

Cancel ButtonUp Button

ASOPISX-00

Down Button

Up Button

ASMVPKR-00


POST, the power-on indicator blinks a sequence that signifies a specific error.See IBM 3449 8 mm Tape Library Operator Guide, GA32-0376, for details onspecific errors and how to correct them. The only other time the power-onindicator blinks, other than POST, is following an unsuccessful microcodedownload command.

Door unlock buttonThe library provides a software controlled door lock and door lock indicator. Wheninitially powering on the library and during POST, the door remains unlocked.Pressing the Door Unlock button on the control panel signals to the library thatthe operator wishes to open the library front door. If the server has not issued acommand (prevent/allow media removal) when the button is pressed, the librarycompletes any move operation in progress and then parks the picker, and thedoor may then be opened.

Whenever the library is opened, the library software assumes the contents of thelibrary have been altered and clears the current inventory. If the Door Unlockbutton is inadvertently pressed, pressing the Cancel button without opening thelibrary door re-locks the library and retains the current library inventory.

If library access is prevented with a software controlled lock from the server or bythe operator manually locking the door with the key lock, and the Door Unlockbutton is pressed, the library displays the message:

UNLOCK NOT ALLOWED BY HOST

When the door is open, the library will not accept any commands from either theserver or the library control panel. However, any manually inserted tape cartridge,such as a diagnostic tape, in the tape drives, can be accessed directly by theserver. The picker can be moved using the move picker buttons located on theinside of the front door, as shown in Figure 50 on page 91.

Key lockThe key lock is a mechanical lock, and can be used to prevent unauthorizedaccess to the library. Both the key lock and the software controlled lock must beunlocked to gain access to the library.

The first step is to check that the SCSI IDs are acceptable, that they match the IDset for the device, and do not conflict with existing SCSI hardware devices in thehost system(s). It is recommended that the tape library be connected separatelyto the supplied SCSI Fast/Wide Differential adapter installed in the host computerto avoid conflicts with other installed/connected SCSI devices. If the split libraryconfiguration is to be used, order a second SCSI adapter and cable kit (part59H3900).

The SCSI ID menu can be accessed from the Set-up menu using the buttons onthe front panel. The SCSI IDs for the 3449 tape library in split configuration havethe following default values:

• Primary library, SCSI ID 3• Secondary library, SCSI ID 4• Drive 1, SCSI ID 0• Drive 2, SCSI ID 2


To access the Set-up menu use the Select button on the control panel to displaythe main menu on the display panel (see Figure 51).

Figure 51. Main menu display

Figure 49 on page 91 shows the layout of the control panel buttons. Use the fourcontrol buttons, Up, Down, Select, and Cancel to the right of the display panel toassist with moving around the menu. These buttons are functional after thecompletion of POST.

Service and diagnostic utilities are accessed by selecting Service from the MainMenu. Refer to IBM 7331 and 3449 8 mm Tape Library Service Guide,GA32-0377 for a detailed flow of the Service menu structure. From the Servicemenu, the following functions are available:

Logs Access logs containing errors logged during operation of the library.Self test Exercise the library by randomly moving tape cartridges from slot to

slot.Calibrate Perform library calibration.

3.13 3570 Magstar MP tape library

The Magstar MP 3570 Tape Subsystem models are compact, high-capacity,integrated storage devices that are available as stand-alone or rack-mountedunits. The subsystems are well-suited for a variety of applications and aretherefore referred to as Magstar MP (Multi-Purpose) units.

The Magstar MP 3570 Tape Subsystem is attached to host processors that usethe differential (high voltage differential, or HVD) SCSI-2 interface.

The current versions of the Magstar 370 library that are optimized for Netfinitysystems, are Models C21 and C22. Both are designed to fit in a Netfinity rack orthe NETBAY22 rack. The C21 model has a single 3570 C drive, while the C22 hastwo tape drives. The included tape drives have a capacity of 7 GB per cartridge(native), 21 GB compressed. Both libraries can hold up to 20 cartridges,combined into two 10-cartridge magazines, which give them a total capacity of

Cancelling an operation in progress may cause an error that displays a UEC(Unit Error Code). Also, a tape cartridge may be left in a tape drive or the pickermechanism.

Cancel button


140 GB in native mode. When using hardware compression, 420 GB of data canbe stored. The sustained data transfer rate equals 7 MBps, 15 MBps when usingcompression.

Figure 52. Magstar 3570 desktop model

All of the Magstar MP units use the Magstar MP Fast Access Linear Tapecartridges with longitudinal serpentine recording. These cartridges use a uniquedesign that is approximately one half the size of IBM 3480, 3490, or 3590 tapecartridges. This cartridge style provides two tape spools with mid-point load forfast access to the metal particle media.

There are three formats of 3570 tape cartridges:

• B-Format (original)• C-Format• C-Format XL (eXtended Length)

The 3570-C drive provides backwards compatibility with all these formats. Thepublished capacity however is obtained by using the C-Format XL cartridge. TheB-Format and C-Format cartridges have a native capacity of 5 GB. The datatransfer rates are the same for both C-formats, while the B-Format has a transferrate of 3.5 MBps.

The standard barcode reader can improve application performance. When thehost re-inventories the cartridges, it can take several minutes for the host tomount each cartridge in a drive and read the volume serial number identificationfrom the tape. A barcode reader eliminates the need to load each cartridge in adrive.


Figure 53 shows the library front assembly.

Figure 53. 3570 Magstar MP front assembly

Both models have a priority cell that can be used to load or unload cartridgesfrom the subsystem without removing the cartridge magazine. Becausecartridges can be inserted without opening the door, the integrity of the tapeinventory is not violated. This adds to the ease of use of this library.

For more information about the IBM Magstar 3570 MP tape library, please refer tothe Magstar MP 3570 Tape Subsystems Installation and Planning Guide,GA32-0392. This document can be viewed online at:

http://www.storage.ibm.com/hardsoft/tape/pubs/prodpubs.html

The 3570 library has the following physical specifications:

• Library requires 6 EIA rack units.• Rack install height: maximum 28 EIA units.• Height: 217 mm (8.5 inches)• Width: 444 mm (17.5 inches)

http://www.storage.ibm.com/hardsoft/tape/pubs/prodpubs.html


• Depth: 714 mm (28.1 inches)• Weight: Model C21 24 kg (52.8 lb), Model C22 29 kg (63.9 lb)

3.13.1 ConfigurationThe library can be configured to provide one of three modes of operation. Thesemodes of operation define how tapes are handled. In the following section, weexplain the different modes, and their uses.

• Random mode

Random mode allows the Magstar MP to act as a self-contained library of upto 19 cartridges, controlled entirely by SCSI hosts. In addition, access isprovided to a 20th cartridge through the priority cell. The host uses SCSIcommands to a Medium Changer device to select a cartridge from a sourceelement and move it to its destination element. Control of the source anddestination elements is left entirely to the host.

A request for an external cartridge to be mounted can be satisfied by insertingthe cartridge into the priority cell in the import position. The Magstar MPnotifies hosts of the presence of a cartridge in the priority cell, but the hostmust specifically address that cell to access the cartridge. When thedestination of a move is a magazine cell, the transport mechanism places thecartridge in the cell in the import position for possible later re-use. However, ifthe destination is the priority cell, the transport mechanism places thecartridge in the cell in the export position. Because the library door must beclosed while in random mode, the priority cell is used as an import/exportstation to add or remove cartridges from the library without violating theintegrity of the magazine inventory.

A host can cause cartridges from the priority cell to be moved to any emptymagazine cell or to a device. It can also cause cartridges from a magazine ora device to be moved to the priority cell. Requests for external cartridges to bemounted can only be satisfied when magazine 1 (the right-most magazine) ispresent. Library inventory and control is entirely the responsibility of the hosts.If the library door is opened while in random mode, the drive responds to thenext command with a Unit Attention condition.

Random mode is suited when using backup/restore applications that arecapable of managing libraries.

• Automatic (sequential) mode

Automatic mode provides the customer the ability to operate the library as asequential autoloader, keeping the tape drive continually fed with cartridges.The initiator controls only the unloading of a cartridge from the tape drive. Thelibrary will automatically load the next available cartridge into the drive afterthe ejected cartridge is put back into the magazine. All media changeroperations are effectively hidden from the system.

When automatic mode is selected, the cartridges are automatically processedaccording to their positions in the magazines. The library processes allcartridges that are in import positions sequentially, beginning at the right-mostcell position and then proceeding from right to left as viewed from the front ofthe library. After processing a cartridge, the library returns it to its originalmagazine cell and places it in the export position. The operator can supplyexternal cartridges to an application by inserting a cartridge in the priority cellin the import position.


Any cartridge inserted in the priority cell will automatically be the nextcartridge that is loaded into the drive. When that specific cartridge isunloaded, the library returns the cartridge to the priority cell in the exportposition and resumes processing cartridges from the magazine. The librarycontinues to search for cartridges until it has searched all cells without findinga cartridge in the import position. The operator can remove cartridges that arein the export position from magazines and add cartridges in the importposition to the magazine while the library is in automatic mode.

The library stops when the door is opened and resumes operation when thedoor is closed. If a cartridge is in a drive when the door is opened, processingcontinues until complete. When the door is closed, the cartridge is returned tothe cell from which it was removed. An operator may also insert full magazinesinto the library when it is in automatic mode. If the operator unloads acartridge from the tape drive by using the operator panel on the Magstar MP3570 Tape Subsystem, the operator must select START on the operator panelto load the next cartridge. If the cartridge is unloaded from the tape drive bythe host, the next cartridge is automatically loaded in the tape drive. There isno need for the operator to select START on the operator panel.

• Manual (sequential) mode

In manual mode, the library functions the same as in the automatic mode,except the operator initiates each load operation. Each time the operatorselects START from the Options Menu, the library selects the cartridge fromthe next unprocessed magazine cell and mounts it in the drive. Manual modeoperation is also activated by placing a cartridge in the import position of thepriority cell and selecting START. Only one cartridge is processed for eachoperator action.

After being unloaded, each cartridge is returned to the magazine location fromwhich it was taken and placed in the export position. The library startsprocessing cartridges beginning at the right-most cell in the library. Thesearch for unprocessed cartridges is from right to left across the magazine(s)as viewed from the front of the library.

Besides the above three basic modes of operation, the C22 can also beconfigured to operate in split mode.

It is advantageous to be able to share a single library between host systems.Unfortunately, some applications (and some systems) do not allow for sharingdevices between systems. Split configuration allows for a single library to be usedby multiple systems by having the library manage this “sharing”. This isaccomplished by having the library appear as two separate half-size libraries onone or two SCSI busses. Two SCSI busses are created when the SCSI busjumper is removed between the drive 1 and drive 2 SCSI ports.

Split configuration is created by logically dividing one physical library into twological libraries.

Logical library 1 consists of:

• Drive 1• Magazine 1 (including the priority cell)• The transport mechanism


Logical library 2 consists of:

• Drive 2• Magazine 2• The transport mechanism

Logical library 1 is available to host systems via the drive 1 SCSI port, and logicallibrary 2 is available to host systems via the drive 2 SCSI port. Cartridges not inthe logical library associated with a port are not accessible to commandsreceived on that port.

In a split configuration, the library mode of operation is selected separately fordrive 1 (logical library 1) and drive 2 (logical library 2). All possible combinationsof modes of operation are allowed in split configuration.

3.13.2 SCSI configurationA differential SCSI adapter (Adaptec AHA2944UW SCSI F/W differential adapter)is included with Models C21 and C22. The 3570 adapter card kit supplies anadditional SCSI differential adapter, 2944/UW for Models C21 and C22. Theadapter is designed for a 32-bit PCI bus in an Intel-based computer using theMicrosoft Windows NT operating system and is equipped with a 68-pinhigh-density connector. Included with the adapter card is a 4.5 meter SCSI cableand a terminator.

3.14 3575 Magstar MP tape library

The Magstar MP 3575 tape library models are compact, high-capacity, integratedstorage devices that are available as stand-alone units (see Figure 54) and arewell suited for a variety of applications. For more information on this library, referto Magstar MP 3575 Tape Library Dataserver: Multiplatform Implementation,SG24-4983.

The Magstar MP 3575 tape library attaches to host processors that have SCSI-2Differential Fast/Wide Adapters. They are intended for use on mid-range orhigh-end Netfinity systems that require reliable tape storage support foroperations such as backup, restore, archive, and data interchange, as well as forapplications that require rapid data access or high data capacity.


Figure 54. 3575 tape library

You can attach the Magstar MP 3575 tape library to the RS/6000, RS/6000 SP,and AS/400 systems, systems from Hewlett-Packard and Sun, and Intel-basedWindows NT servers.

Sustained data rates of up to 15 MBps (with maximum compression) make theMagstar MP 3575 tape library ideal for:

• Automatic tape handling applications• Time-sensitive applications requiring fast access to data• Applications requiring highly intensive I/O operations by multiple users• Traditional save and restore operations

3.14.1 Design highlightsThe key Magstar MP 3575 tape library design features and benefits are listedbelow.

• Supports the C-format XL cartridge.

• Proven library design, coupled with proven library technology, provides fastmove times, high reliability, and high mean swap between failure (MSBF)rates.

• Wide-ranging modularity with sizes from 420 GB to 2.2 TB (or 1.2 TB to 6.8 TBwith 3:1 compression). Capacity can be customized and performance tunedfor each system. Models can be upgraded to allow for expansion as required.

• Multi-path architecture allows multiple SCSI control paths and up to threelogical libraries, depending on model.

• Multi-bus design provides multihost attachment, high data throughput, andhigh availability through component redundancy.

• Bulk loading enables 14 storage slots to be allocated as user-selectable bulkI/O slots. Access is through the bulk load door. Intelligent library reinventoryusing column sensors improves library efficiency.

• Drive auto-cleaning function provides automatic detection and cleaning ofdrives, improved operator productivity and increased reliability.


• Input/output station enables cartridge import and export without requiring areinventory of the library.

• Barcode reader improves inventory times and inventory management.

• Dual-gripper picker enables two cartridges to be handled simultaneously,resulting in faster moves, transactions, and subsystem performance.Appropriate software support is needed for this function.

• Self-contained diagnostics can be run from the operator panel without hostinteraction. An advanced error-detection system reports errors accurately forhigh reliability and less subsystem downtime.

• Operator interaction with the library is through a key touch panel and a liquidcrystal display (LCD).

Figure 55. 3575 I/O components

3.14.2 The multi-path featureIt is advantageous to be able to share a single library between host systems.Unfortunately, most applications and operating systems do not provide methodsor functions for sharing devices between systems. With the multi-patharchitecture, a single library can be used by multiple systems; the librarymanages the sharing.

Multi-path permits the logical partitioning of one physical library into two or threelogical libraries. Each logical library consists of:

• Tape drives• Cartridge slots• Cartridges• The I/O station• The transport mechanism• The library controller

Tape drives, cartridge slots, and cartridges are unique to each logical library. TheI/O station and the transport mechanism are shared between logical libraries on afirst-come-first-served basis.

I/O Station

Operator Panel

Library Viewing WindowBulk Load Door


3.14.3 Bulk I/O slotsFor some applications, it is normal to import and export a significant number ofcartridges on a regular basis. An example of such an application is the ADSMDisaster Recovery Manager (DRM). For this type of application, the bulk I/O slotsoption enables you to configure the library with 14 bulk I/O slots in place of 14storage slots. The slots that can be configured in this way are the first 14addressable fixed slots in the physical library. They are colored in white (if thelibrary was manufactured after April 1998) to ease retrieval of cartridges and toproperly distinguish them from storage slots. When the bulk I/O slots and thelogical library options are selected, only logical library 1 sacrifices 14 storageslots. The number of storage slots for logical libraries 2 and 3 remain unchanged.However, all logical libraries gain access to the 14 bulk I/O slots on afirst-come-first-served basis.

3.14.4 High performanceThe overall performance of tape libraries is attributable to a combination ofmultiple factors such as cartridge move and load time, time needed for internalhousekeeping tasks (for example inventory and calibration), and, mostimportantly, data rates for read and write operations.

Cartridge move time within any Magstar MP 3575 tape library is typically lessthan 4 seconds. The dual-gripper picker can perform one cartridge remove andexchange operation, further improving overall library performance and offeringincreased redundancy and high reliability.

When loaded in the drive, the Magstar MP tape cartridge typically is ready foroperation in less than 8 seconds.

The move time is the time to pick a cartridge from a cell, move the cartridge to adrive, pivot if necessary, and insert the cartridge into a cell. Library performancedata does not include the drive portion of load or unload time. Typically,application and control unit overhead masks these mechanical timings at the userlevel.

A cartridge inventory operation includes calibrating the autochanger, checking tosee whether each cartridge slot in the library is empty or full, and reading thebarcode labels. Inventory times range from 1 minute on the L06 model (see3.14.6, “3575 models” on page 102) to 5 minutes on the L32 models.

Sustained data rates during reads and writes using the new Magstar MP Model Ctape drive are:

• B-Format media

• 3.5 MBps in native mode• 10.5 MBps using Lempel-Ziv (3:1) compression

• C-Format and C-Format XL media

• 7 MBps in native mode• 15 MBps using Lempel-Ziv maximum compression

The Magstar MP Model C tape drives have been designed for high performancein both streaming and start/stop modes of operation. Automatic data caching andread/write buffering enhance performance even further.


3.14.5 High reliabilityAn exclusive thin-film write module designed by IBM with read after write dataverification provides highly accurate recording. IBM's industry-leadingmagneto-resistive (MR) heads are designed for accuracy, high reliability, anddurability. High-availability redundant servo readers also ensure consistent dataintegrity.

The design of the Magstar MP 3575 tape library minimizes the amount of travelfor robotic pickers within the library.

When drive cleaning is required by one of the Magstar MP Model C tape drives, itis automatically performed by the library without requiring operator intervention.

3.14.6 3575 modelsThree different frame sizes and five models of the Magstar MP 3575 tape libraryare available. They offer data capacities ranging from 300 GB to 1.6 TB foruncompressed data, with up to three times that capacity for compressed data.Table 15 lists the characteristics of the available models. Figure 56 shows thevarious models of the Magstar MP 3575 tape library.

Note: The 3575 libraries required a SCSI-2 F/W Differential adapter which is notsupplied with the library.

Table 15. Magstar MP 3575 model characteristics

Figure 56. 3575 library models

Model L06 L12 L18 L24 L32

Number of drives 2 2 to 4 2 to 6 2 to 6 2 to 6

Number of cartridge slots 60 120 180 240 324

Capacity (native) GB 420 840 1200 1600 2200

Capacity (compressed) GB1 1200 2500 3700 5000 6800

Number of logical libraries 1 1 to 2 1 to 3 1 to 3 1 to 3

1. With 3:1 LZ1 compression

3575-L06 3575-L12 3575-L18 3575-L24 3575-L32


3.14.7 Magstar MP tape drivesAll Magstar MP 3575 tape library units use the Magstar MP tape cartridge whichis approximately one-half the size of IBM 3480, 3490, or 3590 cartridges. Thenew, uniquely designed cartridge provides two tape spools with mid-point load forfast access to the metal particle media. Data is read and written using aserpentine longitudinal recording format. Eight tracks at a time are read or writtenwith the C-format cartridge, and four tracks at a time are read or written with theB-format cartridge.

Tape capacity is 5 GB per cartridge in native format. With Lempel-Zivcompression, tape capacity can be 15 GB or more, depending on how well thedata can be compressed.

For the Magstar MP Model C tape drive, data transfer is 3.5 MBps for B-formatmedia in native format and 7.0 MBps for C-format media in native format.Maximum burst rate is 20 MBps and maximum sustained data rate is 15 MBpswith maximum compression.

3.14.7.1 Magstar MP Model C tape driveThe Magstar MP Model C tape drive reads and writes data on 128 tracks percartridge and uses an interleaved serpentine longitudinal recording format.

Using the C-format cartridge, the Magstar MP Model C tape drive writes andreads eight tracks at a time. When B-format cartridges are used, only four tracksat a time are written or read. The first set of tracks is written from the mid-pointalong the length of the tape to near the end of the tape, where the head isindexed to the next set of tracks for return to the tape mid-point. This processcontinues until all 128 tracks are written and is repeated for the other half of themedium until the tape is full. When read and write operations are completed, thetape is positioned to its center or mid-point for fast data access the next time thetape is mounted. The tape motion speed has been increased by about 50% onthe Magstar MP Model C tape drive compared to the 3570-B1A tape drive.

The C-format cartridge and the tape motion speed increase provide a significantperformance improvement over the 3570-B1A tape drive. In addition to very fastaccess to data, the Magstar MP Model C tape drive provides a higher level ofperformance for the applications that demand high throughput.

3.14.7.2 Magstar MP 3570 Model B1A tape driveThe 3570-B1A tape drive reads and writes data on 128 tracks per cartridge, fourtracks at a time. The 3570-B1A tape drive uses an interleaved serpentinelongitudinal recording format. The first set of four tracks is written from themid-point along the length of the tape to near the end of the tape, where the headis indexed to the next set of four tracks for return to the tape mid-point. Thisprocess continues until all 128 tracks are written and is repeated for the other halfof the medium until the tape is full. When read and write operations arecompleted, the tape is positioned to its center or mid-point for fast data accessthe next time the tape is mounted.


3.14.7.3 Tape drive performanceThe following table provides some basic performance information for the twoMagstar 3570 models:

Table 16. Models B1A and C1A performance comparision

Parameter 3570 Model B1A 3570 Model C1A

Average load time (sec) <8 <8

Average search time (sec) 8 8

Average unload time (sec) 5 5

Tape motion (m/s) 2 3.2

Native sustained data rateB-format cartridge

2.2 MBps 3.5 MBps

Native sustained data rateC-format cartridge

N/A 7.0 MBps

Compressed sustained data rateB-format cartridge (3:1)

6.6 MBps 10.5 MBps

Compressed sustained data rateC-format cartridge (3:1)

N/A 15 MBps

Burst data rate 20 MBps 20 MBps


Chapter 4. SAN equipment

This chapter gives an overview of hardware components used in storage areanetwork (SAN) environments. Only the components relevant to a tape-orientedstorage area network will be included.

This includes the following components:

• The Netfinity Fibre Channel PCI adapter (see page 105)• The IBM SAN Fibre Channel Switch (see page 105)• The IBM SAN Data Gateway Router (see page 107)• The Netfinity Fibre Channel hub (see page 109)• Cabling (see page 111)

Additionally, the IBM SAN management software, StorWatch, will be discussed.

Finally, we will give an overview and example of currently supported SANconfigurations using these components in a tape environment.

For more general information on IBM SAN solutions, visit the SAN Web site, at:

http://www.storage.ibm.com/ibmsan

4.1 Netfinity Fibre Channel PCI adapter

The Netfinity Fibre Channel PCI Adapter is a half-length 64-bit PCI busmasteradapter that is installed in the Netfinity server for connectivity to the externalstorage enclosure. The adapter connects to either a Netfinity Fibre Channel Hub,an IBM Fibre Channel switch, an IBM Fibre Channel router or a Netfinity FibreChannel RAID Controller.

The adapter supports short-wave optical cables which may be connected to ashort-wave optical GBIC installed in any other supported component. The cablemay be a 5 meter or 25 meter short-wave 50 micron multi-mode fiber cable (theIBM Netfinity Fibre Channel cables, see 4.5, “Cabling” on page 111) or acustomer-supplied cable of the same specification up to 500 m.

The adapter is often simply referred to as the host adapter. In a SANenvironment, this adapter is also referred to as the host node.

The maximum number of host adapters supported in Netfinity systems is limitedonly by the number of available PCI slots.

4.2 IBM SAN Fibre Channel switch

The IBM SAN Fibre Channel Switch is an 8- or 16-port switch used tointerconnect multiple host servers with storage servers and devices, creating astorage area network (SAN). The switch allows you to build a wide range ofscalable SAN solutions. By creating an intelligent connectivity infrastructure, orfabric, that supports connections across a wide range of host and storage types,the IBM SAN Fibre Channel Switch enables storage resources to be shared.

http://www.storage.ibm.com/ibmsan


The IBM Fibre Channel Switch is available in two versions:

• 2109 Model 08

The Model 08 can hold up to eight fiber optic connections. These connectionsare established by using gigabyte interface converters, or GBICs (see 4.4.0.1,“Netfinity Fibre Channel hub GBICs” on page 110). Both short wavelength andlong wavelength fiber-optic GBIC versions are supported. There are four shortwavelength GBIC modules installed by default.

• 2109 Model 16

The Model 16 is an enterprise version of the Model 08. It holds up to 16GBICs, with four short wavelength ones installed by default.

Both models can be equipped with a redundant power supply.

Intelligence is built into the switch architecture: self-learning allows the fabric toautomatically discover and register host and storage devices, and self-healingenables the fabric to isolate a problem port and reroute traffic onto alternatepaths. In addition, internal to the switch is a processor that provides fabricservices such as name serving, zoning, routing, and dynamic microcodeupgrades.

The IBM SAN Fibre Channel Switch comes with the StorWatch SAN FibreChannel Switch Specialist, which can be used to manage the switch. To do this,the switch needs to be connected to a network, using the integrated Ethernetadapter. You can then assign an IP address to the switch, and manage it througha Java-enabled Web browser.

Figure 57. StorWatch SAN Switch Specialist

Figure 57 shows the Web-based interface of the switch management application.From here, you can monitor the switch, get port statistics and performanceinformation and manage the switch. Management can be done through anadministrative interface, which allows you to perform basic functions. A second

Fabric is a term used to define a scheme of interconnected Fibre Channelservers and nodes.

Note

Chapter 4. SAN equipment 107

way of managing the switch is through a telnet session. This command basedinterface lets you perform more complex management operations (like setupzoning). For more information, refer to the product manuals, at:

http://www.storage.ibm.com/hardsoft/products/fcswitch/refinfo.htm

The IBM SAN Fibre Channel Switch can be used to attach the following SAN andstorage products:

• IBM SAN Data Gateway with the IBM Enterprise Storage Server, the IBMVersatile Storage Server, or the IBM Magstar and Magstar MP tape libraries

• IBM SAN Data Gateway Router with supported IBM tape products• IBM Fibre Channel RAID Storage Server• IBM Netfinity Fibre Channel RAID Controller Unit• IBM Netfinity Fibre Channel Hub

4.3 IBM SAN Data Gateway Router

The SAN Data Gateway Router provides SCSI connectivity and interfacesbetween SCSI storage devices and the SAN. Its main use is to provide integrationof tape libraries, both DLT and Magstar, to a SAN. The router can be used as adesktop model, or as a rack-mounted unit. In this case, it can be mounted in aNetfinity 9306 rack.

The SAN interface is made using a Fibre Channel PCI Mezzanine Card or PMC.The factory installed PMC functions according to the short wavelength standards.Therefore, the maximum distance between this component and its peer in theSAN fabric can be up to 500 meters. For information on future long-wave PMCs,consult the SAN Data Gateway Router Web pages, at URL:

http://www.ibm.com/storage/SANGateway

The router holds two SCSI channels. These can be either Ultra SCSI-2 Widesingle ended, or differential (HVD). The channels have internal terminationenabled, which can be disabled using either jumpers or the StorWatch utility.Each channel supports up to 15 SCSI target IDs, with 32 LUNs per ID. This sumsup to a total of 128 devices supported, minus 1 LUN for command and controloperations. The external 68-pin connectors support cable lengths up to 3 metersfor SE SCSI, and 25 meters for differential.

For management purposes, the router is equipped with both an Ethernet and aserial service port. The Ethernet port is a 10baseT port, using an RJ-45connector. It provides TCP/IP support to communicate with the StorWatch DataGateway Specialist software. The service port is an RS-232 9-pin D-shellconnection, which can be addressed using a standard PC equipped with a nullmodem cable. The port is configured at a speed of 19200 baud, using 8 data bitswithout parity and XON/XOFF data flow control.

As mentioned before, the management and monitoring of the router can be doneusing the StorWatch Data Gateway Specialist software. This product is includedwith the router, and will communicate with the router using SNMP and SCSI overTCP protocols. SCSI over TCP technology encapsulates SCSI commands intoTCP packets, and allows remote configuration of SCSI devices.

http://www.ibm.com/storage/SANGateway

http://www.storage.ibm.com/hardsoft/products/fcswitch/refinfo.htm


The StorWatch Data Gateway Specialist software is a client/server application,which includes the following components (see Figure 58):

• Agent• Server• Client

Figure 58. Storwatch SAN Data Gateway Specialist client/server model

The agent, which is integrated in the router and gateways, will communicate withthe server component. The main communication protocol is SNMP, used toconfigure and query the router information. It is also used to generate traps oralerts. The SCSI/TCP protocol will be used to manipulate SCSI device andchannel parameters on the router.

The server component is a Java application, which coordinates communicationbetween different clients and routers. It also maintains security information, clientviews and configuration settings. Communications between client and server aredone using Remote Method Invocation or RMI. RMI is included in the Javaenterprise API extensions, and defines an interface allowing invocation of objectmethods in a distributed environment (object methods are one of the basecomponents of the Java language, defining the behavior of objects, and theirinteraction with other objects). As such, RMI can be compared to remoteprocedure calls in distributed computing environments.

The client, also a Java application, will use the RMI calls to communicate with theserver software. In order to do this, it requires a TCP/IP connection with theserver component (it can also be installed on the same machine as the server).For some operations, SCSI over TCP will be used to communicate directly withthe routers. The client component also includes a graphical user interface (seeFigure 59).

Server

Workstation

Client

Workstation

Client

Gateway

Agent

Gateway

Agent

Router

Agent

SNMP/SCSIover TCP JAVA RMI


Figure 59. StorWatch SAN Data Gateway Specialist

Client and server components have the following system requirements:

• Windows NT 4.0 server or workstation, Service Pack 5 or higher• SunSoft JRE 1.1.8 Java Virtual Machine (included with the router)

The StorWatch Data Gateway Specialist software has the following features:

• SNMP and SNMP community support• Security• Saved views• Network discovery of routers• Router configuration and operation• Remote router firmware updates• Event logging• Router health checks or diagnostics• SCSI device configuration• Router monitoring

More information on both the router and the StorWatch software can be found inthe user’s guide, located at:

http://www.storage.ibm.com/hardsoft/products/sangateway/refinfo.htm

4.4 Netfinity Fibre Channel hub

The Netfinity Fibre Channel Hub is a seven-port device. Much like in a traditionalnetwork, the hub relays data signals from one port to another. Although notneeded for simple configurations, it is required for cluster and redundancyconfigurations and for those requiring cable lengths greater than 500 meters. Ifnecessary, two hubs can be cascaded together for more complex configurations.

http://www.storage.ibm.com/hardsoft/products/sangateway/refinfo.htm


Figure 60. Netfinity Fibre Channel Hub

The hub supports both short-wave and long-wave fiber optic cabling. Short-waveconnections are used for connectivity to the host adapter and to other SANcomponents (switches and routers) and can be up to 500 meters long. Long-wavecables are used for connections between hubs and can be up to 10 kilometerslong.

Since each hub has seven ports, to build large configurations, the hubs can beconnected together as shown in Figure 61, such that up to a total of 37 ports canbe made available for attachments.

Figure 61. Cascading multiple hubs such that 37 ports are available

4.4.0.1 Netfinity Fibre Channel hub GBICsThe device used to connect the fiber optic cables to the electrical interface withinthe hub is known as a GBIC (gigabit interface converter). Four short-wave GBICsare supplied with the hub.

In the Netfinity Fibre Channel solution there are two GBICs available:

• Netfinity Fibre Channel short-wave GBIC• Netfinity Fibre Channel long-wave GBIC

Any combination of short and long-wave GBICs is supported. The hub can beused for distance as well as expansion of your configuration.

Each of the level 2hubs have sixports available forconnection to sixRAID controllerunits

The level 1 hubhas one portavailable forconnection tothe host adapter

2098

-02 1

1

2345

6


The short-wave GBIC has a black casing as shown in Figure 62 and supportsmulti-mode 50 micron fiber cable. The long-wave GBIC has a blue casing andsupports single-mode 9 micron fiber cables.

Figure 62. IBM Netfinity Fibre Channel short-wave GBICs

The GBIC packaging is designed to prevent improper insertion. The operationalloop performance is not affected when you install or remove a GBIC. GBICs arehot pluggable.

If you insert a GBIC without cables attached, it will remain in the bypassed statewhich means the GBIC is active but there are no active or valid return signals.When you attach a cable and a valid signal is detected, the hub will allow theGBIC and attached devices to join the loop.

4.5 Cabling

The Netfinity Fibre Channel PCI adapter and the router both support short-wavecables, but the Netfinity Fibre Channel Hub and switch support both short-waveand long-wave cables.

The short-wave connections can be up to 500 meters long, and the long-wavecables can be up to 10 kilometers long.

There are two short-wave cables available from IBM, a 5 meter cable and a 25meter cable. These cables are 50 microns in diameter. The 62.5 micronshort-wave cables are not supported.

All Netfinity Fibre Channel devices use cables with SC connectors (SC stands forstandardized connector). These connectors are keyed and can only be plugged inone way.


Figure 63. Fiber optic cables with SC connectors

4.6 Supported configurations

This section explains currently supported SAN configurations using the abovecomponents and tape libraries. The support information can be found on theServerProven Web site, at:

http://www.pc.ibm.com/us/compat/clustering/sanmatrix.shtml

Currently, only two configurations have been tested: the Fibre Channel attachedtape storage configuration and the server consolidation with tape poolingsolution. The configuration using the Microsoft Cluster Server is planned, but notyet tested.

http://www.pc.ibm.com/us/compat/clustering/sanmatrix.shtml


4.6.1 Fibre Channel attached tape storage

Figure 64. Fibre Channel attached tape storage

Figure 64 shows the setup for Fibre Channel attached storage. The followingcomponents are supported:

Netfinity servers• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 5600 (Planned)• Netfinity 7000 M10• Netfinity 8500 R

Tape libraries• 490/980 GB DLT tape library (3502-x14)• Magstar 3570-Cxx• Magstar 3575-Lxx (planned)

SAN equipment• Netfinity Fibre Channel hub• IBM SAN data gateway router• Netfinity Fibre Channel PCI adapter

Software

Netfinity Server

IBM FC SANData Gateway

Netfinity FCRAID Controller

Netfinity DiskEnclosure

NetfinityFC Hub

NetfinityTapeLibrary


4.6.2 Netfinity server consolidation with tape pooling

Figure 65. Netfinity server consolidation with tape pooling

Figure 65 shows the setup for Fibre Channel attached storage, providing serverconsolidation with tape pooling. The following components are supported:

Netfinity servers• Netfinity 5000• Netfinity 5500• Netfinity 5500 M10• Netfinity 5500 M20• Netfinity 5600 (Planned)• Netfinity 7000 M10• Netfinity 8500 R

Tape libraries• 490/980 GB DLT tape library (3502-x14)• Magstar 3570-Cxx• Magstar 3575-Lxx (planned)

SAN equipment• IBM SAN data switch (both 8 and 16 port models)• IBM SAN data gateway router• Netfinity Fibre Channel PCI adapter

4.6.3 Sample SAN configurationThis section will provide you with a detailed example of how to implement theabove technologies. The setup that will be made uses Tivoli Storage Manager(see 5.1, “Tivoli Storage Manager” on page 124) as tape management andbackup/restore software.

Software

Netfinity Server

IBM FC Switch

IBM FC SANData Gateway

NetfinityTapeLibrary


Figure 66. SAN test setup

Figure 66 shows the setup of the test environment. A first server, 1, will be themain Tivoli Storage Manager server. This machine will be responsible for makingbackups of clients attached to the network. In order to do this, the machine hasstorage pools consisting of both disk, and a locally attached tape library (Magstar3570). The second server, 2, represents a large file or application server. Theproblem faced is that network bandwidth is not enough to be able to make abackup of this machine to the main server. The solution using SAN fabric, is toattach the server to a shared 490/980 GB DLT tape library (IBM 3502-R14). Theshared library is also used by the main Tivoli Storage Manager server to makecopies of its local tapes. The purpose of that operation is disaster recovery. Whena local disaster occurs, remote copies of all the local tapes are available.

The setup consists of two major steps: hardware installation and configurationand software installation and configuration.

4.6.3.1 Hardware installation and configurationInstallation of the hardware components is limited to connecting Fibre Channelcables, and installing the PCI Fibre Channel adapter in both Netfinity systems.When starting your Netfinity system, check if the BIOS of the adapter equals thesupported one, which is 1.35. The operating system requirement is Windows NT4.0, Service Pack 5. After booting the operating system, install the requireddevice driver, QL2100.SYS Version 6.16 or later. To do this, open the WindowsNT control panel, and start the SCSI Adapters application. Go to the Drivers tab,

Netfinity 7000Tivoli Storage ManagerLibrary Client

Netfinity 7000Tivoli Storage ManagerLibrary Server

DLT 3502-R14

Magstar 3570

2109-S16 Switch 2108-R03 Router

driv

e/vo

lum

ere

ques

ts

driv

es/v

olum

eha

ndlin

g

Ser

ver-

to-S

erve

rco

mm

unic

atio

n

TCP/IP

1

2

FC PCIadapter

FC PCIadapter

StorWatch

SWL FC Interface

SCSI Interface

Ethernet Interface


and add the driver. You will need to reboot after that. After the reboot, you can goback to the application, and check if all devices are recognized.

Figure 67. Fibre Channel adapter driver

The SAN Data Gateway Router (2108-R03) should only be configured if you willmanage it remotely. In order to do this, you must set an IP address that can beused in your environment. To set this IP address, connect to the router using aserial connection through the service port (see 4.3, “IBM SAN Data GatewayRouter” on page 107). The connection should be made using a standardnull-modem cable. To configure the session, use the following settings:

• 19200 Baud• 8 data bits• 1 stop bit• No parity• Xon/Xoff flow control

Use any terminal program to connect. After connecting through the serialinterface, log on using the default user ID and password, which both are equal toStorWatch. Next, you can use the ethAddrSet and ethEnable commands to set theTCP/IP address of the box and enable the Ethernet connection. The exact syntaxfor the address setting command is:

ethAddrSet “a.b.c.d”

Once this is done, you can use the StorWatch SAN Data Gateway Specialist tomonitor and configure the router.

The setup of the switch is almost the same as the router: configure an IP addressand manage it using the StorWatch SAN Switch Specialist. For the 2109-S16switch in our configuration, this is done using the front panel on the box. For theS08 switch, you can again use the provided RS-232 service port to connect. Toset the IP address using the operator panel, press the down arrow until theconfiguration menu selection appears. Next, use the left arrow button to select theIPaddress option, and then use the left arrow again to set the IP address. Oncethis is done, you can connect to the switch using a Java-enabled browser. Just


enter the IP address that you just set, and the StorWatch SAN Switch Specialistwill load.

This completes the hardware setup of the configuration. For information aboutmore advanced configurations, such as zoning, refer to the manuals of the switchand the router.

4.6.3.2 Software installation and configurationOnce the hardware is installed and configured, as explained in 4.6.3.1, “Hardwareinstallation and configuration” on page 115, you can start the installation of TivoliStorage Manager V3.7 for Windows NT. Both servers will need to be installed.However, the installation will differ for each machine. The reason for this is thatboth will have different functions. In the Tivoli Storage Manager SANimplementation, one server will be called the library manager, while the othersystem will be the library client.

The library manager will control physical access to the library. This means thatthis machine will be responsible for serializing access to the tape devices, andcontrolling the physical volumes inside the library. To be able to do this, thefollowing operations will be done by the library manager:

• Library initialization• Volume mounts and dismounts• Check in and check out of library volumes• Library audits

The library client will send requests to mount volumes to the library manager. Theclient, in other words, has no direct access to the library robotics or the physicalvolumes inside the library. There is however direct access and control over thetape drives in the library.

To install the two Tivoli Storage Manager servers, please refer to 6.1, “TivoliStorage Manager for Windows NT” on page 159. Follow the procedure explainedfor installation. When doing the configuration however, do not define anySAN-connected tape devices or libraries using the wizard for the library manager.The local 3570 Magstar library can be defined using the wizards. In this example,we didn’t use the wizards at all to configure the library client. The reason for thatis that the wizard configures a typical TSM server. Our case however is ratherspecial. That is why we used the command line and Web administration interfaceto configure the machine.

After installation has finished, and initial configuration is done as explained aboveand in 6.1, “Tivoli Storage Manager for Windows NT” on page 159, the followingsteps will need to be performed:

1. Server-to-server communication setup between library client and librarymanager

2. Physical definition of library on library manager3. Logical definition of library on library client4. Setting up the storage hierarchy on the library client

The first step is setting up the server-to-server communication on both machines.Server-to-server communication is used by Tivoli Storage Manager tocommunicate between two servers. Besides the library sharing, it can also beused to define remote storage pools located on a different server. To do this, you


must first set a number of TSM environment variables. Open the Tivoli StorageManager admin command line interface, and log on using your TSM administratoruser ID and password.

On the library manager, issue the following commands:

On the library client, issue similar commands, but with different values:

The definitions above define a name for the server, a password, the TCP/IPaddress and port number (respectively high-level address and low-level address).These definitions should be made on the machine where they are valid. Their useis to import system parameters inside the Tivoli Storage Manager serverapplication. Finally, the CROSSDEFINE parameter is used, so that you only need todefine the remote server on one machine instead of on both.

The server definition command, issued on the library manager is as follows:

DEFINE SERVER FILESERVER SERVERPASSWORD=SAN CROSSDEFINE=YES HLADDRESS=1.1.1.101 LLADDRESS=1500

The above command defines the library client to the library manager, and throughthe cross define setup, also the library manager to the library client.

Now that server-to-server communication has been set up successfully, you willneed to setup the physical library on the library manager. The followingcommands will define a library and the tape drive installed.

Using the above commands, we defined a tape library, named 3502R14,containing one tape device, DLT7000DRV, which functions according to the DLT7000 standard (DEVCLASS definition). The SHARED=YES parameter on the librarydefinition command will enable the library manager to share this library betweenservers. In order to use the library, you still need to label the volumes inserted,and assign them to the library. This can be done through the media labelingwizard, or by using the following two commands:

SET SERVERNAME SANSRVSET SERVERPASSWORD SANSET CROSSDEFINE ONSET SERVERHLADDRESS 1.1.1.100SET SERVERLLADDRESS 1500

SET SERVERNAME FILESERVERSET SERVERPASSWORD SANSET CROSSDEFINE ONSET SERVERHLADDRESS 1.1.1.101SET SERVERLLADDRESS 1500

DEFINE LIBRARY 3502R14 LIBTYPE=SCSI DEVICE=LB0.1.0.4 SHARED=YESDEFINE DRIVE 3502R14 DLT7000DRV DEVICE=MT0.2.0.4 ELEMENT=16DEFINE DEVCLASS DLT7000 DEVTYPE=DLT FORMAT=35C LIBRARY=3502R14


The above commands look for all cartridges inserted in the tape library, and labelthem using the barcode reader (matching the volume label to the barcode labelon each cartridge). If you do not have a barcode reader available, you can use theSOURCE=PROMPT parameter, which will prompt you for a label.

This completes the library definition on the library manager. The next step will beto define the library to the library client. This is done using the followingcommands:

As you can see, the drive and device class definitions are exactly the same as onthe library manager. The difference is the library definition. We define the3502R14 library as being of a shared type, and managed by the primary librarymanager, SANSRV.

Next, we will need to set up a storage hierarchy and policy on the library client.The purpose of this setup is to be able to move data from the library client directlyto the tape device. The reason for this is that we have too much local data to go tothe main TSM server. With this as the goal, the local backup client should back upits data immediately to the tape device. When setting up a storage hierarchy, thefirst step is to set up a storage pool, which reflects volumes in the 3502R14library, and update the policy definition, so that the copy group definition movesits data to the define storage pool.

The storage pool definition can be done using the Web administration interface(see Figure 68 on page 120). Start the interface, go to the Sequential AccessStorage Pools folder in Server Storage, and select Define Storage Pool from theOperations menu.

LABEL LIBVOL 3502R14 SEARCH=YES SOURCE=BARCODECHECKIN LIBVOL 3502R14 SEARCH=YES STATUS=SCRATCH

DEFINE LIBRARY 3502R14 LIBTYPE=SHARED PRIMARYLIBMANAGER=SANSRVDEFINE DRIVE 3502R14 DLT7000DRV DEVICE=MT0.2.0.4 ELEMENT=16DEFINE DEVCLASS DLT7000 DEVTYPE=DLT FORMAT=35C LIBRARY=3502R14


Figure 68. Defining a storage pool using the Web administration interface

One thing that is useful is to set the maximum scratch volumes allowed to a valueother than 0. This will allow you to use tape volumes from the scratch pool,instead of volumes specifically defined to the above storage pool.

Next, update the policy so that it uses the newly defined storage pool. To do this,go to the Copy Group page in the Policy Domain view. Select the defined backupcopy group, and select the Update Copy Group command from the Operationsmenu. This will bring up Figure 69. Update the copy destination file with the newlydefined storage pool.


Figure 69. Update copy group using the Web administration interface

Next, go to the Management Classes folder, and activate the configuration usingthe Operations menu.

Once the above is done, you can start taking backups with the local client on thelibrary client. When the tape is used, you will see a mount request handled by thelibrary manager. This is the only time communication between client and managerwill take place. During the backup, all data moves directly over the SAN fabricfrom the library client to the library.


Chapter 5. Software

This chapter describes some of the major backup software packages availabletoday on the market. Products covered are:

• Tivoli Storage Manager for Windows NT and OS/2• Tivoli Data Protection for Workgroups• VERITAS NetBackup• Legato NetWorker• ARCserveIT for Windows NT and NetWare• VERITAS Backup Exec for Windows NT and NetWare

Installation of the software and how to configure it to work with IBM tape drives iscovered in Chapter 6, “Installation and configuration” on page 159. The followingtables show the IBM tape drives supported by various backup packages.

Table 17. Supported software

40/80 GBDLT

35/70 GBDLT

20/40 GBDLT

20/40 GB8 mm

20/40 GB4 mmDDS-4

12/24 GB4 mmDDS-3

IBM NS20


TSM OS/2V2R1L15

S S S S

TDP forWorkgroups

S1 S1 S1 S1 S1

VERITASNetBackup

NetWorker NTV5.5.1

S1,3 S1 S1 S1 S

NetWorkerNetWare

S2 S1 S1

ARCserveITV6.6x

S1 S S S S1 S1 S1

ARCServeITNetWare V6.6

S1 S S S S1 S1

Backup Exec NT I I I I I I I

Backup ExecNetWare

I I I I I I I

Sytos PremiumV2.2a for OS/2

S S S

I: Supported by IBMS: Supported by software manufacturerBlank: Not supportedNotes:1.Support for generic Quantum, Exabyte and HP devices.2.Only supported on NetWare 4.123.Currently supported as DLT 7000 type


Table 18. Software support for libraries

5.1 Tivoli Storage Manager

IBM’s Tivoli Storage Manager integrates backup, archive and space managementfunctions.

Tivoli Storage Manager manages your storage media based on a set of policies,which you can customize for different types of data and groups of users. You canalso automate some operations, such as client backups and server databasebackups.

Tivoli Storage Manager provides a wide range of versions for different platforms.Server platforms include OS/2 (Version 2.1 server), Windows NT, AIX, HP UNIX,Sun Solaris, AS/400 (Version 3.1), MVS. and VM (Version 3.1). Client platformsinclude Windows NT (Intel and Alpha processor versions), Windows 2000, NovellNetWare (Versions 3.12 through 5.0), Windows 98, Windows 95, AIX, HP UNIXand Sun Solaris. There is also a Linux client available.

IBM 3502Library

IBM 3502Loader

IBM 3447 IBM 3449 IBM 3570C2x

IBM 3575


TSM OS/2 V2R1L15 S S S S

TDP for Workgroups S S S

VERITAS NetBackup S S S S

NetWorker NT V5.5.1 S S S S

NetWorker NetWare

ARCserveIT NT V6.6x S S S S

ARCserveIT NetWareV6.6

S S S

Backup Exec NT S S S

Backup Exec NetWare S S S S

Sytos Premium V2.2afor OS/2

I: Supported by IBMS: Supported by software manufacturerBlank: Not supported

IBM’s ADSTAR Distributed Storage Manager, or ADSM, has been rebranded toTivoli ADSM, and then changed to be the base of the new Tivoli StorageManagement product set. This rebranding also led to new naming and productversion numbers. The current version for what was known as ADSM is nowTivoli Storage Manager Version 3.7.

Note

Chapter 5. Software 125

Figure 70. Tivoli Storage Manager sample client/server environment

5.1.1 Products and base components

The Tivoli Storage Management product set includes the following products:

• Tivoli Storage Manager base product

This is the storage server, including a backup archive client and administrationtools. This collection of functions is also referred to as the first level of dataprotection.

• Tivoli Disaster Recovery Manager

This product enables you to create a disaster recovery plan. Also referred toas the second level of data protection.

• Tivoli Space Manager

Used for automated space management. This function incorporates the oldHierarchical Storage Management, or HSM, functions of ADSM.

• Tivoli Data Protection for application clients

These products enable you to back up and restore specific applications.Currently, the following applications can be backed up through theseapplication clients:

• Lotus Notes• Lotus Domino• Lotus Domino, S/390 edition

Tivoli Storage Manager uses a terminology where machines that are backed upare called client nodes, and the backup server is called the server. In thiscontext, file servers and application servers that require backup, are calledclients or nodes.

Terminology


• Microsoft Exchange• Microsoft SQL server• Oracle• Informix (UNIX)

• Tivoli Data Protection for Workgroups

This disaster recovery tool, described in detail in 5.2, “Tivoli Data Protectionfor Workgroups” on page 135, is a Windows NT stand- alone backup/recoverytool.

Due to the multitude of products currently in the Tivoli Storage Managementproduct set, we will limit ourselves to the base product for now. This base productcan again be split into the following components:

Server Provides storage management for clients andmaintains a database of Tivoli Storage Managerinformation.

Server Storage Contains files that are backed up, archived, andmigrated from workstations. Server storageconsists of pools of random and sequential accessmedia.

Server Database The Tivoli Storage Manager database will hold allinformation used by Tivoli Storage Manager. FromVersion 3.0 on, there is an ODBC driver available,which allows you to retrieve information from thisdatabase using ODBC compliant applications (likeLotus 123, Lotus Approach, etc.).

Enterprise Administration Provides an interface to the Tivoli StorageManager server. Important for people that used towork with ADSM, is that the administrativeinterfaces have been reduced. Currently, only thecommand line interface and the Web-basedinterface are available.

Backup-Archive Client Provides backup and archive services toworkstations. Besides the standard interface, aJava-based Web client is available that enablesyou to do restores to all clients in yourenvironment, and this from one central place.

API Client Provides an application programming interface.

The above components will give us the possibility to perform the followingfunctions:

• Backup and restore

Backup enables you to save copies of files on the Tivoli Storage Managerserver. From a client, you can restore files that have been backed up to theTivoli Storage Manager server. During a restore, Tivoli Storage Manager

The DB2 solution for OS/2 and Windows NT is included in the base API client.

Note


copies the backup version from the Tivoli Storage Manager server to yourclient. Restore enables you to recover a single file or an entire file system.

Starting from Version 3, you can do a so-called Point In Time restore, whichenables you to do a restore of an entire system as it was at a certain point intime.

• Archive and retrieve

Archive enables you to save copies of files for some period of time on theTivoli Storage Manager server. Archive copies are never replaced with morecurrent versions (as is the case with backups). They are preserved exactly asyou store them. The process of restoring the archive packages is calledretrieve. In this new release, enhancements have been made to make disasterrecovery easier. This is implemented by the backup set solution. This backupset has two features:

• Instant archive

Instant archive is used to create a self-contained copy of a client’s files.This copy is placed, for example, on sequential media, and is entirelymanaged by the server’s archive policy and sequential volumemanagement. An additional feature is that this archive can be created frombackup copies of files already residing on the server, meaning that no orlittle network traffic is necessary.

• Rapid recovery

Rapid recovery, as the name suggests, can be used to improveperformance of restores when a client disaster recovery is necessary. Thiscan be accomplished in two ways. The first is a LAN based method thatuses the archive set for restores. This is faster than just using theincremental backup objects, because the entire backup set is one entity forthe server. Also, all the backup objects are located on one media set.

The second possibility, usable for constrained network environments (WANconnections, mobile users), is a LAN free method. Here, portable media iscreated. This portable media can be moved to the client, and be restoredlocally, without using the Tivoli Storage Management server. This impliesthat the created media can be read at the client. So, unless you havecompatible tape hardware at the client side, you should use the FILEdevice class capability of ADSM. This device class definition simulatessequential media on direct access media. You could create sequential fileson a read-write CD, or ZIP drive, either of which is more portable thanhigh-end tapes.

5.1.2 Server data managementThis section describes the different concepts used by the Tivoli Storage Managerto manage the data stored on the server. It includes how data will be arrangedlogically, using policy management, and physically using hierarchical storage.

5.1.2.1 Tivoli Storage Manager PolicyTivoli Storage Manager allows clients to do the following:

• Back up files to server storage to prevent loss of data.

• Store copies of multiple versions of a file.

• Archive files to server storage for long-term storage.


• Utilize hierarchical storage management to free storage space by moving datato server storage. The original file is replaced with a pointer to the location ofthe original in server storage. This is also called space management ormigration. This function is available through Tivoli Space Manager. See 5.1.1,“Products and base components” on page 125.

Policy is defined by administrators in policy objects: policy domains, policy sets,management classes, and backup and archive copy groups. Figure 71 shows howTivoli Storage Manager organizes client data.

Figure 71. How Tivoli Storage Manager controls backup, archive and space management

1 A Tivoli Storage Manager client backs up, archives, or migrates a file. The file isbound to a management class.

2 If, according to the management class, the file is eligible for backup, archive, orspace management, the client sends the file and file information to the server.

3 The server checks the management class or copy group to determine where inserver storage to store the file initially.

4 The server stores the file in the appropriate storage pool and stores informationabout the file in the database. When files in server storage are migrated from onepool to another, the server updates the file information in the database.


Each level of data management has a specific function in organizing data. Thesefunctions are the following:

Policy domain The policy domain is the largest entity, that groups acertain number of policy sets. Nodes that are defined willbe assigned to a policy domain.

Policy set The policy set will group management classes and copygroups. You can define several policy sets for eachdomain, but there can be only one active policy set at atime. This active policy set will be the policy set that will beused.

Management class Management classes are the level to which data objectsare assigned. Each object that is backed up is bound to amanagement class. For each policy set, one defaultmanagement class exists. You can have severalmanagement classes at a time. Files that are backed upwill be bound to the default management class, unless youspecifically send them to another class. Directorieshowever, will be assigned to the management class whichcontains the copy group with the longest retention period.There is a possibility to define one management class,DIRMC, which will only be used for directories.

Copy group The lowest level of the storage policy setup are the copygroups. For each management class, you can have abackup, archive and space management copy group. Thecopy group will define which storage pool will be used, thenumber of versions to keep, how long to keep them, andthe serialization. Serialization is used to determine if a filethat changes during backup will be kept as such, or if theprogram should retry to get a consistent copy of the file.

5.1.2.2 ExpirationFiles remain in server storage until they expire and expiration processing occurs.A file expires based on criteria set in Tivoli Storage Manager policy. For example,backup policy may specify that up to two backup versions of a file can be kept inserver storage. If a third backup version of a file is created, the oldest version inserver storage expires.

Backup policy may also specify that if a file is deleted from a client file system, itexpires after 60 days. During expiration processing, Tivoli Storage Managerdeletes from the database those files that have expired. Physical deletion of thebackup file only happens on random access media (like a hard disk). Onsequential media (tape), a process has to be started to enable deletion of thisspace. This is called reclamation. When designing a backup solution, keep inmind that tape reclamation needs two tape drives. You can use a mechanism thatis called single drive reclamation (available in Version 3 servers), but then youmust have sufficient disk space.

5.1.2.3 Storage devices and mediaTivoli Storage Manager represents physical storage devices and media with thefollowing objects:


Library A Tivoli Storage Manager library is one or moredrives (and possibly robotic devices) with similarmedia mounting requirements.

Drive Each Tivoli Storage Manager-defined driverepresents a drive mechanism in a tape or opticaldevice.

Device Class Each device is associated with a device class thatspecifies the device type and how the devicemanages its media. Tivoli Storage Manager has apredefined device class (DISK) for random accessdevices.

Storage pools and volumes A storage pool is a named collection of storagevolumes, of the same media type. A storage poolis associated with a device class. For example, an8 mm tape storage pool contains only 8 mm tapevolumes. A storage pool volume is associatedwith a specific storage pool.

Figure 72 summarizes the relationships among the physical devices, TivoliStorage Manager storage objects, and Tivoli Storage Manager clients:


Figure 72. Putting it all together

1 When clients or nodes are registered, they are associated with a policy domain.The other Tivoli Storage Manager policy objects are within the policy domain.

2, 3 When a file is backed up, archived, or migrated from a client, it is bound to amanagement class. A management class and the backup and archive copygroups within it specify where files are stored and how they are managed whenthey are backed up or archived.

4, 5 Storage pools are the destinations for backed up, archived, orspace-managed files. Copy groups specify storage pools for backed up orarchived files. Storage pools are mapped to device classes, which representdevices. The storage pool contains volumes as indicated in the device typeassociated with the device class. For example, a storage pool that is mapped to adevice class with a device type of 8MM contains only 8 mm tapes. All devicesrequire a device class that specifies a device type. Tape devices also require alibrary and drive for management of media, including the mounting of that media.


6 Files that are initially stored on disk storage pools can migrate to tape storagepools if the pools are set up in a storage hierarchy.

To use your storage resources efficiently, you can arrange server storage into ahierarchy. You can then define when data is migrated from faster, more expensivestorage pools (disk, for example) to slower, less expensive storage pools (tape,for example). You can also store data on another Tivoli Storage Manager system,and create a two-tier or multi-tier environment (this is called server-to-servercommunication, and is only available with Version 3 servers).

5.1.3 Automating client operationsYou can automate client operations, such as backup and archive. Figure 73shows the Tivoli Storage Manager objects that may be involved in automatedclient operations.

Some of the terminology used in the space management function, tends to getconfused with terminology used in the entire ADSM setup.

The first term is hierarchical storage management (HSM). When talking aboutthe storage management of the ADSM server, we talk about HSM for ADSMserver storage pools. When discussing the file migration and retrieveprocesses, we are talking about HSM for ADSM clients.

The same confusion can exist for migration. Migration in the sense of storagemanagement means moving data from one storage pool to another. Whendiscussing migration in an HSM client environment, it means moving files fromthe client’s file system to storage on the ADSM server.

Terminology


Figure 73. Automating client operations

They are:

• Include-exclude criteria on each Tivoli Storage Manager client

Determines which files are backed up, archived, or space managed, and bindsfiles to management classes.

• Management class

Determines where client files are stored and how they are managed.

• Schedule

Determines when client operations such as backup occur.

• Association defined between client and schedule

Determines which schedules are run for a client.

The client can specify a management class for a file or set of files, or can use thedefault management class for the policy domain. The client specifies amanagement class by using an INCLUDE option in the client’s include-excludelist or file (see A in Figure 73). The management class contains information thatdetermines how Tivoli Storage Manager handles files that clients back up,archive, or migrate. For example, the management class contains the backupcopy group and the archive copy group.

ADSMBackup-Archive Clients

ADSMStorage Pools

ADSM Server

Policy Domain

Policy Set

ADSM Schedules

ManagementClass

(MCENGR)

ManagementClass

(MCCRIT)

Backup CopyGroup

Backup CopyGroup

Archive CopyGroup

Archive CopyGroup

dsm.opt

exclude

include

include

D:\*.obj

C:\dev\*.bak mccrit

C:\res\*.* mcengr

Weekly

Daily

Association


Each copy group points to a destination, which is a storage pool where files arestored when they are backed up or archived (see E in Figure 73).

Clients are assigned to a policy domain when they are registered. Schedules thatcan automate client operations are also associated with a policy domain (see C inFigure 73). To automate client operations, you define schedules for a domain.Then you define associations between schedules and clients in the same domain(see B in Figure 73).

For a schedule to work on a particular client, the client machine must be turnedon and must be running the client scheduler. The scheduled client operations arecalled events, and information about events are stored in the Tivoli StorageManager database (see D in Figure 73). For example, you can query the server todetermine which scheduled events completed successfully and which failed.

5.1.4 Supported devicesThe following tape devices are supported by the IBM Tivoli Storage Manager forWindows NT Version 3 Release 7 device driver:

• 8 mm 20/40 GB tape drive• DLT 20/40 GB tape drive• DLT 35/70 GB tape drive• DLT 40/80 GB tape drive• DLT 3502 autoloader and library• DLT 3447 Library• 8 mm 3449 Library• Magstar 3570• Magstar 3575

If the device is not supported by the Tivoli Storage Manager device driver, but issupported by a Windows NT device driver, you can use the Windows NT devicedriver to control the device. You must define a device class with device typeGENERICTAPE for devices used in this way.

When you use a Windows NT device driver, you must use a device type ofGENERICTAPE when you define the device class for the device. For devicesassociated with such a device class, Tivoli Storage Manager does not know theactual device type or recording format. For example, if you use a Windows NTdevice driver for a 4 mm drive, Tivoli Storage Manager does not know that thedrive is a 4 mm drive, and does not know that the drive is using the DDS2recording format. Tivoli Storage Manager knows only that the device is a tapedrive, and uses the drive's default recording format.

As a result, you must be careful when setting up GENERICTAPE devices.Because Tivoli Storage Manager does not know the device type, Tivoli StorageManager cannot prevent you from making some mistakes that can causeproblems. For example, you could define a 4 mm drive and an 8 mm drive to thesame manual library, then define one GENERICTAPE device class that points tothat library. Tivoli Storage Manager does not know that the drives do not usecompatible tapes and may end up requesting that you do the impossible: mount a4 mm cartridge into an 8 mm drive.


The following tape devices are supported by IBM Tivoli Storage Manager for OS/2Version 2 (V2R1 level 0.15, fix level IP21355):

• 4 mm 12/24 GB DDS-3 tape drive• 8 mm 20/40 GB tape drive• DLT 20/40 GB tape drive• DLT 35/70 GB tape drive• DLT 3447 Library• 8 mm 3449 Library• Magstar 3570• Magstar 3575

For more information and updates, please refer to Tivoli Storage Manager’ssupported devices Web page:

http://www.tivoli.com/support/storage_mgr/adsercli.htm

5.2 Tivoli Data Protection for Workgroups

Tivoli Data Protection for Workgroups, or TDPfW, is a new product, which is partof the Tivoli Storage Management product set (see 5.1.1, “Products and basecomponents” on page 125). It is a disaster recovery tool, usable on Windows NTmachines. Using Object Replication Technology, it is able to create an exactimage of an entire hard disk. This includes partition information, boot records andFAT and NTFS partitions. The copy is created on locally attached tape devices.

When a disaster occurs, a restore can be done using these tapes. In order to dothis, you can create diskettes based on the Windows NT setup diskettes. Sincethe object replication technology works at a level lower than the operating system,all information can be copied and restored. This includes security information andopen files. One thing to keep in mind is that hardware must be equal in order tocreate a bootable system after recovery. This is because all hardware andsoftware configurations are in the disk copy that is created on tape.

5.2.1 ConceptsThe following describes the terminology used within a Tivoli Data Protection forWorkgroups environment.

5.2.1.1 ReplicateDue to the way data is moved to tape, the traditional backup terminology is notaccurate. Since the data is moved by doing a block-by-block capture of the disk,replication of the data is a better description. This also explains how data isreplicated: all disk blocks are moved to tape, and during recovery, these diskblocks are placed in the exact same location on a new hard disk. You canhowever also restore individual files or disk volumes.

5.2.1.2 Tivoli Data Protection for Workgroups hostThis part of the Tivoli Data Protection for Workgroups software is the one that isdoing the actual replication of data from disk to tape. The other major componentperforms administrative tasks.



5.2.1.3 The mount objectThe object holding the replicated data is referred to as the mount. The mount canbe accessed as a normal file system, using for example Windows Explorer. Thismethod is used to restore single files, instead of using the disaster recoveryprocedure.

5.2.1.4 The partition data objectThe partition data object stores information on partition tables from the replicatedhard disk. It is necessary information when doing a disaster recovery to a newhard disk.

5.2.2 ComponentsTivoli Data Protection for Workgroups consists of two components: anadministrative part and the host replication part. The administrative part is usedto start and schedule replications, monitor activity and tape management. It canbe installed on any Windows NT, Windows 98 or Windows 95 system and canmanage a host locally, or several hosts remotely. This is done using TCP/IPcommunication.

The host part will communicate with the attached SCSI tape device. This hostpart is responsible for copying data to tape.

The above components enable TDPfW to be used in small workgroup-likeenvironments. However, it is possible to integrate Tivoli Data Protection forWorkgroups into larger, enterprise storage management setups. This is done bylinking the hosts to the Tivoli Storage Manager (see 5.1, “Tivoli Storage Manager”on page 124). By doing this, you can use the Tivoli Storage Manager to schedulereplications done by TDPfW, and store events centrally in the Tivoli StorageManager server activity log.

The administrative part of TDPfW always communicates with the host usingTCP/IP, even when installed locally. That is why you must always have TCP/IPinstalled and functioning. If you have a stand-alone system, without networkconnection, the Windows NT internal loopback TCP/IP address, 127.0.0.1, canbe used.

Note


Figure 74. Tivoli Data Protection for Workgroups host configuration

5.2.3 Supported devicesTivoli Data Protection for Workgroups supports the following devices:

• IBM 35/70 GB DLT• IBM 20/40 GB DLT• IBM 20/40 GB 8 mm• IBM 20/40 GB DDS-4• IBM 12/24 GB DDS-3• IBM 3447 DLT library• IBM 3449 8 mm library• IBM 3570 Magstar library

5.3 VERITAS NetBackup

VERITAS NetBackup is a client/server backup product, available on Windows NTand UNIX platforms. The NetBackup client software provides backup and disasterrecovery services. Besides standard file backup, you can also perform onlinebackups of Microsoft SQL server, Microsoft Exchange, Oracle DB2 and LotusNotes databases. The NetBackup server holds the storage devices and thedatabases, called catalogs, that contain information about backups, storagedevices and media, configuration settings and errors. The clients connect to thisserver using TCP/IP.


In order to simplify large configurations, NetBackup uses centralizedmanagement for different servers, and has the ability to group servers into socalled clusters. In this cluster environment, one server functions as the master,while others are designated to be slaves. The master backup server is theadministrative control server, and is responsible for controlling operations onslave servers. These control operations include scheduling and backupoperations. The master server also holds the catalog of all backup objects storedon the different slave servers. This provides a transparent approach to backing updata, where users do not need to know where their data is actually stored.

Supported server platforms include Windows NT and several UNIX brands.Supported client platforms include:

• Windows NT• Windows 95, 98 and 2000• Novell NetWare• OS/2• OS/400 (Using LXI Media Management System)• UNIX brands (including Linux)

5.3.1 ConceptsThis section explains the different concepts and terminology used by NetBackup.

5.3.1.1 Storage unitsIn order to simplify the use of multiple storage devices, NetBackup groups thesedevices and media in storage units. When grouping devices of the same type andmedia of the same density, backup images are redirected to these storage unitobjects, rather than the physical devices. This enables you to assign backups to astorage medium with certain attributes, without having to worry about physicaldevices. Storage devices can be either disks or external storage, such as tape oroptical devices. There are three categories of storage units:

• Directly attached external storage devices, under control of the MediaManager (see 5.3.1.5, “Media Manager” on page 140).

• Remote storage units, managed by the media manager, through a mechanismcalled the Network Data Management Protocol.

• Disk file system storage units, consisting of a specific directory.

5.3.1.2 Backup classesBackup classes are used to group clients with specific backup needs. A clientmust belong to one of these classes, but can be part of more than one. Backupclasses define which files need to be backed up, the storage unit that must beused, together with the volumes, and the assigned schedules. Besides theseassignments, specific attributes, like compression, encryption and priority arealso defined in the backup class.

5.3.1.3 SchedulingSchedules are defined to a backup class, and apply to all clients and filescontained in that class. You can control backup and archive processes using theschedules. Attributes that can be set for a schedule include the type of backup,the start time and duration, the frequency and the retention level. You can alsooverride class settings, including the storage unit to be used and the volume pool.


5.3.1.4 Backup and restore processesClient backup can occur in three ways:

• Scheduled backup

Scheduled backups are used to automatically start the backup process at acertain time. They are defined by the administrator.

• Manual backup started by the administrator

• Manual backup started by the client

For all three types of backup, the files are moved from the client to the server. Todo this, the client creates a backup image, which is sent to the server. The serverthen moves this image to the appropriate storage unit. Information about filesresiding in the backup image, is also sent by the client to the server. Thisinformation is stored in the backup image catalog.

Figure 75. Data flow for backup operations

Restores are initiated by the client. A request is made to the server to restore oneor more files. The server then identifies the device and tape volumes (when thebackup resides on a tape volume) necessary to complete the restore. This isdone by looking at the backup catalog. Using the True Image Recovery restoretechnique, deleted files are not restored.

MediaManager

BackupManager

DatabaseManager

NetBackupAgent

Data BackupCatalog

StorageUnits

Client

Backup Image

Catalog info

Initiate Backup

NetBackupServer


Figure 76. Data flow for restore operations

5.3.1.5 Media ManagerThe NetBackup Media Manager is the part of NetBackup that controls tapedevices, and all media associated with them. It consists of three parts:

• Robotic management, used for managing the robotic part of tape libraries andautoloaders.

• Device management, used for tape device management. This includes queriesto the volume database part of the catalog in order to locate volumes andissuing mount requests.

• Media management, which handles everything that concerns tape media. Thisincludes statistic information.

The Media Manager can also be used to share tape libraries between servers. Inthis scenario, the NetBackup servers requiring access to the library sendrequests to the NetBackup server acting as robot master. This robot mastersends the robot requests to the library. For performance, each server can have aseparate data path to the library.

5.3.2 Supported devicesVERITAS NetBackup supports the following IBM tape libraries:

• IBM 3447 DLT tape library• IBM 3449 8 mm tape library• IBM 3570 Magstar library• IBM 3575 Magstar library

For more and updated information, please consult the VERITAS support Webpages, at:

http://support.veritas.com

MediaManager

RestoreManager

DatabaseManager

DataBackupCatalog

StorageUnits

Client

Initiate restore

NetBackupServer

clientsoftware

RestoreDeamon

Restore data

User requestclientinterface



5.4 Legato NetWorker

Legato NetWorker is a backup/restore application, which functions according to aclient/server model. The NetWorker product set is made up of differentcomponents. The base product set consists of the server and client software. Theserver can be installed on Windows NT, NetWare and several UNIX platforms(AIX, HP-UX, IRIX, Dynix/PTX,Tru64 UNIX, SGI IRIX and Sun Solaris). The clientsoftware is supported on current Windows versions (NT Server and Workstation,98 and 95), Novel NetWare, Macintosh and UNIX platforms (including Linux).

Besides this base product, available in three editions (workgroup edition, networkedition and power edition), the following add-on components can be installed:

• Autochanger module, providing support for tape libraries and autochangers.• NetWorker Archive, extending the backup capabilities of the product, and

providing archival functionality.• NetWorker HSM (only for the Solaris platform).• NetWorker SNMP, providing an SNMP agent.• The BusinesSuite, which combines backup agents for the following database

products: DB2, Lotus Notes, Oracle, Sybase, Informix and Microsoft Exchangeand SQL server.

The client/server setup of this product is comparable to the previous productsalready discussed. The server functions as the primary resource, and deals withkeeping backup databases, policies and device and media management. Thesedatabases consist of the client file index, which stores what client backups, orsave sets are stored on the server, and the media database.

The client provides a user interface that sends the save sets to the server. Theclient can be any system in the network, or locally installed on the server.

5.4.1 ConceptsThe NetWorker product is logically split into separate components, calledresources. These resources are the building blocks of the product, and theentities to which the administration product interfaces. The following list providesan overview of these resources, and their definitions:

Server Identifies the local NetWorker server definitions. These includemultiplexing of client backup and restore sessions, securityand notification settings. Also, storage nodes are defined inthis resource. A storage node can be seen as a remotestorage device. The indexes are kept on the local server.Storage nodes cannot be used with the workgroup edition.

Client In the client resource, you define which objects you willbackup. These objects can be entire file systems, specificvolumes or individual files. Besides this, the retention policywill be defined. This enables you to keep a certain number ofversions of a file for a certain amount of time.

Directive Being a subpart of the client resource, directive resources willdefine how certain client data is backed up. Directives aresmall programs, using Application Specific Modules (ASM).Using file filters, you can define an ASM action for a specificfile or sets of files. You can for example assign Aims that



always back up a file (whether it has changed or not since thelast backup), compress a file, don’t back up a file, passwordprotect and encrypt certain files.

Device Describes a device that is connected to the NetWorker server.It can also be a device connected to a remote storage node.NetWorker supports more than one device per server. Themaximum number of devices depends on the type of serveryou have installed. The workgroup edition supports up to 2devices, the network edition 16, and the power edition 32.Besides tape storage devices, you can also define a disk filedevice. This device resource will use the server’s hard disk tostore save sets.

Autochanger Used to describe a tape library or autoloader. You can definethe physical attributes of the library (number of slots anddevice names), as well as certain functions like autoclean anduse of the barcode readers.

Pool Pools are used to group a number of volumes, defining whichdata they can receive. You can define pools for specific groupsof clients, save sets and backup levels.

Staging Save set staging allows NetWorker to move data from onedevice to another. It can be used for example to move datafrom a file device to a tape device.

Label template Provides instructions for NetWorker to follow whenever thestorage management application needs to create a label for avolume. Each pool is associated with a specific label template.

Group Groups clients in order to define timing for schedules.

Notification Using this resource you can define actions to take whencertain events occur.

Policy Sets the period that save sets will be kept on server storageand in the save set index.

Schedule Schedules are used together with the group resource. Whilethe group definition gives the start time of the backupoperation, the schedule resource itself defines which level ofbackup (for example full or incremental) needs to be done onwhich day. Backup levels define which data will be backed upduring the scheduled backup operation. Four self-explaininglevels can be used, including Full, Incremental, Consolidated(differential) and Skip, which is used to skip a certain schedule(for example on a holiday). Besides these four, you can use 9other levels, Level 1 through Level 9. When doing a backup ofa certain level, only data changed since a prior backup with alower level will be backed up. For example, if you back upusing level 1, data changed since the last full backup(considered level 0) will be taken into account. If later a level 2backup is launched, only data changed since the last level 1backup will be moved. Using these levels, you can achievehigh granularity of which data is backed up.


5.4.2 Supported devicesLegato NetWorker for Windows NT supports the following IBM tape drives andlibraries:

• IBM 40/80 GB DLT• IBM 35/70 GB DLT• IBM 20/40 GB DLT• IBM 20/40 GB 8 mm• IBM 20/40 GB DDS-4• IBM 3447 DLT library• IBM 3449 8 mm library• IBM Magstar 3570 library• IBM Magstar 3575 library

The NetWorker for Novell NetWare supports these devices:

• IBM 35/50 GB DLT• IBM 20/40 GB DLT• IBM 20/40 GB 8 mm

For more information about supported devices, consult the Legato CompatibilityGuide, which is accessible at:

http://www.legato.com/product_literature_library.html

5.5 Computer Associates ARCserveIT for Windows NT

ARCserveIT is the rebranding of the well known ARCserve product family. TheARCserveIT servers are available on Windows NT, Novel NetWare and UNIXplatforms. This section is written with a focus on the Windows NT platform.

ARCserveIT is available in 3 editions for the Windows NT platform. The differenteditions are designed to provide the appropriate amount of capability wheninstalled on different classes of machines. The three editions are:

• Workgroup Edition• Advanced Edition• Enterprise Edition

The workgroup edition is used for small environments, supporting one WindowsNT server and the attached clients. The client agents are available for Windowsoperating systems, OS/2, NetWare, Macintosh and UNIX systems. The advancededition is suited for medium size businesses. The difference between theadvanced and workgroup edition is the support for multiple servers, and acentralized management tool. Finally, the enterprise edition adds support for SAPR/3, advanced library systems and cross-platform management.

Additionally, the above editions can be expanded using the following options:

Disaster recovery option This option allows you to completely reinstall aWindows NT server or workstation after file systemloss.

Replication option The replication options performs a real-timereplication of data from one server to another.

http://www.legato.com/product_literature_library.html


When the first server suffers a failure, ARCserveITredirects users to the secondary server.

RAID option The RAID option allows you to arrange tapedevices into a “hard disk like” RAID configuration.It provides data striping across multiple drives andcan also be used for drive mirroring. Theadvantages of this system are availability andperformance.

Image option The image option performs a block-level hard disksnapshot to tape. The advantage of this isperformance.

Backup agent for open files This agent provides a way to back up files that arein use (opened or locked) during the backupprocessing.

Tape library options The tape library option provides support for tapelibraries. This module is primarily intended forlarger libraries, while basic autoloader support isincluded within the base product.

Client agent support Provides backup and restore capabilities fornetworked machines, running any of the followingoperating systems:

• Windows 3.x, 95/98• Macintosh• OS/2• Windows NT server and workstation• NetWare• SUN OS• Solaris SPARC• Solaris Intel• AIX• HP/UX 9.x and 10.x• Silicon Graphics IRIX• Digital UNIX• SCO Open Server• SCO Unixware• AS/400

Networked library option NLO is used to share libraries across multipleARCserveIT servers.

Data migration support Adds Hierarchical Storage Management (HSM)capabilities to the product.

Optical library support This module enables ARCserveIT to use opticallibraries or jukeboxes for HSM use.

Database backup agents Provide online backup capabilities for the followingdatabase or messaging products:

•Lotus Notes•SAP R/3•Microsoft Exchange•Microsoft SQL server•Oracle


•Informix•NonStop SQL/MX

Some of the above options are only available on the advanced or enterpriseeditions. Examples include the HSM options.

For additional and updated information on CA’s ARCserveIT products, pleaseconsult their Web site, at:

http://www.cai.com

5.5.1 ConceptsARCserveIT is made up of two main components, which interact to providebackup and restore functions. The ARCserveIT Manager submits backup andrestore jobs to the server, and is used to manage the server’s database andgenerate reports. The ARCserveIT Server Admin is used to control ARCserveITservices. These services include the Job Engine, Tape Engine and DatabaseEngine.

The job engine is the scheduling system of the ARCserveIT server, and is used tostart jobs at a certain time. The job engine interacts with the Job Queue, whichholds all jobs that need to be run. When a job in the job queue is eligible to run,the job engine will send it to the appropriate handler.

The tape engine is the part that is used to interface with the attached storagedevices. It will select and communicate with a device required to run a certain job.

Finally, the database engine records all activity, maintains a history of backed upobjects (files, directories, drives and machines), as well as job results, statistics,and the media used.

Figure 77 shows the server administration GUI, which can be used to control andconfigure these three engines:

http://www.cai.com


Figure 77. ARCserveIT server admin

The main functions of the product include:

• Backup• Restore• Media management• Device management• Database management• Reporting

Additionally, some utilities are available, including server database recovery, tapescan functions, purge and copy.

5.5.2 Supported devicesThe following IBM drives are supported by ARCserveIT for Windows NT Version6.6x:

• IBM NS20 tape drive• IBM 20/40 GB 8 mm• IBM 40/80 GB DLT• IBM 35/70 GB DLT• IBM 20/40 GB DLT• IBM 12/24 GB DDS-3• IBM 24/48 GB DDS-4• IBM 3447 DLT tape library• IBM 3449 8 mm tape library• IBM 3570 Magstar library• IBM 3575 Magstar library


The current list of supported devices can be found using the Certified Device List,located at:

http://support.cai.com/techbases/asnt/arcnt66.html

The DDS-4 and 40/80 GB DLT drives require a product patch, available at:

http://support.cai.com/Download/patches/asitnt/LO57168.html



5.6 Computer Associates ARCserveIT for NetWare

ARCserveIT for NetWare is a modular client/server data management applicationthat allows you to back up and restore data o n NetWare servers andworkstations. It is made up of the following components:

ARCserve Server: This component runs on a NetWare server, to which atape device is attached. It consists of a scheduler module,job processing modules, a tape server and a database.

ARCserve Manager: This component will run on a Windows 3.x or Windows95/NT workstation. It is the main interface to manage alloperations on the server.

Client Agents: Agents allow workstations to be backed up to the server.ARCserve provides agents for DOS, Windows 3.x,Windows 95 and OS/2. Optionally, Windows NT, UNIXand Macintosh agents can be purchased from Cheyenne.

Alert: The alert modules give you the possibility to send systemand error messages. Possible alert mechanisms areSNMP, fax, e-mail, printers and pagers.

The ARCserve manager and agents use your Novell network to communicatewith your ARCserve server.

The editions and options that are available, are equivalent to those for theARCserveIT for Windows NT product (see 5.5, “Computer AssociatesARCserveIT for Windows NT” on page 143).

Features of ARCserveIT for NetWare include integrated virus scanning, that willpass files through a virus checker before writing to tape. ARCserveIT is alsoequipped with a loader program, which gives you an overview of all actionshappening and checks versions of NLMs when starting ARCserveIT. This isespecially useful in a Novell NetWare environment, where version managementof modules is rather difficult. Finally, management can be centralized using aWindows-based administration program, called the ARCserveIT Manager, that isable to manage all ARCserveIT servers that are installed from one central site.

http://support.cai.com/techbases/asnt/arcnt66.html





5.6.1 ConceptsThe ARCserveIT server is made up of three modules:

• Job processing• Database module• Tape server

The job processing module will scan the ARCserveIT queue for submitted jobs.This queue is based on NetWare’s native queue management services (QMS).Job are submitted to this queue by the ARCserveIT manager. Once a job is readyto run (based on the requested start date and time), the job scheduler will get thejob from the queue and pass it on to the next two modules.

The database module, using BTRIEVE, keeps track of the following information:

• Backed up objects (files, directories, NDS objects, etc.)• Job information• Tape media information• Workstation information• Media pool information• Media locations (for tape cartridges stored off-site)

Finally, the tape server is used to communicate with your tape device. It storesconfiguration settings, and is responsible for all operations (write, read, errorhandling) where tape hardware is involved.

The following diagram, Figure 78, gives an overview of these components, andtheir associated NetWare loadable modules (NLMs).

Figure 78. ARCserveIT for NetWare design

ARCSERV.NLM

APROCESS.NLM(Backup, Restore)ARCOPY.NLM(Copy)

INTREAVE.NLM

WSTAPE.NLM

USERVE6.NLM

MACSERV6.NLM

FSTAPE.NLM

NetWare agentSPX

TCPIP

OS2, Windows 3.x, NT , 95, DOS

UNIX agents

NetWare Push agents

MacIntosh agents

TCPIP

NCP

IPX

Appletalk

Job Processing Module

Tape Server Module

Database Module

MACDB.NLMCLIENTS.NLMASDB.NLM

TAPESRV.NLMTAPEDB.NLM

STANDARD.NLMCHANGER.NLMBOARDSRV.NLM

ARCserveManager

ARCserveQueue


5.6.2 Supported DevicesARCserveIT for NetWare Version 6.1 supports the following IBM tape devices:

• IBM 40/80 GB DLT• IBM 35/70 GB DLT• IBM 20/40 GB DLT• IBM 20/40 GB 8 mm• IBM 12/24 GB DDS-3• IBM 3447 DLT library• IBM Magstar 3570 library• IBM Magstar 3575 library

For more information and updates, please refer to CA’s supported devices Webpage:

http://support.cai.com/techbases/as61/asitnwcdl.html

5.7 VERITAS Backup Exec for Windows NT

VERITAS Backup Exec for Windows NT Version 7.3 is a data managementsolution for Windows NT networks, providing backup and restore capabilities forworkstations and servers across the network. Backup Exec is available in fourconfigurations which should be sufficient for most multi-platform networks ofvarying sizes:

• Multi Server Edition

Provides backup protection for Windows NT workstations and servers, andcontains agent software for workstations running Windows 98, Windows 95,UNIX, and Macintosh. This edition also includes the Windows NT agentaccelerator, which increases backup performance of remote Windows NTsystems.

• Single Server Edition

Protects a single Windows NT server and any number of Windows NTworkstations, Windows 98 and Windows 95 clients.

• QuickStart Edition

Provides backup protection for one Windows NT server.

• Small Business Server Suite

This configuration allows you to administer Backup Exec through the MicrosoftBackOffice Small Business Server Console. Besides the server protection,agents are included to back up and restore SQL and Exchange servers.

Backup Exec provides a number of add-on products that enhance the capabilitiesof the Multi Server and Single Server products. The following components areavailable:

• Seagate Backup Exec Intelligent Disaster Recovery Option

Provides a solution to help protect and recover a failed Windows NT server.

A disaster preparation wizard guides you through the steps of creating a set ofrecovery diskettes to recover the Windows NT backup server. The informationon the recovery diskettes includes the Windows NT system files necessary tomake a failed Windows NT system operational following a disaster, together

http://support.cai.com/techbases/as61/asitnwcdl.html


with information about the hardware profile, and information on the mostrecent backups which are used to recover the system to the point of the lastbackup.

A disaster recovery wizard guides you through the steps necessary to get thecomputer to an operational state, and restore the computer’s data from the lastbackup set.

• Seagate Backup Exec Autoloader Module

The Autoloader Module provides Backup Exec with support for single-driveand multi-drive tape libraries.

• IBM ADSM option

Allows access to the ADSM data storage resources as though it were abackup device. Output from backup jobs can be automatically routed to theADSM system just as if it were a large tape library or autoloader. Multipleservers and workstations can all be protected using the ADSM option, and anynumber of Backup Exec systems can simultaneously connect to one ADSMsystem.

• Agent for Lotus Notes server

• Agent for Oracle database servers

• Agent for SAP R/3 servers (with Oracle database)

This agent provides support to back up Oracle databases in an SAP R/3environment, using the Backint interface.

• Agent for Microsoft SQL Server V6.x and V7

• Agent for Microsoft Exchange Server

• Agent for NetWare Server

Provides Backup Exec with support for NetWare servers, and allows WindowsNT network administrators to perform backup and restore operations onNetWare servers that are connected to the network.

• Agent Accelerator for Windows NT

Accelerator agents help speed up processing of data by performing taskslocally on the server before data is transferred to the backup server. Instead ofsending data in short bursts, data to be backed up is collected and sent to thebackup server as a continuous stream.

• Open File option

Provides support to take snapshot images of files that are in use at time of thebackup.

• RAID director option

Gives you the possibility to build RAID-like tape configurations, using singleSCSI tape devices.

• Shared storage option

This option lets servers share storage devices. This can be used to buildFC-AL tape configurations, or SANs.


5.7.1 ConceptsVERITAS Backup Exec for NT lets you back up data directly to storage deviceswithout using any intermediate stages. Device and media management functionshelp to track usage of media. The built-in scheduler, media overwrite protectionrules, and media rotation all help with the implementation of backup strategies.

Backup Exec for NT is built from the following modules:

• Backup server

The Backup Exec engine runs on the backup server. It handles all jobssubmitted to it, such as backup and restore, and manages all backup devicesand media.

• Client interface

This component can run either on the backup server or a remote server and isthe primary interface for interacting with the Backup Exec system. It is used tosubmit jobs, view results, hardware utility functions, and so on.

• Client agents

These are installed on servers and workstations and allow drives anddirectories on the local system to be protected by Backup Exec.

• Device and media management

Device management functions help to organize and allocate the storagedevices attached to the backup server. Backup Exec can organize drives intopools known as Drive pools and Cascaded drive pools.

In the following section, we will look at these in more detail.

5.7.1.1 ServerThe Backup Exec server is a job-based backup engine. Jobs define backup,restore, file grooming, catalog, verify and backup scan operations. These jobs arethen submitted to the server. Besides manual submission of these jobs, you canschedule jobs to run automatically at a certain time. A job history log ismaintained, together with a catalog, which records what data has been backedup.

Backup Exec uses the file attribute known as the “archive bit” to show that the filehas or has not been backed up. When a file is created or updated the archive bitis switched “on” to indicate the file requires backing up. The backup methods thatcan be used, are as follows:

• Normal

All selected files are backed up. The archive bit is switched off indicating thefiles have been backed up.

• Copy

All selected files are backed up. The archive bit is not modified indicating thefiles have not been backed up. This method allows you to back up files withoutaffecting the current backup strategy.

• Differential

All selected files that were modified or created since the last normal backupare backed up. This method switches the archive bit on, indicating the fileshave not been backed up.


• Incremental

All selected files that were modified or created since the last Normal orincremental backup are backed up. This method switches the archive bit off,indicating the files have been backed up.

• Daily

Files that were changed or created today are backed up. This method leavesthe archive bit intact.

• Working set

Includes all files that where created since the last normal or incrementalbackup. You can also specify to back up files that were accessed within thelast number of days. This method leaves the archive bit on.

Besides backing up data, you can also do file grooming, which can free diskspace on the server volume by migrating directories and files from the server tostorage media. The file grooming operation performs a verify operation after thedata is backed up. If the verify operation fails the file grooming operation isstopped; otherwise the original data is deleted. There is no automatic retrieval ofdeleted files; they must be restored. File grooming operations do not delete datafrom Backup Exec agent workstations, only from the server volume.

Another function of the Backup Exec server is event notification. In case of anevent that requires administrator attention, notifications can be sent usingdifferent methods. These include e-mail, pager, printer, SNMP and the WindowsNT event log.

5.7.1.2 Workstation agentsVERITAS Backup Exec provides backup agent software for backing up data fromWindows 98, Windows 95, Windows NT, Macintosh, and UNIX workstations. Theworkstations interact with the backup server through Backup Exec agents. Onceinstalled, the agent software is configured with the protocol to be used, if morethan one is available, and drives and directories are selected which must bebacked up by the server.

It is also possible to password protect drives and directories thus requiring theadministrator to provide the password before the directory or drive can be backedup. When configuration is complete, the agents generally advertise theirpresence to the backup server. These workstation agents may be seen in thebackup and restore windows, together with local and network drives.

5.7.1.3 Device and media managementBackup Exec automates device management and media management functions.Device management helps to organize and allocate the storage devices attachedto the backup server, while media management helps to categorize and trackusage of media.

Device managementBackup Exec uses the concept of pools: Drive pools and Cascaded drive pools,with the pools containing the actual physical tape devices.

• Drive pools

These are groups of two or more drives to which jobs may be assigned andrun on the first available drive. Offers fault tolerance by moving jobs from a


failed drive to the next available drive in the drive pool; concurrency by runningdifferent jobs on drives in the drive pool at the same time; and load balancingby distributing jobs more evenly across all drives in the drive pool.

• Cascaded drives

These are groups of two or more drives of the same type and capacity,appearing logically as one device. Large backup jobs that exceed the capacityof the media in one drive automatically continue on media in the next drive inthe pool.

When Backup Exec is installed, all storage devices connected to the server areautomatically recolonized as either changers (autoloaders) or stand-alone drives.At installation time, all storage devices are assigned to a default drive pool, DrivePool 1. Devices may be moved between Drive and Cascaded drive pools.

The device management capabilities in Backup Exec allow you to:

• Monitor device usage statistics and track hardware errors.• Generate reports containing details of when a drive was last cleaned, the

number of errors it is generating, hours of use, bytes processed, etc.

Device operationsDevice management functions allow you to manage the physical drives andperform operations on them such as:

• Delete drives• Pause and resume drives• Inventory drives• Rename drives• Erase media in drives• Catalog media in drives• Retension tape media• Eject media• Label media• Format media• View drive statistics and properties• Enable and disable drives• Enable and disable hardware compression

Media managementThe media management capabilities in Backup Exec help to recognize andcategorize media in the storage device. Media management falls into threecategories:

• All media

All media that has been introduced into the Backup Exec system

• System media

Media that has not been allocated to a media set, such as Reusable, Retired,and Imported media.

Reusable media is media that does not yet belong to a media set. It includesnew media, erased media, and media moved from another media set or group,such as Imported media.


Retired media is media that has been discarded because it is prone to anexcessive number of errors and will not be reused. Retired media should beremoved from Backup Exec.

Imported media is media created by another version of Backup Exec oranother product. Data on imported media can be restored until the media isoverwritten.

• User media sets

This is all media that has been assigned to media sets.

Media sets contain actual media which contain the data. Media sets aredefined by a retention period and append period. Until the retention periodexpires, the media is considered allocated, after which the media becomesrecyclable and available for reuse.

Backup Exec automatically creates a default media set, Media Set 1, and setsthe default retention and append periods to Infinite. New media sets may becreated with retention and append periods appropriate for the length of timethat data is to be retained. When a backup job is defined it should be assignedto a media set in the User Media Sets category which has the retention andappend periods you want to use for the job.

Recyclable media is a media set whose data retention period has expired.When a backup job runs, Backup Exec will use reusable media beforeselecting media from recyclable media for the job.

Media overwrite protectionBackup Exec has three levels for protecting media and it is necessary tounderstand these to ensure data is not accidentally overwritten. The generalprotection level is first set when Backup Exec is installed, but can be modifiedlater and set on individual media.

• Full

Media that belongs to an allocated media set and imported media categorycannot be overwritten. This is the safest option. Backup Exec selects media foroverwriting in the following order:

• Reusable• Recyclable

• Partial

Media belonging to an active media set cannot be overwritten. Backup Execselects media for overwriting in the following order:

• Reusable• Recyclable• Imported

• None

Disables the overwrite protection feature. You are responsible for making suremedia is not accidentally overwritten. Backup Exec selects media foroverwriting in the following order:

• Reusable• Recyclable• Imported• Allocated media


Media operationsBackup Exec provides a number of functions to help with media operations:

• Catalog

Media containing data that was stored during a backup or file groomingoperation must be cataloged before that data can be restored or verified.

• Erase• Format• Inventory• Label media• Rename• Retension• Properties

Properties provides a way of gathering usage totals and errors about aparticular media which can help in deciding when to retire the media.

5.7.2 Supported devicesThe following tape devices are supported with Backup Exec Version 7.x forWindows NT:

• IBM 40/80 GB DLT• IBM 35/70 GB DLT• IBM 20/40 GB DLT• IBM 20/40 GB 8 mm• IBM 20/40 GB DDS-4• IBM 12/24 GB DDS-3• IBM NS20 tape• IBM 3502 DLT library and autoloader• IBM 3447 DLT library



5.8 VERITAS Backup Exec for Novell NetWare

Backup Exec Version 8.0 is a storage solution for Novell NetWare networks.Backup Exec is available in four editions:

• Multi-Server edition

Provides a backup solution for any number of servers or workstations, runningNovell NetWare, OS/2, DOS, Windows 3.x, Windows 95, Windows NT, UNIX orMacintosh operating systems.

• Single server unlimited edition

Provides a backup solution for one Novell NetWare file server and clientsrunning DOS, Windows 3.x or Windows 95.

• Single server 25 user edition

Provides a backup solution for one Novell NetWare file server with a maximumof 25 licensed users and clients running DOS, Windows 3.x or Windows 95.



• QuickStart edition

This edition protects one NetWare file server, with one tape device attached.No support is provided for attached client workstations.

In addition, the following add-on products, that enhance the possibilities of theirbase Backup Exec product, are available:

• Intelligent Disaster Recovery Option

Provides recovery for your server after hardware or system failure. This optionwill enable you to restore a disk or entire system, with a minimum of input.

• Advanced Autoloader Option for NetWare

The Advanced Autoloader Module enables you to establish groups of tapeswithin the device magazine - thus enabling you to direct data to user-definedgroups.

• Open File Manager Option

Open File Manager provides protection for active e-mail, database, and otherdata files even while information is being entered or changed by users.

• ADSM Option

Allows network administrators to access the ADSM software (see 5.1, “TivoliStorage Manager” on page 124) through Seagate Backup Exec for NetWare.Seagate Backup Exec uses the ADSM system as a large data storage device,and allows backups to be automatically routed to the ADSM system just as if itwere a large tape library or autoloader. Multiple servers and workstations canall be protected using the ADSM option, and any number of Backup Execsystems can simultaneously connect to one ADSM system.

5.8.1 ConceptsBackup Exec consists of the following components:

• Job manager

The job manager is the main component and resides on the server that hasthe tape device attached. It consists of the job server, which processes allstorage jobs and the job console, which is used as the user interface.

• Workstation clients

Available for Novell NetWare, Windows 3.X, Windows 95 and OS/2 clients(depending on the edition you are using), this component serves as aninterface to submit jobs to the server. It is also used as an administrativeinterface.

• Backup Exec agents

The agents allow the backup server to back up the data residing on their filesystems. Agents cannot operate on their own, since they cannot submit jobs.They will have to rely on jobs planned by workstation clients.

The job manager uses NetWare’s Queue Management Services (QMS) to queuejobs before they are processed. This means that multiple jobs can be submittedsimultaneously. The job manager will use a job history file for logging theprocesses, and a catalog file to store information about processed objects. It canalso be used to perform operations on the tape devices, like rewinding,retensioning, erasing, ejecting, verifying and cleaning.


To differentiate storage options, Backup Exec uses a mechanism called PartitionManagement. A partition is actually a collection of one or more tape devices, andeach job will be routed to a partition. The definition of a partition consists of itsname, the tape drives attached, supported operations (backup, restore, taperotation, file grooming), the users that are able to access the partition, thecompression method (hardware, software or none) and advanced settings whichinclude performance definition and job rerouting options.

Different jobs can run concurrently on different partitions. However, the limitationexists that at least one tape device be attached to a partition, and that a tapedevice can only be defined to one partition. This means that the maximumnumber of partitions equals the number of tape devices. The advantage ofworking with different partitions, is that you can specify a set of definitions for onetype of operation, or specify them for a set of users.

All actions that are started against the job manager, are called jobs. A job isdefined on a workstation client, and is routed to a partition. When defining a job,the first thing to do is define the agents that will be included. You will also have todefine the action to be taken, and specific parameters. For more information, see5.8.2, “Job types” on page 157.

Job manager also holds a tape inventory catalog, which provides information onthe tapes that have been used. This simplifies tape management. Besides thisdatabase, there is also a possibility to define tape rotation schemes (see 5.8.2,“Job types” on page 157).

5.8.2 Job typesBackup Exec can be used to perform the following jobs:

• Backup• Restore• File grooming• Tape rotation

For each operation, a job will have to be created. These jobs can be created on aworkstation client. A job definition will include the type of job, the agents for whichthis job is defined, and the partition that will be used.

5.8.2.1 Backup jobThe first type of job is a backup job. The backup job will create a process on thejob manager that will back up a certain list of agents (referred to as devices byBackup Exec) and include a list of data objects that are included in the backup.The definition of a backup job will include the type of backup to run (normal or full,incremental or differential). There is also a copy function included, whichtransfers selected data objects to the backup server, without setting the backupstatus flag. Initially, you will need to start with a full backup (referred to as anormal backup in Backup Exec).

When defining a backup job, you can also define a start date and time andfrequency. This way, you can define a job to run at certain intervals, and scheduleyour backups.


5.8.2.2 Restore jobA restore job will restore files from the backup media to a client or agent. Thedefinition of objects that need to be restored can be done either on a file namebasis, or by selecting an agent (or device). When started, the job manager willretrieve the needed tape volumes from its catalog, and request that they bemounted.

5.8.2.3 File groomingFile grooming is a mechanism that enables you to migrate files that have not beenaccessed for a while. You can set up a file grooming job that will back up files thatcomply with the specifications you made. After backup, a verification will run, andif this completes successfully, files will be deleted from the client. There is noautomatic retrieval process. If files are needed after they have been moved totape, you will need to restore them.

5.8.2.4 Tape rotationTape rotation jobs are a compound of backup jobs. Using the tape rotation job,you will be able to define a tape rotation scheme, and Backup Exec will define theneeded backup jobs to perform this tape rotation job.

5.8.3 Supported devicesThe following tape devices are supported by Backup Exec Version 8.5 forNetWare:

• IBM 40/80 GB DLT• IBM 35/70 GB DLT• IBM 20/40 GB DLT• IBM 20/40 GB 8 mm• IBM 20/40 GB DDS-4• IBM 12/24 GB DDS-3• IBM 3502 DLT library and autoloader• IBM 3447 DLT library





Chapter 6. Installation and configuration

This chapter discusses the installation and configuration process for thehardware and software discussed in Chapter 3, “Hardware” on page 33 andChapter 5, “Software” on page 123.

6.1 Tivoli Storage Manager for Windows NT

This topic will go through the installation and configuration of the Tivoli StorageManager for Windows NT Version 3.7 Server. For more information, refer to theTivoli Storage Manager product manuals. The Tivoli Storage Manager productmanuals are available on the Internet at the following location:

http://www.tivoli.com/support/storage_mgr/pubs/admanual.htm#ntV37

6.1.1 Software installation

Tivoli Storage Manager for Windows NT has the following system requirements:

• Windows NT 4.0 with service pack 4 or higher• 130 MB disk storage• 64 MB memory (128 MB recommended)

These requirements are only for product code, and do not include space neededfor database, log or storage volumes.

The installation program is automatically started when you insert the product CD,or, if autorun is disabled, by starting setup.exe in the root directory of the CD.When the installation starts, one of the first steps is to choose a destinationdirectory where the product files will be placed.

In this section, we sometimes refer to the Tivoli Storage Manager server assimply the server, and to the Tivoli Storage Manager client as the client.

Note

http://www.tivoli.com/support/storage_mgr/pubs/admanual.htm#ntV37


Figure 79. Installation path

Next, the installation process lets you choose between three different types ofinstallation, namely:

• Typical• Compact• Custom

Since you are going to install server software that will need configurationafterwards, we suggest that you take the custom route. This way, you will knowexactly what you are going to install.

Figure 80. Choosing between typical, compact or custom

Chapter 6. Installation and configuration 161

When choosing the custom route, the following choices are available:

Server Files Which includes server utility files, server executable files andlicense files.

Client Files This includes the Backup Archive client, Web Backup Archiveclient, administrative client, API runtime files and the ODBCdriver.

Online Help Installs Tivoli Storage Manager help files in HTML format.

Language Files Installs Tivoli Storage Manager in a specific language.

The components you will install depend on the use and type of installation. As ageneral rule, the server files, license files and the administrative client files arethe basics for any installation. Unless you know Tivoli Storage Manager by heart,installing the online help files can prove to be very useful.

The Backup/Archive and web shell files are only necessary if you are going to usethe server for local backups. This is the same for the API files. Unless you reallyneed them locally (for use by a Tivoli Storage Manager Data Protection agent forexample), don’t install them.

The Tivoli Storage Manager ODBC driver lets you export database informationusing the ODBC format. This way, you can query the database using severalapplications, such as Lotus 1-2-3. However, currently this driver is onlyavailable for US-English installed Windows NT systems.

Note

The installation program detects the country setting defined in Windows NT,and will install Tivoli Storage Manager clients in this language (if available). Ifyou want the install to run in a language other than the NT language, add thefollowing line to the [Startup] section of SETUP.INI (located in the samedirectory as SETUP.EXE):

EnableLangDlg=Y

This will bring up a dialog in which you can choose the installation language.

Note


Figure 81. Tivoli Storage Manager components

The next step will be to define where initial volumes will be placed for thedatabase, log file and disk storage volumes. You can change these locations.Before proceeding, ensure that you have enough space to accommodate thesevolumes. The initial storage pool volume will need 4 MB, the database volume13 MB and the log volume 9 MB. This is also a good time to think about theplacement of these volumes. Since they all have specific attributes, placementfactors differ. The storage pool volumes, for example, will tend to take a lot ofspace. However, they will typically be copied to the tape storage pools. So, themain concern should be space and speed, rather than availability. A RAID-5configuration would be good.

The database and log volumes tend to be a little smaller (however, in biginstallations they can get very large; mainframe customers, for example, deal withdatabases that can be 60 GB or more in size), but are very important for thefunctionality of the server. You do not want to lose them. Therefore, a combinationof high performance, capacity and availability is the best choice. RAID-1 solutionsare suggested. Also, when using the log file in roll-forward mode, it can be usedto recover a database to its most current state after failure. To give maximumprotection, you should place the log on a different volume than the database. Ifyou do not have the capability to do hardware RAID-1, Tivoli Storage Managergives you the possibility to create mirrors of the database and log files (up to twomirrors of the original) via the software.


Figure 82. Server initial volume placement

Finally, Tivoli Storage Manager lets you choose the program folder where youwant to place the program icons, and gives you an overview of the componentsand configurations you selected.

Figure 83. Tivoli Storage Manager installation settings

The installation will copy necessary files, and start the default definition of theTivoli Storage Manager software. This includes a default policy (STANDARD), adefault disk storage pool and default database and recovery log volumes.

After the installation finishes, you will have to reboot Windows NT to activate thechanges made.


6.1.2 ConfigurationThe first difference you will notice if you have ever installed ADSM, is that afterrestarting the server, Tivoli Storage Manager will give you the possibility to do theentire server configuration using wizards. However, for more experienced users,the powerful command interface is still available for doing the configurationmanually. We will now go through the initial configuration wizards. These include:

• Initial configuration environment wizard• License wizard• Services wizard• Device configuration wizard• Client node configuration wizard• Scheduler wizard• Performance wizard• Storage pool wizard• Database wizard• Recovery log wizard• Network client options file wizard• Media labeling wizard

Figure 84. Initial configuration start screen

The configuration starts by setting up the environment in which this server willrun. The information requested in this section of the initial configuration includesthe following:

• Tivoli Storage Manager administrator name and password• Information level given during the configuration• Whether the subject of this installation will be a stand-alone machine (one

server with one local client), or a server connected to the network.

Next, you will need to define which licenses you bought for your server. This isdone through the license wizard.


Figure 85. License wizard

The server uses license files, which are registered in the server’s database.These files are copied to the hard disk during installation. The following licensefiles exist:

• 1CLIENT.LIC

Provides a one-client license.

• 5CLIENT.LIC

Provides a five-client license.

• 10CLIENT.LIC

Provides a 10-client license.

• 50CLIENT.LIC


• ADVDEV.LIC

Provides a license for using tape devices not included in the base device list.All devices discussed here are included in the base device list, except for theIBM Magstar 3575 tapes (except Model L06 with one tape drive, which is inthe base device list), which require the extended device support.

• DRM.LIC

Provides a license for disaster recovery management operations (see theTivoli Storage Manager manuals for more information). This also includes theserver-to-server virtual volume support.

• NETWORK.LIC

Provides a license for network connections. This is needed when remoteclients are going to connect to your server.


• OPENSYS.LIC

License for Open System environment support.

• SPACEMAN.LIC

Needed for Tivoli Space Management clients.

Figure 86. Tivoli Storage Manager license options

Next, the Windows NT services used by the server need to be configured.

Figure 87. Service configuration wizard


Tivoli Storage Manager can use up to three Windows NT services. Two of them,the server and the SCSI device driver, are server related. The third, the schedulerservice, will be used by the local client.

The server service allows you to run the entire Tivoli Storage Manager as aWindows NT service. The console output of the server can be redirected to a file,the console log, or seen through the console monitor, which is part of the TivoliStorage Manager utilities. The configuration options of the server are the basicones that you have for every Windows NT service: automatic or manual start andthe account running the service. You can also specify the file and path for theconsole log file.

The TSM Device Driver service will be used to access all tape devices. TivoliStorage Manager does not use the standard Windows NT device drivers. Again,options you can set are the type of startup and the account information. If youwant, you can also exclude devices that will not be used by the server. Thisprevents conflicts between the TSM device driver and the one provided byWindows NT. The device driver is called ADSMSCSI.SYS.

The scheduler service is used by the Tivoli Storage Manager client node. Thisservice will be responsible for executing scheduled commands (like backups orarchives) on the client. Here, the options you can set are more detailed. Figure 88shows the available options. These include:

• Node name by which the client is known to the server• The location of the Options file for the client• File names for log files• Password settings

Figure 88. Scheduler service options

After configuring the services, you will be able to start the device configuration.This is done through the Device Configuration Wizard.


Figure 89. Device configuration wizard

Tivoli Storage Manager uses three definitions to specify the storage media.These are the device class definition, the library definition and the drive definition.The device class definition specifies the physical attributes of the library used.The library is a collection of tape devices, or drives. When only one tape device ispresent, it is also represented as a library, of type manual. Tape libraries will belibraries of type SCSI.

The type of drives and the number will be defined in the device class definition.Besides these two, the capacity and the mount parameters will also be set in thedevice class definition. The drive definition assigns specific drives to a definedlibrary. To identify SCSI libraries and tape devices, two parameters are used. Thefirst one, the devicename is based on the type of device and the SCSI address.This name has the form mtx.y.z.n or lbx.y.z.n. The mt indicates a tape device, andthe lb indicates that the device is the controller for a tape autoloader or anautomated library. The x equals the SCSI ID, y the LUN, z the bus and n the portnumber. Figure 90 shows an example of device names. The attached device is aMagstar 3570 library with two tape drives.


Figure 90. Device selection window

To create the above definitions through the wizard, simply drag and drop thelibrary device from the left-hand pane of the window to the TSM Devices icon inthe right-hand pane. Next, drag and drop the tape devices on top of the libraryicon you just added. Figure 91 shows the result of this operation.

Figure 91. Device selection window - setting up devices

You can also add devices of type File. A file device is a sequential device, usingfiles on disk to represent the volumes.

Once you have completed this, the device configuration wizard exits. The nextstep is the configuration of the client nodes.


Figure 92. Client node configuration wizard

This wizard will allow you to do two things: first, define the storage hierarchy. Bydefault, Tivoli Storage Manager installs two disk storage pools, BACKUPPOOLand DISKPOOL. It constructs these pools in such a way that the backup poolredirects its content to the diskpool. In order to make the diskpool migrate itscontent to the tape devices, you must drag and drop the diskpool icon on top ofthe tape pool (see the left-hand panes in Figure 93 and Figure 94).

Figure 93. Client node configuration


Figure 94. Client node configuration - storage hierarchy

Next, you must add client nodes. Clicking on the Add Node button brings up thewindow displayed in Figure 95 and Figure 96. The first information that is neededis the name you want to give to the node. Additionally, you must specify whichstorage pool the node will use. As you can see, the initial storage pool is selected(BACKUPPOOL). The entire process of moving data from this storage pool to thediskpool storage pool, and then to the tape storage pool is done by the server.This storage hierarchy is transparent to the node.

Figure 95. Adding a client node

Next, you must specify the policy that will be used for this client. Using the wizard,you can specify specific information for this client. For the server, this means thatit will assign the client to a certain storage policy. If a policy does not exist, onewill be created. Again, using this wizard this setup is totally transparent.


Figure 96. Adding policy information to a client node (window 2/2)

Next, schedule information will be added using the Scheduler ConfigurationWizard.

Figure 97. Scheduler configuration wizard

Using this wizard, you can define schedules and add client nodes to thisschedule. Figure 98 shows the screen of the wizard where you can associate aclient with a schedule by dragging the node from the right-hand pane to theappropriate schedule.


Figure 98. Define schedules and associate nodes

By clicking the Add button, you will add schedules (see Figure 99 and Figure100).

Figure 99. Schedule identification and operation

You can define the schedule name, the operation and the policy domain it willuse. Also, you can define the time and frequency the scheduled operation will


run. For more information about these values, please refer to the Tivoli StorageManager for Windows NT Administration Guide.

Figure 100. Schedule timing

Next, the configuration process will try to adjust some parameters that affectperformance using the Performance Configuration Wizard.

Figure 101. Performance configuration wizard


The Performance Configuration Wizard will ask some questions concerning thenumber of clients and the average file size of files that will be backed up (seeFigure 102).

Figure 102. Performance options

The wizard will also try to allocate storage volume space on the volume that hasthe best performance and has the most space available. Please keep in mind thatbesides performance and space considerations, availability may also beimportant.

Figure 103. Volume allocation


Finally, the performance wizard leaves you the choice of actually updating theserver option file, or just printing a report with recommended changes.

Figure 104. Updating server options

The next three wizards will guide you in determining optimum size of the neededdisk volumes (storage pool, database and recovery log volumes), and allocatingthe space. The initial installation allocated a certain amount of space. This wizardhowever will add space to the initial volumes to provide you with a configurationthat has enough volume space to function in your environment.

Figure 105. Disk storage pool volume wizard


To determine the size of the volume, the wizard requires an estimate of theamount of data that will be sent to the server each day. This is based on theassumption that we are going to set up a storage hierarchy (see 5.1.2, “Serverdata management” on page 127). The wizard will create a volume equal to thissize, since all data can then be moved to our next storage pool (which will be atape device).

Figure 106. Disk storage pool size input

Based on the amount given above, and the size of the initial volume (4 MB), thewizard will propose that you create a storage pool of a certain size. Someconsiderations that you will need to take into account when estimating the sizeare the following:

• The amount that will be sent daily is equal to the amount of data that changeseach day.

• If you turn on software compression, the actual amount of space necessarywill be less.

• You should keep a safety margin when estimating. Even if the disk storagepool initially has a low utilization rate, the amount of data that is backed updaily is likely to grow.


Figure 107. Recommended storage pool size

When completed, the disk volume wizard will create a volume (which is apre-formatted file) on the server’s disk.

Next, the database size will be estimated by the Database Volume Wizard.

Figure 108. Database volume wizard

The size of the database is estimated using the amount of data that you think theTivoli Storage Manager server will store (see figure Figure 109).


Figure 109. Database volume wizard input window

The next screen (figure Figure 110) will give you the proposed size for thedatabase. By continuing here, the volume will be allocated on the server’s disk.You can always add space to the database later.

Figure 110. Recommended database size

Finally, the recovery log space will be set. This is done through the Recovery LogVolume Wizard.


Figure 111. Recovery log volume wizard

In contrast to the previous two wizards, the recovery log wizard will not propose asize. To help you determine the size of the log, you need to know what it does.The recovery log is mainly used to roll back transactions to the database. Thismeans that when a transaction is done against the database, all changes arerecorded in the recovery log. If for some reason, the transaction cannot complete,this change information is used to undo all changes in the database. If thetransaction completes, and the changes are committed, the log information iscleared. This means that normally the size of the log file is not very big.

There is one exception however, and that is the case of a roll-forward recoverylog. Using the administrative interface, you can put your log in roll-forward mode.By doing this, all database transactions will be logged, until a database backup isperformed. The advantage of this is that whenever a problem occurs, thedatabase can be restored using the last backup, and then rolled forward to reflectthe most recent changes. This means however that log space needed is muchgreateer.


Figure 112. Recovery log size

The next wizard, the Network Client Options File Wizard (see Figure 113) willhelp you set up an option file that can be used for the clients. The wizardarranges this file in such a way that you can access clients from the network.

Figure 113. Network Client Option File Wizard

The first input (see Figure 114 on page 182) will be the communications protocolthat you are going to use between client and server. Tivoli Storage Managerallows you to use TCP/IP, IPX/SPX, NetBIOS or named pipes (for local clients).


Figure 114. Client communication protocol setting

Depending on the choice you make, the next screen will ask you forcommunication parameters. If you choose TCP/IP for example, the server’s IPaddress and port number will be requested. You can also specify the e-mailaddress of the Tivoli Storage Manager administrator, and even append anexisting option file (see Figure 115).

Figure 115. Additional options

Next, you will be asked the file name of this configuration package, and where itshould be placed (Figure 116).


Figure 116. Package name and location

The wizard will create a batch file in the directory you used, which can beaccessed by clients over the network to configure their Tivoli Storage Managerclient.

A final step in the configuration is labeling the media residing in your tape library.This is done through the Autochanger Device Labeling Wizard (see Figure 117).

Figure 117. Autochanger Device Labeling Wizard


Labeling the tapes is made easy with two functions: searching the library forvolumes and barcode readers. Using the barcode reader (if your library has one),Tivoli Storage Manager will use the tape’s barcode label as volume name.

Figure 118 shows the parameters that can be used when labeling volumes in alibrary. One parameter that needs a little attention is the element number. As saidbefore, Tivoli Storage Manager uses an alias name to specify a tape librarydevice (mtx.y.z.n or lbx.y.z.n). To represent a library with all its components,including cartridge slots, Tivoli Storage Manager uses element addresses. Eachcomponent of a tape library (or single tape device) has a unique element number.For example, the library robotics in the Magstar 3570 use element number 16. Ifyou need these element numbers, please refer to Appendix D., “TSM elementaddresses and worksheets” on page 283.

Figure 118. Media labeling parameters

After completing the media labeling, you will have successfully completed theTivoli Storage Manager configuration.

When the configuration is complete, you can start using the server. To administerthe server, you have three options:

• Tivoli Storage Manager utilities (see Figure 119)

This interface, which runs locally on the server, enables you to do most of theadministrative actions through wizards, as described above. It is probably themost easy to use for beginners.


Figure 119. Tivoli Storage Manager utilities

• Administrative Web interface (Figure 120)

Using a Web browser, you can perform all administrative operations on theserver without having local software installed on your client.

Figure 120. Administrative Web interface

• Command line administrative interface

This is the most basic interface. It provides a simple command line interface tothe server (local or remote). The advantage is that this is a very quick way to


do small operations for people who are familiar with Tivoli Storage Managercommands.

6.1.3 Configuring the IBM tapes and librariesAdding devices to Tivoli Storage Manager is made easy using the wizards in theserver utilities. First, connect all the hardware, start the system, and use theutilities to ensure that Tivoli Storage Manager recognizes the tape. Then checkthat the SCSI driver is running (and make sure you are not using the NT tapedriver), and go to the Device Information window in the server utilities (see Figure121). Here you can see if a tape device has been recognized by Tivoli StorageManager.

Figure 121. Device information

Next, click on the Device Configuration tab, which will bring up the deviceconfiguration wizard (see Figure 122). Start this wizard, and follow and performthe same operations as you did during the initial installation. After you haveconfigured the device, do not forget to add media to the library (SCSI or manual)using the media labeling section in the server utilities.


Figure 122. Device configuration window

For reference, the next section explains how to install specific tape devices usingcommands rather than the wizards described earlier. Tivoli Storage Manager hasa feature that allows you to combine a series of commands inside a batch file.This is called a macro. To execute a macro, start a command prompt, and go tothe Tivoli Storage Manager administrative client installation directory. Then, enterthe following command:

DSMADMC MACRO <macro name>

Where <macro name> is the full path and name of the macro file.

The following macros are used to set up the device. To add media and assign thedevices to a storage pool, refer to the Tivoli Storage Manager manuals.

6.1.3.1 Configuring the IBM 40/80 GB DLT tape driveThe name of the device will be something like mt4.0.0.0 (see Appendix D, “TSMelement addresses and worksheets” on page 283 for more information). To definethe 40/80 DLT tape device, we will need to define a library, a device class and adrive object inside the Tivoli Storage Manager database. This can be done usingthe following Tivoli Storage Manager command macro:

/* ---------------------------------------------------------------- *//* Use this macro to define a 40/80 GB DLT tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 device name for the tape drive (for example mt4.0.0.0) *//* %2 mountretention (in minutes) *//* ---------------------------------------------------------------- *//**/define library MANUALLIB libtype=manual device=%1/**/define devclass DLTClass devtype=DLT format=DLT40 library=manuallib -mountretention=%2 estcapacity=40G/**/define drive manuallib device=%1


The above macro file will define a library named MANUALLIB, a device classnamed DLTClass and a drive named DLTTape. To prevent double compression,we define the tape device to work without hardware compression. If hardwarecompression is necessary, the format=DLT40 in the devclass definition can bechanged to format=DLT40C. For more information on these commands, see ADSTARDistributed Storage Manager for Windows NT, Administrator’s Reference,GC35-0293-01.

6.1.3.2 Configuring the IBM 35/70 GB DLT tape driveThe name of the device will be something like mt4.0.0.0 (see Appendix D, “TSMelement addresses and worksheets” on page 283 for more information). To definethe 35/70 DLT tape device, we will need to define a library, a device class and adrive object inside the Tivoli Storage Manager database. This can be done usingthe following Tivoli Storage Manager command macro:

/* ---------------------------------------------------------------- *//* Use this macro to define a 35/70 GB DLT tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 device name for the tape drive (for example mt4.0.0.0) *//* %2 mountretention (in minutes) *//* ---------------------------------------------------------------- *//**/define library MANUALLIB libtype=manual device=%1/**/define devclass DLTClass devtype=DLT format=DLT35 library=manuallib -mountretention=%2 estcapacity=35G/**/define drive manuallib device=%1


6.1.3.3 Configuring the IBM 20/40 GB DLT tape driveTo define the 20/40 DLT tape device, we will need to define a library, a deviceclass and a drive object inside the Tivoli Storage Manager database. This mustbe done using Tivoli Storage Manager commands.

For the IBM 20/40 GB DLT tape drive, the following macro can be used:

/* ---------------------------------------------------------------- *//* Use this macro to define a 20/40 GB DLT tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 device name for the tape drive (for example mt4.0.0.0) *//* %2 mountretention (in minutes) *//* ---------------------------------------------------------------- *//**/


define library MANUALLIB libtype=manual device=%1/**/define devclass DLTClass devtype=DLT format=DLT20 library=manuallib -mountretention=%2 estcapacity=20G/**/define drive manuallib device=%1


6.1.3.4 Configuring the IBM 20/40 GB 8 mm tape driveTo define the 8 mm tape device, we will need to define a library, a device classand a drive object inside the Tivoli Storage Manager database. This can be doneusing the following Tivoli Storage Manager commands.

For the IBM 20/40 GB 8 mm tape drive, the following macro can be used:

/* ---------------------------------------------------------------- *//* Use this macro to define a Mammoth 8 mm tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 device name for the tape drive (for example mt4.0.0.0) *//* %2 mountretention (in minutes) *//* ---------------------------------------------------------------- *//**/define library MANUALLIB libtype=manual device=%1/**/define devclass 8MMClass devtype=8MM format=8900 library=manuallib -mountretention=%2 estcapacity=20G/**/define drive manuallib device=%1

The above macro file will define a library named MANUALLIB, a device classnamed 8MMClass and a drive named 8MMTape. To prevent double compression,we define the tape device to work without hardware compression. If hardwarecompression is necessary, the format=8900 in the devclass definition can bechanged to format=8900C. For more information on these commands, see ADSTARDistributed Storage Manager for Windows NT, Administrator’s Reference,GC35-0293-01.

6.1.3.5 Configuring the IBM 20/40 GB 4 mm tape driveFor the IBM 20/40 GB 4 mm tape drive, the following macro can be used:

/* ---------------------------------------------------------------- *//* Use this macro to define a DDS4 20/40 GB 4 mm tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 device name for the tape drive (for example mt4.0.0.0) *//* %2 mountretention (in minutes) */


/* ---------------------------------------------------------------- *//**/define library MANUALLIB libtype=manual device=%1/**/define devclass 4MMClass devtype=4MM format=DDS4 library=manuallib -mountretention=%2 estcapacity=20G/**/define drive manuallib device=%1

The above macro file will define a library named MANUALLIB, a device classnamed 4MMClass and a drive named 4MMTape. To prevent double compression,we define the tape device to work without hardware compression. If hardwarecompression is necessary, the format=DDS4 in the devclass definition can bechanged to format=DDS4C. For more information on these commands, see ADSTARDistributed Storage Manager for Windows NT, Administrator’s Reference,GC35-0293-01.

6.1.3.6 Configuring the IBM 12/24 GB 4 mm tape driveFor the IBM 12/24 GB 4 mm tape drive, the following macro can be used:

/* ---------------------------------------------------------------- *//* Use this macro to define a DDS3 12/24 GB 4 mm tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 device name for the tape drive (for example mt4.0.0.0) *//* %2 mountretention (in minutes) *//* ---------------------------------------------------------------- *//**/define library MANUALLIB libtype=manual device=%1/**/define devclass 4MMClass devtype=4MM format=DDS3 library=manuallib -mountretention=%2 estcapacity=12G/**/define drive manuallib device=%1

The above macro file will define a library named MANUALLIB, a device classnamed 4MMClass and a drive named 4MMTape. To prevent double compression,we define the tape device to work without hardware compression. If hardwarecompression is necessary, the format=DDS3 in the devclass definition can bechanged to format=DDS3C. For more information on these commands, see ADSTARDistributed Storage Manager for Windows NT, Administrator’s Reference,GC35-0293-01.

6.1.3.7 Configuring the IBM 3502 autoloaderThe first thing to do is check the device detector in the Tivoli Storage Managerserver utilities, to determine the device name of the IBM 3502.

The following macro will define the device:

/* ---------------------------------------------------------------- *//* Use this macro to define an IBM 3502 autoloader with one tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 devicename for library (for example lb6.0.0.0) */


/* %2 mountretention (in minutes) *//* %3 device name for the tape drive (for example mt4.0.0.0) *//* ---------------------------------------------------------------- *//**//**/define library IBM3502 libtype=SCSI device=%1/**/define devclass DLTclass devtype=DLT format=DLT35 library=IBM3502 -mountlimit=1 mountretention=%2 estcapacity=35G /**/define drive IBM3502 DLTtape device=%3 Element=16

The above macro file will define a library named IBM3502, a device class namedDLTClass and a drive named DLTTape. To prevent double compression, wedefine the tape device to work without hardware compression. If hardwarecompression is necessary, the format=DLT35 in the devclass definition can bechanged to format=DLT35C. For more information on these commands, see ADSTARDistributed Storage Manager for Windows NT, Administrator’s Reference,GC35-0293-01.

See Appendix D, “TSM element addresses and worksheets” on page 283 formore information about the element number in the define drive command.

6.1.3.8 Configuring the IBM 3447 libraryThe first thing to do is check the device detector in the Tivoli Storage Managerserver utilities, to determine the device name of the IBM 3447.


/* ---------------------------------------------------------------- *//* Use this macro to define an IBM 3447 library with one tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 devicename for library (for example lb6.0.0.0) *//* %2 mountretention (in minutes) *//* %3 device name for the tape drive (for example mt4.0.0.0) *//* ---------------------------------------------------------------- *//**//**/define library IBM3447 libtype=SCSI device=%1/**/define devclass DLTclass devtype=DLT format=DLT35 library=IBM3447 -mountlimit=1 mountretention=%2 estcapacity=35G /* Change mountlimit to the number of drives installed *//**/define drive IBM3447 DLTtape device=%3 Element=116/*use the following line if a second tape drive is installed in the library*//* define drive IBM3447 DLTtape device=%3 Element=117 */

The above macro file will define a library named IBM3447, a device class namedDLTClass and a drive named DLTTape. To prevent double compression, wedefine the tape device to work without hardware compression. If hardwarecompression is necessary, the format=DLT35 in the devclass definition can bechanged to format=DLT35C. For more information on these commands, see ADSTAR


Distributed Storage Manager for Windows NT, Administrator’s Reference,GC35-0293-01.


6.1.3.9 Configuring the IBM 3449 LibraryCheck the device detector in the Tivoli Storage Manager server utilities todetermine the device name of the IBM 3449.


/* ---------------------------------------------------------------- *//* Use this macro to define an IBM 3449 library with one tape drive *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 devicename for library (for example lb6.0.0.0) *//* %2 mountretention (in minutes) *//* %3 device name for the tape drive (for example mt4.0.0.0) *//* ---------------------------------------------------------------- *//**//**/define library IBM3449 libtype=SCSI device=%1/**/define devclass 8MMClass devtype=8MM format=8900 library=IBM3449 -mountlimit=1 mountretention=%2 estcapacity=20G /* Change mountlimit to the number of drives installed *//**/define drive IBM3449 8MMTape device=%3 Element=23/* use the following line if you have two tape drives installed*//* define drive IBM3449 8MMTape device=%3 Element=24 */

The above macro file will define a library named IBM3449, a device class named8MMClass and a drive named 8MMTape. To prevent double compression, wedefine the tape device to work without hardware compression. If hardwarecompression is necessary, the format=8900 in the devclass definition can bechanged to format=8900C. For more information on these commands, see ADSTARDistributed Storage Manager for Windows NT, Administrator’s Reference,GC35-0293-01.


6.1.3.10 Configuring the IBM 3570 Magstar MP LibraryCheck the device detector in the Tivoli Storage Manager server utilities todetermine the device name.

Let’s take an example of a 3570 model with two drives and the changermechanism:

• Tape Peripheral, mt4.0.0.0


• Medium Changer Peripheral, lb6.0.0.0



/* ---------------------------------------------------------------- *//* Use this macro to define an IBM 3570 with two tape drives *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 devicename for library (for example lb6.0.0.0) *//* %2 mountretention (in minutes) *//* %3 device name for the tape drive1(for example mt4.0.0.0) *//* %3 device name for the tape drive2(for example mt5.0.0.0) *//* ---------------------------------------------------------------- *//**//**/define library IBM3570 libtype=SCSI device=%1/**/define devclass 3570 devtype=3570 format=drive library=IBM3570 -mountlimit=2 mountretention=%2 /**/define drive IBM3570T1 3570 device=%3 Element=16define drive IBM3570T2 3570 device=%3 Element=17

The above macro file will define a library named IBM3570, a device class named3570 and two drives named IBM3570T1 and IBM3570T2. For more informationon these commands, see ADSTAR Distributed Storage Manager for Windows NT,Administrator’s Reference”, GC35-0293-01.


6.1.3.11 Configuring the IBM 3575 Magstar MP LibraryCheck the Device Detector in the Tivoli Storage Manager server utilities todetermine the device name.

Let’s take an example of a 3575 Model L06 with two drives and the changermechanism:



• Medium Changer Peripheral, lb6.0.0.0


/* ---------------------------------------------------------------- *//* Use this macro to define an IBM 3575 l06 with two tape drives *//* ---------------------------------------------------------------- *//* parameters used : *//* ----------------- *//* %1 devicename for library (for example lb6.0.0.0) *//* %2 mountretention (in minutes) *//* %3 device name for the tape drive1(for example mt4.0.0.0) *//* %3 device name for the tape drive2(for example mt5.0.0.0) *//* ---------------------------------------------------------------- *//**//**/define library IBM3575 libtype=SCSI device=%1


/**/define devclass 3570 devtype=3570 format=drive library=IBM3575 -mountlimit=2 mountretention=%2 /**/define drive IBM3575T1 3570 device=%3 Element=16define drive IBM3575T2 3570 device=%3 Element=17

The above macro file will define a library named IBM3575, a device class named3570 and two drives named IBM3575T1 and IBM3575T2. For more informationon these commands, see ADSTAR Distributed Storage Manager for Windows NT,Administrator’s Reference”, GC35-0293-01.


6.2 Tivoli Storage Manager Server V2.1 for OS/2

This section explains the installation and configuration of Tivoli Storage ManagerVersion 2 Release 1 for OS/2. For more information about Tivoli StorageManager, please refer to 5.1, “Tivoli Storage Manager” on page 124.

Tivoli Storage Manager for OS/2 has the following system requirements:

• OS/2 Warp or higher with REXX• 70 MB of free disk space• 12 MB of memory

To start installation of the server, perform the following procedure:

1. Start the installation program (\SERVER\INSTALL.EXE) from the ADSMCD-ROM.

2. Click Continue after reading this instruction screen.

3. On the next screen, Figure 123, you will be asked to update the CONFIG.SYS.Click OK.

The current version of TSM for OS/2 is Version 2 Release 1. This version hassome differences with Version 3, but the general design is the same. Thefollowing list shows new features of Version 3 not available in this OS/2 version.

Additionally, the program itself still refers to the old ADSM name.

The new functions of TSM Version 3 are:

• Event logging and monitoring• SQL queries of the TSM database• Storing data on another TSM server• Server file aggregation• Device support• Administrative client web interface• Point-in-time restoration of client files• Changing server options without stopping the server

Versions


Figure 123. Update CONFIG.SYS

If you decide to not automate the CONFIG.SYS update, the installationautomatically places a file called CONFIG.ADD in the root directory on thedrive from which OS/2 was booted.

4. Mark your selections for installation from the following screen:

Figure 124. Installation screen

The example shown here shows selections for an initial ADSM server andADSM client installation.

Here is a brief description of the installation selections:

• ADSM Server First Time Installation

Use this selection if you do not have a Version 1 ADSM server installed.

• Install/Update ADSM Server from Version 1

When you choose this component, the installation program attempts toperform an upgrade of your Version 1 server database.

• ADSM Client

This selection installs the ADSM administrative and backup-archive clients.

• Lotus Notes Backup Agent

The ADSM Client selection must be installed or selected to install the LotusNotes Backup Agent.


• ADSM Tape Device Driver

This component installs the ADSM tape device drivers. Select thiscomponent when you have a SCSI card and a tape device that is supportedby ADSM attached to your machine.

• Autochanger Device Driver

This component installs the autochanger device driver. This componentrequires that the tape device driver component is installed or selected forinstallation.

5. Click Disk space for the bytes available for drives and select the directory forinstallation. In this example, we are using C:\ADSMV2 for the server files andC:\ADSM for the client files.

Click OK. This returns you to the installation screen.

6. Click Install. After this, the installation progress screen appears. After the fileshave been copied, the installation utility will start command files thatautomatically create default definitions.

7. Exit from the installation screens when the installation completes.

8. Reboot your system to have your updated CONFIG.SYS file changes takeeffect. If you chose not to have the installation program update theCONFIG.SYS file for you, make the changes now and reboot your system.

After rebooting the system, install the latest fix pack level of the ADSM for OS/2server code. At the time of publication, the latest level was L0.16, which can beobtained by installing PTF IP21553 from the following Web page:


Two new folders (see Figure 125 and Figure 126) appear on your desktop for thisexample, one folder labeled ADSM for OS/2 Server V2R1, and another folderlabeled ADSM Client. Double-click the icons to view the folders’ contents. Most ofthe icons are self-explanatory (for example, double-click ADSM Server to start theserver).

After installation, your directory choice cannot be changed if you return to addan additional component.

Note

The ADSM server for OS/2 can also be started by executing RUNSERV.CMD inthe ADSM server directory. This opens a PM REXX interface with the server.The advantage of this is that you have a long screen buffer to see servermessages. The disadvantage is that by pressing F3, you stop the ADSMserver, without closing the database and log files. This could cause corruptionproblems.

Starting ADSM



Figure 125. Server folder

Figure 126. Client folder

The installation program performed the following operations:

• Installed the necessary files for server operation.• Registered one client node named CLIENT with a password of CLIENT.• Registered one administrative node named ADMIN with a password of

ADMIN.• Created and defined a 15 MB backup storage pool called BACKUP1.• Created and defined a 6 MB archive storage pool called ARCHIVE1.• Created a 13 MB recovery log called LOG.DSM.• Created a 5 MB database called DB1.DSM.• Created a dsmserv.dsk file that contains database and recovery log

information in your \ADSMV2 directory.

6.2.1 Server configurationAt this point you will have installed, set up, and started the ADSM server, and oneor more administrative clients and backup-archive clients. This section describescustomizing ADSM by doing the following:

• Registering your ADSM licenses• Adding tape drives to your ADSM system• Setting up storage pools

The configuration described here still does not take advantage of all the optionsavailable to you as an ADSM administrator. For more information on this, pleaserefer to the ADSM manuals.

Here are some ADSM terms that you will find in this section:

The Tivoli Storage Manager manuals can be found in downloadable PDFformat at the following Web page:

http://www.tivoli.com/support/storage_mgr/pubs/admanual.htm

NoteManuals in PDF Format

http://www.tivoli.com/support/storage_mgr/pubs/admanual.htm


Collocation: A process by which the server attempts to keep all filesbelonging to a client on a minimal number of tape volumes.

Device class: A group of storage devices of the same type, for example, diskor cartridge.

Expiration: The process by which files in server storage are marked fordeletion because their retention period has passed.

Library: A collection of one or more drives with similar mountmechanisms. For ADSM to use it, a device must be assignedto a library. There are two types of libraries:

1. Manual volumes that are loaded by a human operator.

2. Automated volumes that are loaded by a roboticautochanger device.

Validation: The process of ensuring that the active policy set contains adefault management class, and reporting on copy groupdefinition errors.

The ADSM server must be running to perform the tasks described here. Start theserver if it is not running by typing DSMSERV in an OS/2 command window or bydouble clicking on the ADSM Server icon.

The first step in configuring the ADSM server is registering your licenses. Thiscan be done using the REGISTER LICENSE command, with the file name of thelicense file as parameter.

The following license files exist:

• 1CLIENT.LIC

Provides a one-client license.

• 5CLIENT.LIC

Provides a five-client license.

• 10CLIENT.LIC


• 50CLIENT.LIC


• DESKTOP.LIC

Provides a license for using desktop clients (OS/2, Windows, Apple, NovellNetWare and DOS).

• UNIX.LIC

Provides a license for UNIX clients.

• NETWORK.LIC

Provides a license for network connections. This is needed when remoteclients are going to connect to your server.

• OEMVS.LIC

License for OpenEdition MVS client.


• SPACEMAN.LIC

Needed for HSM clients.

• DEVMOD1.LIC through DEVMOD2.LIC

Device support modules.

Initial setup in our environment requires ten clients and network connections. Todo this, execute the following commands:

REGISTER LICENSE FILE(10CLIENT.LIC)REGISTER LICENSE FILE(DESKTOP.LIC)REGISTER LICENSE FILE(NETWORK.LIC)

After registering the licenses, we will start by defining our tape device. Before youcan use tape with ADSM, you must do the following:

1. Determine the device names.2. Define the following: a library for the drives, the drives, a device class, and a

storage pool associated with the device class.3. Include the storage pool in your hierarchy.

The ADSM utilities allow you to perform these tasks using the administrativecommand line or the administrative GUI.

Here are some concepts that can help you set up your tape environment:

• Storage pool migration

To prevent disk storage pools from becoming filled with client data, you canspecify that client data be automatically migrated to the tape storage pool. Adisk’s high migration threshold (default value: 90%) determines when data ismigrated. The low migration threshold (default value: 70%) determines whenmigration stops. Thus data migration from the default backup disk storage poolbegins when the pool is 90% full and continues until it is at 70% full or less.

Another default is to cache data (leave the data in the storage pool) even afterthe data has been migrated. Cached data stays on disk for quick access untilthe space is needed for new data. The current status for this cache parameteris to turn it off.

• Mount limit

Mount limit (the number of drives available in a device class) has a defaultvalue of 1. The mount limit should be equal to the number of drives of thesame type in that library.

• Scratch volumes

A scratch volume is a volume that is available for ADSM use. The volume islabeled, is either blank or contains no valid data, and is not defined to ADSM.You can specify the number of scratch volumes that ADSM can request for thispool (MAXSCRATCH parameter in the command or the Maximum scratchvolumes field in the GUI). If you do not specify a value, no scratch volumescan be requested, and you must define each volume to be used.

• Collocation

Collocation is turned off by default. Once clients begin storing data in astorage pool with collocation off, you cannot easily change the data in thestorage pool so that it is collocated.


To start the tape device installation, ensure that your devices are physicallyattached to your system according to the manufacturer’s instructions. Two ADSMdevice drivers are installed on your system as part of the server installation andmust be used for all devices:

ADSMTAPE.SYS: For tape devicesADSMAUTO.SYS: For automatic library devices

The drivers are started when you start OS/2. The devices must be powered on forOS/2 to recognize them.

Determine the device names of your tape drives and autochangers. ADSM devicenames must be in the format TAPEyz$ (for tape drives) or AUTOyz$ (forautomated libraries) where, y is the number of the SCSI adapter and z thenumber of the SCSI ID. For example, tape01$ represents the tape drive with SCSIadapter 0 at SCSI ID 1.

To check the attached devices, start an OS/2 command window, and runADSMSDI.EXE located in the ADSMV2 directory. For each powered-on device,you can see a number for the SCSI adapter and a number for the SCSI ID.

To define the tape device to the ADSM database, the following commands arenecessary:

1. DEFINE LIBRARY2. DEFINE DRIVE

To prevent conflicts, stop the ADSM server by issuing a HALT command.

Note

ADSTAR Distributed Storage Manager - SCSI Device Information (ADSMSDI)Version 2, Release 0, Level 0.2/2.3

Licensed Materials - Property of IBM

5622-112 (C) Copyright IBM Corporation 1994, 1995, 1996, 1997. All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.

Building device list...

** 2 Fixed DASD devices Adap Id Lun VendorID Product ID Rev. ADSM support? ---- -- --- -------- ---------------- ---- ---------------- Device detected, but information unavailable. ?? Note 1 Device detected, but information unavailable. ?? Note 1

** 1 Removable Sequential device Adap Id Lun VendorID Product ID Rev. ADSM support? ---- -- --- -------- ---------------- ---- ---------------- 1 5 0 EXABYTE EXB-89008E000112 V37f YES, as TAPE15$

Note 1: device is already reserved by another driver or application.


3. DEFINE DEVCLASS4. DEFINE STGPOOL

We will define a manual library and associate a drive with it. In this example, wewill be making use of the IBM 20/40 GB 8 mm tape. For the other supporteddevices (see 5.1.4, “Supported devices” on page 134), you can follow the sameprocedure. The only difference will be the DEFINE DEVCLASS command. For the exactsyntax, refer to 6.1.3.6, “Configuring the IBM 12/24 GB 4 mm tape drive” on page190 through 6.1.3.5, “Configuring the IBM 20/40 GB 4 mm tape drive” on page189. We will name the library MANUALLIB. The drive, named 8mm_Tape, isattached to SCSI adapter 1 using SCSI ID 5 (Tape15$). After defining the library,we will add a deviceclass to the drives in this library. Finally, the deviceclass mustbe assigned to a logical storage pool. The following commands perform thesetasks:

define library manuallib libtype=manualdefine drive manuallib 8mm_Tape device=tape15$define devclass tapeclass devtype=8mm format=8900 library=manuallib define stgpool tapepool tapeclass

You can also use the GUI administrator to achieve the same goal (see Figure127):

Figure 127. ADSM for OS/2 GUI administrator

1. Double click Storage Pools.2. Click Edit from the menu bar.3. Click Add Primary Storage Pool from the pull-down menu.4. In the Storage pool name field, enter TAPEPOOL (see Figure 128).


Figure 128. Defining a storage pool

5. Click the Device Class tab and enter the name of the device class you want touse for this storage pool. In our case, TAPECLASS (see Figure 129).

Figure 129. Defining a storage pool - assignment of the device class

6. Click the Add push button.

Before continuing, you can view the results of your definitions. If necessary, youcan update these definitions by using update commands.

• To query the libraries: QUERY LIBRARY• To query the drives: QUERY DRIVE• To query the device classes: QUERY DEVCLASS FORMAT=DETAILED• To query the storage pools: QUERY STGPOOL

After the tape devices are defined, you can start defining tape volumes. All tapevolumes must have standard labels before ADSM can use them. You can use


tapes as scratch volumes, up to the number of scratch volumes specified for thestorage pool. Using scratch volumes allows ADSM to acquire volumes as needed.

You can also use private volumes in a storage pool. You must define all privatevolumes to ADSM, assigning each to a specific storage pool. However, if astorage pool contains only private volumes and runs out of them, storageoperations for that pool stop until more volumes are defined.

If you are using only one tape drive, consider labeling several tapes at this time.You cannot label tapes while the server is writing to or reading from the drive.

If the tape volumes do not already have standard labels, label them. From anOS/2 command prompt, go to the ADSM server directory (for example,D:\ADSMV2):

1. Enter the following command: dsmlabel -drive=tape15$ -overwrite2. When prompted:

• Insert the new volume into the tape drive.• Type a 1 to 6 character volume name (for example, T00001).• Press Enter.

The above actions put a physical header on each tape, allowing it to berecognized. You still need to define the volume objects for these physical tapes inthe ADSM database. Define any volumes that are to be used as private volumes.To define the volume you just named T00001, you can issue the followingcommand:

define volume tapepool T00001

You can also do this using the GUI administrator (see Figure 127 on page 201):

1. Expand the Storage Pools section by clicking the plus sign.2. Double click Storage Pool Volumes.3. Click Edit from the menu bar.4. Click Add from the pull-down menu.5. Enter the following:

• Storage pool name TAPEPOOL (from the drop-down list)• Volume name DSM001

6. Click the Add push button.

Figure 130. Adding a volume


Now that ADSM can use your tape drives, you can update your disk storage poolsso that client data can be migrated to tape. The following commands changeBACKUPPOOL so that data migrates to AUTOPOOL, and changeARCHIVEPOOL so that data migrates to TAPEPOOL.

update stgpool backuppool nextstgpool=autopoolupdate stgpool archivepool nextstgpool=tapepool

You can also do this using the GUI administrator (see Figure 127 on page 201):

1. Double click Storage Pools.2. Click BACKUPPOOL.3. Click Selected.4. Click Open as properties from the pull-down menu.5. Click the Migration tab, go to page 2, and for Next storagepool, do the

following:• Deselect (by clicking) the None check box.• Click AUTOPOOL from the Next pool drop-down list.

6. Click the Apply push button.

Figure 131. Defining storage pool migration

This completes the setup of the ADSM Server for OS/2, so that it makes use of atape device as storage media. Next, you will need to define your backup policy.This consists of defining clients and defining how they will use your storagedevices. Refer to the ADSM manuals for information about this.

6.3 Tivoli Data Protection for Workgroups

This section describes the installation, configuration and main features of TivoliData Protection for Workgroups Version 1.1.0.1. To get this version, install thebase product, and then apply the corrective service IP21830. This PTF isavailable at the following location:

ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance/tivoli-data-protection/v1r1/NT/LATEST/IP21830.ZIP

System requirements for this product are as follows:

ftp://index.storsys.ibm.com/tivoli-storage-management/maintenance/tivoli-data-protection/v1r1/NT/LATEST/IP21830.ZIP


• Windows NT 4 service pack 4 (or higher)• TCP/IP or IPX/SPX installed (if you’re using a stand-alone system, use the

internal loopback address 127.0.0.1 for TCP/IP)• A supported tape device

To install Tivoli Data Protection for Workgroups, insert the product CD in yourCD-ROM drive. If the autorun option is not enabled, start Setup.exe in the rootdirectory of your CD. This will bring up the welcome screen and an informationwindow, where you will have the chance to read the Readme file of the product.Next, you will need to set the installation path. By default, Tivoli Data Protectionfor Workgroups installs in the C:\Program Files\Tivoli\TDPW directory (see Figure132). However, if Tivoli Storage Manager server is already installed, it will installitself in that directory structure.

Figure 132. Tivoli Data Protection for Workgroups installation directory

When the installation continues, it will propose a program group, and an overviewof components that will be installed. Next, all necessary files will be copied. If youhave a single tape device, make sure that you have it configured using theWindows NT Tape Drive program before starting the installation. The deviceshould be running, with the correct driver loaded. If this is not the case, TivoliData Protection for Workgroups will detect this and propose to install the driverduring the installation.

If you already have the Tivoli Data Protection server installed, Tivoli DataProtection for Workgroups will use the ADSMSCSI.SYS driver, which is thedevice driver Tivoli Storage Manager uses to access tape devices (see 6.1.2,“Configuration” on page 164). If you intend to use an autoloader or tape library,you must use this device driver instead of the Windows NT driver.

After installation, reboot your system. This will allow the services and devicedrivers installed to be started. Two services will be installed: the Replica Agentservice and the Replica Server service.


6.3.1 Configuration and useAfter reboot, the TDP host, which is represented by the above service, isautomatically started. To perform any operations, start the Tivoli Data Protectionfor Workgroups program.

In this case, the program is using the Windows NT device driver, and noadditional device configuration is necessary. The user interface has four mainwindows:

• Replicate• Utilities• Recover• Mount Tape

There is also a status window which allows you to monitor activity.

The first interface, Replicate, allows you to create replicas, or backups, ofvolumes. You can only create these at the volume level. The partition data volumeallows you to back up necessary information to re-create the disk’s partitioningafter a disaster.

Figure 133. Tivoli Data Protection for Workgroups replication interface

However, before making a replica, you must label a tape volume, so that it can beused by Tivoli Data Protection for Workgroups. In order to do this, open theUtilities window, and click the Device tab (see Figure 134). Using this interface,you can interact with your tape device, in order to perform operations on the tapevolumes. Once you’ve labeled a tape, you can then create a replica.


Figure 134. Tivoli Data Protection for Workgroups utilities

After a replica has been made, you can recover logical disk volumes (orpartitions) or files using this replica. This recovery can be done at three levels.

The first level of recovery is disaster recovery. Here, you can recover the entiresystem using the replica, and the disaster recovery diskettes created by theproduct. To create these diskettes, use the Utilities window, and select theDisaster Recovery tab. You will also need a copy of the three Windows NT setupdiskettes, and an extra blank diskette. The product will modify the setup diskettes,so it is advisable to use copies of the originals.

To proceed with the recovery, use the diskettes to boot your server. It will proposea list of recognized tape devices, and then check which tape volume is inserted inthe tape device you selected. You can either use that volume, or insert a new tapeand let the recovery program recheck the volume name.

With the correct volume in the tape device, you can start the recovery. All filesfrom the tape will be copied to your hard disk.

If you use an autoloader, the recovery program is not able to mount tapesautomatically. Mount the tapes manually through the operator panel of yourlibrary.

Note


Figure 135. Tivoli Data Protection for Workgroups create recovery disks

The second level of recovery is at the volume level. To do this, go to the Recoverwindow (see Figure 136), select the disk volume you wish to recover, and thetape volume on which the replica is located.

Figure 136. Tivoli Data Protection for Workgroups recovery


The third level of recovery is at the file level. This is implemented by mounting adisk partition from a tape volume. The advantage of this way of working is thatafter the mount, the data on tape is considered as direct access. This means youcan copy files from tape to disk using the Windows NT Explorer, or with a simplecopy command from the command prompt. To mount a tape, use the Mount Tapewindow (see Figure 137). You can assign a drive letter and a share name to thetape you are mounting. Click the Mount Tape button to perform the operation.The status window will show you the status of the process, and give you theability to dismount the tape.

Figure 137. Tivoli Data Protection for Workgroups tape mount

Figure 138 shows the Windows NT Explorer with a tape mounted:


Figure 138. Tivoli Data Protection for Workgroups interaction with Windows NT Explorer

6.3.2 Configuring IBM tape devicesTivoli Data Protection for Workgroups uses the Windows NT device driver tocommunicate with the tape hardware, but only for single tape devices. Forautoloaders, the Tivoli Storage Manager device driver is used.

When using autoloaders, first ensure that the autoloader support is active, byrunning the TDP device manager. When using Windows NT device drivers inconjunction with the ADSMSCSI.SYS driver, you will encounter conflicts. To solvethis, disable all the Windows NT drivers for both the loaders and the tape drives.Next, check the library’s setup, and make sure that it is working in random mode.

The use of an autoloader in this configuration might be beneficial if this is aremote machine, so that you can schedule backups regularly, without having tomount tapes manually. To use the autoloader, you must first label all tapes in thelibrary. This needs to be done through the device utilities. If you are schedulingyour replication jobs, however, the autoloader will mount tapes, and label themwhen necessary.

One concern with autoloaders however is that they will not automatically mounttapes when going through a disaster recovery. In that case, you must manuallymount tapes in the tape drives.

6.4 Legato NetWorker

This section describes the installation of Legato’s NetWorker server for WindowsNT. The system requirements are as follows:

• Windows NT 4.0 Service Pack 3 or higher• TCP/IP installed and configured• 64 MB of memory• 44 MB disk storage for software• 13 MB of documentation


In addition to the above resources, NetWorker will also require space to place itsindexes, which store information about data that has been backed up. As a rule ofthumb, Legato proposes 5% of total backup data. So, if your backup server isstoring 100 GB of data, 5 GB of index space should be available.

The installation of NetWorker starts automatically after inserting the installationCD. The initial screen will be based on a Web page, with a link to start theinstallation program. If your standard Web browser is Netscape, you will not beable to launch this installation program, since Netscape does not allow therunning of executable files directly. To solve this, exit the browser, and start theSetup.exe program in the \I386\netwrkr directory of the CD.

When the installation program starts, you will need to choose the operation youwant to perform (see Figure 139). If you are installing the server, select theServer and Client option.

Figure 139. NetWorker setup options

Next, you will need to specify the location where the product will be installed. Thedefault location is c:\win32app\nsr.


Figure 140. NetWorker installation location

The next window will allow you to define other NetWorker servers that areauthorized to back up the server you are installing, and the names of hosts thatcan perform a remote recovery to the machine you are working on.

Figure 141. Specifying authorized NetWorker servers

Next, the installation program copies necessary files, installs and starts theservices needed to run NetWorker. You do not need to restart your machine inorder to use it.

6.4.1 ConfigurationAfter the installation completes, you can start the NetWorker administrator usingthe program icon in the NetWorker program group. This administration programwill connect to the server, which is started as a service.


When the administrator starts, you can either go through the setup wizard, or godirectly to the administrative interface. If you go to the administrative interface(see Figure 142), you will be able to start configuring your backup devices.

Figure 142. NetWorker administrator interface

For single tape drives, NetWorker can use devices that are recognized byWindows NT. By default, a 4 mm device is installed, defined as \\.\Tape0. If you donot want to use that device, delete it or modify it. To delete a device, click theDevices button in the top right-hand screen. This will bring up the devicemanagement window, as shown in Figure 143.

Figure 143. NetWorker tape device management

To delete a device, right click the icon representing the tape, and select Deletefrom the pop-up menu. To add a device, right click the Devices icon, and selectCreate. This will bring up the panel shown in Figure 144:


Figure 144. Creating a device

The device name used by NetWorker is the name by which the tape drive isdefined in the Windows NT registry, and is of the form \\.\Tapen. To find out thedevice name for the tape you are installing, go to the tape device application inthe Windows NT control panel, select the tape device you want to install, and thenselect Properties. The device map value represents the name of the tape device.You can also use NetWorker commands, located in the /win32app/nsr/bindirectory. The command that displays the tape devices, is tapes. The output of thiscommand is shown below.

Besides setting the device name, you can also specify the media type.

After defining the tape device, right click on the device icon in the Administrationinterface, and select Operations. The Device Operations panel (Figure 145)allows you to label media.

Figure 145. Device Operations dialog

To configure autochangers, go through the above steps, defining each drive in thelibrary. After you have done this, an autochanger device must be added to theNetWorker server. This cannot be done using the GUI, but only by usingcommands. The commands that will be used are changers and autoloader. The firstcommand will show you the autochangers connected to your machine, while thesecond one will actually define the library to NetWorker.

[email protected]:\\.\Tape0 is <QUANTUM DLT7000 1837>


In the example below, we have two tape libraries: the IBM 3570 Magstar, with twodrivers, and the IBM 3502-R14 DLT tape library, with one device. First, ensurethat Windows NT recognizes the tape devices. For the Magstar and 3570 tapedrives, you will need to add a device driver. This driver can be found at thefollowing FTP address:

ftp://index.storsys.ibm.com/devdrvr/WinNT/IBMmag.1.1.5.3.exebin

When you install this driver, it will also install the Magstar changer device driver.This driver conflicts with the autoloader software of NetWorker, so you will needto go into the Devices application in the Windows NT control panel and disablethe above driver.

The changers command shows the attached recognized libraries:

Next, use the autochanger command to define the autoloaders. This command willgive you the following output and choices:

The values shown in brackets are the proposed defaults, and should be used assuch.

You can now use and further configure your libraries, using the administrativeGUI (see Figure 142 on page 213). Select the Autochanger option, which willshow the installed autochangers, as in Figure 146:

[email protected]:Vendor <IBM>, Product <03570B02>, Revision <4234>[email protected]:Vendor <ATL>, Product <L500 6320000>, Revision <001E>

1) Install a SmartMedia Jukebox.2) Install an Autodetected SCSI Jukebox.3) Install an SJI Jukebox.4) Install an STL Silo.

What kind of Jukebox are you installing? [1] 2These are the SCSI Jukeboxes currently attached to your system: 1) [email protected]: IBM 3570 2) [email protected]: Standard SCSI Jukebox, Vendor <ATL>, Product <L500 6320000> 3) [email protected]: IBM 3570Which one do you want to install? 1Installing an 'IBM 3570' jukebox.Name you would like to assign to the jukebox device? MagstarPathname of the control port for the jukebox device? [[email protected]]Enter pathname of media drive 1: ? [\\.\Tape2]Enter pathname of media drive 2: ? [\\.\Tape3]Your jukebox does not report that it has a bar code reader, but it doesreport that it can handle volume tags. Some jukeboxes that have barcodereaders report this way. If your jukebox has a barcode reader,do you want bar code reader support enabled? (yes/no) noJukebox has been added successfully

ftp://index.storsys.ibm.com/devdrvr/WinNT/IBMmag.1.1.5.3.exebin


Figure 146. Autochanger devices

By right clicking on the Autochangers icon, you can select Operations from thepop-up menu. This window lets you perform most operations necessary for tapelibraries. The Label function allows you to label volumes, giving a range of slotsto check (see Figure 147). The Mount function lets you mount specific volumes.You can also mount volumes by dragging the tape icons in the lower left-handwindow to the tape devices on the right. If your library has a dedicatedinput/output slot, you can use the Deposit and Withdraw functions to add tapevolumes.

Figure 147. Autochanger operations

Whenever you remove and reinsert media, NetWorker will need the label of thetape volume you inserted. To do this, use the Inventory function, which will giveyou the ability to check labels of volumes in a certain slot or range of slots (seeFigure 148).


Figure 148. Autochanger media labeling

6.5 Computer Associates ARCserveIT for Windows NT

Installing Computer Associates ARCserveIT is simply a matter of following theprompts displayed by the installation program. This section describes the mainsteps required to install ARCserveIT Version 6.61 on an IBM server runningWindows NT 4.0 Server.

6.5.1 Preparing to install ARCserveITBefore beginning the installation of Computer Associates ARCserve Version 6.6xon a Windows NT server verify that your system meets the following minimumrequirements:

• Hardware

• Processor type - Pentium or higher• SCSI adapter supported by ARCserve and Windows NT• RAM - 32 MB minimum• Disk space - 50 MB of free space• CD-ROM drive if installing from product CD

• Software

• Windows NT 3.51 or higher

6.5.2 Installing ARCserveITBegin the installation of Computer Associates ARCserveIT by inserting theproduct CD into the CD-ROM drive and running the Setup program.

The Product Explorer screen (see Figure 149 on page 218) allows you to selectthe version of ARCServeIT that you will install.


Figure 149. ARCserveIT Product Explorer

After selecting the product and type of installation you want, a welcome screenand a license agreement are presented. Next, you can select the type ofinstallation you want.

The screen will display two installation options:

Complete installation This installs all ARCserve components (Server,Manager, and options on a single machine).

Custom setup This installs one or more components on a singlemachine.

From the Welcome screen, follow the typical installation steps, entering theappropriate information until the completion message appears on your screen.

Click Next.

Enter the company and user information, then click Next to continue. Figure 150appears.


Figure 150. Select home directories for ARCserveIT and Alert

In Figure 150, there are two directories that contain ARCserveIT files. The homedirectory holds most of the main files and the Alert directory holds the specialinformation used for the Alert function of the product. The user can accept thedefault values or enter a different path as desired. Do not install the ARCserveITfiles or the Alert files on a network drive or in the root directory.

Click Next to continue and Figure 151 appears.

Figure 151. Select the database to be used

The user can select the Standard Database supplied by ARCserve as a default orAlternate Database.


The alternate database must be ODBC compliant and be currently installed onyour system. Two reasons for choosing a database other than the ARCservedatabase are scalability and customized report writing.

Click the Next button after selecting the database and Figure 153 appears.

Figure 152. Installation options

After copying the product files, ARCserveIT requires a system account, which willbe used to run the Windows NT services related to the product.

Figure 153. Enter an administrator ID and password

Enter the user name and password that will be used to administer ARCserveIT.The user name and password will automatically be added to the NT User Account


database. The user name is also added to the Administrators group and theBackup Operators group.

The installation program will then display a completion screen to indicate thesuccessful completion of this installation.

6.5.3 Configuring ARCserveIT on Windows NT ServerTo configure ARCserveIT on Windows NT Server open the ARCserveITAdministrator window by double clicking ARCserveIT Server Admin. Figure 154appears.

Figure 154. ARCserve Server Admin panel

From the Server Admin panel, click Admin → Configuration to display theconfiguration panel. Figure 155 appears.


Figure 155. Job Engine configuration panel

Enter the desired values for your installation. For more information on the optionsavailable from this window, see the ARCserveIT manual.

Click the Tape Engine tab to continue the configuration. Figure 156 appears.

Figure 156. Tape Engine configuration panel

Enter the appropriate values for your installation on the Tape Engine configurationpanel. For more information on the options available from this window, see theARCserveIT manual.


Click the Database Engine tab to continue the configuration process. Figure 157appears.

Figure 157. Database Engine configuration panel

Enter the Database Engine configuration parameters and continue to the Alertconfiguration panel. Figure 158 appears.

Figure 158. Alert Configuration Panel

Enter any required alert event information. For more information on the optionsavailable from this window, see the ARCserveIT manual.


Click OK to complete the installation.

6.6 Computer Associates ARCserve Version 6.1 for NetWare

This section will describe the steps involved when installing and configuringARCserve Version 6.1 for NetWare. We go through the installation and thenconfigure the backup server. For more information on ARCserveIT, refer to 5.6,“Computer Associates ARCserveIT for NetWare” on page 147.

6.6.1 InstallationARCserve for NetWare has the following system requirements for the server:

• Novell NetWare 3.1x or 4.x• 16 MB of RAM in addition to that required by the operating system and other

application requirements• 24 MB of hard disk space

The installation program for ARCserve must be run from a Windows workstation,connected to the NetWare server. Since the installation program will extend theNDS schemes, you must have supervisor rights to the root object of your NDS. Inour setup, the workstation is running Windows NT 4.0 Workstation with NTService Pack 3. Besides installing the backup server, it will also install theARCserve manager. However, the files for the manager are not copied locally, butreside on the server.

To start installation, run SETUP.EXE from the DISK1 subdirectory (on yourCD-ROM or on the hard disk of your code server).

After installation of the base product, you should install Service Pack 2 forARCserve Version 6.1. The patch is available from Cheyenne’s technicalsupport home page:

http://www.cheyenne.com/CheyTech/Download/patches/techptch.html

Besides fixing problems, it provides an ARCserve manager that is compatiblewith Windows NT.

ARCserve Service Pack 2


Figure 159. ARCserve installation welcome screen

To advance, click the Next button. In the next dialog (Figure 160) you will have toselect the media you are using for the installation: CD-ROM, diskettes or harddisk (code server).

Figure 160. ARCserve installation source

Click Next and Figure 161 appears.

This dialog allows you to choose between Complete or Custom installation. If thisis a first time install, you should select the Complete option. Selecting theCustom option lets you install separate components or upgrade your license.


Figure 161. ARCserve installation type

We selected Complete. Click Next and Figure 162 appears.

Now you specify the server on which you are going to install ARCserve. Theinstallation program prompts you with all available NetWare servers. Highlight theone you want to install by clicking on it and then click the Add button.

Figure 162. ARCserve installation server selection

Click Next to proceed and Figure 163 appears.

Next you define the installation path. By default, ARCserve proposesSYS:ARCSERVE.6.


Figure 163. ARCserve installation path


One of the features of ARCserve is the integration of Cheyenne’s InoculanAntiVirus product. You can install this feature (see Figure 164) that will scan filesfor viruses as they are backed up. If you do not have any other AntiVirus productrunning, this would be a good option to protect your backups from viruses.

Figure 164. ARCserve installation antivirus installation



Another component is the alert modules. These modules enable the backupserver to send alerts, using SNMP, e-mail, fax, pager or printer output as alertmethod. By default, this is not installed.

Figure 165. ARCserve installation alert modules installation

Click Next.

ARCserve will use the NetWare database system, Btrieve. ARCserve requiresBtrieve Version 6.15 or higher. If it finds an older version, you will be prompted toinstall the 6.15 version, as shown in Figure 166. All the required modules toupgrade Btrieve are included with the ARCserve package. If you select Yes, youwill be shown a list with NetWare modules that will be upgraded.

Figure 166. ARCserve installation Btrieve version

6.6.2 ConfigurationYou now need to select and configure the SCSI host adapter to which your tape isconnected. ARCserve uses two methods to address your SCSI tape:

1. Using the ASPI interface, through the SCSI driver delivered by themanufacturer of your SCSI controller.

2. Using a proprietary driver.

You are prompted in Figure 167 to select one of these options.


You can use the proprietary driver only when no other devices are attached toyour SCSI bus, as only the ARCserve tape manager will be able to communicatewith the devices on this SCSI bus. Also, only a limited number of SCSI controllersare supported by these drivers.

In our case, we will use the standard ASPI interface, since the Adaptec AHA-2940is not supported to be used exclusively by ARCserve. To do this, select theShared and/or ASPI option then click Next.

Figure 167. ARCserve adapter installation - driver type

Next, you will need to select the adapter you are using. We are using the AdaptecAHA-294X controller. Select this adapter from the list box in Figure 168, and clickNext.


Figure 168. ARCserve adapter installation - adapter selection

Figure 169 appears. Once you have selected the adapter type, you will need todefine the SCSI host adapter number. If only one SCSI controller is installed,select 0.

Figure 169. ARCserve adapter installation - configuration


The installation program gives you an overview of the SCSI controller you chose.At this point, you can modify settings, add a second controller or delete theexisting controller.


Figure 170. ARCserve adapter installation - overview


Now, you can select additional components to install. ARCserve gives you theability to install the following options:

• Install Password Database

This will enable ARCserve to store client passwords in a database. Theadvantage of this is that users will not be prompted for a password every timethey connect to the server.

• Automatically start the CLIENTS.NLM module.

This module auto-discovers ARCserve agents on the network. Although this isa user friendly way to define agents, it will increase network traffic. If you arenot using agents, you should not install this option. If you are using agents, itis possible to define them manually to the backup server.

• Create Default Rotation Backup Job

This will create a tape rotation backup job (see 2.2.2, “Backup patterns” onpage 5) using 5 tapes.


Figure 171. ARCserve installation options

Click Next. As we selected Install Manager on Server in Figure 163 on page227, Figure 172 appears where you set up the ARCserve manager.

Figure 172. ARCserve manager installation

The manager code resides on the NetWare server. This means that managerobjects on the workstation must point to the server to access the software.ARCserve lets you choose between using a fixed drive letter, which representsthe mapped drive on your server or using a UNC (Universal Naming Convention)path. Selecting this second option has the advantage that the drive mapping canchange, without affecting the operation of the ARCserve manager installed onyour workstation.


When all this is finished, ARCserve will start installation of server and managercoding on the backup server.

6.6.3 Managing ARCserve for NetWareOnce ARCserve for NetWare is installed, you can start the ARCserve backupserver by typing the following command at the server’s console:

ASTART6

Be sure to load the device driver for your SCSI adapter before you run thiscommand (in the case of an Adaptec 2940 UW or an onboard SCSI adapter, thedriver is AIC7880.DSK). ASTART6.NCF will load the ARCserve loader, which willattempt to start the ARCserve server. You can look at the loading steps in theloader message screen. This screen will deactivate automatically if all ARCservecomponents have started successfully.

When ARCserve is running, you will see the following three screens:

• ARCserve Tape Server• ARCserve Scheduler• ARCserve Run-Time Message

To manage ARCserve, you need to use a Windows 3.X, Windows 95 or WindowsNT based administrator interface, called the ARCserve Manager. Thisworkstation must be equipped with the Novell NetWare client. The MicrosoftClient Service for NetWare is not supported. This manager is automaticallyinstalled on the workstation you used to install the ARCserve server on theNetWare server. You can install it individually by selecting the Custom optionduring installation (see Figure 161 on page 226).

When you start ARCserve Manager, you will get the Quick Access menu shown inFigure 173, which allows you to start the subcomponents needed to performspecific jobs.

After installation of the base product, you should install Service Pack 2 forARCserve Version 6.1x. The patch is available from Cheyenne’s technicalsupport home page:

http://www.cheyenne.com/CheyTech/Download/patches/techptch.html

Besides fixing problems, it provides an ARCserve Manager that is compatiblewith Windows NT.

ARCserve Service Pack 2


Figure 173. ARCserve manager Quick Access menu

If you close the Quick Access menu, you will return to the ARCserve mainwindow, Figure 174. From there, you can perform all operations needed tomanage your backup server, and launch data management operations.

Figure 174. ARCserve manager — main window

The following operations can be performed from the button bar in the mainwindow (Figure 174):

• Network Connections

Using this function, you can look at and manage connections to NetWareservers. It will show all reachable servers, and display if ARCserve is runningon them or not.

• Job Status

The job status function (see Figure 175) shows all jobs processed by theARCserve server. The status of each job is displayed by a colored circle in fontof the job description (green stands for successful, red for unsuccessful and

Network Connections Backup Copy Database Manager

CompareCopy Tapes

Tape CleaningCount

Cue Cards

Media Pools

Device Management

Job Status Restore Job Queue Reports and Logs Merge Tapes

Add New Job Change Job StatusDelete Job

Monitor JobScan TapeModify Job


yellow shows that a warning occurred). You can display the details of each jobby double clicking on it.

Figure 175. ARCserve manager Job Status

• Backup, Restore and Copy

These functions allow you to submit backup, restore or copy jobs to the server.You can define the objects included for the job, schedule jobs and modify jobproperties. The copy job will copy files to ARCserve server file systems.

• Job Queue

The Job Queue manager shows all jobs that are currently in the queue usedby the NetWare server (see Figure 174). This includes all jobs that are inprogress and all jobs that are scheduled. You can also delete jobs, changetheir status, modify settings or see real-time statistics using this function.

Figure 176. ARCserve manager Job Monitor

• Database manager

The database manager can be used to look at the entries in the ARCservedatabase, and modify some values. The following database lists are available:

• Summary (see Figure 177)• Job list


• Media list• Device list• Media pool list• Media location list• Client list• Password list

Figure 177. ARCserve database manager

• Report and Logs

This function will enable you to look at the operation and error logs of theARCserve server. It can also be used to print formatted reports based onpredefined queries from the database.

• Media Pools

This function is used to manage media pools. Media pools are a collection oftapes defined as one entity. This simplifies media management. By default, alltapes will be assigned to the default media pool.

• Merge Tapes

ARCserve will store all information about its operations in the database. Thismeans that you can only use tape media that is defined in the database. Themerge function allows you to enter tapes that are not defined in the database.This could be tapes used in another ARCserve environment, or old tapes usedin a previous setup.

• Scan Tapes

The scan tape operation will scan a tape to check for its contents. It will returninformation about sessions that used the scanned tape. It is also useful forchecking files residing on the tape.

• Compare

The compare function compares tape content to actual files.

• Copy Tapes


This function allows you to copy data from one tape to another.

• Tape Cleaning

This function can be used to set up an automated cleaning schedule. It is onlyavailable when used with autochangers (see 6.6.4, “The ARCserve changeroption” on page 238).

• Count

The count function is used to count the number of files or directories onservers or clients. This tool can be used to estimate the number of tapes thatwill be necessary to run the backup.

• Device Management

The device manager is the main interface to set up your backup devices andperform operations on them. During installation, you defined the SCSI hostadapter to be used with ARCserve. This is the only definition necessary tomake ARCserve recognize your tape device. During startup, it will scan theSCSI bus for tape devices. The devices found by ARCserve will be defined asdevice groups. The device group will be the object used by ARCserve asbackup destination. By default, ARCserve will add all devices found in a groupcalled ARCSERVE. You can add or remove groups, with the limitation thateach group needs at least one device, and that each device can only belong toone group. This means that the maximum number of groups is equal to thenumber of devices.

Figure 178. ARCserve manager NetWare device manager

Using the device manager, you can see information on your tape devices, andturn compression on or off. Additionally, the device manager can be used toperform operations on tape media, like formatting (see Figure 179), erasingand ejecting tapes.


Figure 179. ARCserve manager NetWare device manager — Format Media

6.6.4 The ARCserve changer optionTo enable ARCserve for NetWare to use the IBM 3447 library, you need to installthe changer option. This will enable the ARCserve tape server to send commandsto the robotics of the library, and manage tapes that are in the library.

Before starting the installation, connect the hardware, install and start ARCserveand log in to your NetWare server. Then, start the SETUP.EXE program on yourWindows-based ARCserve manager workstation.

After the welcome screen and some additional information, you will be asked toidentify the NetWare server that you want to install, as shown in Figure 180. If youspecify Connected as the List Type, only the servers that run ARCserve will bedisplayed.

Select the required server, and click Next.

Figure 180. Changer Option Setup — select server

After server selection, you will need to enter the license number for the changeroption. Next the installation program shows the attached changers (see Figure181).

Ensure your library’s changer is listed. If not, your SCSI host adapter driver mightbe incorrect (see 6.6.1, “Installation” on page 224) or a SCSI ID conflict could


exist. Also ensure that your library is turned on and has passed initializationbefore starting the changer installation.

Figure 181. Changer Option Setup — changer detection

Click Next to continue. Figure 182 appears where you configure your changer.

This consists of adding or removing tape devices, assigning a group name to thedevices and specifying if a cleaning cartridge is available. You can also specifywhether a barcode reader is available. This will be used by ARCserve to assignserial numbers to your tape cartridges.

Figure 182. Changer Option Setup — configure changer

Click Next to continue. Figure 183 appears showing the tape drives installed.


Figure 183. Changer Option Setup — tape overview

If this is correct, disable the ARCserve server by typing ASTOP6 at the server’sconsole. Then, click Next and restart your ARCserve server by typing ASTART6 atthe console. This will re-initialize the server and load CHANGER.NLM. Thechanger’s configuration will be stored in CHANGER.CFG, an ASCII file that canbe edited. For more information, refer to the online help.

After starting the ARCserve tape server, it will initialize the library. It checks allavailable cartridges for the barcode and tape header. This can take severalminutes to complete. During this period, the library will not accept anycommands.

Once the initialization has completed, you can open the device manager (click theDevice Management icon in the main window as shown in Figure 174 on page234) and look at the configuration. Figure 184 appears.

The initialization can be turned off by modifying the CHANGER.CFG file. Thismakes the startup faster. However, you will need to run the initializationafterwards if you need to access the tape cartridges in the library.

Initialization


Figure 184. ARCserve device manager with changer installed

You can see the devices (changer and tape), and look at the tape media. Fromhere, it is possible to perform bulk media operations, such as formatting.

One of the advantages of using this changer option is creating a backup job thatwill run without user intervention. This can be done by specifying a backup job touse the Auto Pilot options (see Figure 185).

If your tape media is recognized as <<UNKNOWN TAPE>>, ARCserve will seta software write protection on the tape. This situation happens when tapes areused that were previously used by another application. The only way to getaround this protection is by using the tape server console on the ARCserveserver.

From the tape server console, first, select Changer Management and do aChange Loaded Tape operation. This will mount the tape in the drive. Oncethis is completed, exit the changer management submenu, and go to TapeDevice Management. Here, select Format or Erase Tape. Wait for theoperation to complete. This procedure has to be repeated for everyunrecognized tape cartridge in the library.

<<UNKNOWN TAPE>>


Figure 185. ARCserve backup job using Auto Pilot

You can select the type of backup that needs to be done every day. Also, you canselect the number of days, weeks and months you want to keep your backup.

In Figure 185, we took four versions of daily backups, three versions of weeklyand one monthly. This means that each week, one tape is not overwritten andkept for three weeks. After these three weeks, the first tape will be overwritten bya new weekly backup. The daily backups (Monday, Tuesday, Wednesday andThursday) will each be backed up to a separate cartridge, that will be reused thefollowing week.

Once you’ve scheduled an Auto Pilot backup job, ARCserve will manage thetapes in the library, and automatically mount the needed cartridge. The totalnumber of cartridges needed is equal to the sum of the three defined values. Soin Figure 185, we would need eight tapes.

For more information on Auto Pilot, refer to the ARCserve for NetWare ChangerOption User Guide.

6.7 VERITAS Backup Exec for Windows NT

This chapter discusses the installation and configuration of VERITAS BackupExec for Windows NT Version 7.3. For additional information, please refer to theonline documentation, in particular the Administrator’s Guide, which ships withthe Veritas product on CD-ROM.

6.7.1 Software installationInstallation of Backup Exec for Windows NT is straightforward if the correct devicedriver is installed. The device driver we refer to is the Windows NT tape devicedriver. To check if the tape device is installed and functioning, use the TapeDevice program in the Windows NT control panel.


After you have started the Backup Exec installation process and processed someof the initial installation panels, which include system requirements and licenseagreement, the window shown in Figure 186 will appear where you must choosebetween installing the Backup Exec Software or options, or the RemoteAdministrator.

Figure 186. Install the product, options, or remote administrator

The Remote Administrator provides a way to control the backup server from aremote Windows NT server or workstation.

When choosing the installation of Backup Exec and options, the next installationpanel will request the license information. The License panel will list the LicenseKey for any product or option previously installed. Options are normallypurchased separately, and require a separate license key to operate.

Next, select the options you wish to install as shown in Figure 187.

Figure 187. Option selection panel

You can select to install tape device drivers through this panel. However, somedrivers will be less recent than the ones included in the latest Windows NT serverservice pack. Therefore, if you have successfully installed the NT driver beforestarting the installation program, do not select this option.


After making your selections, and clicking the Next button the installation willstart. After the installation program copies necessary program files, you will berequired to supply details of a Service Account as shown in Figure 188. Theservice account will be the user that is used to run the Windows NT services forthis product. These services include:

• Agent browser• Alert server• Device and media service• Job engine• Naming service• Notification server• Server

Figure 188. Service account details

You can select an existing user, or define a new one. If you choose an existinguser, ensure that the security attributes of that account reflect that the passwordnever expires. If you don’t, Backup Exec will stop functioning when the passwordexpires. This service account, whether existing or new, will be assigned thefollowing rights: Log on as a service, and Administrative rights.

If you selected additional options to be installed, you will go through thatinstallation at this point. Follow the on-screen instructions to finalize theinstallation. Next, shut down Windows NT and reboot the server.

6.7.2 ConfigurationAfter the restart of the system, the Backup Exec software is run for the first time.The configuration wizard, which is started automatically, will help you prepareBackup Exec for use.

It is important to shut down and reboot the server before attempting to start theBackup Exec software. This will allow the Backup Exec services to start beforethe Backup Exec software is used. Omitting this step will cause the clientinterface shown in Figure 193 on page 247 to continually prompt for a server tolog onto.

Shutdown and Reboot


The first step in the configuration of Backup Exec, is to define the way mediaprotection will be handled. You have the choice to either go directly to theprotection level choice, or you can use the Guide me path, which will ask youquestions in order to define the best media overwrite protection for yourinstallation.

Figure 189. Media overwrite introduction panel.

If you go to the overwrite protection level selection screen, directly or through theguide manner, you will have the following choices:

• Full

This is the safest option because the media being protected cannot beoverwritten unless media in the active or imported media set(s) is moved tothe scratch category, or the media has exceeded its user-assigned dataretention period.

• Partial

Media belonging to an active media set cannot be overwritten but this is notthe case for imported and recyclable media which can be overwritten.

• None

This is the least safe option, and basically disables the overwrite protectionfeature. The administrator is responsible for making sure that media in thestorage device does not accidentally get overwritten.

Refer to the VERITAS Backup Exec for Windows NT Version 7 Administrator’sGuide for more details on media overwrite protection.

Next, you will need to define the order in which Backup Exec will select tapesfrom the available pools. You basically have the choice between two types ofmedia: recycled media, which means media that contains data that has exceededits retention period, or scratch media, which is empty.


Figure 190. Media overwrite order

When the media configuration is complete, another screen will ask you to turn onor off virus protection. Backup Exec gives you the possibility to scan data forviruses before taking a backup. This way, you have an assurance that yourbackup copies are virus free.

Now, the device configuration will start. This is done through the deviceconfiguration wizard. The first step shows you all tape storage devices that areattached to your system, and that are recognized by the program.

Figure 191. Detected hardware, with details of IBM 30/70GB DLT tape drive

If the tape device is not shown in this panel, there might be a problem with thedevice or device driver. By pushing the Configure Devices button, theinstallation program will launch the Windows NT tape device configuration panel.Ensure that the device is seen by Windows NT, and that both device and devicedriver are functioning.

Clicking the Next button displays the panel shown in Figure 192 to help verifydrive configuration and ensure that drives appear correctly as stand-alone drivesor as drives in an autochanger.


Figure 192. Verifying drive configuration

After the correct device driver has been installed for the tape device(s), and thedriver configuration verified, the device configuration is complete and we canproceed with the backup process.

6.7.2.1 Backup Exec AssistantThe Backup Exec Assistant provides easy access to all of Backup Exec’s wizards.Wizards help guide you through a variety of tasks, which are shown in Figure 193.

Figure 193. Backup Exec Assistant

The Backup Exec Assistant may be used for most operations. For moreexperienced users there is also a client interface.

If the device driver is not started it will be necessary to shut down Windows NTand reboot the backup server.

Shut down and reboot


6.7.2.2 Backup Exec Client InterfaceAfter the user interface is initialized, the Backup Exec client desktop is displayedas shown in Figure 194.

Figure 194. Client interface

We can use the Devices tab to look at the tape device which was recognizedearlier in the installation process.

Figure 195. Client interface - Devices tab

The tape drive does not appear in the Cascaded Drive Pools section because it isthe only device available. Cascaded drive pools require two or more drives of thesame device type and capacity.

If we do not wish to use the default Drive Pool “Drive Pool 1” we could create ourown drive pool and have it known by a name we assign to it. We can do this byright-clicking Drive Pool.

Toolbar

Devices Tab

BackupExec Assis-


If we are not sure of the state of the media in the drive we should perform anerase and label operation. Right-click the tape drive in the drive pool to obtain thepop-up menu that allows you to perform actions on the device and mediacurrently in the tape device.

The label option is available in the drop-down menu. The label option will requirethe administrator to supply a label. If no label is given, a default cartridge label isused which is comprised of the media type, for example, 8 mm and anincrementing number, for example, 000000. If the tape device has a barcodereader and there is a barcode label on the tape cartridge, the barcode labelautomatically becomes the cartridge label. As long as the media has a barcodelabel, and the device has a barcode reader, Backup Exec will not permit thecartridge label to be changed.

You can also use the client interface to perform media operations using the Mediatab. Here, you can label, format and delete volumes, as well as create sets ofvolumes.

Figure 196. Client interface - Media tab

6.7.2.3 Backing Up DataYou can perform manual backups by pushing the Backup button from the toolbar,which will allow you to select directories and files to back up. In order to facilitatethis operation however, and extend the single backup operation to an automatedbackup rotation schedule, you can use the Create an Automated BackupStrategy button from the Backup Exec Assistant window (see Figure 193 on page247).

This will bring up a setup wizard which will guide you through the necessarydefinitions to set up such a strategy.

To start, you will need to define which data will be backed up. The choice includeslocal drives, backup exec agents, network drives, or user-defined shares.


Figure 197. Backup selection

After selecting what you need to back up, the wizard will allow you to choosethree ways of setting up the rotation schedule. These include the Express, theTypical and the Custom methods. To familiarize yourself with the possibilities, wesuggest that you take the custom option. If you do not know what to choose, youcan leave the defaults as proposed by the software.

After choosing Custom, the first required input is the name of the rotation. Here,you can give a name that defines how the jobs related to this schedule will benamed. Next, you must set the start date for the schedule. The first backup willalways be a normal one. After setting the start date, the wizard prompts you forthe type of intermediate backups. You have the choice between differential,incremental or working set backups (see 5.7, “VERITAS Backup Exec forWindows NT” on page 149). In our example, we chose to keep the default, whichis differential. Next, Backup Exec will propose a rotation scheme based on theinput given so far.

Figure 198. Rotation schedule


As seen in Figure 198, the proposed schedule consists of differential backupMonday through Thursday, with a full normal backup on Friday. You can also setthe required start time of the schedule.

In the next panels, you will need to select the device or device pools for both thedifferential and normal backups, as well as the media you will use. You can eitherchoose to use scratch media, or append the backups to media allocated to aspecific media set. You may also specify the retention period of the media.

Figure 199. Media retention period settings

Finally, you can enable the backup program to verify the backup it just performed.This completes the setup for the automatic rotational schedule jobs. They will belaunched automatically at the required time.

6.7.2.4 Restoring dataWhile backing up data from a device, Backup Exec creates a set of catalog filesthat reside in the C:\Program Files\Veritas\Backup Exec\NT\catalogs directory onthe backup server. These catalog files contain information about the contents ofall media and are used when selections are made for restore jobs.

If the media has not previously been cataloged, such as media that was backedup from another backup server, the media must have a Catalog operationperformed on it before files can be selected to restore. Do this by right-clickingthe tape drive in the Devices tab, and selecting Catalog from the drop-downmenu.


Figure 200. Client Interface - Restore Selections

Assuming the media has already been cataloged we can restore anything from asingle file to entire directories from the selected media. Figure 200 shows therestore selections available from the media. Selecting the Restore button fromthe toolbar will bring up the restore panel allowing file/directory selections to bemade as well as the target drive/directory to be changed.

The following sections show how to configure various IBM tape devices for usewith Backup Exec for Windows NT. Each section assumes the particular tapedevice is already connected to the backup server. Device driver support isprovided in the Backup Exec software for most if not all of the IBM tape devices.Where this is not the case, a note will be provided indicating where the devicedriver may be obtained. Visit the VERITAS Web site regularly to check forupdated device drivers.

6.7.3 Configuring IBM tape drivesLet’s assume the TR4 tape drive has been physically connected to the backupserver and Windows NT Server started. It is necessary to perform the followingtasks to install the correct device driver in order for Backup Exec to recognize thetape device.

6.7.3.1 Installing the device driverOpen the Tape Devices settings by clicking Start → Settings → Control Panel →Tape Devices.

A window similar to Figure 201 appears. Depending on your particular drive thecontents of the window will be different.

Restore


Figure 201. Windows NT recognizes the IBM TR4 4.0/8.0 GB Tape Drive

Select the Drivers tab in Figure 201. A window similar to Figure 202 appears.The driver displayed depends on the tape drive you are using.

Figure 202. Device driver

If this is not the first time this tape drive is being installed then the correct devicedriver may already be shown here. To install the correct device driver, select theAdd button to view a list of device drivers, then select the Have Disk button andenter the path of the device driver. The device driver may be found in the directory\WINNT\DRIVERS\I386\ of the VERITAS Backup Exec CD-ROM.

6.7.3.2 Configuring Backup ExecWith the correct device driver installed, Windows NT will need to be restarted forthe device driver to start. The next step of the configuration process uses BackupExec, so start Backup Exec and select the Devices tab to view device details asshown in Figure 203.


Figure 203. IBM TR4 4/8GB Tape Drive recognized by Backup Exec

You will see the IBM tape device (shown as CONNER 0 for the 4/8 GB TR4) underboth Storage Devices and Drive Pools. It should automatically appear in DrivePool 1. If this is not the case, simply drag a copy from Storage Devices to DrivePool 1 or any other defined pool area.

Installation of the correct device driver and configuration of the tape drive iscomplete and is ready for use. As you can see in Figure 203 we have labeled theTR4 tape cartridge in the drive with TR4TAPE001.

6.8 Veritas Backup Exec for Novell NetWare

This topic will go through the installation and configuration of Backup ExecVersion 8.0 for Novell NetWare.

6.8.1 Software installationBackup Exec for NetWare has the following system requirements:

• Novell NetWare 4.10 or later• 4 MB of RAM in addition to that required by the operating system and other

applications• 14 MB disk space

Backup Exec for NetWare can be installed using two methods. The first one is toload the installation NLM on the backup server itself (see 6.8.1.1, “Server-basedinstallation” on page 255). A second way of installing Backup Exec is to load theinstallation program from a workstation running Windows or OS/2 (see 6.8.1.2,“Installation from a Workstation” on page 257).

DevicesTab


6.8.1.1 Server-based installationThis type of installation will be entirely done on the NetWare server.

1. Insert the Backup Exec CD into the CD-ROM device, and mount it as aNetWare volume. To do this, type the following commands at the server’sconsole:

load aspicdload cdromcd mount seagate

2. Type the following at the system console to start the installation program:

load seagate:netware\beinstl.nlm

3. This will bring up the first window, where you will have to choose the languageyou want to install in.

4. Next, you will need to insert your serial number, which is located on thebarcode label of your CD-ROM.

If you want to upgrade your current license, please contact VERITAS for moreinformation. Choices are the Enterprise Edition or the Single Server Unlimitededition (see 5.8, “VERITAS Backup Exec for Novell NetWare” on page 155).This example will cover the Single Server installation. The Enterprise Editionwill be covered in 6.8.1.2, “Installation from a Workstation” on page 257.

5. The next step will be to choose between a typical or custom installation. Atypical installation will use the default installation paths, update NovellNetWare NLMs, run in Directory Services mode and will not copydocumentation to the server. If you use the custom method, which we did, youcan override these defaults.

Figure 204. Choice between Typical and Custom installation

If you do not enter your serial number, Backup Exec will install itself as a60-day trial version. Press F2 to continue. The next screen asks yo uto acceptthe license agreement. If you do not enter a serial number and agree to use thetrial version, you will have to choose which version you will install: EnterpriseEdition or Single Server.

Serial Number


6. After choosing the custom installation path, the first step will be to update theNovell NetWare NLMs. Backup Exec will need to update some NetWareloadable modules in order to function correctly. During this step, theinstallation program will show a list of modules requiring change.

7. Now, you will have to enter the SCSI controller type. In our case, the Adaptec294X controller is selected.

Figure 205. SCSI adapter selection

The supported DMA option will normally default to Yes for this adapter. If itdoes not, be sure to select it, as otherwise memory below 16 MB will be used.Press F2 to continue.

8. Next, Backup Exec will start copying some preparation files, and then ask youwhere you want to install the files. Figure 206 shows this window.

Figure 206. Installation directories

The different types of files are as follows:

Catalog files: Used to determine tape contents.

Job history files: Store results of jobs processed.

Tape rotation files: These files are used when processing taperotation jobs.

Partition management files: Store partition management databases.


Agent and client files: Used to install the Backup Exec clients andagents to user’s workstation.

Install online documentation: Copies the online documentation from theinstallation CD to the server’s hard disk.

After the copying completes, Backup Exec creates two ncf files: BESTART.NCFand BESTOP.NCF. BESTART.NCF is added to the AUTOEXEC.NCF file, andcontains all necessary information to load tape device support and the BackupExec Job Manager. The BESTOP.NCF file can be used to stop the Backup Execapplication.

6.8.1.2 Installation from a WorkstationThe second way of installing Backup Exec for NetWare is using the client-basedinstallation program. Using this program, it is possible to install the backup serverusing Windows-based interfaces. If you are running Windows 95 or Windows NT,just insert the CD. Otherwise, run the SETUP.EXE program located in the rootdirectory of the CD. This will start the installation interface (see Figure 207).Select the Backup Exec for NetWare option, and select the Install button.

Figure 207. Main installation window

After selecting the language version you want to install, you are given the choicebetween different installation actions (see Figure 208). To install the Backup Execserver, select the Install Backup Exec Software on Backup Server option andclick Next. You then will be asked to install the software or upgrade an alreadyinstalled version. Since this is a fist time installation, select the Install BackupExec for NetWare option. After this, you are requested to enter the serial numberfor the product. If you do not enter a license number, you can install a 60-day trialversion.


Figure 208. Main install options

Next, the license agreement will appear. If you agree, and did not install a license,you will have to choose which product evaluation code you are going to install(see Figure 209).

Figure 209. Select Evaluation Version Desired

We chose the Enterprise Edition. Next, a list of NetWare servers will appear thatshow the possible targets for our installation. Highlight the required server, andclick Next. You will be prompted to enter a user ID and password for this server,with supervisor rights to the root object on your tree (unless you are alreadylogged on as supervisor).

Next, you can choose a typical or custom installation path. For both paths, thenext screen (Figure 210) requires input for both client installation and serverconfiguration. Refer to the Backup Exec manuals for more information. It will alsoshow the required disk space and the available disk space on the target server.After this, additional installation options will need to be entered if custominstallation has been chosen.


Figure 210. Install Options

After clicking Next, you can modify the installation path (if you chose the custominstallation method). See Figure 211 for details. The different directories are usedfor the following:

Catalog files: Used to determine tape contents.

Job history files: Store results of jobs processed.

Tape rotation files: These files are used when processing taperotation jobs.

Partition management files: Store partition management databases.

Agent and client files: Used to install the Backup Exec clients andagents to user’s workstation.

Install online documentation: Copies the online documentation from theinstallation CD to the server’s hard disk.

Figure 211. Directory Options

Next, the appropriate SCSI adapter must be selected. Select the AdaptecAHA-294x adapter (or whatever adapter is appropriate for your installation), and


make sure that the option to use DMA access above 16 MB is checked (seeFigure 212).

Figure 212. Select Controller Type

After you have selected the adapter, the files will be copied to the server. You canread the readme files after the installation finishes. Since you are installing theEnterprise Edition, you will have the possibility to install another server. If youchoose not to, the Windows client will be installed.

You can now automate startup of the Backup Exec backup server by addingBESTART.NCF to the server’s AUTOEXEC.NCF file.

6.8.2 Software configurationOnce the software is installed, you will need to configure it to recognize your tapedevices. To do this, you will need to use Job Manager on the NetWare server toset up partition management. To start the Job Manager, load BEMGR.NLM in theBackup Exec directory, or use the BESTART.NCF file. BESTART.NCF will load allrequired components to use Backup Exec, and this will be done using theSureStart concept. SureStart will check if all necessary software and hardwarerequirements are met, and perform some housekeeping on the product. TheSession Status window (see Figure 213) is the main Job Manager user interface.From here, you can do the following:

• Monitor active jobs.

• View partition information, tape drive configuration and hardware settings.

• Change partition settings.

• Perform tape utility tasks.

• Access the Job Manager options.

• Exit the Job Manager.


Figure 213. Backup Exec Job Manager main window

Press Ctrl-O to open the Options screen. You will be required to log in assupervisor. From the Options window, select Partition Management (Figure214).

Figure 214. Backup Exec Job Manager main options window

Next, select Define/Maintain Partitions (Figure 215).

Figure 215. Backup Exec Job Manager Partition Management window


As shown in Figure 216, Backup Exec has already defined a default partition forthe tape device it detected. To edit this default definition, press Enter. This willbring up the Partition Description window. Here you can change the properties ofthe partition (Figure 217).

Figure 216. Backup Exec partition maintenance window

Figure 217. Backup Exec Partition Description window

Once the partition is defined, the backup server will be ready to accept jobs fromclients.

6.9 Seagate Sytos Premium for OS/2

Sytos Premium for OS/2 is a backup application made for OS/2 Warp Server. It isan easy to use, easy to configure application, that allows you to back up yourservers running OS/2. It is included with most current single-tape devices boughtfrom IBM.

Currently, the following devices are supported:

• IBM 4/8 GB TR4 tape drive• IBM 12/24 NS tape drive• IBM 4/10 GB DDS-2 tape drive• IBM 12/24 GB DDS-3 tape drive• IBM 20/40 GB 8 mm tape drive


Since Sytos does not use clients or agents, backups are limited to the localmachine to which the tape device is connected. You can back up OS/2 networkfile systems to which you are connected from the local server. This limits the useof Sytos Premium in enterprise wide, mixed environments.

Although limited for large sites, Sytos could be a good solution for small locationsor enterprises. It has functions and features that make it a valid backup solution.These features include:

• Able to back up Access Control Lists (ACLs) and file permissions.• Long file name and extended attributes support for HPFS file systems.• Multi-threaded and multi-tasking.• File grooming possibilities.• Autoloader support using the optional Autoloader module (currently, only the

IBM internal 4 mm 12/24 GB autoloader is supported).

Also, Sytos supports non-SCSI devices, like EIDE tapes, diskettes or hard drivesas backup devices.

6.9.1 Installing Sytos Premium Version 2.2Sytos Premium has the following system requirements:

• IBM OS/2 Warp 3.0 or later• LAN Server 3.0 or Warp Server 4.0 or later• 3 MB of free hard disk space (does not include space needed for database

and log files)• 4 MB of RAM free above operating system and other application requirements

When starting the installation of Sytos, the first thing to check is the SCSIconfiguration of your system. Standard SCSI requirements apply. These are:

• SCSI host adapter driver is loaded and configured.• The SCSI bus is properly terminated.

To begin the installation, start the installation utility (SETUP.EXE) on theCD-ROM. This will bring up the License Agreement window and a list of systemrequirements. When you finish reading this information, you will have to enter theserial number that is located on your CD-ROM. After doing this, the installationprocedure begins.

The first step will be to define the installation directory. By default, Sytos uses a\SYPLUS directory on the OS/2 boot drive. Next, you will need to define thebackup device you are using (see Figure 218). You can define more than onedevice by selecting them but there can be only one default device.

Since non-SCSI devices are beyond the scope of this publication please referto Sytos manuals for more information on installation and configuration of thesedevices.

Non-SCSI Devices


Figure 218. Sytos Premium device definition

Once you’ve selected the device you are using (in our case, the IBM 20/40 GB 8mm drive), click Continue. Next, you will have to define the SCSI adapter you areusing. For most IBM servers, select the Adaptec AHA-2940 adapter (see Figure219). You will need to define an adapter for each tape device you’ve selected.

Figure 219. Sytos Premium SCSI adapter selection

Next, you will need to define a default tape set name (see Figure 220). This setname will be the name used to define the tapes that are used by the default jobsdefined in Sytos. Once you’ve entered this set name, the installation program willgive you the possibility to confirm or modify the installation options, and startcopying the files to your hard disk.


Figure 220. Default Tape Set definition

Next, the installation program asks you to modify the CONFIG.SYS file, updatingit with drivers for your tape device (see Figure 221). The driver installed is specificfor each tape device. Table 19 shows an overview of the supported tape deviceswith their associated drivers. If you have problems, or want to find out if newerdevices are supported, you can download drivers from the Sytos Web page:

http://www.seagatesoftware.com/sytosos2

Table 19. Supported drivers

Tape Device Driver

IBM 20/40 GB 8 mm IBM_2040.SYS

IBM 4/10 GB 4 mm DDS-2 IBS_4GBI.SYS

IBM 12/24 GB 4 mm DDS-3 IBM_1224.SYS

IBM TR4 IBMTR4S.SYS

IBM 12/24 GB NS (Driver planned but not availableat time of publication.)


Figure 221. Updating the Config.Sys

This concludes the installation of Sytos Premium for OS/2. You can open the userinterface by double clicking the Sytos Premium Icon on your desktop. Figure 222shows the main user interface. You can immediately take a backup by selectingone of the predefined backup jobs. These jobs will use the default device definedduring installation (tape device and tape set name).

Figure 222. Sytos Premium user interface

For more information on using this interface, please refer to the user guidesincluded on the CD ROM.


Appendix A. Sources of information

These Web sites may be useful for finding out more about tape backup solutionsfor Netfinity systems:

IBM Tape Products —

http://www.storage.ibm.com/hardsoft/tape/index.html

Contains information about IBM’s complete range of tape hardware for allplatforms, notebook to mainframe. Links include the list of media that areavailable from IBM.

Support for IBM Tape Drives —

http://www.pc.ibm.com/support

Click Options by IBM Support then Tape Drives from the list box then thepart number of the drive you are looking for.

IBM Tape Products Compatibility —http://www.pc.ibm.com/us/compat/storage/matrix.shtml

Contains matrixes listing IBM server and IBM tape drive compatibility.

IBM SAN information —

http://www.storage.ibm.com/ibmsan/

DLTtape.COM —

http://www.dlttape.com.

An online resource that is sponsored and maintained by Quantum. It containsthe latest DLT tape-related information including product reviews and pressreleases as well as an online discussion forum.

QIC Drive Standards —

http://www.qic.org

LTO —

http://www.lto.org

Tivoli Storage Manager —

http://www.tivoli.com/products/index/storage_mgr

Tivoli Data Protection for Workgroups —

http://www.tivoli.com/products/index/data_protect/

VERITAS —

http://www.veritas.com.

Where you can find information on VERITAS products: NetBackup, BackupExec and Sytos.

Legato Products —

http://www.legato.com/Products/index.html

http://www.storage.ibm.com/hardsoft/tape/index.html

http://www.pc.ibm.com/support

http://www.pc.ibm.com/us/compat /storage/matrix.shtml

http://www.storage.ibm.com/ibmsan/

http://www.dlttape.com.

http://www.qic.org

http://www.lto.org

http://www.tivoli.com/products/index/data_protect/

http://www.tivoli.com/products/index/storage_mgr

http://www.veritas.com



Information on the Legato NetWorker software.

CA ARCServeIT —

http://www.cai.com/arcserveit/

USA Announcement Letters —

http://www.ibmlink.com/usalets.

All IBM product announcements are available in HTML, PostScript and PDFformats, searchable by date, product name, product number or any search string.


http://www.cai.com/arcserveit/

http://www.ibmlink.com/usalets


Appendix B. Hardware part numbers

This appendix contains a list of all tape drives and libraries, and their associatedpart numbers. Table 20 identifies part numbers associated with the 40/80 GB DLTtape drive:

Table 20. IBM 40/80 GB DLT tape drive part numbers

Table 21 identifies part numbers associated with the 35/70 GB DLT tape drive:


Table 22 identifies part numbers associated with the 20/40 GB DLT tape drive:


IBM 40/80 GB DLT Tape Drive US P/N EMEA P/N

Tape drive (black bezel) 007N7990 007N7990

DLT IV cartridge 59H3040 59H3040

DLT cleaning cartridge 59H3092 59H3092

DLT external SCSI enclosure 3503BOX 03K8705

NetMEDIA storage expansion unit EL 3551001 03K8756

Active terminator 32G3918 32G3918

IBM 35/70GB DLT Tape Drive US P/N EMEA P/N

Tape drive (black bezel) 04K0149 04K0149

Internal 4-drop 68-pin SCSI cable 60H7826 60H7826

DLT III XT 59H3411 59H3411






IBM 20/40GB DLT Tape Drive US P/N EMEA P/N

Tape drive (black bezel) 01K1320 01K1320

DLT III XT 59H3411 59H3411







Table 23 identifies part numbers associated with the 20/40 GB 8 mm tape drive:

Table 23. IBM 20/40 GB 8mm tape drive part numbers

Table 24 identifies part numbers associated with the 20/40 GB DDS-4 tape drive:

Table 24. IBM 20/40 GB DDS-4 tape drive part numbers

IBM 20/40GB 8mm Tape Drive US P/N EMEA P/N

Tape drive 01K1325 01K1325

8 mm 170 m AME data cartridge 59H2679

8 mm cleaning cartridge 59H2898

External half-height SCSI enclosure 3510020 3510020


Internal 2-drop SCSI cable (for Netfinity3500 M10 and Netfinity 5000)

36L9636 36L9636


IBM 20/40GB DDS-4 Tape Drive US P/N EMEA P/N

Tape drive 00N7990 00N7990

DDS-4 data cartridge 59H4458

Cleaning cartridge



Internal 2-drop SCSI cable (for Netfinity5000)

36L9636 36L9636


Appendix B. Hardware part numbers 271

Table 25 identifies part numbers associated with the 12/24 GB DDS-3 tape drive:

Table 25. IBM 12/24 GB DDS-3 tape drive part numbers

Table 26 identifies part numbers associated with the 10/20 GB NS-20 tape drive:

Table 26. IBM 10/20 GB NS-20 tape drive part numbers

IBM 12/24GB DDS-3 Tape Drive US P/N EMEA P/N


DDS-3 data cartridge 59H3465

Cleaning cartridge



Internal 2-drop SCSI cable (for Netfinity5000)

36L9636 36L9636


IBM 10/20GB NS-20 Tape Drive US P/N EMEA P/N




Internal 2-drop SCSI cable (for Netfinity3500 and Netfinity 5000)

36L9636 36L9636


68 to 50-pin SCSI cable convertor 01K1326 01K1326


Table 27 identifies part numbers associated with the 490/980 GB DLT tapelibrary:

Table 27. IBM 490/980 GB DLT tape library part numbers

IBM 490/980GB DLT Tape Library US P/N EMEA P/N

Tower model (3502-314) 3502314 00N79xx1

Rack model (3502-R14) 3502R14 00N79xx2

DLT tape library drive upgrade 33L4979 33L4979



1. Due to country dependent power connections, the two last digits of the part numberdepend on the country in which the library is ordered. The following list gives an overviewof countries and related last two digits (xx):

United Kingdom 77

EU1 type connector 74

Denmark 75

India/South Africa 76

Switzerland 78

Italy 79

Israel 80

2. Due to country dependent power connections, the two last digits of the part numberdepend on the country in which the library is ordered. The following list gives and overviewof countries and related last two digits (xx):

United Kingdom 84

EU1 type connector 81

Denmark 82

India/South Africa 83

Switzerland 85

Italy 86

Israel 87

Appendix B. Hardware part numbers 273

Table 28 identifies part numbers associated with the 280/560 GB DLT tapeautoloader:

Table 28. IBM 280/560 GB DLT autoloader part numbers

Table 29 identifies part numbers associated with the 3449 8 mm tape library:

Table 29. IBM 3449 8mm tape library part numbers

IBM 280/560 GB DLT Autoloader US P/N EMEA P/N

Desktop model (3502-108) 3502108 Country Specific1

DLT Tape library drive upgrade 33L4979 33L4979

DLT IV Cartridge 59H3040 59H3040


1. Due to country dependent power connections, the part number depends on the countryin which the library is ordered. The following list gives an overview of countries and relatedpart numbers:

United Kingdom 00N7970

EU1 type connector 33L4981

Denmark 33L4982

India/South Africa 33L4983

Switzerland 00N7971

Italy 00N7972

Israel 00N7973

IBM 3449 8mm Tape Library US P/N EMEA P/N

Tower Model (3449-355) 3449355 3449355

Rack Model (3449-356) 3449356 3449356

20 GB 8 mm tape drive 59H3391 59H3391

10 cartridge media magazine 87G1728 87G1728

SCSI F/W differential kit 59H3900 59H3900

8mm AME data cartridge 59H2678 59H2678

Cleaning cartridge 59H2898 59H2898


Table 30 identifies part numbers associated with the Magstar 3570 MP tapelibrary:

Table 30. IBM Magstar 3570 MP tape library part numbers

IBM Magstar 3570 MP Tape Library US P/N EMEA P/N

Magstar 3570-C21 MP 3570C21 08L6479

Magstar 3570-C22 MP 3570C22 08L6482

Second C-drive (for 3570-C21) 08L6487

SCSI adapter card kit 08L6517 08L6517

Cleaner cartridge 05H2463 05H2463

Cartridge magazine 49G6598 49G6598

B–Format data cartridge 05H2462 05H2462

B-Format Replacement Label Kit - 10sets of labels

05H9393 05H9393

B-Format Custom VOLSER Label Kit -10 sets of labels

05H9643 1 05H9643 1

C–Format data cartridge 08L6187 08L6187

C-Format Replacement Label Kit - 10sets of labels

08L6191 08L6191

C-Format Custom VOLSER Label Kit -10 sets of labels

08L6192 1 08L6192 1

C-Format XL data cartridge 08L6663 08L6663

C-Format XL Replacement Label Kit -10 sets of labels

08L6665 08L6665

C-Format XL Custom VOLSER LabelKit - 10 sets of labels

08L6666 1 08L6666 1

1. The label and the internally recorded VOLSER must match. If there are existingcartridges where there is a mismatch between the barcode label and the VOLSER withwhich the tape was initialized, a set of custom cartridge labels can be ordered to matchthe barcode label to the internal VOLSER.


Appendix C. Storage area networks and Fibre Channel

Today, the industry considers Fibre Channel (FC) as the architecture on whichmost SAN implementations will be built. Fibre Channel is a technology standardthat allows data to be transferred from one network node to another at very highspeeds. Current implementations transfer data at 100 MB/sec. The 200 MBpsand 400 MBps data rates have already been tested. This standard is backed by aconsortium of industry vendors and has been accredited by the AmericanNational Standards Institute (ANSI). Many products are now on the market thattake advantage of FC’s high-speed, high-availability characteristics.

Note that the word Fibre in Fibre Channel is spelled using British English ratherthan the American form, Fiber. This is because the interconnections betweennodes are not necessarily based on fiber optics, but can also be based on coppercables.

Some people refer to Fibre Channel architecture as the Fibre version of SCSI.Fibre Channel is an architecture used to carry intelligent peripheral interface (IPI)traffic, IP traffic, FICON traffic, FCP (SCSI) traffic, and possibly traffic using otherprotocols, all at the same level on the standard FC transport. An analogy could beEthernet, where IP, NetBIOS, and SNA are all used simultaneously over a singleEthernet adapter, since these are all protocols with mappings to Ethernet.Similarly, there are many protocols mapped onto FC.

FICON is expected to be the standard protocol for IBM System/390, and FCP isthe expected standard protocol for other systems, all using Fibre Channelarchitecture to carry the traffic.

In the following sections, we will introduce some basic Fibre Channel concepts,starting with the physical layer and proceeding to define the services offered.

C.1 Layers

Fibre Channel is structured in independent layers, as are other networkingprotocols. There are five layers, where 0 is the lowest layer. The physical layersare 0 to 2, the upper layers are 3 and 4.

C.1.1 Lower layers

• FC-0 defines physical media and transmission rates. These include cablesand connectors, drivers, transmitters, and receivers.

• FC-1 defines encoding schemes. These are used to synchronize data fortransmission.

• FC-2 defines the framing protocol and flow control. This protocol isself-configuring and supports point-to-point, arbitrated loop, and switchedtopologies.

C.1.2 Upper layers

Fibre Channel is a transport service that moves data fast and reliably betweennodes. The two upper layers enhance the functionality of Fibre Channel andprovide common implementations for interoperability.


• FC-3 defines common services for nodes. One defined service underdevelopment is multicast, to deliver one transmission to multiple destinations.

• FC-4 defines upper layer protocol mapping. Protocols such as FCP (SCSI),FICON, and IP can be mapped to the Fibre Channel transport service.

C.2 Topologies

Fibre Channel interconnects nodes using three physical topologies that can havevariants. Topologies include:

• Point-to-point — The point-to-point topology consists of a single connectionbetween two nodes. All the bandwidth is dedicated for these two nodes.

• Loop — In the loop topology, the bandwidth is shared between all the nodesconnected to the loop. The loop can be wired node-to-node; however, if a nodefails or is not powered on, the loop is out of operation. This is overcome byusing a hub. A hub opens the loop when a new node is connected and closesit when a node disconnects.

• Switched — A switch allows multiple concurrent connections between nodes.There can be two types of switches, circuit switches and frame switches.Circuit switches establish a dedicated connection between two nodes,whereas frame switches route frames between nodes and establish theconnection only when needed. A switch can handle all protocols as it does notlook at the Fibre Channel layer FC-4.

C.3 Classes of Service

Fibre Channel provides a logical system of communication called Class ofService that is allocated by various login protocols. The following five classes ofservice are defined:

• Class 1 — Acknowledged Connection Service

Dedicates connections through the fabric equivalent of a dedicated physicallink and delivers frames with acknowledgment in the same order astransmitted.

• Class 2 — Acknowledged Connectionless Service

Multiplexes frames from multiple sources with acknowledgment. Frame orderis not guaranteed.

• Class 3 — Unacknowledged Connectionless Service

As class 2, without frame acknowledgment. Flow has to be controlled at bufferlevel.

• Class 4 — Fractional Bandwidth Connection Oriented Service

As class 1, but with only a minimum of bandwidth guaranteed. If sufficientbandwidth is available, class 2 and 3 frames will share connections.

• Class 6 — Simplex Connection Service

As class 1, but also provides multicast and preemption.

Appendix C. Storage area networks and Fibre Channel 277

C.4 SAN components

As mentioned earlier, the industry considers Fibre Channel as the architecture onwhich most SAN implementations will be built, with FICON as the standardprotocol for S/390 systems, and FCP as the standard protocol for non-S/390systems. Based on this perception, the SAN components described in thefollowing sections will be Fibre Channel based.

C.4.1 SAN servers

The server infrastructure is the underlying reason for all SAN solutions. Thisinfrastructure includes a mix of server platforms such as Windows NT, UNIX(various flavors) and OS/390. With industry drives towards server consolidationand e-business, the need for SAN will increase. Although the early SAN solutionsonly supported homogeneous environments, SAN will evolve to support a trulyheterogeneous environment.

C.4.2 SAN storage

The storage infrastructure is the foundation on which data processing relies andtherefore must support a company’s business objectives and business model. Inthis environment, simply deploying more and faster storage devices is notenough; a new kind of infrastructure is needed, one that provides enhancednetwork availability, data accessibility, and system manageability than is providedby today’s infrastructure.

The SAN meets this challenge. The SAN liberates the storage device, so it is noton a particular server bus, and attaches it directly to the network. In other words,storage is externalized and functionally distributed across the organization. TheSAN also enables the centralizing of storage devices and the clustering ofservers, which makes for easier and less expensive administration.

C.5 SAN interconnects

The first element that must be considered in any SAN implementation is theconnectivity of storage and server components using technologies such as FibreChannel. The components listed below have typically been used for LAN andWAN implementations. SANs, like LANs, interconnect the storage interfacestogether into many network configurations and across long distances.

Much of the terminology used for SAN has its origin in IP network terminology. Insome cases, the industry and IBM use different terms that mean the same thing,and in some cases, mean different things. For example, after reading C.5.10,“Bridges” on page 280 and C.5.11, “Gateways” on page 280, you will find that theIBM SAN Data Gateway is really a bridge, not a gateway.


C.5.1 Cables and connectors

As with parallel SCSI and traditional networking,there are different types of cables of variouslengths for use in a Fibre Channel configuration.Two types of cables are supported: copper andoptical (fiber). Copper cables are used for shortdistances (up to 30 m) and can be identified bytheir DB9 (9-pin) connector. Fiber cables come intwo distinct types: Multi-Mode Fiber (MMF) for short distances (up to 2 km), andSingle-Mode Fiber (SMF) for longer distances (up to 10 km).

IBM will support the following distances for FCP:

Table 31. Fibre Channel optical cable characteristics

In addition, connectors (see C.5.3, “Gigabit interface converters (GBIC)” on page278) and cable adapters (see C.5.4, “Media interface adapters (MIA)” on page278) have been developed that allow the interconnection of fiber optic basedadapters with copper based devices.

C.5.2 Gigabit link model (GLM)

Gigabit link models are generic Fibre Channeltransceiver units that integrate the key functionsnecessary for installation of a Fibre Channelmedia interface on most systems.

C.5.3 Gigabit interface converters (GBIC)

Gigabit Interface Converters are typically usedwith hubs and switches, and allow both copperand fiber optics to connect up to the same hub orswitch. This works well in an environment wherethe components to be attached may be both fiberoptics and copper, depending on cost anddistance requirements.

C.5.4 Media interface adapters (MIA)

Media Interface Adapters can be used tofacilitate conversion of an optical interfaceconnection to copper and vice versa. Typically,MIAs are attached to host bus adapters, but canalso be used with switches and hubs. When ahub or switch only supports copper or opticalconnections, MIAs can be used to convert thesignal to the appropriate media type (copper or optical).

Diameter (microns) Mode Laser type Distance

9 Single-mode Longwave <=10 km

50 Multi-mode Shortwave <=500 m

62.5 Multi-mode Shortwave <=175 m


C.5.5 Adapters

Adapters are devices that connect to a network,server, or storage device and control the electricalprotocol for communications. Adapters are alsoreferred to as Network Interface Cards (NIC),Enterprise Systems Connection (ESCON)adapters, Host Bus Adapters (HBA), and SCSIhost bus adapters.

C.5.6 Extenders

Extenders are used to facilitate longer distancesbetween nodes that exceed the theoreticalmaximum.

C.5.7 Multiplexors

Multiplexors provide for more effective utilizationof high speed bandwidth resources by interleavingdata from multiple sources onto a single link. Anexample of this would be the FIbre CONnectionChannel (FICON) Bridge, which allows up to eight separate ESCON paths to bemultiplexed over a single FICON link. The FICON bridge is not a separate box; asshown in the picture, it is a card in the ESCON Director. Multiplexors are alsobecoming increasingly efficient in terms of data compression, error correction,transmission speed and multi-drop capabilities.

C.5.8 Hubs

Fibre Channel hubs are used to connect up to 126 nodes into a logical loop. Allconnected nodes share the bandwidth of this single logical loop. Fibre ChannelArbitrated Loop (FC-AL) protocol is the most widely accepted, cost-effectiveimplementation. Each port on a hub contains a Port Bypass Circuit (PBC) toautomatically open and close the loop to support hot plugging. Multiple hubs andlinks can be implemented to provide alternate path failover capability for highavailability server environments. Intelligent hubs are currently being offered thatprovide features such as dynamic loop configuration and some of the benefits ofswitches.

C.5.9 Routers

Storage routing is a new technology based on the old concept of routing as it isunderstood by the data communications industry. Storage routers differ fromnetwork routers in that the data being routed uses storage protocols like FCP(SCSI) instead of messaging protocols such as TCP/IP. The data path used totransfer storage data may be the same as that used for messaging traffic, but thecontent of the data itself contain imbedded storage protocol information. This issimilar to the concept of tunneling protocols used in the broader market. Forexample, a storage router could encapsulate SCSI information in TCP/IP packetsfor transmission over an intervening Ethernet network. The term routing impliesdata transfers over differing transmission media and addressing schemes. As acombination of communications and storage channel capabilities, Fibre Channel


represents the first opportunity to apply communication techniques, such asrouting, to storage traffic.

C.5.10 Bridges

Bridges facilitate communication between LAN/SAN segments and/or networkswith dissimilar protocols. An example of this would be a FICON bridge, whichallows the ESCON protocol to be tunneled over the Fibre Channel protocol.FICON bridges reduce the requirements of ESCON connections, ESCONchannels, ESCON Director ports, and so on; they support large and small blockmultiplexing.

C.5.11 Gateways

A gateway is a network station used to interconnect two or more dissimilarnetworks or devices, and may or may not perform protocol conversion. Theseboxes are typically used to provide WAN access from a LAN. With gateways,SANs can be extended across a WAN.

Note: The IBM SAN Data Gateway is used to attach SCSI devices such as tapelibraries, disk subsystems at one end, and Fibre Channel connections at the otherend, which makes it a router, not a gateway.

C.5.12 Switches

Switches are among the highest performing hardware available forinterconnecting large numbers of devices, increasing bandwidth, reducingcongestion and providing aggregate throughput. Fibre Channel protocol wasdesigned specifically by the computer industry to remove the barriers ofperformance with legacy channels and networks. When a Fibre Channel switch isimplemented in a SAN, the network is referred to as a fabric, or switched fabric.Each device connected to a port on the switch can access any other deviceconnected to any other port on the switch, enabling an on-demand connection toevery connected device. Various FC switch offerings support both switched fabricand/or loop connections. As the number of devices increases, multiple switchescan be cascaded for expanded access (fanout).

As switches allow any-to-any connections, the switch and management softwarecan restrict which other ports a specific port can connect to. This is called portzoning.

C.5.13 Directors

When ESCON was announced, the switches were named directors, as theyincluded high availability and other features, for example, dual power supply, notincluded in traditional switches.

C.5.13.1 ESCONESCON transfers data in half-duplex mode at a transfer rate of 17 MBps. Thedirectors provide dynamic or static connections between attached channels,control units, devices, and other ESCON directors. ESCON Directors providesingle-link distances up to 3 km for multi-mode fiber and 20 km for single-modefiber.


The ESCON director supports the FICON bridge card mentioned in C.5.10,“Bridges” on page 280. Using the FICON bridge, an S/390 system can, through aFICON channel, communicate with ESCON control units and devices attached tothe director.

C.5.13.2 FICONFICON transfers data in full-duplex mode at a rate of 100 MBps. The FICONdirector is a regular Fibre Channel switch with some additional features. Itprovides connections between FICON channels and control units or devices withFICON interfaces. FICON Directors provide single-link distances up to 550meters for multi-mode fiber (50 or 62.5 micron) and 10 km (20 km with RPQ) forsingle-mode fiber (9 micron).


Appendix D. TSM element addresses and worksheets

This appendix provides information and worksheets to help you plan your tapeinstallation. Recording your configuration information using these worksheets willprovide a convenient way to document your backup implementation.

D.1 Device names

For devices supported by either the Tivoli Storage Manager SCSI driver orWindows NT drivers, you can use an alias name to refer to the devices whenusing Tivoli Storage Manager. The alias name replaces the real TSM SCSI nameor Windows NT name for a device in Tivoli Storage Manager commands andscreens. An alias name has the form mt x.y.z.n or lb x.y.z.n. The mt indicates thedevice is a tape device and the lb indicates the device is the controller for a tapeautochanger or an automated library. The alias can be abbreviated. Someexamples follow:

mt3 Tape drive at SCSI ID 3, LUN 0 on port 0, bus 0lb4.1 Library at SCSI ID 4, LUN 1 on port 0, bus 0mt5.0.1 Tape drive at SCSI ID 5, LUN 0, port 1, bus 0

Because the alias name does not change unless you change how the device isphysically attached, we recommend that you always use the alias name fordevices controlled by Windows NT device drivers. To distinguish between a realdevice name and an alias, Tivoli Storage Manager checks for a backslash (\) atthe beginning of the name. If the name begins with a backslash, Tivoli StorageManager recognizes that the name is the real device name and not an alias.Using the real device name for a device controlled by a Windows NT device driveris not recommended because that name can change the next time the machine isbooted.

D.2 Single tape devices

Since manual libraries do not need element numbers, all single-tape devices onlyneed the device name when defining them. The following table can be used torecord the SCSI ID and the device name.

Device SCSI ID Device Name

Tape Drive ______________ mt___.___.___.___


D.3 Tape libraries

The following tables show an overview of element addresses for the IBM tapelibraries and autoloaders.

D.3.1 IBM 3502-108

D.3.2 IBM 3502-x14


Tape Drive 1 (element 16) ______________ mt___.___.___.___

Robot ______________ lb___.___.___.___





Robot ______________ lb___.___.___.___

Appendix D. TSM element addresses and worksheets 285

D.3.3 IBM 3447

D.3.4 IBM 3449




Robot ______________ lb___.___.___.___




Robot ______________ lb___.___.___.___


D.3.5 IBM 3570 C2x

D.3.6 IBM 3575 L06




Robot ______________ lb___.___.___.___




Robot ______________ lb___.___.___.___

16

17

Drive 1

Drive 2

Appendix D. TSM element addresses and worksheets 287

D.3.7 IBM 3575 L12

D.3.8 IBM 3575 L18, L24, and L32






Robot ______________ lb___.___.___.___








Robot ______________ lb___.___.___.___

16

17

Drive 1

Drive 2

18

19

Drive 3

Drive 4


Appendix E. Special notices

References in this publication to IBM products, programs or services do not implythat IBM intends to make these available in all countries in which IBM operates.Any reference to an IBM product, program, or service is not intended to state orimply that only IBM's product, program, or service may be used. Any functionallyequivalent program that does not infringe any of IBM's intellectual property rightsmay be used instead of the IBM product, program or service.

Information in this book was developed in conjunction with use of the equipmentspecified, and is limited in application to those specific hardware and softwareproducts and levels.

IBM may have patents or pending patent applications covering subject matter inthis document. The furnishing of this document does not give you any license tothese patents. You can send license inquiries, in writing, to the IBM Director ofLicensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact IBM Corporation, Dept.600A, Mail Drop 1329, Somers, NY 10589 USA.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The information contained in this document has not been submitted to any formalIBM test and is distributed AS IS. The information about non-IBM ("vendor")products in this manual has been supplied by the vendor and IBM assumes noresponsibility for its accuracy or completeness. The use of this information or theimplementation of any of these techniques is a customer responsibility anddepends on the customer's ability to evaluate and integrate them into thecustomer's operational environment. While each item may have been reviewed byIBM for accuracy in a specific situation, there is no guarantee that the same orsimilar results will be obtained elsewhere. Customers attempting to adapt thesetechniques to their own environments do so at their own risk.

Any pointers in this publication to external Web sites are provided forconvenience only and do not in any manner serve as an endorsement of theseWeb sites.

Any performance data contained in this document was determined in a controlledenvironment, and therefore, the results that may be obtained in other operatingenvironments may vary significantly. Users of this document should verify theapplicable data for their specific environment.

Reference to PTF numbers that have not been released through the normaldistribution process does not imply general availability. The purpose of includingthese reference numbers is to alert IBM customers to specific information relativeto the implementation of the PTF when it becomes available to each customeraccording to the normal IBM PTF distribution process.


The following terms are trademarks of the International Business MachinesCorporation in the United States and/or other countries:

The following terms are trademarks of other companies:

C-bus is a trademark of Corollary, Inc. in the United States and/or other countries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States and/or other countries.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States and/or other countries.

PC Direct is a trademark of Ziff Communications Company in the United Statesand/or other countries and is used by IBM Corporation under license.

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of IntelCorporation in the United States and/or other countries.

UNIX is a registered trademark in the United States and/or other countrieslicensed exclusively through X/Open Company Limited.

SET and the SET logo are trademarks owned by SET Secure ElectronicTransaction LLC.

Other company, product, and service names may be trademarks or service marksof others.

DB2 ESCONIBM MagstarNetBAY3 NetfinityOpenEdition OS/2OS/390 OS/400RS/6000 S/390ServerProven SPStorWatch System/390Versatile Storage Server


Appendix F. Related publications

The publications listed in this section are considered particularly suitable for amore detailed discussion of the topics covered in this redbook.

F.1 IBM Redbooks

For information on ordering these ITSO publications see “How to get IBMRedbooks” on page 295.

• Tivoli Storage Manager Version 3.7: Technical Guide, SG24-5477

• Using Tivoli Storage Manager in a Clustered Windows NT Environment,SG24-5742

• Backup Solutions for Netfinity SAP R/3 on Windows NT, SG24-5431

• Using Tivoli Data Protection for Workgroups, SG24-5490

• Getting Started with ADSM: A Practical Implementation Guide, SG24-5416

• Introduction to Storage Area Networks, SG24-5470

• Storage Area Networks: Tape Future in Fabrics, SG24-5474

• Tivoli ADSM - Windows 2000 Considerations, SG24-5744

• Implementing Netfinity Disk Subsystems, SG24-2098

• IBM Magstar Tape Product Family: A Practical Guide, SG24-4632

• Magstar MP 3575 Tape Library Dataserver: Multiplatform Implementation,SG24-4983

F.2 IBM Redbooks collections

Redbooks are also available on the following CD-ROMs. Click the CD-ROMsbutton at http://www.redbooks.ibm.com/ for information about all the CD-ROMsoffered, updates and formats.

F.3 Other resources

• ADSTAR Distributed Storage Manager for Windows NT, Administrator’sReference, GC35-0293

• 3447 and 7337 Digital Linear Tape Library Setup and Operation Guide,GA32-0399

CD-ROM Title Collection KitNumber

System/390 Redbooks Collection SK2T-2177Networking and Systems Management Redbooks Collection SK2T-6022Transaction Processing and Data Management Redbooks Collection SK2T-8038Lotus Redbooks Collection SK2T-8039Tivoli Redbooks Collection SK2T-8044AS/400 Redbooks Collection SK2T-2849Netfinity Hardware and Software Redbooks Collection SK2T-8046RS/6000 Redbooks Collection (BkMgr Format) SK2T-8040RS/6000 Redbooks Collection (PDF Format) SK2T-8043Application Development Redbooks Collection SK2T-8037IBM Enterprise Storage and Systems Management Solutions SK3T-3694

http://www.redbooks.ibm.com/


• 3447 and 7337 Digital Linear Tape Library Service Guide, GA32-0400

• IBM 3449 8 mm Tape Library Operator Guide, GA32-0376

• IBM 7331 and 3449 8 mm Tape Library Installation, GA32-0375

• Magstar MP 3570 Tape Subsystems Installation and Planning Guide,GA32-0392

• IBM Netfinity Rack Planning and Installation Guide, S24L-8055

• ARCserve for NetWare Changer Option User Guide (shipped with the product)

• VERITAS Backup Exec for Windows NT Version 7 Administrator’s Guide(shipped with the product)

• 490/980 GB DLT Autoloader User’s Guide (shipped with the product)

F.4 Referenced Web sites

• http://www.redbooks.ibm.com

• http://w3.itso.ibm.com

• http://www.pc.ibm.com/us/compat/storage/matrix.shtml#tape

• http://www.dlttape.com/resource/university/home.html

• http://www.storage.ibm.com/hardsoft/tape/lto/lto.htm

• http://www.ibm.com/pc/us/solutions/accessories/tapedrives.html

• http://www.storage.ibm.com/hardsoft/tape/pubs/prodpubs.htm

• http://www.ibm.com/storage/SANGateway

• http://www.pc.ibm.com/us/compat/clustering/sanmatrix.shtml

• http://www.storage.ibm.com/ibmsan

• http://www.storage.ibm.com/hardsoft/products/fcswitch/refinfo.htm

• http://www.storage.ibm.com/hardsoft/products/sangateway/refinfo.htm

• http://www.legato.com/product_literature_library.htm

• http://www.tivoli.com/support/storage_mgr/adsercli.htm

• http://www.cai.com

• http://support.cai.com/techbases/asnt/arcnt66.html

• http://support.cai.com/Download/patches/asitnt/LO57168.html



• http://support.veritas.com

• http://support.cai.com/techbases/as61/asitnwcdl.html

• http://www.tivoli.com/support/storage_mgr/pubs/admanual.htm#ntV37

• http://www.cheyenne.com/CheyTech/Download/patches/techptch.html

• http://www.seagatesoftware.com/sytosos

• http://www.lto.org

• http://www.tivoli.com/products/index/data_protect

Appendix F. Related publications 293

• http://www.storage.ibm.com/hardsoft/tape/index.html

• http://www.pc.ibm.com/support

• http://www.qic.org

• http://www.tivoli.com/products/index/storage_mgr

• http://www.veritas.com

• http://www.legato.com/Products/index.html

• http://www.cai.com/arcserveit

• http://www.ibmlink.com/usalets

• http://w3.ibm.com


How to get IBM Redbooks

This section explains how both customers and IBM employees can find out about IBM Redbooks, redpieces, andCD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.

• Redbooks Web Site http://www.redbooks.ibm.com/

Search for, view, download, or order hardcopy/CD-ROM Redbooks from the Redbooks Web site. Also readredpieces and download additional materials (code samples or diskette/CD-ROM images) from this Redbookssite.

Redpieces are Redbooks in progress; not all Redbooks become redpieces and sometimes just a few chapters willbe published this way. The intent is to get the information out much quicker than the formal publishing processallows.

• E-mail Orders

Send orders by e-mail including information from the IBM Redbooks fax order form to:

• Telephone Orders

• Fax Orders

This information was current at the time of publication, but is continually subject to change. The latest informationmay be found at the Redbooks Web site.

In United StatesOutside North America

e-mail [email protected] information is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)Canada (toll free)Outside North America

1-800-879-27551-800-IBM-4YOUCountry coordinator phone number is in the “How to Order” section atthis site:http://www.elink.ibmlink.ibm.com/pbl/pbl

United States (toll free)CanadaOutside North America

1-800-445-92691-403-267-4455Fax phone number is in the “How to Order” section at this site:http://www.elink.ibmlink.ibm.com/pbl/pbl

IBM employees may register for information on workshops, residencies, and Redbooks by accessing the IBMIntranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materialsrepository for workshops, presentations, papers, and Web pages developed and written by the ITSO technicalprofessionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ forredbook, residency, and workshop announcements.

IBM Intranet for Employees

http://www.redbooks.ibm.com/

http://www.elink.ibmlink.ibm.com/pbl/pbl



mailto:[email protected]

http://w3.itso.ibm.com/

http://w3.ibm.com/





IBM Redbooks fax order formPlease send me the following:

We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card notavailable in all countries. Signature mandatory for credit card payment.

Title Order Number Quantity

First name Last name

Company

Address

City Postal code

Telephone number Telefax number VAT number

Invoice to customer number

Country

Credit card number

Credit card expiration date SignatureCard issued to


Abbreviations and acronyms

ADSM ADSTAR Distributed StorageManager

AIX advanced interactive executive

AME advanced metal evaporated

ANSI American National StandardsInstitute

API application programming interface

ASCII American National Standard Codefor Information Interchange

ANSI American National StandardsInstitute

ASM application specific modules

ASPI advanced SCSI programminginterface

ATAPI advanced technology AttachmentPacket Interface

ATM asynchronous transfer mode

BIOS basic input/output system

CD-ROM compact disk read-only memory

DASD direct access storage device

DAT digital audio tape

DCLZ data compression Lempel-Ziv

DLT digital linear tape

DOS disk operating system

ECC error checking and correcting

ECMA European Computer ManufacturersAssociation

EIA Electronics Industries Association

EIDE enhanced integrated driveelectronics

EMEA Europe/Middle East/Africa

ESCON enterprise systems connection

FAT file allocation table

FC Fibre Channel

FC-AL Fibre Channel Arbitrated Loop

FDDI fiber distributed data interface

FTP file transfer protocol

F/W fast/wide

GB gigabytes

GBIC gigabit interface connector

GUI graphical user interface

HGA head guide assembly

HPFS high-performance file system

HSM hierarchical storage manager

HTML hypertext markup language

HVD high voltage differential

IBM International Business MachinesCorporation

IP Internet Protocol

IPI intelligent peripheral interface

IPL initial program load

IPX Internetwork Packet eXchange

ITSO International Technical SupportOrganization

JRE Java runtime environment

LAN local area network

LCD liquid crystal display

LED light-emitting diode

LTO Linear Tape Open

LUN logical unit number

LVDS low-voltage differential SCSI

LVDS low-voltage differential SCSI

MB megabytes

MIA Media Interface Adapter

MMF Multi-Mode Fiber

MSBF mean swap between failures

MTBF mean time between failures

MVS multiple virtual storage

NDS NetWare Directory Services

NLM NetWare loadable module

NTFS NT file system

OCP operator control panel

ODBC open database connectivity

PBC Port Bypass Circuit

PCI peripheral component interconnect

PDF portable document format

PMC PCI Mezzanine Card

POST power-on self-test

PTF program temporary fix

QIC quarter-inch cartridge

QMS queue management services

RAID redundant array of independent disks


RAM random access memory

RDBMS relational database managementsystem

RF radio frequency

RMI remote method invocation

RPQ request for price quotation

SAN storage area network

SAP Systeme, Anwendungen undProgramme in der Datenverarbeitung(Systems, Products, and Programs inData Processing)

SC standardized connector

SCO Santa Cruz Operation, Inc.

SCSI small computer system interface

SMF Single-Mode Fiber

SNA systems network architecture

SNMP simple network managementprotocol

SPX Sequenced Packet eXchange

SQL structured query language

TCP/IP Transmission ControlProtocol/Internet Protocol

TDP Tivoli Data Protection

TSM Tivoli Storage Manager

UEC Unit Error Code

UNC Universal Naming Convention

URL Uniform Resource Locator

VHD very high density

WAN wide area network


Index

Numerics4 mm tape

See DAT8 mm tape

20/40 GB drive 583449 tape library 83advanced metal evaporated media 39format 39Mammoth technology 39mean time between failure 40metal particle media 39

AAccelis 45ADSTAR Distributed Storage Manager

See Tivoli Storage Manageradvanced metal evaporated media 39agents, backup 23archiving 3ARCserve for NetWare

configuration 228installation 224managing 233

ARCserveITbackup agent for open files 144Certified Device List 147client agent support 144concepts 145concepts, NetWare 148configuration (Windows NT) 221data migration support 144database backup agents 144description 143disaster recovery option 143editions 143for NetWare 147image option 144installation (Windows NT) 217networked library option 144optical library support 144product patch 147RAID option 144replication option 143supported devices (NetWare) 149supported devices (Windows NT) 146system requirements (Windows NT) 217tape library options 144Web site 145

autoloaderSee tape libraries

automatic vaulting 15, 17

Bbackup

agents 23archiving 3

automation 3classes, in NetBackup 138control files 24cumulative incremental 5database servers 23differential 5expiration time 28full 4fuzzy 26incremental 4LAN-free 15log files 24methodologies 4number of copies 28number of tapes 9patterns 5performance 19SAN implementations 14scheduling 19server 10server-free 16simulated offline 25software 123software support matrix 123storage management 3tape rotation 6terminology 3throughput 22why backups are needed 3

bandwidth considerations 20branch office model 13

Ccauses of data loss 3centralized storage administration 10changed data 5Class of Service 276client nodes for Tivoli Storage Manager 171collocation 8compression 21compression, selecting hardware versus software 22copy group 129cost of tape versus disk 17cumulative incremental backup 5

DDAT

Digital Audio TapeSee also DDS12/24 GB DDS-3 drive 6420/40 GB DDS-4 drive 624 mm format 40

dataamount to be backed up 20causes of loss 3changed 5collocation 8


compression 40, 51, 55management with Tivoli Storage Manager 127rate of change 3storage within databases 23

databasecontrol files 24export 25high-availability 25log files 24mirroring 25offline backup 25online backup 26server backup 23terminology 24

DC6000See QIC

DDSDigital Data StorageDDS-2 41DDS-3 41DDS-4 41DDS-DC 41DDS-SC 40evolution 41Media Recognition System 40

differential backup 5Digital Audio Tape

See DATDigital Data Storage

See DDSDigital Linear Tape

See DLTdirect tape connection 10disaster recovery 13, 17, 143, 150distributed site 11DLT

Digital Linear Tape20/40 GB drive 54280/560 GB autoloader 743447 tape library 7735/70 GB drive 5140/80 GB drive 474000 drive 37490/980 GB library 697000 drive 37characteristics 37external SCSI enclosure 48, 53, 57format 36tape path 38Web site 37

Eenvironmental control 4expansion options for ARCserveIT 143expiration 129expiration time 28

Ffabric, SAN 106

failure rate 29Fibre Channel

cabling 111Class of Service 276ESCON 280GBIC 110hub 109long-wave 17loop 276physical layers 275point-to-point 276SAN components 277SAN technology 275standardized connector 111switch 106switched 276tape storage 17topologies 276

full backup 4fuzzy backup 26

Ggrandfather-father-son 6

Hhardware compression 21hierarchical storage 22hierarchical storage management 128, 132high availability 3, 15host adapter 105host node 105

IIBM

data storage heritage 1incremental backup 4intelligent peripheral interface 275intermediate backup server 11

LLAN-free backup 15Legato NetWorker

add-on components 141client resource 141concepts 141configuration 212description 141device management 213directive resources 141editions 141installation 210media labeling 214resources 141supported devices 143system requirements 210

Lempel-Ziv compression algorithm 51, 55library, tape 27, 33Linear Tape Open

301

See LTOlog files 24long-wave GBIC 110low voltage differential SCSI 47LTO

Linear Tape OpenAccelis 45, 46Ultrium 45, 46

LZ-1 compression algorithm 51, 55

MMagstar

3570 MP Fast Access Linear tape cartridge 433570 tape library 933575 tape library 98B-Format cartridge 43, 44C-Format cartridge 43, 44C-XL format cartridge 45Model C tape drive 43multi-path feature 100

Mammoth tape technology 58Mammoth technology 39management class 129management of tape media 5mean time between failure 28metal particle media 39methodologies 4migration 132mount object 136multi-tier model 13

NNetfinity

3000 63, 65, 683500 49, 60, 685000 53, 56, 60, 63, 65, 685500 49, 53, 56, 60, 63, 655600 49, 56, 60, 637000 49, 53, 56, 60, 66, 688500R 50, 56, 60external SCSI half-height enclosure 60, 63, 66, 68Fibre Channel Hub 109Fibre Channel PCI Adapter 105Fibre Channel Switch 105NetMEDIA storage expansion unit 48, 53, 57, 60, 64,66, 68tape drive support matrix 33

network bandwidth 11

OOS/2

Tivoli Storage Manager 194

Ppartition data object 136pattern

full/differential 7full/incremental 5

incremental forever 8of backups 5

patternseffect on time to back up 9

performancebandwidth 20compression 21network 20optimizing 19scheduling backups 19

Poisson formula 29policy domain 129policy set 129pooling, tape 18

QQIC

Quarter-Inch Cartridge10/20 GB NS drive 663020 tape format 423095 tape format 42format 42format support matrix 43NS20 drive 42TR1, TR2, and TR3 drives 42TR4 drive 42TR5 drive 42Travan technology 42

Quantum, DLT technology 36Quarter-Inch Cartridge

See QIC

Rreclamation 129reclamation, of tape 8reliability 28replication 135resources, in Legato NetWorker 141roll back 24roll-forward 24rotation schedules 6

SSAN

storage area networkbackup implementations 14cost benefits 17Data Gateway Router 107definition 14fabric 106Fibre Channel attached tape 17Fibre Channel Switch 105interconnects 277management software 105PCI Adapter 105performance 15products 107recommended redbooks 14


sample configuration 114StorWatch 105support matrix Web site 112supported configurations 112switch 18Web site 105

scheduling backups 19SCSI ID 50, 54, 57, 61, 73, 80Seagate Backup Exec Autoloader Module 150Seagate Backup Exec IntelligentDisaster Recovery Option149Seagate Sytos Premium

for OS/2 262installation 263supported devices 262system requirements 263Web site 265

server storage hierarchy 13server-free backup 16short-wave GBIC 110simulated offline backup 25single server model 10software 35software compression 21software support matrix 123split configuration 18standardized connector 111storage area network

See SANstorage environment 4storage management 3storage policies 4storage pool 130storage units 138StorWatch

SAN management software 105support matrix 33

Ttable space 24tape

See also tape drivesSee also tape libraries8 mm format 39Accelis 45capacity 27cost versus disk 17costs 5devices 27direct connection 10DLT format 36drive format matrix 47drive selection 27Fibre Channel attached 17format 36libraries 27LTO 45management 5migration of data to 23Netfinity drives 33

Netfinity libraries 33Netfinity support matrix 33number required, examples 9pooling 18, 114QIC format 42reclamation 8reliability 28rotation schedules 6software, supported 35storage area network 105Ultrium 45

tape drives10/20 GB NS QIC 6612/24 GB 4 mm tape 64, 19020/40 GB 4 mm tape 62, 18920/40 GB 8 mm tape 58, 18920/40 GB DLT 54, 18835/70 GB DLT 51, 18840/80 GB DLT 47, 187Magstar 3570 MP drivers 215

tape libraries280/560 GB DLT autoloader 74, 1903447 DLT library 77, 1913449 8 mm tape library 83, 1923570 Magstar MP 93, 1923575 Magstar MP 98, 193490/980 GB DLT 69

tape librarymodes of operation 71, 75, 79, 87, 89, 96

terminologybackup 3database 24

throughput 22time to complete a backup, examples

backuptime to perform, examples 9

Tivoli Data Protection for application clients 125Tivoli Data Protection for Workgroups

autoloader, use for disaster recovery 207backup/recovery tool 126configuring tape devices 210disaster recovery 207enterprise integration 136host 135installation and configuration 204mount object 136operation 206partition data object 136replicate 135supported devices 137system requirements 204terminology 135

Tivoli Disaster Recovery Manager 125Tivoli Space Manager 125Tivoli Storage Manager

adding client nodes 171allocating storage pools 177archive and retrieve 127automated client operations 132backup and restore 126

303

base product 125command interface 164communications protocol 181configuration 164configuring tape devices 186copy group 129data management 127Database Volume Wizard 178description 124disk configuration 162expiration 129for Windows NT and OS/2 123installation (for Windows NT) 159license files 165macros 187management class 129media labeling 183Network Client Options File Wizard 181ODBC driver 161Performance Configuration Wizard 174platforms 124policy 127policy domain 129policy set 129product manuals 159reclamation 129Recovery Log Volume Wizard 179sample SAN configuration 114Scheduler Configuration Wizard 172scheduler service 167storage devices and media 129storage media definitions 168storage pools and volumes 130supported devices 134system requirements 159system requirements for OS/2 194terminology 125V2.1 for OS/2 194Windows NT services 166

topologies, system and storage 10topology

branch office model 13direct tape connection 10multi-tier model 13single server model 10two-tier model 11

Travan technologySee QIC

two-tier model 11

UUltrium 45

Vvaulting, automatic 15VERITAS Backup Exec

add-on products 149Agent Accelerator for Windows NT 150Agent for Lotus Notes server 150

Agent for Microsoft Exchange Server 150Agent for Microsoft SQL Server 150Agent for NetWare Server 150Agent for Oracle database servers 150automated backup rotation schedule 249Backup Exec Assistant 247client 248concepts 151configuration (NetWare) 260configuration (Windows NT) 244configuring tape drives 252description 149device management 152device operations 153editions 149for Novell NetWare 155IBM ADSM option 150installation (NetWare) 254installation (Windows NT) 242manual backups 249media management 153media operations 155media overwrite protection 154, 245Open File option 150RAID director option 150restoring data 251shared storage option 150supported devices (NetWare) 158supported devices (Windows NT) 155system requirements (NetWare) 254virus protection 246Web site 155

VERITAS NetBackupbackup and restore processes 139backup classes 138concepts and terminology 138description 137Media Manager 140scheduling 138storage units 138supported devices 140

WWeb site

ARCserveIT 145Certified Device List for ARCserveIT 147Fibre Channel switch manuals 107IBM SAN solutions 105Netfinity ServerProven 48Netfinity tape drive support matrix 33patches for ARCserveIT 147Quantum DLT University 37SAN configurations 112Seagate Sytos Premium 265Tivoli Storage Manager manuals 159VERITAS Backup Exec 155


IBM Redbooks review

Your feedback is valued by the Redbook authors. In particular we are interested in situations where a Redbook"made the difference" in a task or problem you encountered. Using one of the following methods, please review theRedbook, addressing value, subject matter, structure, depth and quality as appropriate.

• Use the online Contact us review redbook form found at http://www.redbooks.ibm.com/• Fax this form to: USA International Access Code + 1 914 432 8264• Send your comments in an Internet note to [email protected]

Document NumberRedbook Title

SG24-5218-01Netfinity Tape Solutions

Review

What other subjects would youlike to see IBM Redbooksaddress?

Please rate your overallsatisfaction:

O Very Good O Good O Average O Poor

Please identify yourself asbelonging to one of the followinggroups:

O CustomerO Business PartnerO Solution DeveloperO IBM, Lotus or Tivoli EmployeeO None of the above

Your email address:The data you provide here may beused to provide you with informationfrom IBM or our business partnersabout our products, services oractivities.

O Please do not use the information collected here for future marketing orpromotional contacts or other communications beyond the scope of thistransaction.

Questions about IBM’s privacypolicy?

The following link explains how we protect your personal information.http://www.ibm.com/privacy/yourprivacy/



http://www.ibm.com/privacy/yourprivacy/

SG24-5218-01

Printed in the U.S.A.

Netfinity

Tape

SolutionsSG

24-5218-01

®

Netfinity tape solutions sg245218

Technology

Transcript of Netfinity tape solutions sg245218