Patch Name: PHSS_18241 Patch Description: s700_800 10.X OV OB2.55 patch - MA packet Creation Date: 00/03/22 Post Date: 00/04/20 Hardware Platforms - OS Releases: s700: 10.00 10.01 10.10 10.20 s800: 10.00 10.01 10.10 10.20 Products: OmniBackII A.02.55 Filesets: OMNIBACK-II.OMNI-MA-P OMNIBACK-II.OMNI-ACS-P OMNIBACK-II.OMNI-DAS-P Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_18241 Symptoms: PHSS_18241: Id = NSMex02921 If a DDS drive is empty, instead of a mount prompt, OmniBack II reports the error: "Invalid physical device type => aborting" Id = NSMex01898 Restore session fails with the error message: "Can not seek to requested position" Id = NSMex01958 Cleaning does not work for DLT7000. Id = NSMex01968 OmniBack II does not handle DAS errors properly. Id = NSMex02048 OmniBack doesn't interpret the ACS error code STATUS_VOLUME_IN_DRIVE correctly. Id = NSMex02165 Bad performance of the media agent. Id = NSMex02315 Busy drive dismount doesn't work with ACS and DAS integration. Id = NSMex02145 After the system reboot the SCSI Library can not mount a medium. Error message is displayed: "Can not load exchanger medium (...)" Id = NSMex02763, NSMex02816 Device intermittently reports an I/O error and the tape gets stuck in the drive. Id = NSMex02668 Drive cleaning on StorageTek ACSLS with OmniBack CLEANME option set runs into an infinitive loop. PHSS_16709: Id = NSMex01577 Opening a library sometimes fails with "cannot open exchanger control". Id = NSMex01499 Additional device status checking, after an I/O error. Id = NSMex01447 & Id = NSMex01627 Copying media with omnimcopy fails with "Communication error to MM MA" Id = NSMex01587 & Id = HSLco09947 Import of Tape failed with "Cannot read EOD", or seek to the end of tape failed with an error "Cannot seek to the end of tape ..." Id = NSMex01592 Restore of data from ExaByte EXB-480 fails with error "Unexpected status of medium.". Id = NSMex01511 Backup to MO fails with error "Can not switch to exclusive access." Id = NSMex01641 Door locking not implemented for Tape Libraries. Id = NSMex01682 Uma "stat" option doesn't work correctly. Id = NSMex01494 Unload of exchanger medium fails with "Can not unload exchanger medium (Unknown device type specified.)" PHSS_15793: Id = NSMex01357 If Media Agent failed then OmniBack II sent 2 down commands to GRAU device. Id = NSMbb18594 or NSMbb18593 or NSMbb18406 Problems with enter/eject operations. Id = NSMex01438 Backup to ACS-LS Media Agent failed with: STATUS_LOCKID_NOT_FOUND. Id = NSMex01463 Backup could overwrite part of the data during append. PHSS_15466: Id = NSMex01379 Backup Media Agent for direct access devices corrupted the data on the MO medium. Id = NSMex01411 Backup to the Media Agent running on AIX or Sinix Operating system failed with "Unknown internal error. PHSS_14970: Id = NSMex01041 Backup to MO device on HP-UX 9.x failed with "Can not switch to exclusive access." Id = NSMbb17300 Backup and rescan of an autoloader connected to HP-UX 9.x failed with: '[MINOR] REQUEST SENSE call failed. Invalid Argument.' Id = NSMex01052 OmniBack II did not handle eject of media from STK - SILO properly. Id = NSMex01172 OmniBack II did not report correct barcodes during rescan of scsi II libraries. Id = NSMex01215 At the end of a copy session, the error 'Can not open device (No such device or address)' was displayed if an exchanger device was used. Id = NSMex01246 Handling of busy drives failed if the exchanger robotic was connected to a different host Id = NSMex01284 Backup could overwrite part of the data during append PHSS_14337: Id = NSMex01087 The Media Agent failed during backup of the database integration. Defect Description: PHSS_18241: Id = NSMex02921 Accessing an empty drive produces a misleading error message instead of a mount prompt. Resolution: Mount prompt issued now instead of the bad error message when a DDS drive is empty. Id = NSMex01898 When doing an appended backup the backup completes successfully but in fact the positions on tape are not correctly updated in the database. This is only a problem on tapes created with Solaris BMA which had st.conf configured as proposed in 2.10 Release Notes and after it was upgraded from 2.10 to 2.55 and the MA agent was installed without changing the st.conf as proposed in 2.55 Release Notes Resolution: Special environment variable has been introduced to enable old restore type. See Special Installation Instructions on details how to use the variable. Part of SSPUX255_116. Id = NSMex01958 Cleaning tape is not handled properly with DLT 7000 devices. Resolution: The tape cleaning now works with DLT 7000 the same way it does with DLT 4000. Part of SSPUX255_120. Id = NSMex01968 When mounting a tape into a drive and a aci_mount returns EPROBVOL (d_errno=6), OB2 tries to mount another tape and this can cause all tapes to become poor. Resolution:: EPROBVOL is now treated as a failure and agent is aborted. It will not try to mount another tape, and the drive needs to be checked manualy. Part of SSPUX255_122. Id = NSMex02048 If StorageTek robotics cannot dismount a tape and some other Media Agent tries to use the same tape in another drive, then ACS error STATUS_VOLUME_IN_DRIVE occurs and the session is aborted instead of using another tape. Resolution: Special environment variable has been introduced to avoid this situation. See the Special Installation Instructions for details. Part of SSPUX255_124. Id = NSMex02165 OmniBack is able to simulate device error conditions, if there are some special files present in the tmp directory. Checking for the presence of these files causes bad backup performance. Resolution: Checking is only done, if the environment variable OB2SIMENABLE is set. Part of SSPUX255_129. Id = NSMex02315 Busy drive dismount does not work. An error message is issued instead of dismounting the media from the drive. Resolution: Busy drive handling improved. Part of SSPUX255_137. Id = NSMex02145 After the system reboot and potentialy the SCSI Library reboot, the first use of the SCSI Library fails with the error message: "Can not load exchanger medium (...)" The file syslog.log is filled up with SCSI Request Timeout system reports because device doesn't responds to the device driver in expected timeframe. Resolution: A timeout added to wait for the device to become ready. Part of SSPUX255_141. Id = NSMex02763, NSMex02816 If an I/O error occurrs on a device, it is possible that the subsequent operations (rewind, offline) fail and the medium is stuck in the drive. Resolution: Timeout and retry has been introduced for the rewind and offline operations before giving up. See Special Installation Instructions for details on setting the timeout and retry values. Part of SSPUX255_144. Id = NSMex02668 When a dirty drive is detected in StorageTek ACSLS, a Cleaning Tape is loaded and Media Agent tries to open it. Open of the cleaning tape fails and the tape is dismounted, and immediatelly mounted again. The whole procedure is repeated over and over again. Resolution: Dirty drive cleaning on ACSLS is now handled correctly. Part of SSPUX255_146. PHSS_16709: Id = NSMex01577 After opening and closing the CAP, uma misinterpreted the library status. It could fail with the message: "Cannot open exchanger control device, ...". Id = NSMex01499 I/O errors which occured during backup or restore (write or read) were not thoroughly checked. Solution: Additional device checking was implemented. Part of SSP255_84 and SSP255_95. Id = NSMex01447 & NSMex01627 When copying a medium with omnimcopy, receiving the early warning EOT caused session to abort, and tape being scratched. The reason was an incorrect counting of filemarks after the EOT warning. Part of SSP255_64. Id = NSMex01587 & HSLco09947 Import of a tape failed, or appended backup to a tape failed due to a seek failure. The problem was that end of tape was not marked correctly. This happened when backup was used with reconnect option and was been aborted. Part of SSP255_80. Id = NSMex01592 Restoring data from ExaByte EXB-480 fails because of an 'unexpected status of medium'. The read function returns 0 when it hits the filemark. OmniBack II then checks the status of medium to verify that it hit a filemark. The ExaByte device didn't respond as expected. Solution: Setting the environment variable in .omnirc file to: OB2READ0_FSM=1 causes OmniBack II to ignore the 'unexpected status of medium' and take it as a filemark. Part of SSP255_84. Id = NSMex01511 When a magneto optical medium is dirty, then backup may fail with the error: "Can not switch to exclusive access.". Solution: Setting the environment variable in .omnirc file to: OB2MO_REOPEN=1 causes OmniBack II to retry switching into exclusive mode 5 times. Part of SSP255_84. Id = NSMex01641 Door of a SCSI-II exchanger was not locked after entering the cartridges. If evironment variable is set in .omnirc file: OB2DOORLOCK=1 Solution: The door is unlocked with the 'eject' operation and remains unlocked until the 'enter' operation was performed. (Note that this is not exactely the same approach as for door locking with ACSLS configuration) Part of SSP255_94. Id = NSMex01682 UMA fails with the "stat S1" command, in the case when slot 1 has internal address 0. Part of SSP255_94. Id = NSMex01494 The tape drive in the ADIC autochanger immediately reported successful completion of the 'offline' operation. A following 'move' operation was then started too early and therefore failed. To solve the problem, a new variable OB2OFFLINESLEEP was introduced. It allows to specify the number of seconds the device has to wait before an attempt to move the tape from the drive is made. We suggest this variable to be set between 30 and 60 seconds. Apply the variable only to devices which experience the described problem with unload operation. PHSS_15793: Id = NSMex01357 In the case that media agent failed for some reason, two "DOWN" commands were sent to GRAU. Part of SSP255_57. Id = NSMbb18594 When entering multiple media into a library with only one mailslot, then if a medium was put into the mailslot immediately after the previous one had been taken out, the operation could fail and the medium was not entered into the slot. Part of SSP255_62 and SSP255_73. Id = NSMex01438 If the ACS-LS Media Agent was aborted two unlock commands were sent. Because of that error was shown: "StorageTek ACS error in "acs_unlock": STATUS_LOCKID_NOT_FOUND." Part of SSP255_66. Id = NSMex01463 To append to a medium, omniback uses the seek function which is supposed to fail at the End Of Data. This function could fail for other reasons, causing the write operation to start from a wrong position on the tape and overwriting valid data. An additional check was added to prevent this. If the seek failed then the tape, that was used during seek is marked as poor. Such tape has to be verified. Part of SSP255_68. PHSS_15466: Id = NSMex01379 If the direct access medium (optical disks, disks, files) contained a great number of small backups (maximum 475), there was a possibility of corruption of the data. Number of the segments on the medium is now restricted to 950. Part of SSP255_54. Id = NSMex01411 If the offical patch (PHSS_14970/PHSS_14971) was installed and during backup the backed up data were appended to the tape then the backup failed with "Unknown internal error". The problem happened only if Media Agent was running on Sinix or on AIX. Part of SSP255_56 PHSS_14970: Id = NSMex01041 Backup to MO device on HP-UX 9.x failed with "Can not switch to exclusive access." Part of SSP255_10. Id = NSMbb17300 Backup and rescan of autoloader connected to HP-UX 9.x failed with: "[MINOR] REQUEST SENSE call failed. Invalid Argument." Part of SSP255_10. Id = NSMex01052 OmniBack II did not handle eject of media from STK-SILO properly if there was one of the selected tapes located in a drive. In such a situation the information about tapes was not properly updated in the OmniBack II DB. Part of SSP255_26. Id = NSMex01172 OmniBack II did not report correct barcodes during rescan of scsi II libraries. Rescan failed. Part of SSP255_30. Id = NSMex01215 Handling for media close was not OK if copy failed for some reason (in particular case because the destination tape was shorter than original). Part of SSP255_39. Id = NSMex01246 Busy drive handling (eject feature) did not work if robotic was on the remote host. Part of SSP255_40. Id = NSMex01284 To append to a medium, omniback uses the seek function which is supposed to fail at the End Of Data. This function could fail for other reasons, causing the write operation to start from a wrong position on the tape and overwriting valid data. An additional check was added to prevent this. Part of SSP255_46 PHSS_14337: Id = NSMex01087 OmniBack II did not handle the end of the database integration backups properly, if at the same time the tape was at the end. As result of it the bma failed with different errors. Part of SSP255_19. SR: 1653288902 1653289702 1653293829 1653293829 1653270348 Patch Files: /opt/omni/databases/vendor/acs/hp/s800/hp-ux/A.02.55/ packet.Z /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.02.55/ packet.Z /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.02.55/ require.dat /opt/omni/databases/vendor/ma/hp/s800/hp-ux/A.02.55/packet.Z /opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.02.55/ packet.Z /opt/omni/databases/vendor/ma/siemens/r400/sinix/A.02.55/ packet.Z /opt/omni/databases/vendor/ma/ibm/rs6000/aix/A.02.55/ packet.Z /opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.02.55/ packet.Z /opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.02.55/ require.dat /opt/omni/databases/vendor/ma/sun/sparc/solaris/A.02.55/ packet.Z /opt/omni/databases/vendor/das/hp/s800/hp-ux/A.02.55/ packet.Z /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.02.55/ packet.Z /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.02.55/ require.dat what(1) Output: /opt/omni/databases/vendor/acs/hp/s800/hp-ux/A.02.55/ packet.Z: None /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.02.55/ packet.Z: None /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.02.55/ require.dat: None /opt/omni/databases/vendor/ma/hp/s800/hp-ux/A.02.55/ packet.Z: None /opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.02.55/ packet.Z: None /opt/omni/databases/vendor/ma/siemens/r400/sinix/A.02.55/ packet.Z: None /opt/omni/databases/vendor/ma/ibm/rs6000/aix/A.02.55/ packet.Z: None /opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.02.55/ packet.Z: None /opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.02.55/ require.dat: None /opt/omni/databases/vendor/ma/sun/sparc/solaris/A.02.55/ packet.Z: None /opt/omni/databases/vendor/das/hp/s800/hp-ux/A.02.55/ packet.Z: None /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.02.55/ packet.Z: None /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.02.55/ require.dat: None cksum(1) Output: 1675071921 2210549 /opt/omni/databases/vendor/acs/hp/s800/ hp-ux/A.02.55/packet.Z 1589678795 2356190 /opt/omni/databases/vendor/acs/hp/s800/ hp-ux-10/A.02.55/packet.Z 3490244583 21 /opt/omni/databases/vendor/acs/hp/s800/ hp-ux-10/A.02.55/require.dat 729788473 1606841 /opt/omni/databases/vendor/ma/hp/s800/ hp-ux/A.02.55/packet.Z 2903494870 1767543 /opt/omni/databases/vendor/ma/hp/s800/ hp-ux-10/A.02.55/packet.Z 3809912062 1718527 /opt/omni/databases/vendor/ma/siemens/ r400/sinix/A.02.55/packet.Z 2083125541 1397298 /opt/omni/databases/vendor/ma/ibm/rs6000/ aix/A.02.55/packet.Z 1726042674 1660055 /opt/omni/databases/vendor/ma/ibm/rs6000/ aix-42/A.02.55/packet.Z 3422067154 17 /opt/omni/databases/vendor/ma/ibm/rs6000/ aix-42/A.02.55/require.dat 932888671 1620125 /opt/omni/databases/vendor/ma/sun/sparc/ solaris/A.02.55/packet.Z 2758164951 1650051 /opt/omni/databases/vendor/das/hp/s800/ hp-ux/A.02.55/packet.Z 1184001751 1798461 /opt/omni/databases/vendor/das/hp/s800/ hp-ux-10/A.02.55/packet.Z 3490244583 21 /opt/omni/databases/vendor/das/hp/s800/ hp-ux-10/A.02.55/require.dat Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_14337 PHSS_14970 PHSS_15466 PHSS_15793 PHSS_16709 Equivalent Patches: PHSS_18242: s700: 11.00 s800: 11.00 Patch Package Size: 17450 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_18241 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_18241.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_18241. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_18241.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_18241.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_18241: NOTE! Patch has to be installed on the Cell Server host. * The Media Agent package needs to be redistributed to the appropriate systems, where the Media Agent Clients are installed, from within the "Cell Administration Install" window of the OmniBackII graphical user interface before the patch modifications take effect. NOTE! Make sure that no backup or restore or media management session is running while you distribute the package to the MA clients. NOTE! A special environment variable is introduced to allow restoring from tapes made on Solaris with st.conf set as suggested in OmniBack II 2.10 Release Notes instead of 2.55 Release Notes (problem NSMex01898). The variable must be set on Solaris media agent host, in the file /usr/omni/.omnirc. This is the syntax: OB2NOSEEK=0 | 1 0: normal 2.55 behaviour (default) 1: enable restore from 2.10 st.conf made tape It is strongly suggested that after the restore has been made, the st.conf is updated to the 2.55 Release Notes setting in order to avoid future restore problems. NOTE! To enable the functionality of using another tape (problem NSMex02048), new environment variable has been introduced. The variable must be set in the file /opt/omni/.omnirc (HP-UX 10.x) or /usr/omni/.omnirc (other unix systems). This is the syntax: OB2ACS_VOLUMEDRIVE_POOR=1 The default value is 0 (functionality disabled). NOTE! In order to solve the problems NSMex02763 and NSMex02816, new environment variables have been introduced to specify the timeout and retry values for the rewind and offline operations. The variables must be set on the Media Agent host file /opt/omni/.omnirc (HP-UX 10.x) or /usr/omni/.omnirc (other unix systems). This is the syntax: OB2REWINDRETRY= OB2REWINDSLEEP= OB2OFFLINERETRY= OB2OFFLINESLEEP= The default value for all variables is 0 (no timeout and retry). NOTE! In order to resolve Defect with Id NSMex01052, also the OMNIBACK II A.02.55 CS packet patch has to be installed. This is currently: PHSS_21321 - on HP-UX 10.x PHSS_21322 - on HP-UX 11.x but may be superseded by a newer version in the future. From the patch PHSS_16709/PHSS_16710 on OmniBack II supports MA on AIX 4.3. Before pushing Media Agent to AIX 4.3 the latest CS patch has to be installed. This is currently: PHSS_21321 - on HP-UX 10.x PHSS_21322 - on HP-UX 11.x PHSS_14970/PHSS_14971: From this patch on OmniBack II officially supports ACS Library System Integration on HP-UX 11.x. Patch includes the following Site Specific Patches: SSPUX255_010 SSPUX255_019 SSPUX255_026 SSPUX255_030 SSPUX255_039 SSPUX255_040 SSPUX255_045 SSPUX255_046 SSPUX255_054 SSPUX255_056 SSPUX255_057 SSPUX255_062 SSPUX255_066 SSPUX255_064 SSPUX255_068 SSPUX255_069 SSPUX255_073 SSPUX255_080 SSPUX255_084 SSPUX255_091 SSPUX255_094 SSPUX255_095 SSPUX255_099 SSPUX255_116 SSPUX255_120 SSPUX255_122 SSPUX255_124 SSPUX255_126 SSPUX255_129 SSPUX255_137 SSPUX255_141 SSPUX255_144 SSPUX255_146