Ref: 11640079
Title: Troubleshooting 3+Backup Backups or Restores
Date: 7/27/89

Copyright 3Com Corporation, 1991.  All rights reserved.

After running 3+Backup to back up or restore files, check the
BACK_LOG, REST_LOG, or STAT_LOG files in the \3PLUS\3BACKUP
directory of the backup server to confirm the success of your
backup or restore.

If a backup or restore attempt fails or performs poorly, but all
other services in 3+Share seem to work, answer the following
questions in the order given below.  Try the suggestions that
apply to the server or servers you are working on.  If these are
not successful, contact your network supplier.

1.  Is there a message on the backup server LCD or in the backup
server's STAT_LOG, TAPE_LOG, BACK_LOG, or REST_LOG files?

If so, consult the 3+ Messages Guide.  If the 3+ Messages
Guide does not list this message, call your network supplier
or continue to the next question.

2.  Are your CIOSYS, 3+Share, and ETH3.SYS or ETH386.SYS
parameters consistent with the tuning guidelines for the
server model you are using?

If not, correct these settings by running the 3OPT program or
editing CONFIG.SYS.

3.  Did the backup fail during an automatic backup?

If the 3+Backup fails during an automatic backup, try a
manual backup.  If the manual backup works, check for a
typographical error in the backup server's AUTOTIMS file.

4.  Did the backup fail on-line?

If 3+Backup fails or performs poorly during an on-line
backup, take the server off-line and try to back up.  If the
off-line backup works, the problem may be with the volume of
network traffic to the servers.

If the backup fails when the network is in heavy use, back up
at a less busy time.

If the backup fails when network activity is low, check the
server's tuning parameters.

5.  Did the backup fail off-line?

If 3+Backup fails during an off-line backup, the problem may
be with the hardware.  Run TAPETEST.EXE on the server and
call your network supplier.

6.  Did the backup fail at the beginning?

If 3+Backup fails near the start of a backup or restore,
check the tuning guidelines for your source and backup
servers.

7.  Did the backup fail towards the middle or the end?

If 3+Backup fails towards the middle or the end of a backup,
you could have media problems.

Change the tape and clean the tape heads.  If these measures
do not improve the backup, the problem may be data corruption
on the source server's hard drive.

Run the 3DISK or 3DISK386 program to check the condition of
the source server's hard disk.  See "The Disk Maintenance
Program" in the 3Server3 Guide, or "3Disk386:  The Disk
Maintenance Program" in the 3Server386 Guide.

8.  Did the backup fail to a 2.3 GB capacity tape drive?

See "Resetting the 2.3 GB Tape Drive" in the 3+Backup 1.5.2 User
Release Notes.

9.  Did the backup fail during an appended incremental backup?

If the failed backup was an appended incremental backup and
you are using a Tandberg drive as the backup drive, check the
PROM and controller levels.  See "Tandberg Tape Drive PROM
Compatibilities" in the 3+Backup 1.5.2 User Release Notes.

10. Did the backup fail during a partial backup?

If 3+Backup fails during a partial backup, try backing up
another partition.  If you are able to back up the other
partition, then the problem could be a bad sector or
corrupted file on the partition where the failure occurred.

Run the 3DISK or 3DISK386 program to check the condition of
the source server's hard disk.  See "The Disk Maintenance
Program" in the 3Server3 Guide, or "3Disk386:  The Disk
Maintenance Program" in the 3Server386 Guide.

11. Did the backup fail or perform poorly during an over-the-
network backup?

If you are backing up files from one server to another, both
the source and backup server need their CIOSYS and 3+Share
settings properly tuned.

If the CIOSYS and 3+Share settings are all right, check the
cable between the two servers.

12. Did the backup fail during a PC server backup?

If 3+Backup fails while backing up a  PC server, try backing
up only the D partition.  If the backup is successful, your
problem may be in the C partition.

Check the version of DOS in the C partition.  3+Backup
requires DOS 3.1 or higher.

13. Did the backup fail on a server with expansion units?

If 3+Backup fails to back up a server with expansion units or
performs poorly while doing so, use the 3OPT program to check
the "Adjust CIOSYS Buffer Pools" screen.  If the expansion
unit hard drive is formatted in partitions larger than those
on the base unit, assign a separate buffer pool to the
expansion unit partitions.  See "'Adjust CIOSYS Buffer Pools'
Screen" in the "Tuning CIOSYS Parameters section" of the 3+Backup
1.5.2 User Release Notes.

Check the "EMS left for CIOSYS buffers" field on the "Adjust
CIOSYS Buffer Pools" screen.  If the amount shown is less
than recommended for the server, install more EMS in the
source server.

Try backing up only the base unit.  If backing up only the
base unit works, the problem could be on your expansion disk.

If backing up only the base unit does not work, try backing
up only the expansion unit.  If backing up only the expansion
unit works, the problem could be on your base unit.

If backing up only the expansion unit does not work, then
check the tuning guidelines for this server.

14. Did you recently change the server configuration?

If you have added higher capacity disks or expansion units
and have not increased EMS memory on that server, you should
do so.

If you get the server back to its original state and the
problem goes away, then the problem is with the recent
changes.

15. Have you checked the cable connections between the source and
backup server?

If not, do so.

16. Are the jumper settings correct for the tape drive?

To find out, place a tape in the drive, turn your server off,
and then turn it back on.

If the tape drive is a Tandberg (with a door that swings
down) or a Wangtek (with an open tape slot), you should hear
it  "shoe-shine," that is, wind briefly one way and then the
other, when you turn on the server.

If the tape drive is an Archive (with a sliding door over the
tape slot), you should hear a brief ratcheting sound when you
turn on the server.

If your tape drive does not behave as described, remove the
drive and check its jumper settings.  See the 3Server Drive
Options Guide for correct settings.

17. Does your model server require SCSI terminating resistors in
its tape drive or elsewhere?

Make sure that all SCSI devices that are connected to the
server and require SCSI terminating resistors have SCSI
terminating resistors installed.  Also make sure that all
other SCSI devices are free of SCSI terminating resistors.
See "Terminating the Server's SCSI Bus" in the 3+Backup 1.5.2
User Release Notes for details.

18. Do you follow standard procedures with backup tapes?

You should regularly rotate your backup tapes.

If your backup tape is new, erase it twice and clean the tape
drive heads before running the backup.

19. Is the correct tape driver installed on your server?

Make sure you have the correct tape driver in the server's
root directory and listed as a device in its CONFIG.SYS file.

3Server and 3Server3 servers require the TDRIVE.SYS driver.

3Server386 and 3Server/500 servers require the TAPE.SYS driver.

The System Software #1 diskette that you use to establish the
console connection with the server also requires the correct
tape driver (in the \DRIVERS directory off the root).

20. Were you using a 120 MB tape cartridge?

If you are backing up to a 120 MB tape cartridge on a 3Server
or 3Server3, that server's CONFIG.SYS device line for
TAPE.SYS must include the /120 parameter.  If it does not,
add it.  For example:

    device = tape.sys /120

21. Still no luck?

If you suspect software problems, use the 3OPT program to
generate a server configuration report (see "Generating
Server Reports" in the 3+ Network Tuning Guide), and contact
your network supplier.

If you suspect hardware problems, run the TAPETEST.EXE
program.  Run steps A, B, C, and Q.  Then contact your
network supplier.
