Virtual TapeServer 6.04.04 for NonStop Servers Release Notes

Known Issues | 30
 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)
 Error message erroneously logged if the local copy of the key server backup
utility changes volumes and is placed in another vault. If the local copy of the key
server backup utility changes volumes and is placed in another vault, it may trigger a
critical error in the event log indicating a duplicate pool. This critical log entry can be
ignored. (TL-984)
 Non-SecureVTS servers do not indicate when cartridges are encrypted.
Encrypted cartridges will not show any indication of encryption if listed on a VTS that
does not have encryption enabled. (TL-977)
 Unmounted vaults may cause a key database restore to fail. If a vault is not
mounted, it may cause a key database restore to fail. (TL-951)
WORKAROUND: Remove the backup host and force a backup with the Backup to All
button. Then, restore using the Restore From Disaster Recovery button. After the restore
is successful, re-add the backup host.
 A corrupt key database backup can be propagated to all key database backup
hosts. If a key database backup is corrupted, the corrupt backup can be propagated to all
key database backup hosts. (TL-941)
WORKAROUND: Archive key database backups on a regular basis. Store archives
outside of the VTS environment to ensure that you can return to a working copy of the key
database in the unlikely event that the copy in use becomes corrupted.
 The ks_backup.log file may contain DOS line terminations. Some lines in the
ks_backup.log file contain DOS line terminations, which may appear as ^M if viewed with
certain editors. (TL-930)