This chapter describes the supported hardware for the TruCluster Server product. It also contains some specific requirements for some of the hardware components.
See the TruCluster Server Release Notes for the latest information about supported hardware and firmware revisions.
Table 3-1 lists the supported systems by product and the SCSI adapter used for shared SCSI buses on each system. Section 3.1.1 provides the specific requirements for member systems in a TruCluster Server cluster.
| System | SCSI Adapter |
| AlphaServer 800 | KZPSA |
| AlphaServer 1000 | KZPSA |
| AlphaServer 1000A | KZPSA |
| AlphaServer 1200 | KZPSA |
| AlphaServer 2000 | KZPSA |
| AlphaServer 2100 | KZPSA |
| AlphaServer 2100A | KZPSA |
| AlphaServer 4000 | KZPSA |
| AlphaServer 4000A | KZPSA |
| AlphaServer 4100 | KZPSA or KZPBA-CB |
| AlphaServer 8200 and 8400 | KZPSA or KZPBA-CB |
The requirements for member systems in a TruCluster Server cluster are as follows:
Each supported member system requires a minimum firmware revision. See the TruCluster Server Release Notes for information about required firmware.
TruCluster Server supports up to eight systems in a cluster.
TruCluster Server does not support the XMI CIXCD on an AlphaServer 8200 or 8400 system.
Ethernet and Asynchronous Transfer Mode (ATM) networks are supported by TruCluster Server. The following sections describe these adapters.
The following Ethernet network adapters are supported:
DE500 (PCI/Fast Ethernet)
DEFPA (PCI/FDDI)
DE435 (PCI/Ethernet)
DEFEA (EISA/FDDI)
DE422 (EISA/Lance Ethernet)
DE425 (EISA/Ethernet)
DEMNA (XMI/Ethernet)
DEMFA (XMI/FDDI)
PMAD (TURBOchannel/Ethernet)
DEFTA (TURBOchannel/FDDI)
DEFZA (TURBOchannel/FDDI)
Asynchronous Transfer Mode (ATM) is a high-speed, connection-oriented, cell-switched technology. It meets the real-time networking requirements of multimedia applications, while providing increased bandwidth for current installations.
The TruCluster Server product supports the use of ATM Lan Emulation as a network for client access.
ATM is a cell-switching and multiplexing technology where the sender negotiates a path with the network for a connection to the destination.
Information to be sent, which may be data, voice, or video, is segmented into a 53-byte, fixed-length cell (48 bytes of actual information with a 5-byte header).
An ATM network consists of the following components:
ATM switch: A specialized system that connects one end system to another and forwards, or switches, ATM cells from one end system to another. The ATM switch contains information necessary to route the cells from one end system to another based upon cell header information.
End system: A system physically connected to a switch. It communicates with other end systems through one or more switches.
The DGLPB-AB ATMworks 350 155 MB/sec multimode fiber optics PCI adapter is supported.
Any high-performance ATM switch with 155 MB/sec ports is supported. A minimum of one ATM switch is required for each ATM circuit.
To connect a member system to a shared SCSI bus, you must install a SCSI bus adapter in an I/O bus slot. Table 3-2 describes the supported SCSI adapters.
| SCSI Bus Adapter | Transmission Method |
| KZPBA-CB | Differential UltraSCSI |
| KZPSA-BB | UltraSCSI, Differential |
The following sections describe the SCSI adapters in more detail.
KZPSA-BB SCSI adapters have the following restrictions:
If you have a KZPSA-BB adapter installed in an
AlphaServer 1000, 1000A, 2000, 2100, or 2100A system, you must
set the
bus_probe_algorithm
console variable to
new
by entering the following command:
>>>set bus_probe_algorithm new
On AlphaServer 1000A and 2100A systems, updating the firmware on the KZPSA-BB SCSI adapter is not supported when the adapter is behind the PCI-to-PCI bridge.
Compaq's Tru64 UNIX operating system supports a maximum of 48 SCSI buses. Only 30 shared SCSI buses are supported in a TruCluster Server cluster.
Each system supporting the KZPBA-CB UltraSCSI host adapter limits the number of adapters that may be installed. The maximum number of KZPBA-CB UltraSCSI host adapters supported with the TruCluster Server product follow:
AlphaServer 800: 2
AlphaServer 1000A and 1200: 4
AlphaServer 4000: 8; Only one KZPBA-CB is supported in IOD0 (PCI0).
AlphaServer 4100: 5; Only one KZPBA-CB is supported in IOD0 (PCI0).
AlphaServer 8x00: A maximum of 8 KZPBA-CB options are supported. To achieve 30 shared buses, use KZPSA-BBs for the remaining 22 shared buses.
The KZPBA-CB is supported on the DWLPB only, it is not supported on the DWLPA module.
A maximum of four HSZ50 or HSZ70 RAID array controllers can be placed on a single KZPBA-CB UltraSCSI bus. Only two redundant pairs of array controllers are allowed on one SCSI bus.
The KZPBA-CB requires ISP 1020/1040 firmware Version 5.57, available with the system SRM console firmware on the Alpha Systems Firmware 5.3 Update CD.
The maximum length of any SCSI bus segment is 25 meters, including the length of the SCSI bus cables and SCSI bus internal to the SCSI adapter, hub, or storage device.
See the KZPBA-CB UltraSCSI Storage Adapter Module Release Notes (AA-R5XWD-TE) for more information and a list of supported disk devices.
Table 3-3 describes the supported Memory Channel hardware.
| Memory Channel Hardware Component | Designation | Description |
| Memory Channel PCI adapter | CCMAA-AA or CCMAA-BA | Memory Channel PCI adapter used as the cluster interconnect. |
| Memory Channel hub | CCMHA-AA | PC-class enclosure that is populated with line cards and used to connect Memory Channel adapters. A hub is required if you have more than two member systems. |
| Line card | CCMLA-AA | Installed in a Memory Channel hub to allow connection of more than two systems. |
| Link cable | BC12N-10 (10 meters) | Connects a Memory Channel adapter to a hub or one Memory Channel adapter to another Memory Channel adapter (virtual hub). |
The Memory Channel hardware restrictions are as follows:
A Memory Channel interconnect can use either virtual hub mode (two member systems connected without a Memory Channel hub) or standard mode (two or more systems connected to a hub).
The maximum length of a Memory Channel link cable is 3 meters (10 feet).
Always check a Memory Channel link cable for bent or broken pins. Be sure that you do not bend or break any pins when you connect or disconnect a cable.
Table 3-4 lists the supported disk devices for shared SCSI buses and the data paths available for each disk type.
| Disk | Data Path |
| RZ26 | Narrow |
| RZ26L | Narrow and wide |
| RZ26N | Narrow and wide |
| RZ28 | Narrow and wide |
| RZ28B | Narrow |
| RZ28D | Narrow and wide |
| RZ28L | Narrow and wide |
| RZ28M | Narrow and wide |
| RZ29 | Narrow and wide |
| RZ29B | Narrow and wide |
| RZ29L | Narrow and wide |
| RZ40 | Narrow and wide |
| RZ40L | Narrow and wide |
| RZ1BB | Narrow and wide |
| RZ1CB | Narrow and wide |
| RZ1DB | Narrow and wide |
The restrictions for disk devices are as follows:
Supported disks require a minimum firmware revision. See the TruCluster Server Release Notes for information about the required firmware.
Disks on shared SCSI buses must be installed in external storage shelves.
The TruCluster Server product does not support Prestoserve on any disk in a cluster, regardless of whether it exists on a shared bus or a on a bus local to any given member.
RAID controllers provide high performance, high availability, and high connectivity access to SCSI devices through a shared SCSI bus. The following RAID controllers are supported in a TruCluster Server cluster.
SWXRA-Z1 (HSZ20)
HSZ40-Bx
HSZ40-Cx
HSZ50-Ax
HSZ70
The HSZ40 controller can be configured with one to four SCSI IDs and with one to eight logical unit numbers (LUNs) for each SCSI ID. For any number of disks, having more SCSI IDs with fewer LUNs for each SCSI ID provides better performance than a configuration with fewer SCSI IDs and more LUNs.
Each RAID controller requires a specific minimum Hierarchical Storage Operating Firmware (HSOF) revision. See the TruCluster Server Release Notes for information about required HSOF revisions.
TruCluster Server supports single-controller, single-bus HSZ40 array configurations and dual-controller, single-bus HSZ40 configurations.
Table 3-5 lists the supported disk storage shelves.
| Storage Shelf | Transmission Mode | Data Path | Internal SCSI Bus Length |
| BA350 | Single-ended | Narrow | 0.9 Meter |
| BA353 | Single-ended | Narrow | 0.9 Meter |
| BA356 | Single-ended | Wide | 1.0 Meter |
| UltraSCSI BA356 | UltraSCSI Single-ended | Wide | 1.0 Meter |
Disk storage shelves have the following restrictions:
Storage shelves must be external with an independent power supply.
You must connect a SCSI signal converter to a storage shelf that has a single-ended SCSI interface, such as a BA350, BA353, or non-UltraSCSI BA356 storage shelf.
A shared differential UltraSCSI bus is connected to the DS-BA35X-DA personality module in an UltraSCSI BA356.
The following sections discuss these storage shelves in more detail.
Up to seven narrow (8-bit) StorageWorks building blocks (SBB) can be installed in the BA350. Their SCSI IDs are based upon the slot they are installed in. For instance, a disk installed in BA350 slot 0 has SCSI ID 0, a disk installed in BA350 slot 1 has SCSI ID 1, and so forth.
The BA350 storage shelf contains internal SCSI bus termination and a SCSI bus jumper. There are occasions when the termination must be removed from the BA350 (for example, when daisy chaining two BA350s together). The jumper is not removed during normal operation.
The BA350 can be set up for two-bus operation, but that option is not very useful for a shared SCSI bus and is not covered in this manual.
Figure 3-1 shows the relative locations of the BA350 SCSI bus terminator and SCSI bus jumper. They are accessed from the rear of the box. For operation within a TruCluster Server cluster, you must install the J jumper.
The BA353 is probably of little use in TruCluster Server configurations; it only has three slots for shared disks.
The SCSI ID for disks installed in a BA353 is defined by device address switches on the back of the BA353. The switches are located to the left of the SCSI input and SCSI output connectors, as shown in Figure 3-2.
The switches are marked as Left (Slot 1), Center (Slot 2), and Right (Slot 3). Slot 1 is the leftmost slot when the BA353 is viewed from the front.
The On position of a switch generates a logic 1 in the device address, and switch one is the least significant bit (LSB) in the device address. The SCSI IDs shown in Figure 3-2 would be 0, 1, and 2, left, center, and right.
There are two variations of the BA356 used in TruCluster Server clusters: the UltraSCSI BA356 and the non-UltraSCSI BA356.
An example of the non-UltraSCSI BA356 is the BA356-KC, which has a wide, single-ended internal SCSI bus. It uses the BA35X-MH 16-bit personality module and has a 150-watt power supply.
The DS-BA356-JF (or DS-BA356-KH) has a single-ended, wide UltraSCSI bus. The DS-BA35X-DA personality module provides the interface between the internal, single-ended UltraSCSI bus and the shared, differential UltraSCSI bus. The UltraSCSI BA356 uses an 180-watt power supply.
The non-UltraSCSI BA356, like the BA350 can hold up to seven StorageWorks building blocks (SBBs). However, unlike the BA350, these SBBs are wide devices. Also, like the BA350, the SBB SCSI IDs are based upon the slot they are installed in, but the switches on the personality module (BA35X-MH) have to be set to off, the default switch positions. Verify that the personality module switches are all off.
Figure 3-3 shows the relative location of the BA356 SCSI bus jumper, BA35X-MF. The jumper is accessed from the rear of the box. For operation within a TruCluster Server cluster, you must install the J jumper in the normal position, behind slot 6. Note that the SCSI bus jumper is not in the same position in the BA356 as in the BA350.
Termination for the BA356 single-ended bus is on the personality module, and is active unless a cable is installed on JB1 to daisy chain two BA356s together. In this case, when the cable is connected to JB1, the personality module terminator is disabled.
Like the BA350, you can set up the BA356 for two-bus operation by installing a SCSI bus terminator (BA35X-ME) in place of the SCSI bus jumper. However, like the BA350, two-bus operation in the BA356 is not very useful for a TruCluster Server cluster.
You can use the position behind slot 1 to store the SCSI bus terminator or jumper.
Figure 3-3 shows the relative locations of the BA356 SCSI bus jumper and the position for storing the SCSI bus jumper, if you do install the terminator. For operation within a TruCluster Server cluster, you must install the J jumper.
Note that JA1 and JB1 are located on the personality module (in the top of the box when it is standing vertically). JB1, on the front of the module, is visible. JA1 is on the left side of the personality module as you face the front of the BA356, and is hidden from the normal view.
To determine if a jumper module or terminator module is installed in a BA356, remove the devices from slots 1 and 6 and note the following pin locations (see Figure 3-4):
The identification pin on a jumper module aligns with the top hole in the backplane.
The identification pin on a terminator module aligns with the bottom hole in the backplane.
The UltraSCSI BA356 can also hold up to seven StorageWorks building blocks (SBBs). These SBBs are UltraSCSI single-ended wide devices. The SBB SCSI IDs are based upon the slot they are installed in, but the SCSI bus address switches (S3-1 through S3-7) on the personality module (BA35X-DA) have to be set to OFF, the default switch positions. Verify that the personality module SCSI bus address switches are all OFF.
The jumper module is positioned behind slot 6 as with the non-UltraSCSI BA356 shown in Figure 3-3. For operation within a TruCluster Server cluster, you must install the J jumper. You verify the presence or absence of the jumper or terminator modules the same as for the non-UltraSCSI BA356, as shown in Figure 3-4.
Termination for both ends of the UltraSCSI BA356 internal, single-ended bus is on the personality module, and is always active. Termination for the differential UltraSCSI bus is also on the personality module, and is controlled by the SCSI bus termination switches, switch pack S4. For normal cluster operations, S4-1 and S4-2 should normally be ON. Section 4.5.2.2 discusses these switches in more detail.
If you are using a storage shelf with a single-ended SCSI interface in your TruCluster Server hardware configuration, you must connect it to a SCSI signal converter. SCSI signal converters convert narrow or wide, single-ended SCSI to wide, differential SCSI. Some signal converters are standalone desktop units and some are StorageWorks building blocks (SBBs) that you install in storage shelves disk slots.
Note
The UltraSCSI hubs could probably be listed here, but they are covered separately.
Table 3-6 lists the supported SCSI signal converters.
| Device | Description |
| DWZZA-AA | Standalone unit |
| Converts single-ended, narrow SCSI to differential, wide SCSI. Use with a BA350 or BA353 storage shelf. | |
| DWZZA-VA | SBB |
| Converts single-ended, narrow SCSI to differential, wide SCSI. Install in a BA350 or BA353 storage shelf. | |
| DWZZB-AA | Standalone unit |
| Converts single-ended, wide SCSI to differential, wide SCSI. Use with a BA356 storage shelf. | |
| DWZZB-VW | SBB |
| Converts single-ended, wide SCSI to differential, wide SCSI. Install in a BA356 storage shelf. |
The restrictions for SCSI signal converters are as follows:
For each type of SCSI signal converter, a TruCluster Server cluster requires a specific, minimum hardware revision. See the TruCluster Server Release Notes for information about required hardware revisions.
If you remove the cover from a standalone unit, be sure to replace the star washers on all four screws that hold the cover in place when you reattach the cover. If the washers are not replaced, the SCSI signal converter may not function correctly because of noise.
If you want to disconnect a SCSI signal converter from a shared SCSI bus, you must turn off the signal converter before disconnecting the cables. To reconnect the signal converter to the shared bus, connect the cables before turning on the signal converter. Use the power switch to turn off a standalone SCSI signal converter. To turn off an SBB SCSI signal converter, pull it from its disk slot.
If you observe any "BUS Hung" messages, your DWZZA signal converters may have the incorrect hardware. In addition, some DWZZA signal converters that appear to have the correct hardware revision may cause problems if they also have serial numbers in the range of CX444xxxxx to CX449xxxxx.
To upgrade a DWZZA-AA or DWZZA-VA signal converter to the correct revision, use the appropriate Field Change Order (FCO), as follows:
DWZZA-AA-F002
DWZZA-VA-F001
The DS-DWZZH series UltraSCSI hubs are SCSI-2 and draft SCSI-3 compliant SCSI 16-bit signal converters capable of data transfer rates of up to 40 MB per second.
They could be listed with the other SCSI bus signal converters, but as they are used differently in TruCluster Server clusters, they will be handled differently in this document.
A DS-DWZZH UltraSCSI hub is installed in a StorageWorks DS-BA356 shelf (which has the required 180-watt power supply). Cluster member systems and HSZ50 or HSZ70 RAID array controllers are radially connected to the hub ports.
Improves the reliability of the detection of cable faults.
Provides for bus isolation of cluster systems while allowing the remaining connections to continue to operate.
Allows for more separation of systems and storage in a cluster configuration because each SCSI bus segment can be up to 25 meters in length. This allows a total separation of nearly 50 meters between a system and the storage.
The DS-DWZZH-03 and the DS-DWZZH-05 UltraSCSI hubs are supported in a TruCluster Server cluster.
If you are using shared SCSI buses, you must determine if you need cables with connectors that are low-density 50-pins, high-density 50-pins, high-density 68-pins (HD68), or Very High Density Cable Interconnect (VHDCI) 68-pins (UltraSCSI). You also have the choice of straight or right-angle connectors. In addition, each supported cable comes in various lengths. Use the shortest possible cables to adhere to the limits on SCSI bus length.
Table 3-7 describes each supported cable and the context in which you would use the cable.
| Cable | Connector Density | Pins | Configuration Use |
| BN21V-0B | One high, two low | 50-pin | This Y cable attaches to a PMAZC and can be terminated if necessary. |
| BN21W-0B | Three high | 68-pin | A Y cable that attaches to a KZPSA, HSZ40, HSZ50, or the differential side of a signal converter. It can be terminated if necessary. |
| BN21R or BN23G | One high, one low | 50-pin | Connects narrow devices such as the BA350, or BA353 to the single-ended side of a DWZZA signal converter. (Replaces the BC09D cable.) |
| BN21H or BN21J | Two high | 50-pin | Connects narrow devices, such as a BA350 or a BA353. |
| BC19J or BC06P [Footnote 2] | Two low | 50-pin | Connects BN21V-0B Y cables to each other or the single-ended end of a DWZZA to a TZ885 or TZ887. |
| BN21M | One low, one high | 50-pin LD to 68-pin HD | Connects the single-ended end of a DWZZB-AA to a TZ885 or TZ887. |
| BN21K or BN21L | Two HD68 | 68-pin | Connects BN21W Y cables or wide devices. For example, connects HSZ40s, the differential sides of two SCSI signal converters, or a DWZZB-AA to a BA356. |
| BN38C or BN38D | One HD68, one VHDCI | VHDCI to HD68 | Connect a high-density (HD68) Y cable (BN21W-0B) to a VHDCI trilink. |
| BN37A | Two VHDCI | VHDCI to VHDCI | Connect two VHDCI trilinks to each other. |
The requirement for SCSI cables is as follows:
Always check a SCSI cable for bent or broken pins. Be sure that you do not bend or break any pins when you connect or disconnect a cable.
Table 3-8 describes the supported SCSI terminators and the context in which you would use them.
| Terminator | Density | Pins | Configuration Use |
| H879-AA | High | 68-pin | Terminates an H885-AA trilink connector or BN21W-0B Y cable. |
| 12-37004-04 | High | 50-pin | Terminates a BA353 input connector. |
| H8863-AA | VHDCI | 68-pin | Terminate a VHDCI trilink connector. |
Table 3-9 describes the supported trilink connectors and the context in which you would use them.
| Trilink Connector | Number of Connectors | Pins | Density | Configuration Use |
| H885-AA | Three | 68-pin | High | Attaches to high-density, 68-pin cables or devices, such as a KZPSA, HSZ40, HSZ50, or the differential side of a SCSI signal converter. Can be terminated with an H879-AA terminator if necessary. |
| H8861-AA | Three | 68-pin | VHDCI | Attaches to VHDCI 68-pin cables, UltraSCSI BA356 JA1, HSZ70 RAID controllers. Can be terminated with an H8863-AA terminator if necessary. |
The requirement for trilink connectors is as follows:
If you connect a SCSI cable to a trilink connector, do not block access to the screws that mount the trilink, or you will be unable to disconnect the trilink from the device without disconnecting the cable.
Do not install an HD68 trilink if installing it will block an adjacent peripheral component interconnect (PCI) port. Use a BN21W-0B Y cable instead.
The following tape devices are supported by the TruCluster Server; product:
TZ88--The TZ88 is a streaming Digital Linear Tape (DLT) cartridge tape device capable of holding up to 40 GB data per CompacTape IV cartridge when using 2:1 compression. It is capable of storing/retrieving data at a rate of up to 10.8 GB per hour.
Two TZ88 models are supported: The TZ88N-TA, a table-top model, and the TZ88N-VA, a StorageWorks building block (SBB) 5.25-inch carrier. The SBB version takes up three slots in a BA350 StorageWorks enclosure.
The TZ88 uses CompacTape III, CompacTape IIIXT, or CompacTape IV media.
TZ89--Another streaming DLT cartridge tape drive, the TZ89 has a capacity of up to 70 GB per cartridge (CompacTape IV) when using 2:1 compression. In compressed mode it can back up 36 GB of data per hour.
Two TZ89 models are supported: The DS-TZ89N-TA, a table-top model, and the DS-TZ89N-VW, a StorageWorks building block (SBB) 5.25-inch carrier. The SBB version takes up three slots in a BA356 StorageWorks enclosure.
The TZ89 also uses CompacTape III, CompacTape IIIXT, or CompacTape IV media.
TZ885--The TZ885 is a DLT magazine tape subsystem combining a cartridge tape drive and an automatic cartridge loader. It uses a five-cartridge (CompacTape IV) removable magazine to provide a mini-tape library with a total capacity of 200 GB of compressed data. The TZ885 uses the TZ88N-AX tape drive, a single-ended drive. The SCSI bus connector is 50-pin low-density, single-ended.
The TZ887 Digital Linear Tape (DLT) Mini-library combines a cartridge tape drive (TZ88) and an automatic cartridge loader. It uses a seven-cartridge (CompacTape IV) removable magazine with a total capacity of nearly 280 GB compressed. It is capable of reading/writing at approximately 10.8 GB per hour.
TL893 and TL896-- The TL893 and TL896 Automated Tape Libraries (ATLs) are designed to provide high-capacity storage and robotic access for the Digital Linear Tape (DLT) series of tape drives. They are identical except in the number of tape drives and the maximum capacity for tape cartridges.
Each tape library comes configured with a robotic controller and bar code reader (to obtain quick and accurate tape inventories).
The libraries have either three or six TZ89N-AV drives. The TL896, because it has a greater number of drives, has a lower capacity for tape cartridge storage.
Each tape library utilizes bulk loading of bin packs, with each bin pack containing a maximum of 11 cartridges. Bin packs are arranged on an eight-sided carousel that provides either two or three bin packs per face. A library with three drives has a carousel three bin packs high. A library with six drives has a carousel that is only two bin packs high. This provides for a total capacity of 24 bin packs (264 cartridges) for the TL893, and 16 bin packs (176 cartridges) for the TL896.
The tape library specifications are as follows:
TL893--The TL893 ATL is a high-capacity, 264-cartridge tape library providing up to 18.4 TB of storage. The TL893 uses three fast-wide, differential TZ89N-AV DLT tape drives. It has a maximum transfer rate of almost 10 MB per second (compressed) for each drive, or a total of about 30 MB per second.
The TL893 comes configured for three SCSI-2 buses (a three-bus configuration). The SCSI bus connector is high-density 68-pin, differential.
TL896--The TL896 ATL is a high-capacity, 176-cartridge tape library providing up to 12.3 TB of storage. The TL896 uses six fast-wide, differential TZ89N-AV DLT tape drives. It also has a maximum transfer rate of almost 10 MB per second per drive (compressed), or a total of about 60 MB per second.
The TL896 comes configured for six SCSI-2 buses (a six-bus configuration). The SCSI bus connector is also high-density 68-pin, differential.
Both the TL893 and TL896 can be extended by adding additional cabinets (DS-TL893-AC for the TL893 or DS-TL896-AC for the TL896). Up to five cabinets are supported in a TruCluster Server cluster.
For TruCluster Server, the tape cartridges in all the cabinets are combined into one logical unit, with consecutive numbering from the first cabinet to the last cabinet, by an upgrade from the multi-unit, multi-LUN (MUML) configuration to a multi-unit, single-LUN (MUSL) configuration.
The TZ89 DLT MiniLibrary family includes the following hardware:
DS-TL891-NE/NG: A rack mount MiniLibrary with bar code reader, robotic controller, one TZ89N-AV tape drive, and a 10-cartridge removable magazine.
DS-TL891-NT: A tabletop MiniLibrary with bar code reader, robotic controller, one TZ89N-AV tape drive, and a 10-cartridge removable magazine.
DS-TL892-UA: An upgrade kit that includes one TZ89N-AV tape drive to upgrade either TL891 model to a TL892 model.
The TL891 and TL892 MiniLibraries use a 10-cartridge magazine with a random-access loader mechanism. The magazine holds either CompacTape III, CompacTape IIIXT, or CompacTape IV cartridges.
In the TL892 two-drive model, the library robotics can load any of the cartridges in the system into either of the TZ89 tape drives.
The total capacity of one base module using CompacTape IV media is 350 GB uncompressed (10 cartridges, 35 GB per cartridge).
The SCSI bus connectors are HD 68-pin, and the SCSI transfer is high-speed differential.
TL890--You can use a DS-TL890-NE/NG expansion unit with up to three TL891/TL892 MiniLibraries (DS-TL891-NE/NG, DS-TL892-UA) in a rack mount configuration to manage simultaneous access to up to 46 cartridges and six TZ89N-AV tape drives. The TL890 DLT MiniLibrary expansion unit adds 16 cartridges to the ten-cartridge capacity of each TL891/TL892 DLT MiniLibrary base unit used with the expansion unit for a total capacity of 26, 36, or 46 cartridges. These DLT MiniLibraries may be mounted in SW500, SW800, or RETMA cabinet configurations.
The SCSI bus connectors are HD 68-pin, and the SCSI transfer is high-speed differential.
TL894-- The TL894 is a midrange DLT automated tape library with four fast-wide, differential tape drives. This tape loader uses differential TZ89N-AV tape drives. The SCSI bus connector is 68-pin, high-density differential.
The TL894 has a capacity of 48 DLT cartridges in a fixed-storage array. An operator accessible load port can hold an additional four cartridges for a total of 52 DLT cartridges. This provides a storage capacity of 1.68 to 1.82 TB uncompressed for the TL894 automated tape library.
The DS-TL895-H2 and DS-TL895-BA automated digital linear tape libraries consists of two and five TZ89N-AV tape drives respectively, and 100 tape cartridge bins (96 storage bins in a fixed storage array (FSA) and 4 load port bins). The storage bins hold either CompacTape III, CompacTape IIIXT, or CompacTape IV cartridges. The maximum storage capacity of the library is 3500 GB uncompressed based upon 100 CompacTape IV cartridges at 35 GB each.
The TL895 may be upgraded to seven tape drives maximum with the addition of multiple DS-TL89X-UA upgrade kits.