Virtual TapeServer 8.4 Release Notes
Upgrade and Downgrade | 11
Upgrade and downgrade issues
Upgrade may fail because TapeServer process could not be stopped. Processes
can be started intermittently by the web server (such as the System Status page) and cron
jobs. If one of these processes runs a process from /usr/local/tape/bin during an upgrade,
the upgrade could fail. (TL-5007, EAR-10253)
WORKAROUND: Stop
all processes using the service vts-services stop command and
then attempt the upgrade again. If this workaround does not result in the processes being
stopped, contact Support for assistance.
After clustering is updated, downgrading will not revert it to the earlier
version. If you choose to downgrade, the cluster update will not be reverted, and the
newer version of clustering will remain in place. This has been shown to work without
issue on downgraded systems. (TL-7031)
No disk space available after an upgrade. After an upgrade, there exists the potential
to exceed the amount of available disk space. (TL-3885)
WORKAROUND: Regula
rly remove unused files, such as those located in the /tmp and /
var/log directories.
/usr/local/tape/log/vts-post-install.log contains FATAL error messages. The VTS
installation log, /usr/local/tape/log/vts-post-install.log, contains FATAL error
messages regarding missing modules.dep files. These messages can safely be ignored.
(TL-2201)
After upgrading to 8.4, tape to tape exports using the Virtual Tape format will
be incompatible with older versions of the product due to a format change with
the block size used to write to tape. (TL-8575)
WORKAROUND: If co
mpatibility is needed, the Host Native format should be used.
While upgrading to 8.4, multiple “’GET FW STATE’ failed” messages may be
listed on the console. These messages can be ignored. The upgrade completes
successfully. (TL-7697)
Links missing from System Updates page after downgrade. After downgrading,
links may be missing on the System Updates page. (TL-7611)
WORKAROUND: Log
out, shut down the browser, and then relaunch a browser and log
in again.
VTD fails after upgrade if SCSI port is switched to Physical mode while virtual
device is still functioning. Previously, a SCSI port could be switched back to “Physical”
mode while still allowing a “Virtual” device defined on it to function properly. This is no
longer supported, and any port that has a “Virtual” device on it must be in “Virtual” mode.
(TL-5207)
Update process does not roll back changes after a failure. If there is a failure
during the installation of a patch or interim release, an error is returned but the web
interface does not change the version information of the software. The system is left in an
unusable state. (TL-4108)
WORKAROUND: Stop all proces
ses from the Manage System Tasks page and attempt
the upgrade again.