BackPak H4.00 Troubleshooting and Messages Manual

Troubleshooting
9 BackPak H4.00 Troubleshooting & Messages
ScriptControllerRestoreNskSession_<n>.log
Messages about the forwarding of local messages forwarded to NonStop EMS.
Complement to EVMessageLog_<n>.
\Script\<data-store-id>\ sub-directories
Each executed Windows script leaves its output in a file located in a sub directory
named according the Data Store Id of the involved virtual volume:
\Script\DataStoreId\.
The log file is named according executed script with a suffix from #1 to #1000, in
order to re-use the same files and avoid cleanup task.
These logs contain the messages output by the Enterprise Backup clients run by the
scripts.
For example
C:\ProgramData\ETINET\VTC\Log\\Script\WIN1\
ADMIN_BACKUP.CMD#1#
EMULFC_BACKUP.CMD#1#
EMULFC_BACKUP.CMD#2#
EMULFC_RESTORE.CMD#1#
C:\ProgramData\ETINET\VTC\Log\Script\WIN2\
EMULFC_BACKUP.CMD#1#
EMULFC_BACKUP.CMD#2#
EMULFC_RESTORE.CMD#1#
TSM API log and traces
For the BackBox used in conduit mode with the IBM Tivoli Storage Manager API,
consult the documentation for messages written in logs and for control and
interpretation of traces.
C:\ProgramData\ETINET\VTC\Log\DSIERRORLB<label>.log
This is the standard DSMERROR.log file of the Tivoli Storage Manager world. It is the
log of the TSM API for operations related the tape volume <label>.
These logs are always created, and are empty in normal cases.
TSM API Trace
The TSM API can produce very detailed traces, if directed to the MS-WINDOWS
system disk, these traces can be larger than the data processed and make the server
crash.
The level of trace and the trace file is controlled by the DSM.OPT file used for tape
emulation. The setting is dynamic, each load request will initiate a new session with
the TSM API.