Virtual TapeServer 6.04.03.01 for NonStop Servers Release Notes

Known Issues | 28
 “URL not found” message displayed when creating a system restore image with
insufficient disk space. If there is not enough space to create a system restore image,
the user should be notified that there is not enough space rather than a “URL not found”
message. (TL-4176)
 System restore image is incomplete if there is insufficient disk space before
image. When attempting to create a system restore image on a system that does not have
enough disk space, no warning is displayed indicating that there is not enough room.
Instead, files are omitted from the TAR file. (TL-4021)
 System restore does not handle database restore failure well. If a problem occurs
while restoring the database during a system restore, the server may be left with a partial
or no database. The return code indicates a failure, though it is unclear how to resolve the
failure. (TL-4099)
 System restore image may duplicate database entries. Applying a system restore
image may duplicate database entries, causing the system to malfunction. (TL-4003)
WORKAROUND: Log in to the server, su to bill, and stop the vts_xmlrpc_server service:
service vts_xmlrpc_server stop
Then, apply the system restore image.
 Restoring database from previous version corrupts the server. 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)
Documentation
 Operations and Administration Guide indicates 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. (TL-4266)
 Operations and Administration Guide states that port 443 is not used. This is not
correct. All web traffic is redirected to port 443. (TL-4049)
 Documentation states 4TB is the maximum partition size then provides
examples that create 4.4TB partitions. Documentation should be changed to indicate
that 4.4TB partitions are allowed. (TL-4102)
 Documentation should indicate to run fsck on all disk subsystems. (TL-4107, EAR
6174)
 Workarounds should be documented for sudden shutdowns. Following a hard
(unclean) shutdown of VTS (such as a system crash or loss of power), the system may 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. Here is an example of a service failing to start due to a stale PID file that
resulted from a crashed server, in /var/log/messages. (TL-3444)
Nov 6 12:29:18 ProdVTS rhdb: Starting PostgreSQL - Red Hat Edition
service: failed
WORKAROUND: Reboot the server twice. This will allow the server to clean up the PID
files as the server shuts down and allows all of the necessary services to start properly
when the server boots up.