Release Notes HP Virtual TapeServer for NonStop Servers Product Version: 8.3 September 2012 Part Number: 702037-001 © 2004 - 2012 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. . . . . . . . . . . . . . . . . . . . . . . . . .
General operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Status page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 8.
Installation and Configuration This section describes how to access information about installing and configuring release 8.3 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 TapeServerQuick Start Guide. Instructions to upgrade from 8.0 or 8.2 to 8.
Host bus adapter support The following host bus adapters (HBAs) have been tested for use with VTS and IBM Power System servers: For use with Power 7: Feature code CCIN Description 0647, 1912, 5736, 5775 571A PCI-X DDR Dual Channel Ultra320 SCSI Adapter 5749 576B 4 Gigabit PCI-X2 Dual Port Fibre Channel Adapter 5774 5774 4 Gigabit PCI Express Dual Port Fibre Channel Adapter 5735 577D 8 Gigabit PCI-E Dual Port Fibre Channel Adapter Feature code CCIN Description 2765 2765 2 Gigabit Fi
Library Interface IBM TS3100 with LT04 and LTO-5 drives FC, SCSI IBM TS3100 with LTO-4 drives FC IBM TS3580 with LTO-3 drives FC Overland NEO with LTO-5 drives FC The following standalone drives were tested with Stacked Export jobs: Tape drive Interface HP Storageworks 960 Ultrium3 SCSI HP Storageworks 960 Ultrium3 FC The following standalone drives were tested with Tape-to-tape Export jobs (Host-native and Virtual formats): Tape drive Interface HP Storageworks 960 Ultrium3 FC HP Storage
Tape drive emulation VTS supports one virtual tape drive (VTD) per SCSI port and up to four VTDs per Fibre Channel port. All together, a maximum of 32 VTDs are supported per VTS server. For best performance, VTS can perform a maximum of 16 simultaneous backups at one time. Note Virtual tape drives support up to 256KB (262144 byte) blocks. Tape library emulation Multiple virtual tape libraries (VTLs) are supported per VTS system.
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.5 and 7 • EMC RSA Legato Networker 7.5.2 • CommVault Galaxy 7.0 • CommVault Simpana 8.0 • CA ARCserve Backup r15.0 From Windows Server 2008 hosts: • IBM Tivoli Storage Manager 5.5 • Symantec Veritas NetBackup 7.0 • Symantec Backup Exec 2010 • EMC RSA Legato Networker 7.4 and 7.
Upgrade and Downgrade This section provides procedures for upgrading and downgrading the VTS appliance(s) in your environment. It also provides a list of known issues related to upgrade and downgrade. Upgrading to 8.3 You can upgrade to 8.3 from version 8.0 or 8.2 only. During the upgrade, a backup of /usr/ local/tape/ is created, the upgrade is performed, and new system RPMs are installed. After the upgrade completes, you can view the upgrade logs from the Manage Logs page of the web interface.
9. Select From Local File. 10. In the Location of Revision Update File field, type the full path to the UPG file. /tmp/VTS83.UPG 11. Click UPGRADE. 12. Click OK to continue. Note Upgrading may take a while. Do not navigate away from the page until the upgrade completes. 13. Confirm that the following message is displayed: Completing Upgrade... Revision Update Successful! System must now be rebooted. 14. Click REBOOT to complete the update. 15. Restart the web browser and launch the web interface. 16.
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 root partition of the VTS appliance before downgrading. 2. If possible, locate the system restore image that was created before the system was upgraded. 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.
Resolved Issues and Enhancements The following changes have been incorporated into the software since the 8.2 release. Hardware, configuration, and hardware replacement Bootup was delayed without Ethernet configuration or connection. If the Ethernet was not configured, or in some cases, if there was no Ethernet cable plugged into the appliance, bootup may have been delayed when bringing up the processes for the web interface. This is no longer an issue.
After updating to version 8.2, the Virtual Device Status section of the System Status page would be empty. The Virtual Device Status would be empty after updating to 8.2 if the database contained any pieces of a VTD or VTL that were not connected to a functioning VTD/VTL. This prevented the System Status page from loading correctly. The System Status page no longer attempts to display any unconnected VTD/VTLs.
SCSI bus resets did not clear reservations. When VTS received a SCSI bus reset, it should have cleared any existing VTD or VTL reservations, but it did not. The reservations are now cleared. (TL-6096) Cancels left in cancel queue might have caused backups to fail. Mount cancels that remained in the cancel queue due to an infrequent timing issue, could have caused a mount to be canceled that shouldn't have been. Cancels are no longer left in the queue for over 24 hours.
File size limit of 2TB could be overridden through the Pool Management page in the UI. If you set the virtual tape limit above 2TB, VTS would not get an EOM before the file system reached the file limit and failed the I/O to VTS. This has been resolved. (TL2171) No virtual tapes were displayed after clicking Clear Cache. When you clicked Clear Cache, the cartridges were removed from the page and you had to refilter to display the tapes.
Inserting more virtual tapes into a VTL than there were slots available did not indicate that there was a failure. There was no indication that the action to insert virtual tapes was successful or failed and the shelf remained displayed with the tapes still showing the check marks. Now an error message will be displayed. (TL-7619) Migration and sStacked export and import A stacked export job never started, but the UI indicated it was still running.
Instant DR did not check vaults when checking for duplicate files. Instant DR incorrectly copied the same file into different vaults if the same cartridge exists in the same pool in multiple vaults. The vault name should have be added to the duplicate check (it only checked the cartridge and pool). The vault name is now checked for as well as the cartridge and pool. (TL-7452, EAR-8585) Data Encryption (SecureVTS) Virtual Tape Details page reported a virtual tape as unencrypted when it was encrypted.
Known Issues The following known issues, or “errata,” apply to the 8.3 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 59. Hardware, configuration, and hardware replacement Adding or removing an HBA may cause the port configuration to change.
netconfig will not allow setting a non-default static route. When using netconfig to configure interfaces, there may be a need to set a different gateway for eth1 other than the default gateway. There is currently no way to do this using netconfig. (TL-7340) Connection issues may occur when using 4Gb Fibre Channel cards. Connection issues can occur when using the 4Gb Fibre Channel card directly connected to AS/400 on v5r4. When it comes up as private loop, there are issues seeing the devices.
General operations vtsa user cannot mount CD or DVD. The vtsa user is not able to execute mount commands. (TL-6748) WORKAROUND: Use the bill user instead. Incorrect serial number of SCSI VTD is displayed in the System Tools menu with V7iOS (V7R1). The serial number does not display correctly in the System Tools menu with V7iOS (V7R1) when a SCSI VTD is used. (TL-6260) System locks up if debug log consumes disk space. With debug log set to verbose and if you run out of disk space, VTS “locks” up.
• ems_telnet.pl • hsmdelete.pl • hsmget.pl • hsmput.pl • vtsisc_cancel.pl • vtsisc_mount.pl • vtsisc_unmount.pl • vts_scratch_erase.pl The most common symptom of this problem is that VTS will not be able to log into a host server. Log messages may make it appear as if a password has not been set, though it has been set since encrypted passwords cannot be decrypted.
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. Cartridges created in a batch show the same creation time in the event log.
Troubleshooting package will not download with IE8 in security toolbar. (TL6616) WORKAROUND: Disable popup blockers or add this as a safe and trusted website for pop-ups. IE can prevent troubleshooting packages from being downloaded on the first try but after disabling, will work correctly. Restarting the browser may also be required. Web interface not refreshed after capacity license is applied.
Cartridges not owned by bill are not erased as indicated in the interface and log file. However, the debug.log correctly indicates that the file failed to erase. (TL-2061) System ID is displayed as rc=3 on Apply Software Change page. This can be ignored. (TL-2287) Clicking the browser Back button after creating a system restore image causes download to start again. After clicking Support > System Updates > Create a System Restore Image, a file download dialog box is displayed.
Jobs (general) On the Job Results page the cartridge status and encryption state are listed in the same field. On the Job Results page for a Tape to Tape Export, the status of the cartridge which was transferred is included in the same field as the drive encryption state. The field labeled Drive Encryption will appear as: “Drive Encryption: false: OK”. The false denotes the drive encryption and the OK is the status of the Cartridge transfer.
The status of tapes shown in the Virtual Tapes page may not be current. When tape operations occur outside the Virtual Tapes page, the tapes shown in the Virtual Tapes page may be out of date. Removing a large number of Virtual Tapes can also result in out of date information. (TL-7996, TL-8026) WORKAROUND: A manual refresh for a single tape or clear cache for the entire page will update the cartridge information to the latest available.
Cartridge size check done on Cartridge Maintenance page instead of Pool Maintenance page. Though you specify a maximum cartridge size on the Pool Maintenance page, the system does not check for the size; it checks on the Cartridge Maintenance page. (TL-3772) Cannot click button to confirm deletion of cartridges if deleting many. When deleting many cartridges, the confirmation dialog box extends off the screen and does not show the OK button.
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”.
Data size incorrect on Manage Virtual Tapes page after data change during a stacked export. Data sizes may vary between the Configure Tapes and Pools page and the Manage Virtual Tapes page if a stacked export is being performed and then new data is written to the cartridge while the stacked export is in progress. (TL-4953) WORKAROUND: For accurate cartridge size information, view cartridge information using the pop-up dialog box on the Manage Virtual Tapes or Configure Tapes and Pools page.
Manage Virtual Tapes page becomes unresponsive when trying to display a VTL that was created when a pool with the same name exists. If you create a VTL using the same name base that is used by an existing pool, the page hangs when you try to filter by cartridge or pool. The production log shows that the page is looking for the original VLM that would have been created if a pool by that name did not already exist.
Manage Virtual Devices (Manage Connections) Poor performance accessing Virtual Devices page. When attempting to access the Virtual Devices page, it can take up to 60 seconds to render the page. (TL-7256) Cancel button when creating a VTL does not work. This occurs when using Firefox on upgraded systems only. (TL-7350) WORKAROUND: Navigate away and return to the page. Slow performance of the Manage Virtual Devices page.
Incorrect error message displayed when attempting to create a VTL on a bus that has more drives than LUNs. When attempting to create a VTL on a bus that has more drives than LUNs, the error message is incorrect. It states, for example, “Unable to create VTL with the specified number of drives as bus 4 lun 8 combination is already in use”. The indicated LUN does not exist and, therefore, cannot be in use. (TL-4466) VTL creation may only be done as the first device on a port starting with LUN 0.
Change Group option not available after adding new user and group. After adding a new user and group, you must deselect the new user in the Users drop-down list and then select it again to get the “Change Group” option to appear. (TL-3278) Certain Access Control settings cause each update cycle to prompt for a password.
VTL For VTL drives, the eject button on the drives page will be visible, but not usable. Attempting to use the eject button to eject a tape from a VTL drive will fail as expected since the drives are controlled by the changer. The unmount attempt will result in the following error: “Failed to umount, umount command failed with 101". This error message can be ignored. (TL-7918) Last slot in VTL shows up as cleaning tape in EMC RSA Legato Networker.
Incorrect error message displayed if attempting to add locked cartridge to library. If the library is full when adding a cartridge to a library, check the Mounts and Locks page to determine if the cartridge is locked. If so, you may receive this message: “Unable to insert cartridge because magazine is full.” A locked cartridge cannot be added to a library, but the error message is incorrect in this case. (TL-4004) WORKAROUND: Resolve the locked condition and then add the cartridge to the library.
Fibre Channel client lists incorrect number of devices after library definition is modified. If you remove all Library objects associated with a library definition prior to editing the definition, the edit operation is allowed even if there are still Physical and Logical Libraries that reference that library definition. The Edit page shows a warning that it is not allowed, but it does not prevent the edit.
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.
Creating cartridges in an encrypted pool when Data Encryption is not running generated confusing message. If Data Encryption 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. Data Encryption encryption operations performed when no key database backup host is configured causes the web interface to remain busy for up to 10 minutes.
Data Encryption 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. (TL-1001) Error message erroneously logged if the local copy of the key server backup utility changes volumes and is placed in another vault. If the local copy of the key server backup utility changes volumes and is placed in another vault, it may trigger a critical error in the event log indicating a duplicate pool.
Retention time is not displayed correctly on Scan/Cleanup page. Retention is shown in weeks until retention time exceeds a year, then it is shown in years. Time is stored as a number of seconds but incorrectly converted for display. (TL-2629) Scan/Cleanup page performance is slow. Loading the Scan/Cleanup page is slow if a large number of cartridges exists. It takes about a minute for a pool containing 1,000 cartridges.
Importing cartridges with similar names can be imported to the same virtual tape. If a library has two cartridges with similar names (first 6 characters the same) and they are selected for import, they can be imported to the same virtual tape. This is an error condition that can be avoided by having uniqueness in the first six characters of the cartridge. (TL-6530) WORKAROUND: Tape libraries attached to VTS should be configured to ignore the media version (the Lax at the end of a barcode).
Import fails if virtual tape meets pool cartridge quota when it is exported. If a quota size is set for a pool and you export a virtual tape in the pool that meets that quota, imports will fail if the cartridge is the maximum size allowed. If the cartridge is not full, imports work fine. (TL-4046) Physical tape could be corrupted if system is rebooted during a tape-to-tape export. (TL-5456) WORKAROUND: If the job log reports that an export failed, re-run the export job.
NetBackup media ID may be listed twice. VTS retrieves information from the NetBackup output log for information about a backup job, including the media ID(s) used for the backup. Depending on the NetBackup version in use in conjuction with the VTS implementation to retrieve this information, the media IDs may be listed twice for a backup job. (TL-7625) Unmigrating a pool does not restore virtual tapes. Restoring a pool after migration does not restore the virtual tapes.
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.
Restoring individual files from export that spanned files using CA ARCserve fails. (TL-6517) WORKAROUND: Restore the entire backup to obtain the single file. TSM running on a host system fails to label tapes when the VTDs are Ultrium. Though the drives are detected and associated with the library, when it tries to load the tapes for labeling, an error is displayed indicating it cannot label the volume.
SSH login fails during Autocopy or Instant DR if replication has been setup. The reverse is true, too; SSH login fails during replication if Autocopy or Instant DR is setup. (TL-7003) WORKAROUND: Delete the entries from the known_hosts file and then setup SSH again. Replication jobs fail to run if a source has been removed from a target configuration. The error message will be similar to the following.
Stop on error for import does not stop on failure. When the first error occurs for a cartridge within a VTL, the job should fail and no other cartridges should be processed. (TL-5982) WORKAROUND: To avoid this issue, import one cartridge at a time. Fetch Destination Details in Remote Export does not give error message on connection timeout.
Autocopy locks the source cartridge but not the target. VTS is not locking and could cause the cartridges to be corrupted if they are not used on the remote side. (TL2529) AutoCopy may create pools on a server that could not otherwise be created. AutoCopy may be used to create pools on a VTS server that could not otherwise be created, such as having both a 'TEST' and a 'test' pool.
EMS restart function fails to function if the host name in the EMS messages and the host name as configured in the EMS Configuration page are not identical (including case). For example, if the host name as sent by the host is 'DEV4' but the host name as configured in the EMS Configuration page is 'dev4', the loss of EMS keepalive messages will not be detected and the EMS restart function will fail to work.
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) Policy Based Actions When a pool is renamed its policies are not transferred. When a pool is renamed the policies associated with the pool are not transferred to the updated pool.
Virtual tapes are unusable by other systems if one clustered system crashes. Virtual tapes within a VTL are indicated by an attribute saved on the file system with the virtual tape. The attribute is managed by the system that hosts the virtual tape library. If that VTS hosting the VTL crashes and is never recovered, the attributes will remain on the file system. This issue will likely only affect GFS customers.
HP SIM fails to function properly with a DL185. HP SIM does not show several items on the System Management Homepage. (TL-5246) HP SIM and GFS conflict. A component of HP SIM could conflict with the port used by GFS. This could cause one process to stop functioning if the other one is correctly working. (TL-5252) 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.
Incomplete image created when creating a system restore image with insufficient disk space. If there is not enough space to create a system restore image, the user should be notified that there is not enough space. Instead, “URL not found” message is displayed and files are omitted from the TAR file. (TL-4176) System restore does not handle database restore failure well. If a problem occurs while restoring the database during a system restore, the system may be left with a partial or no database.
Troubleshooting This section includes information about how to troubleshoot problems and notes about items that may need clarification. Installation, upgrades, updates, and restore Upgrading to GFS if it is currently installed. If you choose to downgrade, the GFS update will not be reverted, and the newer version of GFS will remain in place. This has been shown to work without issue on downgraded systems. (TL-7031) No disk space available after an upgrade.
Must run /usr/local/tape/bin/grub-serial.bash to access GRUB from the console. When VTS boots, you must press a key when prompted if you wish to see the GRUB menu. The /usr/local/tape/bin/grub-serial.bash command will modify the system boot configuration to provide serial console access to the GRUB boot menu. This command must be run as root.
(0x69) Nov 15 failed Nov 15 (0x69) Timeout (elapsed time 100 jiffies) 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 Changing tape library settings could cause the drives to be unusable. When a tape library was changed from random access mode to auto loader mode, the Physical Device settings could become confused. This caused the changer to be disconnected and the drive entries could not be edited from the Physical Drives page. This can be avoided if the settings in the Manage Settings page are first changed to “Disabled” for the device and saved, followed by the device being changed to auto loader mode.
Tape-to-Tape export Tape library must be configured for encryption to support export of encrypted tapes. The external tape library must be correctly configured to allow VTS to manage encryption. Refer to the library documentation for instructions. (TL-6435) Virtual tapes must be exported to a physical tape library that has physical cartridges with matching barcodes. If a matching cartridge is not found during a tape-to-tape export to a library, the job.
Utilities and services CLIM does not see more than 8 LUNs after changing the tape type. This occurs if VTS is started after device discovery. (TL-6777) WORKAROUND: Device discovery on the CLIM can be best accomplished by first starting VTS, then connecting the CLIM. Done this way, devices should be discovered correctly. Finally, the device may be mapped with the CLIM to the NonStop. CLIM device discovery is fragile. Best practice is to set up and connect VTS to the CLIM.
Issue Index EAR-4030 Device names beginning with $ result in ems_hostdevs and ems_virtdevs are not logged.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EAR-4286 Virtual tape appears to be created in a locked pool but is not. . . . . . . . . . . . . . . . . . . . . . . EAR-4456 Incremental backup backs up all cartridges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EAR-9117 VTS installation using a TEAC DVD drive stops with an error message. . . . . . . . . . . . . . EAR-9126 After updating to version 8.2, the Virtual Device Status section of the System Status page would be empty.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EAR-9178 Creating a VTD failed on a VTS running more than 60 days without using a VTD . . . . . EAR-9252 A non-virtual cartridge in an autoloading pool caused a fault.. . . . . . . . . . . . . .
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-1155 TL-1158 TL-1168 TL-1205 TL-1206 TL-1239 TL-1384 TL-1480 TL-1526 TL-1562 TL-1662 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-2155 TL-2158 TL-2171 TL-2179 TL-2189 TL-2201 TL-2255 TL-2272 TL-2279 TL-2280 TL-2287 TL-2292 TL-2293 TL-2303 TL-2317 TL-2318 TL-2320 TL-2324 TL-2342 TL-2347 TL-2350 TL-2358 TL-2365 TL-2367 TL-2388 TL-2390 TL-2529 TL-2551 TL-2629 Cartridge mounted too quickly after enabling TapeServer results in error code 102 and cartridge will not mount.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-2641 TL-2645 TL-2770 TL-2772 TL-2885 TL-3001 TL-3005 TL-3011 TL-3012 TL-3020 TL-3032 TL-3041 TL-3048 TL-3052 TL-3071 TL-3105 TL-3117 TL-3125 TL-3151 TL-3152 TL-3156 TL-3165 TL-3168 TL-3170 TL-3171 TL-3175 TL-3190 TL-3212 TL-3278 TL-3300 TL-3304 TL-3310 TL-3377 TL-3429 TL-3440 TL-3456 TL-3463 TL-3491 TL-3512 TL-3515 TL-3562 Fibre Channel ports do not initiate link status and lasers are off if ports are set to target mode and VTDs are not defined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-3624 TL-3643 TL-3672 TL-3702 TL-3721 TL-3742 TL-3756 TL-3766 TL-3772 TL-3788 TL-3825 TL-3837 TL-3844 TL-3847 TL-3849 TL-3853 TL-3874 TL-3877 TL-3885 TL-3897 TL-3940 TL-3950 TL-3953 TL-3962 TL-3982 TL-3985 TL-4004 TL-4007 TL-4011 TL-4012 TL-4014 TL-4018 TL-4033 TL-4035 TL-4046 TL-4063 TL-4073 TL-4099 TL-4108 TL-4139 TL-4141 TL-4142 TL-4156 TL-4163 TL-4176 TL-4199 TL-4232 TL-4235 VTL may be loaded with too many cartridges.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-4260 TL-4265 TL-4267 TL-4286 TL-4287 TL-4299 TL-4308 TL-4313 TL-4326 TL-4371 TL-4391 TL-4398 TL-4399 TL-4414 TL-4429 TL-4434 TL-4439 TL-4447 TL-4456 TL-4464 TL-4466 TL-4469 TL-4536 TL-4569 TL-4607 TL-4616 TL-4620 TL-4669 TL-4670 TL-4779 TL-4806 TL-4822 TL-4857 TL-4859 TL-4922 TL-4940 TL-4953 TL-4956 TL-5023 TL-5034 Keep alive options cannot be set for multiple streams over RSH. . . . . . . . . . . . . . . . . . . . Rebooting while Replication is splitting files leaves a running job. . . . . . . . . . .
TL-5063 TL-5111 TL-5137 TL-5177 TL-5179 TL-5207 TL-5246 TL-5252 TL-5456 TL-5586 TL-5635 TL-5677 TL-5698 TL-5707 TL-5738 TL-5741 TL-5742 TL-5757 TL-5790 TL-5806 TL-5845 TL-5850 TL-5859 TL-5862 TL-5882 TL-5892 TL-5924 TL-5930 TL-5944 TL-5946 TL-5948 TL-5951 TL-5954 TL-5969 TL-5971 TL-5975 TL-5976 TL-5980 TL-5982 TL-5988 TL-5990 TL-5997 TL-5998 TL-6004 TL-6005 Web interface may fail to allow the virtual media removal from the virtual tape drive. .
TL-6096 TL-6110 TL-6117 TL-6135 TL-6150 TL-6152 TL-6180 TL-6191 TL-6260 TL-6263 TL-6279 TL-6310 TL-6312 TL-6376 TL-6384 TL-6388 TL-6417 TL-6429 TL-6435 TL-6489 TL-6517 TL-6530 TL-6540 TL-6548 TL-6552 TL-6564 TL-6598 TL-6604 TL-6606 TL-6616 TL-6628 TL-6646 TL-6651 TL-6667 TL-6697 TL-6698 TL-6708 TL-6723 TL-6736 TL-6741 TL-6748 TL-6755 TL-6757 SCSI bus resets did not clear reservations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-6773 TL-6777 TL-6788 TL-6817 TL-6820 TL-6832 TL-6835 TL-6862 TL-6866 TL-6874 TL-6915 TL-6982 TL-6984 TL-7003 TL-7031 TL-7117 TL-7139 TL-7160 TL-7179 TL-7212 TL-7213 TL-7221 TL-7247 TL-7256 TL-7265 TL-7266 TL-7272 TL-7300 TL-7311 TL-7320 TL-7325 TL-7326 TL-7333 TL-7336 TL-7340 TL-7343 TL-7346 TL-7350 TL-7362 TL-7363 TL-7367 TL-7370 TL-7372 TL-7374 TL-7378 TL-7379 Encryption options can be checked when there is no encryption license set.. . . . . . . . . . .
TL-7380 TL-7381 TL-7391 TL-7392 TL-7406 TL-7409 TL-7447 TL-7450 TL-7451 TL-7452 TL-7453 TL-7454 TL-7456 TL-7458 TL-7494 TL-7531 TL-7545 TL-7550 TL-7572 TL-7579 TL-7586 TL-7588 TL-7591 TL-7595 TL-7598 TL-7599 TL-7608 TL-7610 TL-7611 TL-7617 TL-7619 TL-7622 TL-7625 TL-7632 TL-7634 TL-7641 TL-7651 TL-7656 TL-7658 TL-7693 TL-7697 TL-7708 Error message in vts-post-install.log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL-7709 TL-7720 TL-7725 TL-7727 TL-7731 TL-7736 TL-7750 TL-7768 TL-7783 TL-7791 TL-7810 TL-7812 TL-7813 TL-7814 TL-7818 TL-7820 TL-7821 TL-7894 TL-7896 TL-7897 TL-7898 TL-7917 TL-7918 TL-7934 TL-7940 TL-7944 TL-7959 TL-7967 TL-7988 TL-7994 TL-7996 TL-8007 TL-8018 TL-8024 TL-8026 TL-8030 TL-8034 TL-8038 TL-8043 TL-8044 TL-8045 TL-8046 TL-8052 TL-8063 Replication using WAN acceleration was not using an optimum transfer mode and could have resulted in slower transfers or transfers failing to complete.. . . .
TL-8071 TL-8082 TL-8094 TL-8095 TL-8098 TL-8099 TL-8112 TL-8114 TL-8117 TL-8123 TL-8124 TL-8137 If a large number of virtual tapes were deleted at the same time and the key server was not on the same system that the virtual tapes were on, it could have taken longer than usual and network traffic might have increased. . . . . . . . . . . . . . . . . . . . . . . Replications should be kept to less than 400 virtual tapes at a time. . . . . . . . . . . . . . . . .
