Virtual TapeServer 8.3 Release Notes

Resolved Issues and Enhancements | 13
 File size limit of 2TB could be overridden through the Pool Management page in
the UI. If you set the virtual tape limit above 2TB, VTS would not get an EOM before the
file system reached the file limit and failed the I/O to VTS. This has been resolved. (TL-
2171)
 No virtual tapes were displayed after clicking Clear Cache. When you clicked
Clear Cache, the cartridges were removed from the page and you had to refilter to display
the tapes. Now a message states “Clearing cache and intiating a data collection job” and
the page is refreshed. The page refresh clears the filters, so the desired filter must be
selected. (TL-7598)
Manage Virtual Devices (Manage Connections)
 VTD type was displayed incorrectly when editing a VTD. When you edited a SCSI
VTD, the FC option was selected and the SCSI option was disabled, so you could not save
the VTD without switching its type and moving it to a different port. The VTD type is now
displayed correctly. (TL-7651)
Certificate Management
 A certificate that is generated through the GUI would not properly install. The
certificates were being installed in the wrong directory. This issue has been resolved. (TL-
8038, EAR-8982)
VTL
 AIX 6.1 and AIX 7.1 were unable to recognize a Virtual Tape Library. AIX 6.1 and
AIX 7.1 were unable to recognize a Virtual Tape Library when the Virtual Tape Library
and a real tape library of the same type were both connected to the same fiber channel
port. This issue has been resolved. (TL-7820, EAR-9029)
 Selecting a “3580” tape type in a “TS3500” library resulted in errors. In previous
versions of 8.X, the “3580” tape type appeared in the “TS3500” library configuration as a
possible tape drive type within the library. Choosing this type would result in errors when
attempting to use the library. Other “ULT3580” types were available and worked
correctly. Now, the “3580" tape type has been renamed to “ULT3580-TD1” and will work
correctly if selected for the “TS3500” tape library. (TL-7768)
 A Virtual Tape Library (VTL) that failed to start caused other libraries to be
disabled. If a VTL failed to start at startup, processing would stop, which caused any
subsequent libraries to be disabled. The processing will continue now. (TL-7720)
 VTL with “$” in the name did not respond correctly to an inquiry. In addition the
VTL could not be deleted. A VTL can now contain “$” in the name. (TL-7451)
 VTL with up to 31 LUNs could be created though only 30 LUNs were discovered
by the host. Now all 31 LUNs can be created and will be discovered by the host. (TL-
7454)
 VTL could be deleted if a virtual tape was in a virtual tape drive. The system
should have prevented the removal of a VTL when there was a virtual tape in a virtual
tape drive. A VTL can no longer be removed if it is in use. (TL-7545)
 VTLs failed if virtual tapes were not deleted before the containing VTL was
deleted. Virtual tapes had to be removed from the VTL before the VTL was deleted.
Failure to do this could have resulted in failure of all VTLs on the system. This issue has
been fixed. (TL-7634, TL-7622)