Virtual TapeServer 6.04.03 for NonStop Servers Release Notes

Known Issues | 27
 Labeling a virtual tape in an Autocopy pool logs error messages in ems.log.
Messages similar to the following are logged when a tape in an Autocopy pool is labeled.
Sat May 26 07:28:36 2007 DEV4: 07-05-26 13:20:09 \DEV4.
TANDEM.TAPE.G06 000659 : STATUS 1512 - TOOL14 TAPE DISMOUNTED FROM
DRIVE
Sat May 26 07:28:36 2007 DEV4: DISMOUNT Cartridge: TOOL14,
doAutoCopy: 2.
Sat May 26 07:28:36 2007 DEV4: ems_telnet.AUTOCOPY Error
autocopy_Host for TOOL14 is not configured.
The tape is mounted and dismounted during labeling, which causes AutoCopy to copy the
tape to the backup system. AutoCopy should copy a tape to the backup system only when
a tape is used, not labeled. (TL-405)
 Online help incorrectly describes the All Files option. In the online help provided
on the Instant DR page, the All Files option is described as follows:
“This option pertains to the use of wildcards in the source cartridge name. If All Files is
not checked, then only the most recently modified file in the set of cartridges identified
with the wildcard will be backed up. Checking All Files bypasses this selection process
and causes all of the wildcard identified files to be backed up.”
The description should read as follows:
“Select the All Files checkbox if you want to send all the files listed in the job to the
remote system. If you do not select this checkbox, only the newest virtual tape
(determined by the timestamp) is transmitted.” (TL-369)
GFS
 Pool Maintenance page loads slowly in a GFS environment. When you display the
Pool Maintenance page in a GFS environment, the page gathers all of the file system
statistics using the df command. On a busy GFS system or cluster that is fencing, df
hangs. (TL-434)
Utilities and services
 RSH must be disabled if not running Instant DR, to pass security vulnerability
reports. RSH is enabled by default. (TL-3927)
WORKAROUND: To disable RSH, log in to the server as root, edit /etc/xinetd.d/rsh to
change the line that reads “disable = no” to “disable = yes”. Then, run the “service xinetd
reload” command.
 hp-ilo module cannot rebuild itself after an upgrade then downgrade. When
performing an upgrade from 6.04.02, kernel headers are not backed up. Upgrading to
6.04.03 upgrades the kernel headers, which removes the old kernel headers. If you
downgrade to 6.04.02, there are no kernel headers for the 6.04.02 kernel. Therefore, there
is now way to install the hp-ilo module, which is part of the HP monitoring tools. The hp-
ilo module rebuilds itself when it is installed, and with the missing kernel headers after
the downgrade, the module cannot be built. (TL-4008)