ARCserve tape drive can’t be found.

Export to PDF | Export to DOC

Problem: ARCserve tape drive can’t be found.  SCO ARCserve/Open has been installed on a system but when ARCserve starts, the tape drive is not found and tape operations fail.

Cause: The tape drive is on the second SCSI adapter.

Solution: Follow the next three steps for setting up the tape drive:

1. Verify tape drive works via the operating system.

OpenServer 5.0.x:

# cd /tmp

# tar cvf /dev/rStpN /stand/unix.old
This command will verify that the tape drive can be
written to.

# tar xvAf /dev/rStpN
This command will verify that the tape drive can be
read from. Note that the A flag of the tar command
will restore the files using a relative rather than
an absolute path and this will prevent possible
corruption of the original source file.

# sum -r /stand/unix.old /tmp/stand/unix.old
This command will verify the integrity of the read/write

UnixWare 2.1.x and 7.x:

# cd /tmp

# tar cvf /dev/rmt/ctapeN /stand/unix.old

# tar xvAf /dev/rmt/ctapeN

# sum -r /stand/unix.old unix.old

2. Check or modify ARCserve configuration files.

1. # cd /usr/lib/ARCserve

2. # cp tapesvr.cfg tapesvr.cfg.orig

3. # vi tapesvr.cfg

Once in the file, search for the string “Device”. This should be the first entry for the Device Table.

4. Comment out all of the ID entries with the exception of the ID entry for the tape device. If the tape device is on SCSI ID 4, insert a “;” before all
entries except the ID 4 entry. Each entry would change as follows:

DEVICE = “/dev/cscsi/0” SCSIID 0
DEVICE = “/dev/cscsi/01” SCSIID 0,1


;DEVICE = “/dev/cscsi/0” SCSIID 0
;DEVICE = “/dev/cscsi/01” SCSIID 0,1

Notice that there are two entries for each SCSI ID. The second entry is for a device on LUN 1 for that SCSI ID. This entry will be used by a tape changer. (ARCserve does NOT support tape drives on any but LUN 0.) It should not be necessary to comment out the LUN entry on the SCSI ID for
the tape device, but it will not hurt to comment out the LUN entry.

5. Save the file and then exit the file.

6. # astop <– This will stop ARCserve

7. # astart <– This will restart ARCserve

3.  Verify correct kernel configuration for cheyenne driver.

OPENSERVER ONLY – This section applies to SCO OpenServer 5.0.x products only and will not work on UnixWare systems.   See section below for Unixware.

The “chey/space.c”
file must be checked to ensure that the correct entries were stored at the time of configuration.

1. # cd /etc/conf/pack.d/chey

2. # cp space.c space.c.orig

3. # vi space.c

4. Search for the string “#include”. The first line to check is the first entry after the #INCLUDE lines. This line begins with “extern int” and contains
the adapter model. Make sure that the correct SCSI adapter is entered here.

5. The remainder of the file is made up of entries for each SCSI ID on the bus. The entries are identical and look like this:

/* SCSI ID 0 */
0x0, /* Device index */
“chey”, /* Device driver name prefix */
(dev_t)139, /* Device driver major number */
(unsigned char)0x0, /* Host Adapter number */
(unsigned char)0x0, /* SCSI Priority */
(unsigned char)0x0, /* Logical Unit number of the device */
(unsigned char)0x0, /* Used for multiprocessing purposes */
slha_entry, /* Host adapter entry point */
(paddr_t)0x0 /* Extensions to SCSI */

6. Check each of the SCSI ID entries for the correct “Host Adapter number” and the correct “Host adapter entry point”.

Host Adapter Number: This is the number for the SCSI adapter to which the tape is connected. By default it is set to 0x0 which is the first SCSI
adapter of the specified type. If the tape drive is on the second adapter, the entry should be changed to 0x1. All of the Host Adapter number entries
for each of the SCSI IDs should be set to the same value.

Host adapter entry point: This is the model of the SCSI adapter. This entry should match the “extern int” as described in part 4 above. All of the
Host adapter entry points should be the same.

7. After making any necessary changes to the file, save the file and exit vi.

8. If the file was changed, a kernel relink and system reboot must be completed for the changes to take effect. Once the kernel has been relinked and
booted, test to see if ARCserve finds the tape drive.

UNIXWARE ONLY – This section applies to UnixWare 2.1.x and 7.x products only and will not work on SCO OpenServer systems.   See section above for Open Server.

The “astart” script can be modified to specify a particular tape device.

Note: For the following changes to have any effect on ARCserve, the tape device must have a tape cartridge and it must be online and ready. If the
tape device is not online and ready, then making these changes will have no effect.

1. # cd /opt/ARCserve <—- UnixWare 2.1.x systems 1a.# cd /usr/bin <—- UnixWare 7.x systems

2. # cp astart astart.orig

3. # vi astart

4. Search for the string “rroot”. There should be two lines with the rroot string in them. They look like:

$ARC_HOME/mkpassthru /dev/rroot “/dev/chey$HA,$i,0” $i $LUN0 $HA
>/dev/null 2>&1
$ARC_HOME/mkpassthru /dev/rroot “/dev/chey$HA,$i,1” $i $LUN1 $HA
>/dev/null 2>&1

5. Change the /dev/rroot entry in each line to specify the exact tape device on the system. If the tape device on the system is /dev/rmt/ctape1, the
modified lines would look like this:

$ARC_HOME/mkpassthru /dev/rmt/ctape1 “/dev/chey$HA,$i,0” $i
$LUN0 $HA >/dev/null 2>&1
$ARC_HOME/mkpassthru /dev/rmt/ctape1 “/dev/chey$HA,$i,1” $i
$LUN1 $HA >/dev/null 2>&1

6. After making the changes, save the file and exit vi.

7. Make sure that the tape device has a tape in it and that it is online and ready. If there is no tape in the tape device or the device is off line, these
changes will have no effect. Once the tape device is online and ready, run “astop” to stop ARCserve and then “astart” to restart ARCserve.

8. Test to see if the tape device is being seen by ARCserve.

Leave a Reply

Your email address will not be published. Required fields are marked *