Release Notes HP Virtual TapeServer for NonStop Servers Product Version: 6.04.05 February 2011 Part Number: 639318-002 © 2004 - 2011 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 Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Support. . . . . . . . . . . . . . . . . . . . . . . . . .
Clustering (GFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Utilities and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation and help . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction Virtual TapeServer (VTS) is a fully integrated virtual tape, hardware and software solution. VTS offers complete disaster recovery capabilities. As a primary repository for data center backups, VTS can be used as secondary tiered storage for replicated data to meet disaster recovery requirements. Overview of features Release 6.04.05 introduces the following new features and support to VTS: • P2000 support — P2000 MSAs are now supported as external disk storage arrays.
Installation and Configuration This section describes how to access information about installing and configuring the release 6.04.05 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 2003 hosts: • IBM Tivoli Storage Manager 5.5 • Symantec Veritas NetBackup 6.
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.05. 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://h20000.www2.hp.
e. Edit the /etc/hosts file and add gems.rubyforge.org to the 127.0.0.1 line, like this: 127.0.0.1 localhost.localdomain localhost gems.rubyforge.org Note An error message similar to the following may be added to the VTS upgrade log: ERROR: http://gems.rubyforge.org/ does not appear to be a repository. This error message may be ignored. 3. If GFS is in use in your environment, stop the cluster before upgrading. You can use the cluster administration user interface, which is documented here: http://www.
11. Select From File on the following page. 12. In the Location of Revision Update File field, type the full path to the UPG file. 13. Click UPGRADE. 14. Click OK to continue. 15. Confirm that the following message is displayed: Completing Upgrade... Revision Update Successful! System must now be rebooted. 16. Click REBOOT to complete the update. 17. Launch the web interface and navigate to the System Status page to verify that the version was installed. 18.
4. Click Apply Software Change. The following page is displayed: 5. Enter the location and name of the file. Use the Browse button to navigate to the file or type in the full path of the location. 6. Click UPLOAD to apply the changes. 7. Launch the web interface and navigate to the System Status page to verify that the version was installed. VTS automatically reboots. Downgrading the VTS server Complete the following steps if you want to downgrade the server (to a previously installed version of 6.04.0x).
7. Click OK to continue. The server is downgraded. 8. Reboot the VTS server. 9. Launch the web interface and navigate to the System Status page to verify that the version was uninstalled. Upgrade and downgrade issues Upgrade or downgrade may fail if web interface is refreshing. The system status page displays information from the database, and it refreshes automatically. If the page refreshes during an upgrade, the database update could fail because the database is open by the refresh.
Update process does not roll back changes after a failure. If there is a failure during the installation of a patch or IR, an error is returned but the web interface does not change the version information of the software. The server is left an unusable state. (TL-4108) WORKAROUND: Stop all processes from the Supervisory Functions page and attempt the upgrade again. Upgrade process does not ensure all processes are shut down. The upgrade may not shut down all processes before starting.
Resolved Issues and Enhancements The following changes have been incorporated into the software since the 6.04.04 release. General operations Virtual devices functioned correctly after restart or reboot and appeared in the web interface correctly but were inaccessible from the host. Virtual devices may have been inaccessible from the host though they functioned correctly after a restart or reboot and properly displayed in the web interface. This has been fixed.
Web interface Version column showed the marker version of the cartridge prior to 6.04.03. If the metadata isn't available, a hyphen will be shown in this field. With the 6.04.03 release, it always shows a hyphen for this information even when the metadata is available. 6.04.05 correctly displays the information when the metadata information is available.
System restore Restoring database from previous version corrupted the server. If a database was backed up using the Download Database page and then restored on a later version of VTS, VTS became inoperable. Now, the whole configuration is saved and restored together. (TL-2521, EAR 4873) Old system restore images remained in /var/www/html/tmp. The server may have run out of disk space because old system restore images remained stored in /var/www/html/tmp.
Documentation Installation and Administration guides have been combined into the Configuration guide. Links to the configuration guide and help system can be found on the About page. (TL-5827) Quick Start Guide instructed user to log in as root via SSH. SSH to root is not available. The Quick Start Guide now instructs the user to log in as bill and then su to root.
Known Issues The following known issues, or “errata,” apply to the 6.04.05 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 41. Hardware, configuration, and hardware replacement netconfig sequence may leave ethernet port down.
If the controller ID and the host SCSI ID are set to the same value, kernel panics occur. Kernel panics occur on VTS if two devices are set to the same ID. (TL-2303) WORKAROUND: When using SCSI VTDs, make sure the SCSI controller ID is set to something different than your host machine's SCSI ID. Contact your Support representative if need assistance changing the controller ID. Kernel panic may occur if SCSI VTD is edited while host is scanning devices.
During boot up, warning messages displayed about already initialized constants. When booting up, there are warning messages printed to the console, which can be ignored. (TL-5888) Starting vts xmlrpc server Server started successfully, pid file is in /var/www/media/lib Starting cleanup_suspended_jobs.rb: [ OK ] Starting cleanup_termination_fifos.rb: [ OK ] Starting clear_per_destination_transfer_counters.rb: ** Loaded vendor plugin: Certificates /var/www/media/lib/rath_initializer.
Ownership of files is changed if encryption software is run by root. If a program that uses encryption software is run by the root account, ownership of critical files is changed, which will prevent programs from running correctly under normal user authority. The programs that must not be started as root include the following: • ems_master.pl • ems_mounts.pl • ems_send.pl • ems_telnet.pl • hsmdelete.pl • hsmget.pl • hsmput.pl • vtsisc_cancel.pl • vtsisc_mount.pl • vtsisc_unmount.
File size limit of 2TB can be overridden through the Pool Management page in the UI. If you set the virtual tape limit above 2TB, VTS will not get an EOM before the file system reaches the file limit and fails the I/O to VTS. (TL-2171) WORKAROUND: Set the limit to 2TB, which is the maximum setting. Cartridge mounted too quickly after enabling tape server results in error code 102 and cartridge will not mount.
To disable ISC, two parameters must be set. The ems_InterSystemCommunication_hosts and interSystemCommunication_enable parameters must be set to indicate that ISC should be disabled. Otherwise, ISC will still be enabled. (TL-240) WORKAROUND: To disable ISC, set these parameters in the VTS configuration file: interSystemCommunication_enable="NO" ems_InterSystemCommunication_hosts="" Then, stop ISC from the Supervisor Functions page.
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”.
Message on Manage System Licenses page implies that key was saved when it was not. On the Manage System Licenses page, if you select the Update checkbox, paste a license key in the License Key field, and then deselect the Update checkbox, a message 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. Page loads slowly if expanded pool contains many cartridges.
Cartridge sizes are not displayed properly. Cartridges created with 1TB, 1GB, or 1MB limits will display, respectively, as 1024GB, 1024MB, and 1024K. However, 2TB cartridges display as 2TB, 2GB carts display as 2GB, and 2MB cartridges display as 2MB. (TL-2365) After logging in as admin for SecureVTS functions in an open system, changing access controls to default closed results in excessive numbers of dialogs. SecureVTS requires login for certain functions in the UI.
Cannot cancel a manual mount request using the Cancel button. If you press the Mount button to mount a cartridge then press the Cancel button instead of the OK button, the cartridge is mounted on the VTD. The operation is not cancelled. (TL-543) Manage Connections 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.
Cannot re-log in to the 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. The Log In button on the interface will not log you in as another user. (TL1033) User and group changes can be applied but not saved as part of the Custom Defaults.
Key database restore fails if an IP address is used instead of a hostname. If a key database was backed up and an IP address was specified, restoring the backup fails. (TL-4033) WORKAROUND: Restore the backup using these steps: a. Delete the IP address entry. b. Add a new entry for the same backup host but use a hostname instead of IP address. (If DNS is not used, add an entry to /etc/hosts). A different backup file name must be used or the previous backup will be overwritten. c.
Creating cartridges in an encrypted pool when SecureVTS is not running generated confusing message. If SecureVTS is not running and you attempt to create cartridges in an encrypted pool, messages similar to the following are displayed. (TL-3048) Created 0 of 10 in P17 of size 2T successfully: Cartridge BBB000 in P17 failed encryption rc=254 Restoring corrupt key database succeeds when it should not.
EMS cancel mount attempts loop indefinitely after a failed mount of an encrypted cartridge. A cancel mount request sent from a NonStop server after an encrypted cartridge could not be serviced by VTS will attempt to cancel and fail the cancel operation for approximately 10 minutes. (TL-1205) WORKAROUND: Restart the TapeServer process. SecureVTS encryption operations performed when no key database backup host is configured causes the web interface to remain busy for up to 10 minutes.
Adding a key database backup host fails but lists erroneous error message if too many characters are specified in the fields. When adding a key database backup host and entering very long host names (such as 256 characters), user names (256 characters), or destinations (512 characters), adding the host will fail but the message may indicate that the server was not responding. (TL-1056) SecureVTS automated key database backups do not log their backups to the event.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 Retention time is not displayed correctly on Scan/Cleanup page.
Native Export Physical tape could be corrupted if server is rebooted during a native export. (TL-5456) WORKAROUND: If the job log reports that an export failed, re-run the export job. Migration Login path for CommVault 8 set to /opt/galaxy/Base/qlogin. The path should be set to /opt/simpana/Base. (TL-5707) WORKAROUND: Use the following commands as root: mkdir /opt/galaxy cd /opt/galaxy ln -s /opt/galaxy/Base/qlogin /opt/simpana/Base Default vts.conf file does not include migrate_all parameter.
Instant DR allows the creation of cartridges with invalid names. Instant DR can create a cartridge on the target server that contains an underscore or other special character in the cartridge name. The Instant DR job succeeds and the pool with the cartridge is created on the target. However, you cannot expand the pool on the web interface; it disappears. (TL-4287) Aborted error message listed in debug log when Instant DR job is dispatched.
EMS EMS may be restarted inappropriately if the Keep Alive Interval is set but Keep Alive is not set. If the Keep Alive option on the EMS Configuration page is not enabled (ems_keep_alive=FALSE in vts.conf), the keep alive messages will not be sent, but if Keep Alive Interval (ems_keep_alive_interval) is non-zero, the EMS service will still be restarted after three keep alive messages should have been received.
Device names beginning with $ result in ems_hostdevs and ems_virtdevs are not logged. If VTS is used with an HP NonStop host and the device names begin with $, the ems_hostdevs and ems_virtdevs values are blank in the log. This can cause confusion if reviewing the logs. (TL-1562, EAR 4030) SMTP and notifications Low disk space alert messages are sent regardless of the notifications_interval parameter setting.
`log/log' cp: will not overwrite just-created `cfg/network' with `/etc/ sysconfig/networking/profiles/default/network' cp: cannot stat `/usr/local/tape/patch': No such file or directory ls: /vault: No such file or directory WORKAROUND: Use the button on the web interface to obtain the logs. Message logged to console and /var/log/messages until iLO is configured.
Help Set displayed over main web interface page. The Help Set (available on the About page in the Product Documentation section) opens in the main web frame, rendering it unusable. (TL-5925) WORKAROUND: Right-click on the Help Set link and select “Open in a New Window”.
Troubleshooting This section includes information about how to troubleshoot problems and notes about items that may need clarification. 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: 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.
32-bit processor platforms are not supported. 6.04 is not supported on the DL380 G3 and ML530 platforms. (TL-1287) VTD with no connection to a logical tape is still presented on the bus. If a VTD is created and connected to a logical tape then the VTD is disconnected, the VTD is still shown to the client. An SG device is created and an Inquiry command succeeds. However, a Status command does not and the VTD cannot actually be used.
Error message displayed on console after the server is booted for the first time. Messages similar to the following are displayed on the console the first time VTS is booted: Mounting other filesystems: [ OK ] Starting hp-ilo:/opt/hp/hp-ilo/drivers/char/hp_ilo/CpqCiKlx.c: In functionoctl32_handler': /opt/hp/hp-ilo/drivers/char/hp_ilo/CpqCiKlx.c:680: warning: assignment makes pointer from integer without a cast /opt/hp/hp-ilo/drivers/char/hp_ilo/CpqCiKlx.
File size of a mounted tape being written may not be updated. If a virtual tape is mounted and being written to, the size shown on the page may not be updated until the tape is dismounted. Normally, this value will be updated when file marks are written to the tape, so usually this is not an issue for most users. (TL-881) Native export Native export fails when library is moved to a different port.
Utilities and services SNMP must be enabled to use HP Insight Manager. SNMP is disabled by default for security reasons. HP Insight Manager requires SNMP to operate, so it must be enabled after installation or upgrade. As the root user, enter this command: chkconfig snmpd on (TL-4689) HP monitoring services web interface may become unresponsive. (TL-3063) WORKAROUND: snmpd may need to be restarted by running “service snmpd restart” as root. The Tcl executable is installed in a different location.
Issue Index EAR 4030 Device names beginning with $ result in ems_hostdevs and ems_virtdevs are not logged. . 33 EAR 4286 Virtual tape appears to be created in a locked pool but is not. . . . . . . . . . . . . . . . . . . . . . . 20 EAR 4456 Incremental backup backs up all cartridges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 EAR 4873 Restoring database from previous version corrupted VTS. . . . . . . . . . . . . . . . . . . . . . . . . .
TL-0880 TL-0881 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-1205 TL-1206 TL-1239 TL-1287 TL-1480 TL-1562 TL-1662 TL-1741 TL-1752 TL-1755 TL-1802 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-1804 TL-1836 TL-1844 TL-1853 TL-1869 TL-1886 TL-1903 TL-1920 TL-1962 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 Cartridge mounted too quickly after enabling tape server results in error code 102 and cartridge will not mount. . . . . . . . . . . . . . . .
TL-2629 TL-2641 TL-2645 TL-2770 TL-2772 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 Retention time is not displayed correctly on Scan/Cleanup page. . . . . . . . . . . . . . . . . . . .
TL-3491 TL-3512 TL-3549 TL-3562 TL-3643 TL-3686 TL-3702 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 Manage Connections page does not select available values when creating VTDs. . . . . . .
TL-4434 TL-4464 TL-4584 TL-4607 TL-4689 TL-4822 TL-4857 TL-4940 TL-4956 TL-5007 TL-5063 TL-5077 TL-5111 TL-5136 TL-5159 TL-5179 TL-5196 TL-5203 TL-5207 TL-5246 TL-5252 TL-5291 TL-5299 TL-5306 TL-5313 TL-5340 TL-5349 TL-5437 TL-5439 TL-5447 TL-5456 TL-5469 TL-5487 TL-5501 TL-5502 TL-5560 TL-5561 TL-5664 TL-5677 TL-5698 SCSI speed is 3.3MB/s after TapeServer is restarted.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Writing to VTD fails if you attempt to create a VTD on same bus. . . . . . . .
TL-5707 TL-5738 TL-5827 TL-5860 TL-5872 TL-5888 TL-5925 TL-5932 TL-5941 TL-5946 TL-5951 TL-5954 TL-5959 TL-5960 TL-5971 TL-5975 TL-5988 TL-5990 TL-6004 TL-6005 TL-6008 TL-6411 Login path for CommVault 8 set to /opt/galaxy/Base/qlogin. . . . . . . . . . . . . . . . . . . . . . . . 30 Using double quotes in the vts.conf file produces inconsistent results. . . . . . . . . . . . . . . . 14 Installation and Administration guides have been combined into the Configuration guide. . . . . . . . . . . . . . . . . .
Index of Resolved Issues by Release 6.04.04.01 TL-5447 TL-5501 Could not create VTDs on ports in slot 8 after upgrading DL585. . . . . . . . . . . . . . . . . . . 10 Could not delete a VTD after upgrading from 6.04.01 directly to 6.04.04. . . . . . . . . . . . . 10 6.04.
