Virtual TapeServer 6.04.05 for NonStop Servers Release Notes

Upgrade and Downgrade | 8
7. Click OK to continue. The server is downgraded.
8. Reboot the VTS server.
9. Launch the web interface and navigate to the System Status page to verify that the
version was uninstalled.
Upgrade and downgrade issues
 Upgrade or downgrade may fail if web interface is refreshing. The system status
page displays information from the database, and it refreshes automatically. If the page
refreshes during an upgrade, the database update could fail because the database is open
by the refresh. This could cause the upgrade to fail. This could also happen during a
downgrade, and the system restore may fail to restore the system. The system could then
be left in an unusable state. (TL-5203)
 RPM warnings during upgrade. When RPMs are installed on a system, there are
occasional conflicts where the new RPM has a configuration file which is different than
the configuration file currently on the system. When this happens, the configuration file
on the system is renamed to xxx.rpmsave and the new configuration file inside the RPM is
delivered. This new configuration file may have new/different settings than the previous
configuration. (TL-5313)
If you have not added any software to the VTS other than what was delivered in the
product and have not made any changes to configuration files on VTS other than what
was directed by the product documentation, this message may be safely ignored. However,
if the you have made configuration changes or added software to VTS, you should scan the
log file to determine what changes were made and if those changes affect your
configuration or software. These changes are not the responsibility of VTS.
 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)
 System unusable if hostname is changed after upgrade and a downgrade is then
performed. After an upgrade, if the system's hostname was changed by an
administrator, if a downgrade is then performed, it will fail to complete, leaving the
system in a unusable state. (TL-5196)
WORKAROUND: Do not change the hostname of the system. If the hostname has
changed, reset it to its pre-upgrade hostname prior to performing a downgrade.
 Upgrade fails 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 server process from /usr/local/tape/bin during an upgrade,
the upgrade could fail. (TL-5007)
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 downgrading from 6.04.05, Apache displays warning message. After
downgrading from 6.04.05, the Apache configuration file (used for the web interface) is
unchanged on downgrade and thus points to a resource that does not exist in the
downgraded version. This warning can be safely ignored. (TL-5872)