Virtual TapeServer 6.04.03.01 for NonStop Servers Release Notes

Resolved Issues and Enhancements | 6

Web interface

This section has been subdivided to better classify the issues.

General

 Could not edit EMS hosts or virtual devices. If more than one EMS host or virtual

device was created, you could not edit any of them other than the first in the lists. This

has been fixed. (TL-3714)

 Logwatch Parent Directory link displayed nested pages. Selecting from the

Supervisor Functions -> Examine Logwatch Output -> Parent Directory link caused the

page to be displayed within the same page. This has been fixed. (TL-3728)

Manage Connections

 Web interface allowed the creation of two devices using same bus and LUN.

Now, if you attempt to create multiple devices using the same bus and LUN, an error

message is displayed: “Unable to create VTL with the specified number of drives as bus 7

lun 1 combination is already in use.” (TL-4259)

 Fields on Edit Virtual Tape page were too small. When editing a virtual tape, the

fields for tape_type and host_type were too small and you could not see what was selected.

The fields have now been resized. (TL-4085, EAR 6135)

 Could not modify the bus number assigned to a VTD. Because of the - (dash) in the

drive's serial number, you could not alter the bus number for the VTD. Any alteration to

the drive's serial number caused any backup application to see the drives as new

hardware. This has been fixed. (TL-3379)

Migration

 NetBackup migrate jobs were marked with “Success message not found” errors.

The success message was written to the NetBackup log after the log was captured by the

hsmput.pl script. Now, a delay occurs before capturing the log file. (TL-4096, EAR 6145)

AutoCopy and Instant DR

 Retry message erroneously given when AutoCopy started. An erroneous error was

given when AutoCopy was started:

2009-11-25

(retry: 1) of /VAULT02/SYDB_TAPEPOOL/B00036 started

instead of the correct starting message:

2009-11-25

VAULT02/SYDB_TAPEPOOL/B00036 started

This has been fixed. (TL-4034, EAR 5982)