Virtual TapeServer 6.04.04.01 for NonStop Servers Release Notes

Known Issues | 13
 Tape label not checked when writing to the tape. VTS does not check to ensure that
the label being written on the tape is the same as the name of the tape, thus allowing for
the possibility for a mislabeled tape. (TL-1051)
WORKAROUND: Delete the tape on the VTS host and recreate it with the correct label.
 Pool is restored to a cartridge resulting in data not being stored as expected. If
an exported pool is restored to a cartridge, the data will not be restored as separate
cartridges but will be stored as regular data on one cartridge. (TL-1041)
WORKAROUND: Restore pools to pools, not cartridges.
 Importing a pool into a different pool can create duplicate cartridges. When a
pool is imported, the cartridges are created. If the pool that is being used to import the
pool already has cartridges of the same name as the imported ones, duplication of
cartridges will result. This could cause other pools to disappear, cartridges to display
incorrectly or not appear. (TL-1039)
WORKAROUND: Review cartridges restored in this manner when there might be
conflicts with existing cartridges. You can rename the cartridges from the command line
(log in as the bill user) or delete duplicate cartridges.
 Cartridges created in a batch show the same creation time in the event log.
(TL-996)
 Virtual tape names must be unique. If virtual tape names are not unique, unexpected
results can occur in the VTS interface. For example, an error message might be displayed
after attempting to mount one of the tapes whose name is not unique. (TL-199, TL-219)
 Request to mount cartridge fails if a currently mounted cartridge is unmounted
by another process while processing the mount request. If a request is issued to
mount a cartridge in a virtual tape drive where another cartridge is mounted, the request
is ignored if the mounted cartridge is unmounted while VTS is processing the mount
request. (TL-368)
WORKAROUND: Attempt to mount the cartridge again.
 To disable ISC, two parameters must be set. The
ems_InterSystemCommunication_hosts and interSystemCommunication_enable
parameters must be set to indicate that ISC should be disabled. Otherwise, ISC will still
be enabled. (TL-240)
WORKAROUND: To disable ISC, set these parameters in the VTS configuration file:
interSystemCommunication_enable="NO"
ems_InterSystemCommunication_hosts=""
Then, stop ISC from the Supervisor Functions page.
 No activity or a “hung” command occurs when an import request is issued to a
physical drive that is unavailable. If a physical drive is unavailable (powered off,
cable disconnected, and so on), VTS does not properly handle the error and a timeout does
not occur, causing VTS to hang and require a reboot. (TL-61)