Virtual TapeServer 8.3 Release Notes

Known Issues | 47
 Autocopy locks the source cartridge but not the target. VTS is not locking and
could cause the cartridges to be corrupted if they are not used on the remote side. (TL-
2529)
 AutoCopy may create pools on a server that could not otherwise be created.
AutoCopy may be used to create pools on a VTS server that could not otherwise be
created, such as having both a 'TEST' and a 'test' pool. (TL-868)
WORKAROUND: When using AutoCopy, you may need to review of all AutoCopy pools
to ensure that there are no duplicate pool names and correct for any such occurrences.
 Online help incorrectly describes the All Files option. In the online help provided
on the Instant DR page, the All Files option is described as follows:
“This option pertains to the use of wildcards in the source cartridge name. If All Files is
not checked, then only the most recently modified file in the set of cartridges identified
with the wildcard will be backed up. Checking All Files bypasses this selection process
and causes all of the wildcard identified files to be backed up.”
The description should read as follows: “Select the All Files checkbox if you want to send
all the files listed in the job to the remote system. If you do not select this checkbox, only
the newest virtual tape (determined by the timestamp) is transmitted.” (TL-369)
EMS
 If the web server is restarted, it may fail to restart. This may occur because EMS
has taken ownership of UDP port 80 which the web server requires. To resolve this
problem reboot the VTS. (TL-7494)
 Event Management System may not start after a system restore. After applying a
system restore image, the Event Management System (EMS) may not start. If EMS
was configured, the ownership of the file /usr/local/tape/log/ems.log may need to be
changed to bill.bill. (TL-8112)
WorkAround: Ownership can be changed with the following command: chown bill.bill /
usr/local/tape/log/ems.log
 If ems_keep_alive_interval is set too small, a “keep-alive lost!” message is
generated. If the ems_keep_alive_interval is set too small, a very large number of
Event Monitoring System (EMS) messages may be queued. This could result in a
“keep-alive lost!” message being generated. (TL-8124)
WORKAROUND: To avoid this keep the value of the ems_keep_alive_interval parameter
just smaller than the timeout value for telnet or SSH depending on which is being used
for EMS.
 Missing EMS messages after VTSPolicy completion. Some completion messages
may be missing from the EMS log. (TL-6835)