Release Notes HP Virtual TapeServer for NonStop Servers Product Version: 6.04.04.01 October 2010 Part Number: 639609-001 © 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 Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Installation and Configuration. . . . . . . . . .
EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Utilities and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Installation, upgrades, updates, and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Issue Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
Installation and Configuration This section describes how to access information about installing and configuring the release 6.04.04.01 of VTS. It also provides compatibility notes. Installation, upgrade, update, and downgrade The following documentation provides information about installing, upgrading, updating, and downgrading VTS: Initial installation and configuration is described in the Virtual TapeServer Quick Start Guide.
VTS emulates the following tape drive types: IBM Ultrium 3580 TD1 IBM Ultrium 3580 TD3 IBM Ultrium 3580 TD4 Compaq Network Services Division 5257 IBM 519x Quantum SDLT320 Quantum DLT7000 IBM 3490 Ultrium-1 SCSI HP LTO Ultrium-3 SCSI Backup management application support Host connections are supported with the following backup applications: From Windows Server 2008 hosts: • Symantec Veritas NetBackup 6.5, 6.5.4, and 7.
Upgrade and Downgrade This section provides procedures for upgrading, updating, and downgrading the VTS server(s) in your environment. It also provides a list of known issues related to upgrade and downgrade. Upgrading the VTS server If you are upgrading from 6.03.x, you must upgrade to 6.04.01 before upgrading to 6.04.04. Refer to the 6.04.01 Virtual TapeServer Operations and Administration Guide for information about upgrading to 6.04.01. This guide can be found at http://docs.hp.
9. If you are upgrading from 6.04.01 or 6.04.02 to 6.04.04, complete these steps: a. Type the full path to the UPG file in the field: b. Click SUBMIT to begin the upgrade. c. Verify that the following messages are listed on the page: You MUST re-run this upgrade for the process to complete! Revision Update Successful! System must now be rebooted. d. Do not reboot. Instead, click Supervisor Functions on the navigation pane. e. Click Apply Revision Update. 10. Select From File on the following page. 11.
Requires the System Upgrade/Update Functions access right To update VTS 1. If necessary, unzip the IR package. Then, on the system from which you access the Virtual TapeServer server, copy the .VTSINSTALL and .VTSUNINSTALL files to a local directory. 2. Log in to the VTS web interface. Click the Log In button at the top of the page and enter a username and password. 3. Click Supervisor Functions on the navigation pane. 4. Click Apply Software Change. The following page is displayed: 5.
Requires the System Upgrade/Update Functions access right To downgrade VTS 1. Verify that at least 1GB of free disk space is available on the VTS server before downgrading. 2. If possible, locate the system restore image that was created before the system was upgrade. The version of the system restore image should match the version to which you will be downgrading. Store this image in a safe location. 3. If necessary, log in to the VTS web interface.
Upgrade process does not ensure all processes are shut down. The upgrade may not shut down all processes before starting. (TL-3196) WORKAROUND: Shut down processes before upgrading, on the Supervisory Functions page. Downgrade may attempt to load a bad system restore image. If you attempt to downgrade and the system restore image taken during the upgrade was renamed to a similar filename, the downgrade process succeeds until it attempts to untar the .tgz file.
Resolved Issues and Enhancements The following changes have been incorporated into the software since the 6.04.04 release. General operations Could not delete a VTD after upgrading from 6.04.01 directly to 6.04.04. After applying this IR, you can now delete VTDs. (TL-5501) Could not create VTDs on ports in slot 8 after upgrading DL585. The value of the PTLI for the VTD is now stored to allow VTDs on to be created in slot 8.
Known Issues The following known issues, or “errata,” apply to the 6.04.04 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 34. Hardware and configuration VTDs are not started properly and the host does not see the VTDs after upgrade.
General operations Writing to VTD fails if you attempt to create a VTD on same bus. If data is being written to a VTD and you attempt to create a VTD on the same bus, writing fails with this error: Cannot write: Input/output error (TL-4464) Mode page response to compression is enabled by default. This setting is enabled by default and static for each emulation.
Segfaults occur during shutdown and reboot. A performance monitoring agent may segfault during shutdown. This causes no system impact. (TL-3320) Corrupt virtual tape causes server to become unresponsive. If the VTS server loses power during a backup, causing the corrupt cartridge, the backup will fail. (It is likely that the host running the backup will log a failure message.) As a result, VTS may become unresponsive. (TL-3512) WORKAROUND: Erase the resulting virtual tape and rerun the backup.
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 This section has been subdivided to better classify the issues. General Importing invalid certificate displays error. Attempting to import an invalid certificate displays the error “Nested asn1 error”. (TL-4822) System Status page indicates that TEST_UNIT_READY command was processed and complete, but no commands were processed. The System Status page indicates that a TEST_UNIT_READY command was completed.
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”.
VTD names and serial numbers should not be case-sensitive. When creating VTDs, the web interface checks the case of the specified VTD name and serial number. However, VTD names and serial numbers are not case-sensitive on the host server. For example, you can create VTAPE01 and vtape01 on the VTS server, but the host server only sees VTAPE01. (TL-3212) WORKAROUND: Do not specify VTD names or serial numbers that have the same combination of letters, no matter the case.
Web interface shows incorrect size of a cartridge that was created by the host server and then erased. With an empty cartridge, the label and trailer size are combined. When the cartridge is erased, the label remains, but the trailer is removed. If there is data on the cartridge, the label size is accurate before and after the erase. (TL-3020) Cartridges not owned by bill are not erased as indicated in the interface and log file. However, the debug.
Firefox improperly renders Cartridge Maintenance page when Multiple Select checkbox is unchecked. If you use Firefox to view the interface and you deselect the Multiple Select option on the Cartridge Maintenance page, the browser renders the page incorrectly, displaying items in the wrong place and not preserving information. (TL-346) WORKAROUND: Click the Clear Form button to correct the display problem.
SecureVTS No notification that restore fails because remote key server was not added after restoring from a disaster recovery site. The local key server should be removed prior to restoring the key database. The web interface should notify the user when a restore from a disaster recovery site fails because a local key server already exists. (TL-4399) Key database restore fails if an IP address is used instead of a hostname.
used as a backup, use the Restore from Disaster Recovery Site button rather than the restore icon under the Action column of the table of backups when restoring the key database. Error message indicates that host is not responding instead of incorrect username if erroneous username is specified. When adding a key database backup host, if you enter an incorrect username for a backup host, an error message is generated that indicates that the host is not responding.
the key as submitted was not valid. Afterward, the (invalid) key is not displayed. (TL-2320) WORKAROUND: Submit all license keys with surrounding characters removed. If a quoted license key was submitted, on the Licensing page, click the Update checkbox, type or paste the correct license key, and then click SUBMIT. Doing this will discard the invalid license key and replace it with the correct one. When restoring a SecureVTS key database, initial attempts may fail and indicate that the file is not found.
If the RSA key of a remote host changes, SecureVTS operations to that host may fail. Typically, the RSA key will not change unless the operating system on that host is reinstalled. If the RSA key does change, attempts to backup a key database to the host with the changed RSA key may fail. Attempts to delete and re-add that backup host may also fail. (TL-1074) WORKAROUND: Manually delete the entry for the remote host from the /home/bill/.ssh/known_hosts file.
VTSPolicy commands Q_INC and Q_DIFF variables used in the CommVault VTSPolicy backup all cartridges. Q_INC and Q_DIFF variables used in the CommVault VTSPolicy should backup the changed cartridges since the last backup. Instead, all cartridges all in the pool are backed up. (TL-2770) VTSPolicy BEX Erase is ignored. The Erase parameter of the VTSPolicy BEX command is not functioning and, if included, is ignored. (TL-2363) WORKAROUND: Issue the VTSPolicy ERASE command after the VTSPolicy BEX command.
menu_ScanCleanup=”YES” parameter, which displays the scan/cleanup option from the window drop-down list on the Virtual Media page (TL-505). WORKAROUND: Add this line to the VTS configuration file. To edit the VTS configuration file, click Supervisor Functions on the navigation pane, and then click Edit Configuration File under the Utilities section of the resulting page. Cartridge having less than minimum size is listed as erasable in Scan/Cleanup after migration.
EMS Vault restrictions in EMS configuration not working. In the EMS configuration, the option to restrict vaults accessed by VTS is not working. A cartridge that resides in a restricted vault can be mounted and written to. (TL-4857) Supervisory Functions page shows EMS started when it did not. If EMS could not be started, the System Status page indicates that it is not running while the Supervisory Functions page shows EMS as started.
AutoCopy and Instant DR Adding backup host fails if ICMP is blocked. When adding a backup host, VTS attempts to ping the backup server name. If ICMP is blocked, adding the backup host fails even if SCP is configured and functioning properly. (TL-4371, EAR 6359) Unlabeled cartridges are not copied to target server. Cartridges that are unlabeled and have been written to from the host server are not copied to the target server during AutoCopy.
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 Activity log is not displaying messages in date order. The latest job should be on the top. (TL-4299) WORKAROUND: Use the Clear Log button to correct the UI.
Message logged to console and /var/log/messages until iLO is configured. Until HP-iLO is configured, the following message may continue to print: INIT: Id "s1" respawning too fast: disabled for 5 minutes The message is also logged to /var/log/messages with no other information. (TL-2279) System restore Old system restore images remain in /var/www/html/tmp. The server may run out of disk space because old system restore images remain stored in /var/www/html/tmp.
Troubleshooting This chapter includes information about product features that need improvement or may cause user error. Hardware and configuration Starting a VTD on the NonStop results in two errors logged to debug.log. Immediately after the NonStop command “SCF START TAPE $VTAPE00” is issued to start a virtual tape device, one or more of the following messages may appear on the VTS server in /usr/local/tape/log/debug.
General operations Performance degrades when a disk fails because disk cache writes are disabled. When a disk fails within a RAID set, the controller will automatically turn off disk cache writes. This will decrease system performance because of this degraded condition. After the failed disk is replaced and the RAID set is rebuilt, performance will return to normal without need of intervention. Contact Support for field replacement instructions.
The “mount /dev/cdrom” command no longer works because CD media is handled differently. The new VTS operating system (CentOS 5.2) handles removable media mounting differently than in previous releases. Removable media is automounted on /media through the Hardware Abstraction Layer (HAL) without entries in /etc/fstab in much the same manner as removable media in Windows XP. From the console, however, media is not automounted. (TL-1755) Linux kernel error message logged to /var/log/messages.
AutoCopy An error message from ems_telnet.pl indicates that AutoCopy is not configured. For AutoCopy to work as designed, manual procedures that mount a tape must end with unmounting the tape. AutoCopy depends on receiving mount and unmount messages through EMS to work correctly, and when a tape is manually mounted, the EMS subsystem is unaware of this. When the manual operation is completed, the tape must be unmounted manually. (TL-1480) VTSPolicy Incremental backup backs up all cartridges.
Installation, upgrades, updates, and restore No disk space available after an upgrade. After an upgrade, there exists the potential to exceed the amount of available disk space. (TL-3885) WORKAROUND: Increase the root partition from 10GB to 20GB. In addition, you should regularly remove unused files, such as those located in the /tmp and /var/log directories. /usr/local/tape/log/vts-post-install.log contains FATAL error messages. The VTS installation log, /usr/local/tape/log/vts-post-install.
Issue Index EAR 4030 Device names beginning with $ result in ems_hostdevs and ems_virtdevs are not logged.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 EAR 4286 Virtual tape appears to be created in a locked pool but is not. . . . . . . . . . . . . . . . . . . . . . . 15 EAR 4360 Apache servers are prone to cross-site scripting weakness. . . . . . . . . . . . . . . . . . . . . . . . .
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-1205 TL-1206 TL-1239 TL-1287 TL-1480 TL-1562 TL-1662 TL-1741 TL-1752 TL-1755 TL-1802 TL-1804 TL-1836 TL-1844 TL-1853 TL-1869 TL-1886 TL-1903 Non-SecureVTS servers do not indicate when cartridges are encrypted.. . . . . . . . . . . . . .
TL-1920 TL-1962 TL-1985 TL-1997 TL-2061 TL-2063 TL-2079 TL-2086 TL-2141 TL-2155 TL-2158 TL-2171 TL-2173 TL-2179 TL-2189 TL-2201 TL-2255 TL-2272 TL-2279 TL-2280 TL-2287 TL-2290 TL-2292 TL-2293 TL-2303 TL-2317 TL-2320 TL-2324 TL-2342 TL-2347 TL-2350 TL-2358 TL-2363 TL-2365 TL-2367 TL-2388 TL-2390 TL-2521 TL-2529 TL-2551 TL-2629 TL-2641 TL-2645 TL-2770 TL-2772 Certain Access Control settings cause each update cycle to prompt for a password. . . . .
TL-3001 TL-3005 TL-3011 TL-3012 TL-3020 TL-3032 TL-3041 TL-3048 TL-3052 TL-3063 TL-3071 TL-3105 TL-3117 TL-3125 TL-3139 TL-3151 TL-3152 TL-3156 TL-3165 TL-3168 TL-3170 TL-3171 TL-3174 TL-3175 TL-3190 TL-3196 TL-3212 TL-3278 TL-3300 TL-3304 TL-3310 TL-3320 TL-3377 TL-3429 TL-3440 TL-3456 TL-3463 TL-3491 TL-3512 TL-3549 TL-3562 TL-3643 TL-3686 TL-3702 Incorrect error message displayed when restoring key database with incorrect file permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-3721 TL-3756 TL-3772 TL-3788 TL-3853 TL-3877 TL-3878 TL-3885 TL-3940 TL-3948 TL-3950 TL-3954 TL-3962 TL-4000 TL-4003 TL-4008 TL-4011 TL-4018 TL-4021 TL-4025 TL-4033 TL-4035 TL-4046 TL-4073 TL-4099 TL-4108 TL-4141 TL-4163 TL-4176 TL-4232 TL-4235 TL-4286 TL-4287 TL-4299 TL-4308 TL-4311 TL-4313 TL-4368 TL-4371 TL-4391 TL-4399 TL-4434 TL-4464 TL-4584 TL-4607 TL-4689 TL-4804 TL-4822 Cannot edit VTD named “0”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-4857 TL-4859 TL-4940 TL-4956 TL-5007 TL-5044 TL-5063 TL-5111 TL-5136 TL-5428 TL-5447 TL-5463 TL-5501 TL-6411 Vault restrictions in EMS configuration not working. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Last Mounted time incorrect for new cartridges on Manage Connections page. . . . . . . . . 18 System Status page indicates that TEST_UNIT_READY command was processed and complete, but no commands were processed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
