Virtual TapeServer 8.2 Release Notes

Known Issues | 38
 Fibre Channel client lists incorrect number of devices after library definition is
modified. If you remove all Library objects associated with a library definition prior to
editing the definition, the edit operation is allowed even if there are still Physical and
Logical Libraries that reference that library definition. The Edit page shows a warning
that it is not allowed, but it does not prevent the edit. If the Library definition is edited
without all library entities (including Logical and Physical) associated with the Library
definition deleted, the web interface and backend protocol layers become inconsistent.
(TL-2318)
WORKAROUND: Remove all associated library objects (including Physical and Logical),
edit the file again, and recreate the library.
 VLM cannot be loaded if a pool is moved. The full path to a virtual tapes is used
when the virtual tape is added to a VLM. If you attempt to move a pool that contains a
virtual tape referenced by a VLM, the move fails if the virtual tape is locked by VTL.
(TL-1526)
WORKAROUND: Remove the cartridge from the VTL, perform the move, and then
reinsert the cartridge back into the VTL.
Data Encryption (SecureVTS)
 Erasing an encrypted virtual tape requires the encryption key. If the system does
not have the key, the erase will fail and the virtual tape will remain locked. (TL-6606)
WORKAROUND: Use the Mounts and Lock page or restart Tapeserver to remove the
locks.
 Encryption backup uses / if Data Encryption is configured prior to adding
storage vaults. Encryption and decryption operations work successfully, but there are
logs of the failure that change ownership to bill in the ks_backup.log. (TL-5990)
WORKAROUND: Add a VAULT, and then remove and re-add the Data Encryption
license key.
 Encryption fails after failed system restore. This is caused by a failed attempt to
apply a system restore image, which does not match the current version of the system.
The encryption configuration is incorrectly removed before the system restore could be
applied. (TL-5988)
WORKAROUND: Reconfigure Data Encryption after a failed system restore operation.
 After logging in as admin for Data Encryption functions in an open system,
changing access controls to default closed results in excessive numbers of
dialogs. Data Encryption requires login for certain functions in the UI. If you start with
an open system and then close it by setting 'default closed' in 'Access Control', you are
continually prompted for your username and password as you navigate around. Once you
enter credentials on a password section, you are allowed to go back to that section. (TL-
970)
WORKAROUND: Restore the defaults for closed access control, close the browser, and
relaunch the browser.
 No notification that restore fails because remote key server was not added after
restoring from a disaster recovery site. The local key server should be removed prior
to restoring the key database. The web interface should notify the user when a restore
from a disaster recovery site fails because a local key server already exists. (TL-4399)