BackPak H4.00 Troubleshooting and Messages Manual

Troubleshooting
4 BackPak H4.00 Troubleshooting & Messages
INTRODUCTION
This manual applies to both BackBox and BackLib products.
The TROUBLESHOTING chapter provides hints or procedures to handle abnormal
events.
Some frequent or special cases have dedicated documentation in this chapter.
All BackPak numbered messages are described in the last chapter MESSAGES.
TROUBLESHOOTING
Source of information
In addition to the immediate symptom present on the output of a tape application or
on a BackPak GUI page, an error in BackPak produces most of the time messages in
the
NonStop EMS log that always must be browsed.
The various sources of information are listed below. Then the tools to send a case
documentation to the Product Support are presented.
Log in NonStop
The EMS log that is already the main console for the NonStop tape system, is also
the main console for BackPak. In all abnormal events occurring during regular
operations or during installations and updates, the EMS log must first be browsed.
EMS will gather:
− the messages from the NonStop tape system
− the messages from the BackPak NonStop components
− a copy of the most important messages logged by the VTCs in the MS-
Windows platform
The BackPak distribution set contains an EMS filter for the messages above, and a
sample obey file (OEMS) that extracts these tape related messages to an Enscribe
file. Before executing OEMS, edit it by TEDIT it to update the period to select.
The OEMS2 obey file (macro to fetch by “RUN OEMS2”) extracts the current tape
messages to the TACL home-terminal. It is useful to start before trouble shooting
tests when there are numerous non-tape related EMS messages in a busy system.
EMS log is even useful to get more details about symptoms shown in the GUI.
For an issue related to the operation of a tape device, check EMS from the time the
mount request was issued by $ZSVR. If the tape device is not attached to the node