Virtual TapeServer 8.0 Configuration Guide

Troubleshooting | 133
Exporting an encrypted tape:
A message similar to the following is displayed on the web interface:
Thu 2008-01-17 09:49:31: SHARE:SH0000 Export data transfer failed,
rc=3
Erasing all virtual tapes in a pool on the Cartridge Maintenance page:
A message similar to the following is displayed on the web interface:
Erased 1 cartridge; Erasure of cartridge SH0002 in pool SHARE failed!
Setting the virtual tape size on the Pool Maintenance page:
A message similar to the following is displayed on the web interface:
Unable to set size limit on SHARE:SH0001, rc=2. Operation aborted!
After the operation aborts for the encrypted tape, any tapes for which this operation is
attempted will also fail.
You can also check /usr/local/tape/log/SecureVTS.log, which logs all tape operations
associated with encryption. Go to the bottom of the log to look for problems.
Log files
VTS provides many log files for troubleshooting issues with various functions of the system.
For example, the EMS log contains all messages (dependant on filters) received from the
NonStop server and the responses sent from VTS. VTS adds text that describes successful or
unsuccessful mounts, VTSPolicy commands that were interpreted, and so on. This file enables
you to diagnose the EMS configuration to and from the NonStop.
To access logs from the VTS web interface
Click SupportLogs on the navigation pane and then click a link to examine logs.
This section provides in-depth information about several of the logs. Refer to the online help
for information about using the web interface to view and download log files.
Event log
The event log file is an especially useful log that is generated by VTS. It records information
about system events, such as the creation and deletion of virtual tapes, failures of processes
and services, and the status of jobs and policies. The messages include information about the
time and date of the event as well as the name of the user who initiated the event. Use the
messages in this file to detect problems, track down the source of faults, and audit users. In
addition, information in the system event log can be retrieved by third-party applications,
such as Prognosis or Insight Manager, for notification purposes.