HP NetServer AA 4000 User manual

12/08/99 Hewlett-Packard Co. 1
Backup/Recovery Guide for HP
Assured Availability Systems
While HP Assured Availability Systems provide very high level of server availability, HP
recommends that backups be done at first install, at upgrade times, and periodically to
preserve data in the event of disasters. This guide provides important information to help
system administratorsconfigure and setup the system for backup.
•Backup topologies and their tradeoffs
•AA related backup configuration/setup notes
•Disaster recovery procedures
•Part numbers for ordering backup configurations
Backup topologies and tradeoffs
There are many backup topologies one might consider for backing up HP AA systems.
To help system administrators configure and setup backups HP recommends three
topologies.
IOP
CE
IOP
CE
DLT
80r
CE boot disk
DLT
80r
SSDL SSDL
IOP boot disk
data disksdata disks
IOP boot disk
CE boot disk IL
LAN
DLT
40r
DLT
40r
Figure 1: Pure-local backup configuration
The first topology is a pure-local backup configuration (see figure 1). This configuration uses
a HP SureStore TapeRack with two DLT80r and two DLT40r tape drives. The two DLT80r
tape drives are configured using the Marathon Configuration Utility to be "owned" by the
CEs – each DLT80r act as independent tape drives in the CE. Backup software, such as
Veritas Backup Exec 7.3 or Computer Associates ArcServe IT 6.61, is installed on the CE

12/08/99 Hewlett-Packard Co. 2
and run on the CE. Backup software backs up the CE NOS disk and the data disks in the
same manner as in a standard (standalone) system. Each HP DLT 40r is used to backup the
IOP NOS disk and any other IOP local disks. The tape drives, whether owned by IOP or CE,
on each IOP can be controlled by the same SCSI HBA. In the current HP supported
configurations, the built-in SCSI channels in an IOP are used for disk storage. This means
that an additional SCSI HBA must be installed on each IOP for the tape drives. The figure
shows two DLT80r and two DLT40r drives. This is the recommended configuration for
assured availability and for load balancing purposes. It is possible to use a single DLT drive
attached to one IOP, but each of the IOPs must still add an additional separate SCSI card.
Note: "Autoloader" tape devices for local backup are not supported at this time. Support of
these devices will be available in the future.
IOP
CE
IOP
CE
DLT
or
DAT
CE boot disk
DLT
or
DAT
SSDL SSDL
IOP boot disk
data disksdata disks
IOP boot disk
CE boot disk IL
CE Public LAN
CE Public LAN
IOP LAN
IOP LAN
Figure 2: Semi-Local backup configuration
The second topology is a "semi-local backup configuration" (See figure 2). This
configuration is similar to pure-local backup except that there is no local backup tape device
for the IOPs. The NOS disks of the IOPs can be backed up via the Marathon virtual network
between CE and each IOP but preferably should be done using an external network
connections (e.g. each IOP has there own dedicated network connection to CE public LAN).
The two tape drives in the figure are shown as attached to the IOPs and redirected to the CE
through the Marathon Configuration Utility. This configuration allows balancing of load and
certain performance gain in some cases. It is possible for both to be attached to just one of
the IOP’s. In fact, it is possible to have just a single tape drive. Again, since both built-in
SCSI channels in the IOPs are used in the standard configurations, an additional SCSI HBA
must be added to each of the IOP’s for the tape device and to maintain the hardware
redundancy configuration.

12/08/99 Hewlett-Packard Co. 3
IOP
CE
IOP
CE
CE boot disk
SSDL SSDL
IOP boot disk
data disksdata disks
IOP boot disk
CE boot disk IL
Public LAN
Backup LAN
CE Backup LAN
IOP Backup LAN
CE Public LAN
CE Backup LAN
IOP Backup LAN
CE Public LAN
Figure 3: Network backup topology
The third topology (see Figure 3) is a network backup configuration. In addition to CE
“owned” NICs that are connected to the public LAN, there is one NIC configured for each
CE on the private Backup LAN. A separate NIC is also installed on each IOP to support
network backup of each IOP. The two backup NICs in each IOP are connected to a private
backup LAN. The best network backup performance (but is slower than any local backup) is
obtained with a private backup network through a dedicated switch with no network traffic
other than backup clients and backup server. One NIC is owned by the CE and used to
backup CE NOS disk and data disks; the other owned by the IOP is for backing up the IOP
NOS disk. In this configuration, the backup software backs up the CE and the two IOPs as
three individual systems. Note that the two CE "owned" backup NICs are in a mirror
configuration just the same as CE public NICs. In some cases, a system administrator might
opt to use the public LAN as the backup LAN. In this case, the CE public NIC will be used
for CE backup as well and a separate CE backup NIC is not required. This is not generally a
recommended configuration, since when the backup is in progress, it can utilize the whole
bandwidth of the public LAN and this might cause interruption to services.
For systems administrators that are adding a dedicated NIC in each IOP to support TopTools
management of the IOP’s, the same IOP NIC can be shared as the backup NIC at the
discretion of the administrator.

12/08/99 Hewlett-Packard Co. 4
The following table lists the factors of tradeoff among the three configurations:
Local Backup Semi-Local Backup Network Backup
Backup
Performance Gives best backup performance. Backup performance is good. But the virtual
network (or an extra
dedicated IOP network
card) is relatively slow,
the backup
performance for the
IOP disks is much less
than the rated tape
drive performance.
This may be acceptable
since the IOP, in
general, has very little
storage requirement.
Also, IOPs are static in
nature and they do not
need to be backed up
frequently. Overall, the
impact is moderate. (A
500MB IOP can be
backed up in as little as
20 minutes.)
Slowest for backup
performance. Backup
network becomes a
major additional factor
that limits the
throughput of backup.
One should take into
consideration the
network bandwidth
that is shared among
many systems.
Centralization of
Backup No centralization. Requires separate
management of
multiple tape drives
and multiple tape
cartridges. If data set
backed up is large,
this can require
significant IT
operator time.
No centralization.
Requires separate
management of
multiple tape drives
and multiple tape
cartridges. If data set
backed up is large, this
can require significant
IT operator time.
Network backup allow
a single backup server
to backup all the
systems from central a
data center. Tape
media management
should be less and IT
operator time is less,
since autochangers
hold more tape
cartridges. Backup
software aids in media
management.
Installation /
Configuration Local backup requires a separate
SCSI channel that is
not shared with hard
disks. A dedicated
Tape SCSI HBA
must be installed on
Semi-local backup on
the internal SCSI
channels is not
recommended because
normally both hot swap
cages (for LH series)
will be used and tape
Network backups
requires two additional
NICs in each IOP with
two additional IP
addresses to configure,
one on each IOP and
one on the CE.

12/08/99 Hewlett-Packard Co. 5
each IOP. The tape
rack has two SCSI
channels, that each
operate two of the
tape devices. On
each of the IOP one
tape device is
configured on the
CE using the
Marathon manager,
the other tape device
is left in the IOP.
devices can degrade
performance of a SCSI
HBA channel. Use a
dedicated SCSI HBA
and save internal SCSI
for the disk Netraid.
The internal DLT drive
requires two bay slots
and the DAT only
requires one. Use
Marathon manager to
configure Tape device
into CE.
If virtual network link
to IOP is not available
for network backup,
add dedicated network
card on each IOP.
Connect to a private
backup LAN for best
network backup
performance and to
reduce load on user
network.
Tape devices Pure-local backup
requires duplicate
tape drives for both
CE and IOPs for
assured availability.
Preferably the larger
capacity DLT drive
should backup CE
where most of the
data resides.
Since the storage
size for the IOP in
general is small,
low-cost and smaller
capacity DAT drives
are ideal.
In semi-local backup
configuration, only
tape drives for CE are
required. Again use
DLT 80 tape drives for
greater data storage
capacity or can use
DAT 24 where data
capacity is not
significantly large.
Use an autochangers
for the network
backup. Since the
changer usually cost
more but can be
shared to backup other
systems on the same
network.
Backup software
installation/config
uration
Pure-local backup
requires three
complete installation
of backup software.
One for CE, and one
for each IOP.
Install backup software
on CE for local backup.
The IOPs are clients to
the CE. Only client-
side backup software
components are
required on each IOPs.
In network backup
configuration, the CE
and both IOP are
backup clients. Each
require only the client-
side backup software
components.

12/08/99 Hewlett-Packard Co. 6
HP AA related configuration/setup notes
Pure-local backup configuration
•The DLT40r and DLT80r tape drives can share the same SCSI channel. Note that the
SCSI ID of each device must be set properly.
•CE owns the DLT80r tape drives1; each IOP owns the DLT40r drive that is directly
attached.
•Follow the Marathon SCSI configuration rules in the installation guide. Non-shared SCSI
devices must use SCSI IDs that are used on only one of the IOP (e.g. if a DLT drive has
SCSI ID 4 on a SCSI channel, the matching SCSI channel on the other IOP must not have
a SCSI device with ID of 4). For simplicity, it is best to configure each tape devices in
the tape rack with a unique SCSI IDs (e.g. 2, 3, 4, and 5).
•Backup software should be properly installed on the CE and both IOPs. The three
instances of backup software run independently and require three licenses.
•Using Veritas Backup Exec 7.3 in this configuration will give a “Storage device
configuration error”on the IOP. This is the result of the DLT 80r being configured in the
CE but not available to the IOP. This is okay because the Marathon Configuration
Manager has taken away the usage of the DLT 80r for use in the CE.
Semi-local backup configuration
•The DLT or DAT tape drives are independent devices owned by the CE. Note that these
tape drives are not mirrored devices but are unique SCSI devices; the Marathon SW does
not write the same data to the tape drives as it does for disks.
•SCSI ID of tape drives must be configured according to Marathon SCSI configuration
rules.
•CE backup software backs up all disks, CE's and IOP's, in a HP AA system.
•If the Virtual network connection between the CE and the IOPs is used to backup each
IOP, it must be set up properly. The CE must be configured to see each IOP server
through the internal virtual link as in the standard HP AA system setup.
•The recommended configuration for backing up data on each IOP is to use a dedicated
NIC configured in each IOP for performing a CE controlled network backup over the
public (default) CE network connection. Below is the network backup configuration for
setting up a dedicated network connection to each IOP using unique IP addresses.
First install the new NIC cards and add the NIC adapter driver in each IOP. Next,
configure adapter bindings.
1DLTs with autochangers for a local backup will be supported in a future release.

12/08/99 Hewlett-Packard Co. 7
IL Network Adapter
Enable – NetBEUI Protocol
Disable – TCP/IP Protocol
Disable – Wins Client (TCP/IP)
Enable – Marathon Datagram Services
Disable – Marathon Ethernet Provider
Enable – MTCEtx driver
Original Adapter (for default CE communication)
Disable - NetBEUI Protocol
Disable - TCP/IP Protocol
Disable - Wins Client (TCP/IP)
Enable - Marathon Datagram Services
Enable - Marathon Ethernet Provider
Disable - MTCEtx driver
Marathon MtcVnP Virtual Adapter
Enable - NetBEUI Protocol
Disable - TCP/IP Protocol
Disable - Wins Client (TCP/IP)
Disable - Marathon Datagram Services
Disable - Marathon Ethernet Provider
Disable - MTCEtx driver
New Network Adapter (for dedicated IOP communication to CE)
Disable - NetBEUI Protocol
Enable - TCP/IP Protocol
Enable - Wins Client (TCP/IP)
Enable - Marathon Datagram Services
Enable - Marathon Ethernet Provider
Disable - MTCEtx driver
Configure a unique IP address for each dedicated IOP network connection. Then, go to
the CE Network Properties, and change the bindings on both Marathon MtcVnR to the
following.
Marathon MtcVnR (for internal communication between IOP1 and CE)
Enable – NetBEUI Protocol
Disable – TCP/IP Protocol
Disable – Wins Client (TCP/IP)
Marathon MtcVnR (for internal communication between IOP2 and CE)
Enable – NetBEUI Protocol
Disable – TCP/IP Protocol
Disable – Wins Client (TCP/IP)

12/08/99 Hewlett-Packard Co. 8
Marathon MTCETHR Virtual Adapter (public LAN on CE)
Enable – NetBEUI Protocol
Enable – TCP/IP Protocol
Enable – Wins Client (TCP/IP)
Now reboot the HP AA system. After reboot, check that you can ping IOP1 and IOP2 IP
addresses from the CE and from a third remote computer.
Network backup configuration
•Each pair of NICs assigned to CE, whether connected to the public LAN or the backup
LAN, must be properly configured using Marathon Configuration Utility.
•Each IOP must have a separate backup NIC connected to the backup LAN. The backup
network may also serve as the management network. In this case some management
tools, such as TopTools, can access IOPs through the management network.
•The CE and the two IOPs are configured as three individual backup clients.
•The dedicated IOP and CE network cards are configured as below.
First install the new NIC cards and add the NIC adapter driver. Next, configure adapter
bindings.
IL Network Adapter
Enable – NetBEUI Protocol
Disable – TCP/IP Protocol
Disable – Wins Client (TCP/IP)
Enable – Marathon Datagram Services
Disable – Marathon Ethernet Provider
Enable – MTCEtx driver
Original Adapter (for default CE communication)
Disable - NetBEUI Protocol
Disable - TCP/IP Protocol
Disable - Wins Client (TCP/IP)
Enable - Marathon Datagram Services
Enable - Marathon Ethernet Provider
Disable - MTCEtx driver
Marathon MtcVnP Virtual Adapter
Enable - NetBEUI Protocol
Disable - TCP/IP Protocol
Disable - Wins Client (TCP/IP)
Disable - Marathon Datagram Services
Disable - Marathon Ethernet Provider
Disable - MTCEtx driver
New Network Adapter (for dedicated IOP communication to CE)

12/08/99 Hewlett-Packard Co. 9
Disable - NetBEUI Protocol
Enable - TCP/IP Protocol
Enable - Wins Client (TCP/IP)
Enable - Marathon Datagram Services
Enable - Marathon Ethernet Provider
Disable - MTCEtx driver
New Network Adapter (for dedicated backup CE network)
Disable - NetBEUI Protocol
Disable - TCP/IP Protocol
Disable - Wins Client (TCP/IP)
Enable - Marathon Datagram Services
Enable - Marathon Ethernet Provider
Disable - MTCEtx driver
After completing the adapter bindings, then configure a unique IP address for each
dedicated IOP NIC.
For dedicated backup CE NIC (one in each IOP because mirrored for AA), use the
Marathon manager in IOP1 and IOP2 to configure a second NIC into the CE.
Next, go into CE network properties and add an additional Marathon MTCETHR Virtual
Adapter. Set up the adapter bindings as follows.
Marathon MtcVnR (for internal communication between IOP1 and CE)
Enable – NetBEUI Protocol
Disable – TCP/IP Protocol
Disable – Wins Client (TCP/IP)
Marathon MtcVnR (for internal communication between IOP2 and CE)
Enable – NetBEUI Protocol
Disable – TCP/IP Protocol
Disable – Wins Client (TCP/IP)
Marathon MTCETHR Virtual Adapter (public LAN on CE)
Enable – NetBEUI Protocol
Enable – TCP/IP Protocol
Enable – Wins Client (TCP/IP)
Marathon MTCETHR Virtual Adapter (private backup LAN on CE)
Enable – NetBEUI Protocol
Enable – TCP/IP Protocol
Enable – Wins Client (TCP/IP)
Set up a separate IP address (different than the original CE user IP) for the dedicated
backup network. The dedicated backup network with IOP1, IOP2, CE1 and CE2 backup

12/08/99 Hewlett-Packard Co. 10
NICs should be on a private switch or a backup network separate from normal user traffic
network for performance reasons. After rebooting HP AA system, check that you can
ping each dedicated IOP IP addresses from a separate outside computer (e.g. network
backup computer). Then check that you can ping each of the CE IP addresses from the
same outside computer.
Disaster recovery procedures
In the event of a disaster or an operator's error, it is possible that the CE OS can be put in an
inoperable state. When this occurs it may be possible to recover the system without restoring
from backup tapes. Below is a set of procedures to assist system administrators to recover
systems with minimum downtime. The procedures must be followed in order listed below.
1. Last Known Good (Control Set)
Some failures of a CE OS to boot (after a reconfiguration) can be recovered from by selecting the
“Last Known Good” configuration. This functionality is exactly the same as the reference machine
(standard NT) case where you strike the space bar on the keyboard when prompted – and prior to the
first log on following the configuration change. Follow below steps:
•Boot both IOPs in Marathon Operation Mode and observe if both CE NOS disks are up-to-date
(i.e., both should be green on the Marathon Management GUI). If so, select one of the two tuples
as the "booting tuple." If only one of them is up-to-date, select the tuple containing the the up-to-
date NOS disk as the "booting tuple."
•Set the monitor/keyboard switch to enable keyboard on the "booting tuple" side.
•Set the monitor switch on SSDL of the "booting tuple" to CE.
•Power on only the CE in the "booting tuple".
•System will initialize itself. When you receive the message on the CE "Initiating Marathon Boot",
followed by MIC BIOS: CE Boot will be serviced by IOP1 or IOP2 (verify this IOP is indeed in the
"booting tuple.")
•After several moments, NTLDR program will starts and you will receive a message to depress
the space bar to load the "Last Known Good" configuration. (Note that the time window allowed
for depressing of space bar can be rather short. Be ready.) Then boots NT with "Last Known
Good" configuration.
•Power on the other CE to join the Marathon system.
2. Minor Repair Using An IOP In Off Line Mode
Use an IOP in offline mode to invoke the repair to the CE BOOT disk - then force a mirror copy in the
proper direction as you recover.
•Choose an IOP to undertake the repair on the CE BOOT device (cannot be the unfinished target
of a mirror copy)
•Reboot the selected IOP to MARATHON OFFLINE MODE (the server already is down/cannot be
rebooted - or you would repair it from the running CE OS).
•Replace the driver or delete the service - or otherwise make repairs to the CE BOOT device.

12/08/99 Hewlett-Packard Co. 11
•Perform a Marathon software installation for the CE ONLY while operating on the IOP (in offline
mode).
1. Select Endurance Software Installation
2. Check CE and explicitly un-check IOP
3. When prompted for the location of the CE root browse or enter d:\winnt (or an alternative
pathname that defines your CE OS).
4. If prompted to overwrite files that are newer on disk - choose NO for all files that begin with
“mtc”. Such files are Marathon components that have been upgraded via a hotfix installation.
By choosing NO it will not be necessary to reapply the Marathon hotfixes.
•Reboot the IOP(s) in Operational Mode
•Boot the repaired CE OS. The CE WILL NOW BOOT (if the proper repair was made)!!
3. Restore A Saved Copy Of Windows NT
Prepare and maintain an EMERGENCY RECOVERY COPY of the CE OS. Use an IOP in offline
mode to invoke a recovery - then force a mirror copy in the proper direction as you recover2. Re-
apply your tape backups to bring the system to a fully consistent state.
Marathon provides a tool (normally used during installations) that supports this procedure.
Mtccpynt.exe is located on the Marathon CDROM and can be used to “clone” the running NT
installation to another disk partition for safe storage. (See Marathon Endurance 4000 User's Guide,
Chapter 6-Marathon tools and utility -- for Mtccpynt usage.) If necessary it can be used to reverse the
copy direction - and therefore restore a disk to the state that was most recently saved.
There are limitations to this approach - just as there are when depending on Emergency Repair Disks
(ERDs). You need to update the information each time a significant change to the CE OS is made or
it becomes out of date. A recovery from the saved data should be upgraded with the latest back up
(of the system disk). Several files can out of date (particularly the registry and user profiles) after
making the (safe) copy – and before executing a recovery that uses it.
The steps to implement this scheme are included below:
PERIODICALLY CREATE AN EMERGENCY RECOVERY COPY of your CE OS
In the following discussion:
•Determine the pathname where mtccpynt.exe can be located (Marathon CD-ROM Z:\support for
purposes of the following discussion.)
•Determine the drive letter where the CE OS resides.- from the perspective of the CE. (C: for
purposes of the following discussion)
•Determine the drive letter where the EMERGENCY RECOVERY COPY will be created (X: for
purposes of the following discussion.)
•Create a small partition for this purpose - and label it conspicuously (i.e. CE_RECOVER). A
minimum of 200MB should be enough (compressed NTFS is recommended). A nominal NT
Server install consumes about 80MB but over time this can grow. Locate this storage area in
accord with one of the following two alternatives:
•On a CE mirror set.
–OR-
2In the normal HPAA system, it is recommended that the System Administrator keep a spare
good copy of the CE boot drives on a 200MB or larger partition. This can be an insurance
policy for a system recovery.

12/08/99 Hewlett-Packard Co. 12
•On both IOP disks access the partitions from the CE using the virtual network—a feature first
available in V2.2.0. Remember that the virtual network is slow, so plan the time when this is
done to have minimal impact to users.
•After each successful update to the CE OS, use Marathon’s MTCCPYNT utility to “clone” the
current (running) CE root as the “emergency recovery copy”. (Browse the marathon CD ROM
and run z:\support\mtccpynt c:\winnt x:. If using the IOP disk alternative, one mtccpynt (of two)
must be targeted at each IOP.
Note when performing updates to the emergency recovery copy, you will be prompted to
overwrite existing directories. Answer yes in all cases.
•Repeat the above procedure each time your would otherwise update your NT Emergency Repair
Disk.
4. TO RECOVER the CE OS USING AN EMERGENCY RECOVERY COPY
The CE is down already (it cannot be booted, due to the problem we are recovering from).
•Choose the IOP best suited to support the recovery and reboot it into Marathon Off-line Mode.
(Choose an IOP that is known to have a good copy of the CE BOOT DISK.)
•Determine the drive letter where the CE OS resides. (D: for purposes of the following
discussion).
•Determine the drive letter where the EMERGENCY RECOVERY COPY exists (X: for purposes of
the following discussion.)
•Determine the pathname where mtccpynt.exe can be located (CD-ROM Z:\support for purposes
of the following discussion.)
•Execute mtccpynt to reverse the procedure that created the EMERGENCY RECOVERY COPY.
(Browse the marathon CDROM and run z:\support\mtccpynt x:\winnt d:). (Note that during the
copy process you will be prompted to overwrite existing directories (except if the disk is empty).
Answer yes in all cases.)
•Perform a Marathon software installation for the CE ONLY while operating on the IOP (in off line
mode).
1. Select Endurance Software Installation
2. Check CE and explicitly un-check IOP
3. When prompted for the location of the CE root browse or enter d:\winnt (the target of the
mtccpynt command - and the CE_BOOT device).
4. If prompted to overwrite files that are newer on disk - choose NO for all files that begin with
“mtc”. Such files are Marathon components that have been upgraded via a hotfix installation.
By choosing NO it will not be necessary to reapply the Marathon hotfixes.
•Reboot the IOP(s) in Operational Mode
•The CE WILL NOW BOOT!
•Consider performing the appropriate series of restore operations (from your most recent backups)
to bring the disk up-to-date.

12/08/99 Hewlett-Packard Co. 13
Part Numbers for Backup Configurations
Pure-local backup
•C5695A - HP SureStore TapeRack for HP 19” server rack, includes one 0.9m SCSI cable, two
2.5m SCSI cables, and two SCSI terminators (Tape Rack holds 4 tape devices – select from r
types below).
•C5727A – HP SureStore DLT80r (need two – 1 on each IOP configured for CE).
•C5697A - HP SureStore DLT40r (need two - 1 on each IOP).
•D5025A – PCI ultra-wide SCSI host bus adapter (need two – 1 on each IOP).
•Backup Software - Computer Associates ArcServe IT 6.61 or Veritas Backup Exec 7.3 (need
three licenses 1 on each IOP and 1 on CE).
Alternative Tape Rack Kit Configuration for Pure-local backup
•C6543A - HP SureStore 3Uk 19” Rack kit – Holds either 4 half-height DATs, or 2 full-height DLTs,
or 2 half-height DATs and 1 full-height DLT. Includes one Y cable power cord and one 0.5m 68-
68 pin SCSI cable. Select from k type tape drives below.
•C6541A - HP SureStore DAT40k Tape Drive – includes one 2.5m SCSI cable, 1 SCSI
terminiator, and 1 power cord (need two – 1 on each IOP configured for CE).
•C6525A - HP SureStore DAT24k Tape Drive – includes one 2.5m SCSI cable, 1 SCSI terminator,
and 1 power cord (need two – 1 on each IOP).
•D5025A – PCI ultra-wide SCSI host bus adapter (need two – 1 on each IOP).
•Backup Software - Computer Associates ArcServe IT 6.61 or Veritas Backup Exec 7.3.
Rack Kits are not available in all countries. Please check with your reseller or
HP salesperson.

12/08/99 Hewlett-Packard Co. 14
Semi-Local backup
•C5725A – HP SureStore DLT80i internal tape drive for LH-series Netserver - includes mounting
tray, jumpers, and screws.
•C5686A – HP SureStore DAT40i internal tape drive for LH-series Netserver - includes mounting
tray, jumpers, and screws.
•C1555D – HP SureStore DAT24i internal tape drive for LH-series Netserver - includes mounting
tray, jumpers, and screws.
•D5025A – PCI ultra-wide host bus adapter (need two – 1 on each IOP).
•Optional use C7430A - PCI Ultra2-wide LDVS host bus adapter – when connecting only to
DLT80i tape drives for maximum performance.
•D5013A – HP 10/100 TX network interface card (need two for dedicated IOP LAN).
•Backup Software - Computer Associates ArcServe IT 6.61 or Veritas Backup Exec 7.3.
Alternative Tape Rack Kit Configuration for Semi-local backup
•C6543A – HP SureStore 3Uk 19” Rack kit – Holds either 4 half-height DATs, or 2 full-height
DLTs, or 2 half-height DATs and 1 full-height DLT. Includes one Y cable power cord and one
0.5m 68-68 pin SCSI daisy chain cable. Select from k type tape drives below.
•C6542A – HP SureStore 2Uk 19” Rack kit – Holds 2 half-height DATs. Includes one Y cable
power cord and one 0.5m 68-68 pin SCSI daisy chain cable. Select from k type tape drives
below.
•C6529A – HP SureStore DLT80k Tape Drive – includes one 2.5m SCSI cable, 1 SCSI terminator,
and 1 power cord.
•C6515A - HP SureStore DLT40k Tape Drive – includes one 2.5m SCSI cable, 1 SCSI terminator,
and 1 power cord.
•C6541A – HP SureStore DAT40k Tape Drive – includes one 2.5m SCSI cable, 1 SCSI
terminator, and 1power cord.
•C6525A - HP SureStore DAT24k Tape Drive – includes one 2.5m SCSI cable, 1 SCSI terminator,
and 1 power cord.
•D5025A – PCI ultra-wide SCSI host bus adapter (need two – 1 for each IOP).
•Optional use C7430A - PCI Ultra2-wide LDVS host bus adapter – when connecting only to
DLT80i tape drives for maximum performance.
•D5013A – HP 10/100 TX network interface card (need two for dedicated IOP LAN).
•Backup Software - Computer Associates ArcServe IT 6.61 or Veritas Backup Exec 7.3.
Rack Kits are not available in all countries. Please check with your reseller or
HP salesperson.

12/08/99 Hewlett-Packard Co. 15

12/08/99 Hewlett-Packard Co. 16
Network backup
•C7202NB – HP SureStore Tape Library 2/20 – 2 DLT 8000 Drives, 20 slots, rackmount LDVS
Library.
•C7430A - PCI Ultra2-wide LDVS host bus adapter – recommend two - 1 HBA per tape drive for
maximum performance.
•D5013A – HP 10/100 TX network interface card (need four additional NICs for dedicated backup
network).