![[Contents]](TOC.GIF){kind=small}
![[Prev. Chapter]](REW.GIF){kind=small}
![[Next Section]](NEXT.GIF){kind=small}
![[Next Chapter]](FF.GIF){kind=small}
![[Index]](INDEX.GIF){kind=small}
![[Help]](HELP.GIF){kind=small}
This chapter describes the supported hardware for the TruCluster Software Products: TruCluster Available Server Software, TruCluster Production Server Software, and TruCluster MEMORY CHANNEL Software. This chapter also contains some specific requirements for some of the hardware components.
See the TruCluster Software Products Release Notes for the latest information about supported hardware and firmware revisions.
Table 2-1 lists the supported systems by product and the SCSI adapter used for shared SCSI buses on each system. Section 2.1.1 and Section 2.1.2 provide the specific requirements for member systems in a TruCluster Available Server Software (AS), TruCluster Production Server Software (PS), or TruCluster MEMORY CHANNEL Software (MC) configuration.
| System | SCSI Adapter | AS | PS | MC |
| DEC 3000 | PMAZC or KZTSA | Yes | No | No |
| DEC 7000 and DEC 10000 | KZMSA | Yes | No | No |
| AlphaServer 300 | KZPSA | Yes | No | No |
| AlphaServer 400 | KZPSA | Yes | No | No |
| AlphaServer 800 | KZPSA | Yes | Yes | Yes |
| AlphaServer 1000 | KZPSA | Yes | No | No |
| AlphaServer 1000A | KZPSA | Yes | Yes | Yes |
| AlphaServer 1200 | KZPSA | Yes | Yes | Yes |
| AlphaServer 2000 | KZPSA | Yes | Yes | Yes |
| AlphaServer 2100 | KZPSA | Yes | Yes | Yes |
| AlphaServer 2100A | KZPSA | Yes | Yes | Yes |
| AlphaServer 4000 | KZPSA | Yes | Yes | Yes |
| AlphaServer 4000A | KZPSA | Yes | Yes | Yes |
| AlphaServer 4100 | KZPSA | Yes | Yes | Yes |
| AlphaServer 8200 and 8400 | KZPSA | Yes | Yes | Yes |
![[Prev. Section]](PREV.GIF){kind=small}
Member systems in a TruCluster Available Server Software environment have the following requirements:
Each supported member system requires a minimum firmware revision. See the TruCluster Software Products Release Notes for information about required firmware.
If you have a system with a PMAZC or a KZMSA installed, you can use only three member systems in the ASE.
For TURBOchannel-based systems, the
boot_reset
console variable must be set to on.
If the
variable is not set to on, the TURBOchannel (TC) option self-test may fail
and the system may not automatically reboot.
A system may not boot properly if it does not have a graphics head attached. If a system does not have a graphics head, but has a terminal interface, you must use the following command:
>>> set console serial
You must perform the following steps to turn on and turn off a system that is connected directly to a SCSI signal converter:
You must turn on a system and allow it to complete its startup diagnostics before you turn on the signal converter that is connected to the system.
Before you turn off a system, you must first turn off any signal converter that is connected to the system.
If your system is a DEC 3000 Model 300, you must follow these steps to enable the system to automatically boot as a server:
Ensure that a keyboard and mouse are attached to the system with a BC13M cable, which is connected to the 15-pin D-sub in the back of the system. A graphics monitor is not required, but a keyboard and mouse must be connected to prevent errors when you turn on the system.
Connect a serial terminal to the 25-pin serial port in the back of the system. The serial terminal must be set to 9600 baud, 8 data bits, 1-stop bit, and no parity.
Attach a jumper to pins 2 and 3 (the middle pins) on the W2 jumper on the system motherboard (54-22257). The W2 jumper is located on the front of the board, to the left of the SIMM connectors.
Turn on the system.
If the system does not automatically boot, enter the following command at the console prompt:
>>> set auto_a boot
Turn off and turn on the system.
Ensure that the
BOOTDEF_DEV
console variable is set to the correct boot
device.
The requirements for member systems in a TruCluster Production Server Software or TruCluster MEMORY CHANNEL Software environment are as follows:
Each supported member system requires a minimum firmware revision. See the TruCluster Software Products Release Notes for information about required firmware.
Production Server Software supports up to eight systems in a hardware configuration.
MEMORY CHANNEL Software supports up to eight systems in a hardware configuration.
Production 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 Available Server Software and TruCluster Production Server Software. 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.
TruCluster Available Server Software supports ATM Lan Emulation (LANE) as a communication path between systems in a TruCluster environment. Both TruCluster Available Server Software and TruCluster Production Server Software products support the use of ATM Lan Emulation as a network for client access.
ATM is a cell-switching and multipexing 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 2-2 describes the supported SCSI adapters.
| SCSI Bus Adapter | Transmission Method |
| KZPSA [Footnote 3] | Differential |
| KZTSA [Footnote 4] | Differential |
| KZMSA [Footnote 4] | Single-ended |
| PMAZC [Footnote 4] | Single-ended |
The following sections describe the SCSI adapters in more detail.
KZPSA SCSI adapters have the following requirements:
If you have a KZPSA 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 SCSI adapter is not supported when the adapter is behind the PCI-to-PCI bridge.
Before you install a KZPSA adapter in a PCI slot, you must remove the termination from the adapter.
KZTSA SCSI adapters have the following requirements:
If you are using both a KZTSA adapter and a KZMSA adapter
on a shared bus in the available server environment (ASE), you must disable
the
wide
parameter on the system in which the KZTSA
adapter is installed.
However, you must first obtain the SCSI ID for the
KZMSA adapter.
To display the target ID of the KZTSA adapter and then
disable the parameter, use the following commands on the system in which
the KZTSA is installed:
>>> t tc# >>> set target_id wide disable
The # specifies the TC slot in which the KZTSA adapter is installed. The target_id specifies the SCSI ID of the KZMSA adapter.
KZMSA SCSI adapters have the following requirements:
If your system has a KZMSA adapter installed, you can use only three member systems in the ASE.
You must attach a DWZZA-AA signal converter to each KZMSA adapter that you connect to the shared bus.
The KZMSA hardware revision level is contained in its boot ROM. You must contact your field service representative to update the KZMSA boot ROM to Revision F03, if necessary. You can determine the hardware revision level by using console commands, or by examining the 23-class part number printed on the EPROM located at module position E7. The part numbers and associated hardware revisions are shown in the following table:.
| Part number | Hardware Revision |
| 23-368E9-01 | Revision F01 |
| 23-386E9-01 | Revision F02 |
| 23-419E9-01 | Revision F03 |
KZMSA adapters must have one of the following revision part numbers:
609-3400546
609-3400563
If the two NCR 53C710 chips on the KZMSA adapter are not marked with either of these part numbers, return the adapter to DIGITAL for replacement.
You must enable the Disable Reset configuration option for each KZMSA channel that you use for a shared bus. Keep the option disabled if the channel will not be used for a bus.
Available Server supports up to 16 KZMSA adapters installed in XMI slots.
PMAZC TURBOchannel SCSI controllers have the following requirements:
If your system has a PMAZC controller installed, you can have at most three member systems in the ASE.
If you update the firmware for a PMAZC controller, the update procedure may change the PMAZC option settings to the default settings. For example, the SCSI ID may be reset to 7 and the bus speed may be reset to slow.
If you want to run a PMAZC controller in Fast SCSI mode, DIGITAL recommends that you use DWZZA signal converters and a differential bus in your hardware configuration.
When a system with a PMAZC controller installed is turned on, it may hang on the PMAZC self-tests if the module is not terminated either internally or externally.
Table 2-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 requirements 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 2-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 requirements for disk devices are as follows:
Supported disks require a minimum firmware revision. See the TruCluster Software Products Release Notes for information about the required firmware.
Disks on shared SCSI buses must be installed in external storage shelves.
TruCluster does not support Prestoserve on any shared disk.
RAID controllers provide high performance, high availability, and high connectivity access to SCSI devices through a shared SCSI bus. Table 2-5 lists the RAID controllers supported in the Available Server (AS) and Production Server (PS) environments.
| RAID Controller | AS | PS |
| HSZ10-Ax | Yes | No |
| SWXRA-Z1 (HSZ20) | Yes | Yes |
| HSZ40-Ax | Yes | Yes |
| HSZ40-Bx | Yes | Yes |
| HSZ40-Cx | Yes | Yes |
| HSZ50-Ax | Yes | Yes |
| HSZ70 | Yes | Yes |
RAID controllers have the following requirements:
The HSZ10 controller must be used in an available server environment (ASE) that includes a PMAZC controller exclusively.
The HSZ10 controller uses only one SCSI ID.
The HSZ40 controller can be configured with one to four SCSI IDs.
The HSZ40 controller can be configured 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 Software Products Release Notes for information about required HSOF revisions.
Production Server supports single-controller, single-bus HSZ40 array configurations and dual-controller, single-bus HSZ40 configurations.
Table 2-6 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 requirements:
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 2-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 TruCluster operations, you must install the J jumper.
The BA353 is probably of little use in TruCluster 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 2-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 2-2 would be 0, 1, and 2, left, center, and right.
There are two variations of the BA356 used in TruCluster configurations: 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 2-3 shows the relative location of the BA356 SCSI bus jumper, BA35X-MF. The jumper is accessed from the rear of the box. For TruCluster operations, 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 environment.
You can use the position behind slot 1 to store the SCSI bus terminator or jumper.
Figure 2-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 TruCluster operations, 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 2-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 switches on the personality module (BA35X-DA) have to be set to off, the default switch positions. Verify that the personality module switches are all off.
The jumper module is positioned behind slot 6 as with the non-UltraSCSI BA356 shown in Figure 2-3. For TruCluster operations, 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 2-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 switch pack S4. For normal cluster operations, S4-1 and S4-2 should normally be on. Section 3.6.2.2 discusses these switches in more detail.
If you are using a storage shelf with a single-ended SCSI interface in your TruCluster 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.
Table 2-7 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 requirements for SCSI signal converters are as follows:
For each type of SCSI signal converter, a TruCluster environment requires a specific, minimum hardware revision. See the TruCluster Software Products 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
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 2-8 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 KZTSA, KZPSA, HSZ10, 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 PMAZC, KZMSA, 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 5] | Two low | 50-pin | Connects BN21V-0B Y cables to each other or the single-ended end of a DWZZA to a TZ885 . |
| BN21K or BN21L | Two HD68 | 68-pin | Connects BN21W Y cables or wide devices. For example, connects KZTSAs, KZPSAs, HSZ10s, 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 2-9 describes the supported SCSI terminators and the context in which you would use them.
| Terminator | Density | Pins | Configuration Use |
| H8574-A or H8860-AA | Low | 50-pin | Terminates a BN21V-0B Y cable. Used with Available Server configurations only. |
| H879-AA | High | 68-pin | Terminates an H885 trilink connector or BN21W-0B Y cable. |
| 12-37004-04 | High | 50-pin | Terminates a BA353 input connector. |
| 12-41667-01 | High | 50-pin | Terminates an unused PMAZC port. Used with Available Server configurations only. |
| H8863-AA | VHDCI | 68-pin | Terminate a VHDCI trilink connector. |
Table 2-10 describes the supported trilink connectors and the context in which you would use them.
| Trilink Connector | Number of Connectors | Pins | Density | Configuration Use |
| H885 | Three | 68-pin | High | Attaches to high-density, 68-pin cables or devices, such as a KZTSA, KZPSA, HSZ10, 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 Available Server Software and TruCluster Production Server Software products:
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.
Other TZ88 models (for instance, the TZ88N-AV fast-wide, differential drive) are supported as the tape devices for tape loaders. These TZ88 tape drives cannot be used as standalone drives.
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.
Other TZ89 models (for instance, the TZ89N-AV fast-wide differential drive) are supported as the tape devices for tape loaders. These TZ89 tape drives cannot be used as standalone drives.
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.