Release Notes HP Virtual TapeServer for NonStop Servers Product Version: 6.04.03 March 2010 Part Number: 586322-004 © 2004 - 2010 Hewlett-Packard All rights reserved No part of this document may be copied in any form or by any means without prior written consent of HP. All drawings, schematics and artwork used in the manufacture of the products described herein are copyrighted.
Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Overview of features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Installation and Configuration. . . . . . . . .
AutoCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VTSPolicy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Utilities and services . . . . . . . . . . . . . . . . . . .
Introduction Virtual TapeServer (VTS) is a fully integrated virtual tape, hardware and software solution. VTS allows host systems to read from and write to a local or SAN-attached file system. Data is automatically migrated to a tape device based on policies or manually migrated to physical tape for archival storage or disaster recovery, if long-term backup copies are required.
• Compatibility with Mediacom and DSM/TC • Support for migration through the use of backup management applications Optional features that further enhance the benefits of VTS include the following: • Global File System (GFS) support — Offers enhanced access to shared vaults and eliminates single points of failure by deploying multiple VTS systems into a set of clustered nodes.
Installation and Configuration This section describes how to access information about installing and configuring the release 6.04.03 of VTS. It also provides compatibility notes. Upgrades and updates If you are upgrading from 6.03.x, you must upgrade to 6.04.01 before upgrading to 6.04.03. Refer to the 6.04.01 Virtual TapeServer Release Notes and Operations and Administration Guide for information about upgrading to 6.04.01. To upgrade from 6.04.
Backup management application support The following backup applications were tested and are supported for use with VTS: Symantec Veritas NetBackup 6.5 IBM Tivoli Storage Manager 5.5 EMC RSA Legato Networker 7.4 CommVault Galaxy 7.0 Browser support The following browsers are supported for use viewing the VTS web interface: Microsoft Internet Explorer 6.
Resolved Issues and Enhancements The following changes have been incorporated into the software since the 6.04.02 release. Hardware and configuration Maximum block size for host connections is 256k. Previously, this limit was not documented. (TL-3810, EAR 5863) General operations Fibre Channel resources were lost after command was aborted.
Files may have accumulated in /var/spool/clientmqueue, possibly filling up the file system. Mail generated on the local system was stored in /var/spool/clientmqueue until sendmail or other mail transfer agent picks it up for delivery. Logwatch no longer generates email output for delivery to root. (TL-865, EAR 3395) Web interface PHP error messages were in Apache error_log. Error messages may have been listed in /var/log/httpd/error_log when a VTD was created or modified. This no longer occurs.
SecureVTS Encryption or decryption failed if cartridge was also being mounted by EMS. If you encrypted or decrypted a cartridge while EMS was performing the copy/compare step, the encryption or decryption failed. This has been fixed. (TL-3178) comForte SSH now supported when connecting to host systems for EMS using TACL. comForte SSH can now be configured for each EMS host. (TL-3361) EMS Before configuring EMS, log in to each Nonstop for which comForte SSH will be used for EMS.
SSH connection for EMS accepted any fingerprint from the remote system. Previously, when connecting with an SSH connection to an EMS remote host for the first time, any DSA key fingerprint was accepted. Now, the first connection must be made manually so that the fingerprint can be verified and accepted if correct. If the fingerprint changes, the connection will not be made. If the fingerprint has not been accepted, the EMS connection will fail.
Upgrade failed if EMS was running. Now, the upgrade process properly shuts down EMS before upgrading. (TL-3148) Documentation Configuring a closed access account without access to cartridges was not documented. The guides now include this procedure, in the Access Control chapter.
Known Issues The following known issues, or “errata,” apply to the 6.04.03 release. The issue tracking number is provided in parentheses. Refer to this number when making inquiries to Technical Support. There is a table of tracking numbers listed in ascending order, with the summary and document section number, in Issue Index on page 36. Hardware and configuration No automatic reboot after setting system limits on Fibre Channel ports.
General operations Editing a VTD without a license causes the VTD to be deleted. If the license is removed and then you attempt to edit a VTD, the system deletes the VTD. (TL-3962) vtsa user cannot issue mount command. From the command line, the vtsa user cannot issue the /bin/mount command. (TL-3981) WORKAROUND: Log in as bill and su to root, or log in as root, to run this command. Ownership of files is changed if encryption software is run by root.
Cannot cancel pending mounts. The web interface indicates “Cancelled 0 pending mounts” but pending mounts are re-queued and given new reqnums every six seconds. The clearmount process attempts to match the reqnum of the pending mount. If they match, the pending mount is cancelled. If they do not match, the pending mount is not cancelled, as indicated by this message in the interface and log: “Error: clearmount found no match in mount queue for reqnum 000000663”.
Failures may occur if an autoloading pool contains an invalid cartridge. Only valid cartridges should be added to pools within vaults. If other files are there, inconsistent or unpredictable behavior may occur. (TL-3125) WORKAROUND: Restart the Tapeserver service. Error message written to debug log if a physical tape drive is added that is similar to an existing one.
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.
Web interface Web interface does not clearly indicate location of system restore image. The web interface does not indicate that the restore image file is saved on the local file system. It also does not warn the user that the Save File dialog might be blocked. (TL-4011) WORKAROUND: Ensure browser pop-ups are enabled. Cartridge size check done on Cartridge Maintenance page instead of Pool Maintenance page.
is displayed indicating that the license key is already present. The message is displayed even though the key has not been saved. (TL-3175) WORKAROUND: Navigate away from and back to the page. Virtual Media page loads slowly if expanded pool contains many cartridges. If you view or refresh the Virtual Media page and a pool that contains many cartridges is expanded, the web interface is very slow to display the page.
No message is displayed when system restore image is created. If you create a system restore image, the web interface should display a message before creating the image. Currently, the web interface does not indicate that it is creating the image and the page may be blank for several minutes. (TL-3105) Ultrium 1 physical tape drive not displayed in web interface.
Pop-up windows display stale, cached data. When pop-up windows are displayed, some browsers may display stale, cached data rather than the current information. (TL2342) WORKAROUND: To ensure that the information is accurate, use your browser's refresh or reload function to update the information. Long pool names cause cartridge creation to fail but report success.
SecureVTS If invalid license key is used, SecureVTS appears to be configured though it is not. If an invalid license key is used, no key generator is created. The server should indicate that the license key is not valid. (TL-3549) Cannot encrypt or decrypt after upgrade to 6.04.x. If you upgrade to 6.04.x, you cannot decrypt cartridges that were encrypted before the upgrade and cannot encrypt existing cartridges. SecureVTS-upgrade.log shows the following. (TL-3692) Copied /VAULT00/.
SecureVTS cannot restore key database from remote server if backup file name contains a period. When trying to restore from a remote host, an error message similar to the following is generated if the backup file name contains a period. (TL-3168) Unable to restore backup because remote_host does not exist in the database. WORKAROUND: When specifying a file to be used for the destination for a remote backup of a key database, do not include a period in the file name.
Misleading, informative message is added to log file when an unencrypted cartridge is mounted. If SecureVTS is enabled and an unencrypted cartridge is mounted, a message similar to the following is added to the SecureVTS.log file: Tue Sep 30 09:22:14 2008: [statinfo:27849 vt] SecureVTS file mounted and key acquired This is an informative log file message; there is no error condition.
SecureVTS encryption operations performed when no key database backup host is configured causes the web interface to remain busy for up to 10 minutes. If SecureVTS encryption operations (creating an encrypted tape, encrypting an alreadyexisting tape) are attempted when no Key Database Backup/Restore Hosts are configured, the web interface will appear busy for up to 10 minutes before displaying an error message.
Cannot re-log in to the SecureVTS web interface using the Log In button. If you are logged in as a non-administrative user, you must close the browser window and log in again as an administrator to access SecureVTS functions. The Log In button on the interface will not log you in as another user. (TL-1033) SecureVTS automated key database backups do not log their backups to the event.log file. For details on automated backups, consult the ks_backup.log file.
VTSPolicy TSM Archive command for a vault results in an error message. Issuing a VTSPolicy TSM Archive command for a vault will fail to back up the vault. An error message such as “Error: /VAULT00 not on this system” will be written to the VTS log. (TL-221) WORKAROUND: A vault may be backed up by issuing VTSPolicy TSM Archive commands for the individual pools or cartridges in the vault. Scan/Cleanup Scan/Cleanup is not enabled though the web interface indicates that it is. scanat.
Error, miscellaneous messages logged after successful NetBackup migration. Message similar to the following are logged in the debug log after a successful migration with NetBackup 6.5: Fri Nov 7 14:45:27 2008: [slave_signal_thread 15713] SIGCHLD received while no active child, ignoring it. Fri Nov 7 14:45:32 2008: [cli_tape 0x05000107] ERROR UNKNOWN tape command 0x44 for Id 0 Fri Nov 07 14:46:15 2008: [lsof.pl] Error: lsof.
Mounts fails when ems_virtdevs and ems_hostdevs entries are delimited by commas. In vts.conf, the entries for the ems_virtdevs_ and ems_hostdevs_ must be separated by a space. Using a comma delimiter does not work. (TL-2292) If a mount command is sent to a non-existent virtual tape drive, VTS reports that the tape is missing, not the drive.
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 TANDEM.TAPE.G06 000659 : DRIVE Sat May 26 07:28:36 2007 doAutoCopy: 2. Sat May 26 07:28:36 2007 autocopy_Host for TOOL14 DEV4: 07-05-26 13:20:09 \DEV4. STATUS 1512 - TOOL14 TAPE DISMOUNTED FROM DEV4: DISMOUNT Cartridge: TOOL14, DEV4: ems_telnet.AUTOCOPY Error is not configured.
XMLRPC and Ruby logs are not rotated. The XMLRPC and Ruby production log files are not rotated according to the logrotate settings. (TL-3997) WORKAROUND: Check the size of the log files periodically. To rotate the logs, restart the logging processes. EMS service should be started before drives are initialized. EMS log reports that the drive requested for the mount had an invalid BLTI because the drive had not been started.
System restore image may duplicate database entries. Applying a system restore image may duplicate database entries, causing the system to malfunction. (TL-4003) WORKAROUND: Log in to the server, su to bill, and stop the vts_xmlrpc_server service: service vts_xmlrpc_server stop Then, apply the system restore image. Cannot use a system restore image for a different version. You cannot use, for example, a 6.04.02 restore image on a 6.04.03 system.
Authorization required when upgrading or restoring system image after a downgrade. If you are logged in to the web interface, an Authorization Required message is displayed if you attempt to restore a system image or upgrade after a downgrade. (TL-3827, TL-3735) WORKAROUND: Restart the browser after downgrading. Temporary files are not removed after an upgrade. After upgrading to 6.04.03, temporary files remain in the temporary directory prefixed /tmp/vtsupg_XXXXXX.
Documentation Workarounds should be documented for sudden shutdowns. Following a hard (unclean) shutdown of VTS (such as a system crash or loss of power), the system may left in an inconsistent state. Many services running on the server use PID files to tell the system that a service is running. When a service is started, the PID file is created. When a service is shutdown, the PID file is deleted. If VTS is shutdown uncleanly, the PID files will not be deleted.
Troubleshooting This chapter includes information about product features that need improvement or may cause user error. Hardware and configuration Fibre Channel ports do not initiate link status and lasers are off if ports are set to target mode and VTDs are not defined. When a Fibre Channel port is enabled for target mode, the port will not initiate link status until a VTD has been defined on that port and the lasers will be off. The port will appear to be disconnected unless a VTD has been defined.
Nov 15 failed Nov 15 (0x69) 13:46:52 vts15 kernel: isp0: Mailbox Command 'GET FW STATE' (TIMEOUT) 13:46:52 vts15 kernel: isp0: Interrupting Mailbox Command Timeout (elapsed time 100 jiffies) When encrypting or decrypting a cartridge and Tapeserver stops, temporary directory and file are not deleted. Do not stop Tapeserver or restart VTS unless the system is quiesced. (TL-3071) SCSI EJECT command on an empty VTD hangs the calling client's mt command.
Web interface 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) Apache servers are prone to cross-site scripting weakness. VTS uses version 2.2.
EMS The default interval for EMS keep-alive messages has been increased to 300 seconds. If you upgraded VTS to 6.04.02, verify the keep-alive interval to ensure that a reasonable value is being used in the EMS configuration in vts.conf. Or, disable the keepalive messages if not needed. (TL-3174) Utilities and services HP monitoring services web interface may become unresponsive. (TL-3063) WORKAROUND: snmpd may need to be restarted by running “service snmpd restart” as root.
Issue Index EAR 3395 Files may have accumulated in /var/spool/clientmqueue, possibly filling up the file system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 EAR 4030 Device names beginning with $ result in ems_hostdevs and ems_virtdevs are not logged.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-0880 TL-0881 TL-0905 TL-0930 TL-0941 TL-0951 TL-0970 TL-0977 TL-0984 TL-0996 TL-1001 TL-1033 TL-1035 TL-1039 TL-1041 TL-1051 TL-1056 TL-1073 TL-1074 TL-1088 TL-1107 TL-1121 TL-1136 TL-1150 TL-1155 TL-1158 TL-1168 TL-1191 TL-1205 TL-1206 TL-1216 TL-1239 TL-1287 TL-1480 TL-1562 TL-1662 TL-1741 If too much data is transferred in a refresh period, the transfer rate and compression ratio displayed on the System Status page may be inaccurate.. . . . . . . . . . . . . . . . . . . . . . . . . .
TL-1752 TL-1755 TL-1802 TL-1804 TL-1836 TL-1844 TL-1853 TL-1869 TL-1886 TL-1903 TL-1920 TL-1962 TL-1985 TL-1997 TL-2061 TL-2063 TL-2079 TL-2086 TL-2141 TL-2155 TL-2158 TL-2165 TL-2171 TL-2173 TL-2179 TL-2189 TL-2201 TL-2255 TL-2272 TL-2279 TL-2280 TL-2287 TL-2288 TL-2289 TL-2290 TL-2292 TL-2293 TL-2303 TL-2315 TL-2317 TL-2320 TL-2324 TL-2341 When mounting a cartridge over another using the web interface, the second does not get mounted if the first cartridge is already dismounted. . . . . . . . . . . . . .
TL-2342 TL-2347 TL-2350 TL-2358 TL-2359 TL-2363 TL-2365 TL-2367 TL-2378 Pop-up windows display stale, cached data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Error, miscellaneous messages logged after successful NetBackup migration.. . . . . . . . . 25 Cartridge Status pop-up dialog is not updated while a cartridge is mounted.. . . . . . . . . . 17 Scan/Cleanup page performance is slow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-3126 TL-3136 TL-3139 TL-3146 TL-3147 TL-3148 TL-3151 TL-3152 TL-3156 TL-3157 TL-3165 TL-3167 TL-3168 TL-3169 TL-3170 TL-3171 TL-3174 TL-3175 TL-3178 TL-3188 TL-3190 TL-3194 TL-3196 TL-3212 TL-3213 TL-3222 TL-3277 TL-3278 TL-3300 TL-3304 TL-3310 TL-3313 TL-3320 TL-3340 TL-3361 TL-3377 TL-3379 TL-3380 TL-3400 TL-3429 TL-3440 TL-3444 TL-3456 TL-3463 TL-3470 TL-3483 PHP error messages were in Apache error_log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-3491 TL-3512 TL-3549 TL-3552 TL-3562 TL-3643 TL-3668 TL-3686 TL-3692 TL-3701 TL-3702 TL-3714 TL-3721 TL-3724 TL-3728 TL-3735 TL-3740 TL-3756 TL-3772 TL-3788 TL-3810 TL-3818 TL-3827 TL-3853 TL-3877 TL-3878 TL-3885 TL-3900 TL-3907 TL-3917 TL-3924 TL-3927 TL-3940 TL-3946 TL-3948 TL-3950 TL-3954 TL-3961 TL-3962 TL-3963 TL-3966 TL-3967 TL-3968 TL-3971 TL-3981 TL-3997 TL-4000 TL-4001 Manage Connections page does not select available values when creating VTDs. . . . . . .
TL-4002 TL-4003 TL-4006 TL-4008 TL-4011 TL-4018 TL-4019 TL-4020 TL-4026 XMLRPC service must be stopped before downgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 System restore image may duplicate database entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Restoring a backup succeeds if versions do not match. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 hp-ilo module cannot rebuild itself after an upgrade then downgrade. . . . . . . . . . . . . . . .
Index of Resolved Issues by Release 6.04.02.01 TL-3361 comForte SSH now supported when connecting to host systems for EMS. . . . . . . . . . . . . 7 6.04.03 TL-0865 TL-2288 TL-2289 TL-2341 TL-2359 TL-2436 TL-2540 TL-3050 TL-3083 TL-3100 TL-3126 TL-3146 TL-3148 TL-3157 TL-3169 TL-3178 TL-3188 TL-3194 TL-3213 TL-3222 TL-3277 TL-3313 TL-3400 TL-3470 TL-3483 TL-3552 TL-3668 TL-3724 TL-3740 TL-3810 TL-3818 TL-3900 Files may have accumulated in /var/spool/clientmqueue, possibly filling up the file system. . .
