Virtual TapeServer 6.04.03.02 for NonStop Servers Release Notes

Resolved Issues and Enhancements | 8

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)

EMS

 Split EMS lines may not have matched, causing missed mounts. Backups ran

slowly and mounts were missed if the mount line was split into two lines that should be

matched by MATCH 61 (first line) and MATCH 62 (second line); the first line was not

matched. This caused the MATCH 62 to skip the mount because the variables that should

be set by the first line were not set. This has been fixed. (TL-4039, EAR 5671, EAR 5929)

 Tapes were mounted as “tape not write enabled”. In rare cases, tapes were mounted

by EMS but the tape was not write enabled. The backup hung until the tape was

unmounted and remounted. This no longer occurs. (TL-3147)

Utilities and services

 Debug log consumed too much space. The debug log was flooded with messages

similar to the following:

[vtmeta] MODULE ENTRY: UNKNOWN (0000/00/00, 0.000)

While this message was not an error, it caused the file to grow and consumed filesystem

space. This has been fixed. (TL-4241, EAR 6277)

 getVTS_dbginfo now includes network and operating system information.

Network configuration information, including ifconfig and ethtool output, and operating

system information, including sysctl -a output and the /etc/sysctl.conf file for evaluating

performance, have been added to getVTS_dbginfo output. (TL-4048, TL-4208)

 PostgreSQL log files were filling up the file system. The postgresqlDAY.log files in /

var/lib/pgsql/data/pg_logs were filling up the filesystem with as much as 1GB per day

logging bill connections and disconnections from database. This has been fixed. (TL-4051,

EAR 6075)