Virtual TapeServer 8.4 Release Notes
Known Issues | 33
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 al
l 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 tape 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: Rem
ove the cartridge from the VTL, perform the move, and then
reinsert the cartridge back into the VTL.
Data Encryption (SecureVTS)
An individual cartridge that is a member of an encrypted pool cannot be
decrypted from the Virtual Media Page. The Jobs page will indicate that the
decryption succeeded, but the Virtual Tapes page will still show the tape as encrypted.
(TL-8557)
WORKAROUND: Decry
pt the individual cartridge using the Advanced Media Actions
page.
Encrypting a pool will force all the virtual tapes within that pool to be
encrypted. In order to decrypt a single tape within an encrypted pool, encryption needs
to be turned off for the entire pool. (TL-8098)
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: Ad
d 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 faile
d 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-
0970)
WORKAROUND: R
estore the defaults for closed access control, close the browser, and
relaunch the browser.