Virtual TapeServer 6.04.05 for NonStop Servers Release Notes

Resolved Issues and Enhancements | 10
Resolved Issues and Enhancements
The following changes have been incorporated into the software since the 6.04.04 release.
General operations
 Virtual devices functioned correctly after restart or reboot and appeared in the
web interface correctly but were inaccessible from the host. Virtual devices may
have been inaccessible from the host though they functioned correctly after a restart or
reboot and properly displayed in the web interface. This has been fixed. (TL-5349)
 VTDs were not started properly and the host did not see VTDs after upgrade. On
DL380 G6 servers with more than four cards installed, or on all DL585 G1 servers, VTDs
created on host buses higher than 9 were incorrectly converted during the upgrade. Thus,
ports could not be enabled and the host could not see the ports.This issue has been fixed.
(TL-5437)
 Mounting a virtual tape as Read-Only changed mtime and may have resulted in
data loss. This issue is seen in 6.04.03.xx, 6.04.04, and 6.04.04.01. If you mount a virtual
tape as Read Only, the mtime (modify time) of the most recently written virtual tape,
which may not be the virtual tape being mounted as Read-Only, is incorrectly modified to
be the previous time that the virtual tape was modified. This error can result in the
actions taken based on the virtual tape’s mtime being incorrectly performed. For example,
Scan/Cleanup could erase tapes that are not meant to be erased due to the earlier mtime
indicated. Additionally, if a backup management application is in use and it uses mtime to
decide what data should be backed up, the expected file(s) might not be backed up if there
have been virtual tapes mounted as Read-Only. This issue has been fixed in this release.
(TL-5708, EAR 6904)
Note If you implemented the workaround for this issue by editing the vts.conf file to
add engine_KeepFileTimeChange=’YES’, remove this line after updating to
6.04.04.02. This workaround caused SPHiNX to always change a virtual tape's
mtime when SPHiNX actions were performed on the virtual tape, thereby
avoiding this issue. The workaround should be removed so that a backup
management application does not backup unnecessary files.
 Error message written to debug log if a physical tape drive was added that was
similar to an existing one. If an Ultrium physical tape drive was attached to VTS and
one was already in the database, an error message may have appeared in the debug log
indicating that it was unable to add this physical tape to the database. This has been
fixed. (TL-2290)
 Operations failed and errors were logged when log files exceeded 2GB in size.
When a log file grew to over 2GB in size in less than a day, some commands failed and
errors similar to the following were logged. This has been fixed. (TL-3139)
ERROR: C06001 is locked by Filesize limit exceeded.
 Could not delete a VTD after upgrading from 6.04.01 directly to 6.04.04. After
applying 6.04.05, you can now delete VTDs. (TL-5501)
 Could not create VTDs on ports in slot 8 after upgrading DL585. The value of the
PTLI for the VTD is now stored to allow VTDs on to be created in slot 8. (TL-5447)