Virtual TapeServer 6.04.03.01 for NonStop Servers Release Notes

Known Issues | 21
 Empty labeled encrypted cartridges may show a compression ratio. An encrypted
cartridge that is labeled and then decrypted will show 0 size and a compression ratio. Re-
encrypting that cartridge will continue to show a compression ratio. This does not reflect
the compression ratio that a cartridge will display once data is written to that cartridge
and can safely be ignored. (TL-1155)
 Empty, unlabeled encrypted cartridges may show a compression ratio. If a blank
cartridge is labeled and then encrypted, the cartridge shows a compression ratio. If a
blank cartridge is encrypted and then labeled, it does not show a compression ratio. The
file sizes of the two cartridges are slightly different. This does not reflect the compression
ratio that a cartridge will display once data is written to that cartridge and can safely be
ignored. (TL-1088)
 Encrypting a cartridge after it is created can take much longer than encrypting
a cartridge during creation. After-the-fact encryption can take up to eight times longer
than on-the-fly encryption. (TL-1150)
 Attempting to mount a cartridge that cannot be decrypted causes repeated
mount requests. If a host server requests the mount of an encrypted cartridge that VTS
cannot decrypt, VTS continually attempts to mount the cartridge every six seconds. (TL-
1136)
 Removing a key generator may cause a delay before cartridges can be
encrypted again. After removing a key generator, if there are any key generators left, it
may take up to 5 minutes before cartridges can be encrypted again. (TL-1121)
 If the RSA key of a remote host changes, SecureVTS operations to that host may
fail. Typically, the RSA key will not change unless the operating system on that host is
reinstalled. If the RSA key does change, attempts to backup a key database to the host
with the changed RSA key may fail. Attempts to delete and re-add that backup host may
also fail. (TL-1074)
WORKAROUND: Manually delete the entry for the remote host from the
/home/bill/.ssh/known_hosts file.
 If the SecureVTS local backup file is written to /home/bill/, an error message is
written to the ks_backup.log file. The error message indicates a permission problem
when attempting to change the file's ownership. This error may safely be ignored. (TL-
1073)
 Adding a key database backup host fails but lists erroneous error message if too
many characters are specified in the fields. When adding a key database backup
host and entering very long host names (such as 256 characters), user names (256
characters), or destinations (512 characters), adding the host will fail but the message
may indicate that the server was not responding. (TL-1056)
 Cannot re-log in to the SecureVTS web interface using the Log In button. If you
are logged in as a non-administrative user, you must close the browser window and log in
again as an administrator to access SecureVTS functions. The Log In button on the
interface will not log you in as another user. (TL-1033)
 SecureVTS automated key database backups do not log their backups to the
event.log file. For details on automated backups, consult the ks_backup.log file. (TL-
1001)