Virtual TapeServer 8.3 Release Notes

Troubleshooting | 56
Web interface
 Changing tape library settings could cause the drives to be unusable. When a
tape library was changed from random access mode to auto loader mode, the Physical
Device settings could become confused. This caused the changer to be disconnected and
the drive entries could not be edited from the Physical Drives page. This can be avoided if
the settings in the Manage Settings page are first changed to “Disabled” for the device
and saved, followed by the device being changed to auto loader mode. (TL-7812)
 Adding a new certificate does not display the new certificate page. If the browser
recognizes the uploaded certificate's authority as a verified authority, no warnings are
generated. Firefox and IE will not generate a warning for a signed certificate if the chain
follows to a trusted authority. On Firefox and IE, installed SSL certificates information
can be obtained directly from the browser's address bar. (TL-6598)
 TapeServer and EMS service can be stopped and started by user who is not
logged in. If the user did not log in on an open system, the user can access the
TapeServer and EMS links on the Manage System Tasks page. (TL-3440)
 Reserved VTDs are available when creating an export job. If you create a mount
job in the future, you can choose a VTD that is currently in use. When the job runs, VTS
will determine that the VTD is available. (TL-4620)
 Logging in to web interface on localhost does not redirect to secure page. When
accessing the web interface from the localhost, HTTPS is not needed because data is not
transmitted. (TL-3643)
 Browser may display old data or errors if not refreshed. If an unexpected error
occurs or data appears to be old, refresh the browser. Old data is cached and may need to
be cleared. (TL-1662)
 File size of a mounted tape being written may not be updated. If a virtual tape is
mounted and being written to, the size shown on the page may not be updated until the
tape is dismounted. Normally, this value will be updated when file marks are written to
the tape, so usually this is not an issue for most users. (TL-881)
VTL
 Must remove reservations before disabling a VTL. If you cannot disable a VTL
though no virtual tapes are loaded in the VTDs, make sure no reservations exist for one of
the VTDs in the VTL. For AS/400, this can be done by “varying off” the MLB device or de-
allocating the TAP devices. (TL-3837)
 Multiple tape device types may not be supported in a VTL. Using mixed tape
devices within the VTL will only function as well as the host backup software functions in
that environment. Typically, this can cause the host software to confuse tape types and
drive types. It is recommended that all tape drives are of the same type. (TL-3844)
VTSPolicy commands
 Memory issues occur when too many concurrent VTSPolicy migrations are
attempted. At most, one migrate per physical tape drive should occur at any one time.
(TL-6135, EAR-7280)