BackPak H4.00 Troubleshooting and Messages Manual

Troubleshooting
8 BackPak H4.00 Troubleshooting & Messages
Note that this trace control works correctly only when a VTC receives activity (i.e.
load requests) from a single BackPak domain; this might require to stop EMS
Extractors of domains sharing the same VTC but have different trace setting for the
VTC..
It is also possible to control the trace level in the file BBFcEmulAppCfg.xml. See the
Appendix D in the BackBox User Manual
.
Installation.log is written by the BackBox SETUP.EXE installer.
LB<label>.log is written by the various services accessing the storage of virtual
volumes.
A file is written per volume virtual, the file name prefix is LB for labelled volume and
NL for un-labelled volumes.
For “unlabelled volumes”, the file name is (NL<pseudo-label>.log).
These logs are written only if the VTC tracing is enabled in BBSL.OPT (See the
Appendix D in the BackBox User Manual
), and in very specific cases such as when
errors are detected during the checking of the integrity of a tape volume stored
through the TSM API.
These files are not purged from old entries. Detailed tracing (more than level 1)
must not be kept enabled for long periods of time.
MESMessageLog_<n>.log
Messages about the forwarding of local messages forwarded to NonStop EMS.
Complement to EVMessageLog_<n>.
These logs are automatically purged: up to 5 or 10 occurrences of these files of
limited size are produced in a round-robin fashion.
ScriptControllerBackupNskSession_<n>.log
Messages about the forwarding of local messages forwarded to NonStop EMS.
Complement to EVMessageLog_<n>.
ScriptControllerLog_<n>.log
Messages written by the Script controller handling BACKUP requests.
ScriptControllerLogR_<n>.log
Messages written by the Script controller handling RESTORE requests.