Virtual TapeServer 8.0 Release Notes

Upgrade and Downgrade | 14
 Error displayed when downgrading a system that does not have a capacity
license. The following error will be seen when downgrading a system that does not have a
capacity license:
mv: cannot stat '/usr/local/tape/etc/capacity_license': No such file
or directory
This is a benign error that can be ignored. (TL-6844)
 Reverting to a previous version may revert the system to an unexpected
version. The upgrade process determines the version to revert to by checking the
timestamps of all system backup images in the /home/bill directory and reverting to the
last (newest) backup image in that directory. If the timestamps have changed on the
backup images due to touching or moving the images, the wrong image may be used to
revert. (TL-6152, EAR 7329)
WORKAROUND: If the system backup image timestamps have changed as a result of
touching or moving the images, identify the image that needs to be used by looking at the
timestamps in the filename. Then, issue the touch sysbackup-image_name.tbz
command from the command line before clicking the revert link in the web interface. This
will cause the proper backup file to be used when reverting to a previous version.
 The sysbackup file listed in the upgrade log is not always correct. The variable
that is used to hold the sysbackup filename during upgrade processing is sometimes
incorrectly overwritten, which results in the wrong sysbackup name being listed in the
upgrade log. This is a logging issue only and does not affect functionality. (TL-6150)
 Version updated though upgrade fails. If an upgrade fails, the system may display
the incorrect version. This is misleading. (TL-6180, EAR 7386)
WORKAROUND: Confirm the upgrade is successful by reviewing the upgrade-
YYYYMMDD-HHMMSS.log log.
 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
opened 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)