Virtual TapeServer 8.3 Release Notes

Resolved Issues and Enhancements | 11
 After updating to version 8.2, the Virtual Device Status section of the System
Status page would be empty. The Virtual Device Status would be empty after updating
to 8.2 if the database contained any pieces of a VTD or VTL that were not connected to a
functioning VTD/VTL. This prevented the System Status page from loading correctly. The
System Status page no longer attempts to display any unconnected VTD/VTLs. (TL-7917,
EAR-9126)
General operations
 Creating a VTD failed on a system running more than 60 days without using a
VTD. If a VTS was up and running for more than 60 days without using any of the VTDs,
some of the fifo files may have been automatically removed from the server. These
missing fifo files caused the creation of new VTDs to fail. Restarting TapeServer would
cause the fifo files to be recreated which allowed a new VTD to be created. In some cases
the TapeServer might have stopped responding which required the VTS to be rebooted.
The fifo files are no longer automatically removed. (TL-8052, EAR-9178)
 If a large number of virtual tapes were deleted at the same time and the key
server was not on the same system that the virtual tapes were on, it could have
taken longer than usual and network traffic might have increased. This issue was
caused by the virtual tapes being erased before being deleted. With encrypted tapes this
results in extraneous network traffic to the key server. A virtual tape is no longer erased
before it is deleted. (TL-8071, EAR-9340, EAR-9341)
 Older troubleshooting packages were consuming disk space unnecessarily.
Older troubleshooting packages were not removed when a new package was created. To
prevent multiple copies of troubleshooting packages from unnecessarily consuming disk
space, the old troubleshooting package are now removed when a new package is created.
(TL-4569)
 Could not edit a Virtual Tape Drive (VTD). On a system that was licensed for VTDs
only, a VTD could not be edited. Nothing would happen when the edit icon was clicked.
This has been resolved (TL-7821, EAR-9292)
 Import from physical library may have failed. Importing physical tapes to virtual
tapes may have failed in multi-tape libraries. This issue has been corrected. (TL-7959)
 A non-virtual cartridge in an autoloading pool caused a fault. If a non-virtual
cartridge existed in an autoloading pool, the module that communicates with the Virtual
Cartridges might have faulted which made the VTD unusable. VTS will no longer try to
load the non-virtual cartridge. (TL-8045, EAR-9252, EAR-9281)
 Web interface erroneously enabled you to eject a virtual tape from a VTD in a
VTL. From the Virtual Drives page, if you attempted to eject a virtual tape in a VTL, the
following errors were generated:
Tue Mar 8 09:58:02 2011: [vtape] Clearing device 2a000407
Tue Mar 8 09:58:02 2011: [server] TS_VTAPE_CLEAR: ERROR reserved and
NOT forced, - return error to vtape
Tue Mar 8 09:58:02 2011: [server] TS_VTAPE_CLEAR: ERROR Device not
found in routing table or not connected.
Tue Mar 8 09:58:02 2011: [vtape] Unrecognized device (btli)
specified: 2a000407
The last two messages were incorrect and you should not be allowed to eject the tape. The
last two error messages have been updated with the correct message. (TL-6310)