Virtual TapeServer 6.04.02.01 for NonStop Servers Release Notes

Known Issues | 22
f. Issue the following commands to find the boot device:
chroot /mnt/sysimage
grep boot= /boot/grub/grub.conf
Note the device returned by the grep command (/dev/cciss/c0d0, /dev/sda/, and so on).
g. Install GRUB on the device. /dev/cciss/c0d0 is used in this example:
grub-install /dev/cciss/c0d0
h. Exit the chroot environment and reboot by issuing these commands:
exit
reboot
Upgrade process does not ensure all processes are shut down. The upgrade may
not shut down all processes before starting. (TL-3196)
WORKAROUND: Shut down processes before upgrading, on the Supervisory Functions
page.
Restore fails if restore image contains a copy of the MACHINEID file. If there are
multiple copies of the /boot/MACHINEID file on the system, the restore image will be
unusable. Only one instance of this file should exist on a system and it should not be
copied to another system. (TL-3188)
Database restore fails if SecureVTS is licensed. If a SecureVTS license is enabled
and then a database backup is created, restoring the database backup will fail. (TL-3133)
After downgrading from 6.04.02, files that were installed with 6.04.02 remain on
the system. The files can be ignored. (TL-3167)
Restoring database from previous version corrupts VTS. If a database is backed up
using the Download Database page and then restored on a later version of VTS, VTS
becomes inoperable. (TL-2521, EAR 4873)
WORKAROUND: Create a VTS system restore image (from the Supervisory Functions
page).
Must reconfigure and re-enable multipath devices prior to rebooting after
restoring System Restore Image. After restoring a System Restore Image, you must
take extra steps to completely restore VTS. See the Reinstalling appendix in the Virtual
TapeServer Operations and Administration Guide for details. (TL-2378)
Browser cache and cookies may become stale after an upgrade. This could cause
some features of the VTS web interface to not work as expected, such as not being able to
mount a cartridge with autoloading enabled. (TL-1191)
WORKAROUND: After an upgrade, clear the browser cache and cookies.
If upgrade is performed from a Telnet session, upgrade can exit leaving server
in an unrecoverable state. If the Telnet window closes unexpectedly, the system could
require additional steps for recovery and to complete the upgrade. (TL-905)
WORKAROUND: Perform the upgrade from the system console.
All VTS servers should be upgraded. To avoid potential interoperability issues, all
VTS servers should be upgraded to the same release level (6.04). This is particularly
important to ensure stability in a VTS GFS environment.