Virtual TapeServer 6.04.02.01 for NonStop Servers Release Notes

Known Issues | 14
 Creating cartridges in an encrypted pool when SecureVTS is not running
generated confusing message. If SecureVTS is not running and you attempt to create
cartridges in an encrypted pool, messages similar to the following are displayed. (TL-
3048)
Created 0 of 10 in P17 of size 2T successfully: Cartridge BBB000 in
P17 failed encryption rc=254
 Restoring corrupt key database succeeds when it should not. If you “Restore from
Disaster Recovery Site” and select a corrupt key database file, the file is restored
successfully with no error. (TL-3005)
 Incorrect error message displayed when restoring key database with incorrect
file permissions. If the file permissions are incorrectly set for the key database file, the
web interface will display “Unable to restore backup because login credentials are
incorrect” if you attempt to restore the file. (TL-3001)
 Errors are logged to encry_key.log during exports and uploads. During exports
and uploads, messages similar to the following are logged to encry_key.log:
Fri Mar 6 08:51:59 2009 [6632]: Error: missing device specification!
These log messages can be ignored. (TL-2772)
 Decrypting or encrypting a cartridge not owned by bill causes the system to
hang. If a user attempts to encrypt or decrypt a cartridge that is not owned by bill, the
system makes a copy of the file into <CARTNAME>.<RANDSTR>/temp.vts but hangs
when attempting to write the cartridge back to the original file.The web interface simply
attempts to refresh, allowing no other connections in. To check cartridge ownership, run
ls -al from the VTS server command line for the /VAULT##/POOLNAME/. (TL-2063)
 Misleading, informative message is added to log file when an unencrypted
cartridge is mounted. If SecureVTS is enabled and an unencrypted cartridge is
mounted, a message similar to the following is added to the SecureVTS.log file:
Tue Sep 30 09:22:14 2008: [statinfo:27849 vt] SecureVTS file mounted
and key acquired
This is an informative log file message; there is no error condition. (TL-1206, TL-2189)
 If the storage connected to the VTS server becomes unavailable during an
upgrade, SecureVTS may not function correctly after. For example, if /VAULT01 (a
Fibre-attached ext3 file system) was available prior to the VTS upgrade but unavailable
during any part of the upgrade procedure, and SecureVTS was enabled, SecureVTS may
not function correctly after the upgrade. (TL-2315)
WORKAROUND: Maintain all storage connected to the VTS server during the entire
upgrade procedure. If the problem with SecureVTS occurs, recover with the following
steps:
1. Restore connectivity and function to all storage that was available prior to the upgrade.
2. From the Linux command line, execute “/usr/local/tape/bin/ks_backup restore” (as bill).
3. From the Linux command line, execute “sudo service te-server start” (as bill).
 A quoted SecureVTS license key does not enable SecureVTS completely. If you
enter a SecureVTS license key and surround it with quotes, SecureVTS is not fully
enabled. The Virtual TapeServer Licensing page reports “Secure VTS Key successfully