Virtual TapeServer 6.04.04 for NonStop Servers Release Notes

Resolved Issues and Enhancements | 17
 TapeServer processes are no longer restarted after installing a patch or interim
release (IR). TapeServer processes are no longer restarted after an update. The user
must reboot the system when indicated after the patch or IR install is complete. (TL-4304)
 Reboot required after applying update. If you update the VTS server using the Apply
Software Change page, a message is now displayed indicating that you must reboot after
applying the change. (TL-4086)
 XMLRPC service had to be stopped before downgrading. The service is now
stopped before a downgrade. (TL-4002)
 System restore image timed out and Huh? message displayed if old system
restore image resided on system. Creating a system restore image may have timed
out if the file was too large and a Huh? error message was displayed. This has been fixed.
(TL-3968)
 Restoring a backup succeeded if versions do not match. If you attempted to restore
a system restore image that was a different version than the current system, the restore
succeeded. This has been fixed. (TL-4006, TL-3971)
 Ambiguous redirect error displayed if you restored an image that had been
restored. If you attempted to restore a system image from the version of VTS that has
already been restored, an “ambiguous redirect” error message was displayed though the
restore succeeds. This has been fixed. (TL-3961)
Documentation
 Documentation did not state that a static IP address is required for GFS
environments. If GFS is configured in your environment, you must configure the VTS
server to use a static IP address. This is now documented. (TL-4554)
 Operations and Administration Guide indicated that vaults should have 755
permissions. Vaults should have 750 permissions, not 755. This is to prevent locked-
down accounts, such as vtsa, from listing the contents of vaults. The documentation has
been updated. (TL-4266)
 Operations and Administration Guide stated that port 443 was not used. This
was not correct. All web traffic is redirected to port 443, and the documentation has been
updated. (TL-4049)
 Documentation stated 4TB was the maximum partition size then provided
examples that created 4.4TB partitions. Documentation has been changed to indicate
that 5TB partitions are allowed. (TL-4102)
 Documentation did not indicate to run fsck on all disk subsystems. This has been
fixed. (TL-4107, EAR 6174)
 Workarounds were not documented for sudden shutdowns. Following a hard
(unclean) shutdown of VTS (such as a system crash or loss of power), the system may be
left in an inconsistent state. Many services running on the server use PID files to tell the
system that a service is running. When a service is started, the PID file is created. When a
service is shutdown, the PID file is deleted. If VTS is shutdown uncleanly, the PID files
will not be deleted. When the system comes back up, it assumes that the service is
running and does not try to restart the service. This will cause VTS to function incorrectly
or not at all. This is now documented in the troubleshooting section of the Administration
Guide. (TL-3444)
 Return codes for export failures are now documented. Refer to the Administration
Guide for the codes. (TL-4543)