Virtual TapeServer 8.2 Release Notes

Known Issues | 52
 If a mount command is sent to a non-existent virtual tape drive, VTS reports
that the tape is missing, not the drive. When a mount request is received by EMS, if
the request specifies a tape drive that is not configured on the VTS, VTS sends a
notification to the host that the tape is not found. It should send a notification that the
drive is not found. (TL-2293)
 VTDs intermittently stop on NonStop if tapeserver is restarted repetitively. If
tapeserver is restarted several times in a row, the connection could be lost from the VTS
to host. (TL-1844)
WORKAROUND: Stop, reset, and restart the tape drive(s) from the host.
 Device names beginning with $ result in ems_hostdevs and ems_virtdevs are not
logged. If VTS is used with an HP NonStop host and the device names begin with $, the
ems_hostdevs and ems_virtdevs values are blank in the log. This can cause confusion if
reviewing the logs. (TL-1562, EAR 4030)
SMTP and notifications
 Clicking Send without an email address on SMTP Settings page leaves web
interface in Sending state. When configuring SMTP settings, if you leave the email
address blank and click Send, the web interface displays an error message but leaves the
button in “Sending” mode. If you type a valid email address, it is not reset to Send. (TL-
7374)
WORKAROUND: Click the Apply button on this page and then the button is reset and
you can re-validate the email address.
 Running a disabled job does not generate an email. A notification email will not be
sent when a disabled job is run. (TL-6820)
 Low disk space alert messages are sent regardless of the notifications_interval
parameter setting. This parameter specifies how often to check for notifications,
suggesting that it will limit the interval for the low disk space notifications to the host.
However, this parameter is not used. (TL-5159, EAR 6839)
 Subject Line Prefix not used in email notifications. Though you can specify a
Subject Line Prefix when configuring SMTP settings for email notifications, the prefix is
not used. (TL-5137)
Clustering (GFS)
 Unmigrating a virtual tape may fail in a GFS environment if the migrate was
performed on a different node in the GFS cluster than the node performing an
unmigrate. (TL-7572, EAR 8787)
 GFS cluster will not start if hostname is specified with uppercase and lowercase
characters. (TL-7265)
WORKAROUND: Specify GFS hostnames using lowercase characters only.
 Generating a troubleshooting package with GFS takes a long time. When VTS is
configured in a GFS cluster, it may take a long time to gather information used to create
the troubleshooting package. (TL-6915)
 Cannot resolve the hostname in a GFS environment without a DNS server.
Currently, you cannot configure GFS to use a fully qualified domain name without the use
of DNS. (TL-6874)