Patch Name: PHSS_18701 Patch Description: s700_800 10.X OV OB3.00 patch - MA packet Creation Date: 99/07/30 Post Date: 99/08/05 Repost: 99/12/20 The patch documentation was modified to remove references to a problem that is not addressed in PHSS_18701. The patch does not allow more than 15 drives in the EMASS/GRAU library as was originally reported (defect id HSLco14440). 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.03.00 Filesets: OMNIBACK-II.OMNI-DAS-P OMNIBACK-II.OMNI-ACS-P OMNIBACK-II.OMNI-HPUX-P OMNIBACK-II.OMNI-OTHUX-P Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_18701 Symptoms: PHSS_18701: Id = HSLco12897 Tape drives are left locked in a EMASS/GRAU Library after the session. Id = NSMex02331 Eject fails, but no message is reported if the mailslot is full/empty during the eject/enter operation. Id = NSMex02048 OmniBack II tries to mount a medium that is already in another drive. The operation fails, and the session is aborted. Id = NSMbb23166 In EMASS/GRAU Library with more than one drive the drives are connected to multiple Media Agent hosts. If this is the configuration, then the EMASS/GRAU robotics cannot be accessed from multiple Media Agent hosts. Id = HSLco12765 Platters with capacity > 2Gb per side cannot be used in magneto optical devices. Id = NSMex02501 When trying to backup to a device attached to a different host than the picker, the error is reported and session is aborted: "Can not open exchanger control device (Details unknown.)" Id = NSMex02216 OB2BAR or Disk Agent process can not attach to the shared memory. PHSS_17303: Id = NSMbb21763 Aborted backup session with reconnect option doesn't write catalog to medium. The error message comes up: "Physical position of the last segment is not consistent ...". Id = HSLco11087 Ejecting more than one selected tape from EMASS/GRAU repository sometimes reports incorrect number of actually ejected tapes. Id = HSLco12763 OmniBack II doesn't report a dirty drive even the cleanme signal on device is pending. Id = NSMbb21763 Tape drives are left locked in a EMASS/GRAU Library. Id = NSMex01795 Media Agent on Sun Solaris hangs when trying to dismount the tape from Surestore 12000e device. Id = NSMex01843 Append on 3480 tape is not possible. Id = NSMex01898 Can not seek to requested position during restore. Id = NSMex01905 If system has only ACS or DAS packet installed, it cannot be configured as a 'device server', and no device can be configured for that system. Id = NSMex01958 Dirty drive detection on DLT7000 doesn't work. Id = NSMex01970 Install window doesn't show MA packet installed on a system after ACS or DAS agent has been installed on that system. Defect Description: PHSS_18701: Id = HSLco12897 When using more than one drive in EMASS/GRAU Library backup session might successfully dismount the tapes but the drives are left locked. The next backup session will fail because the drives are still locked by the previous session. Part of SSPUX300_032 Resolution: The aci_init() function is only called when there are no tapes mounted in drives. Id = NSMex02331 During eject/enter into/from full/empty mailslot on SCSI-II Library nothing happens for 10 minutes. There is no warning message that mailslot is full or empty and UMA is actually waiting for the operator to do the proper action (remove or enter the medium into the mailslot). Resolution: New message informs the operator that the medium should be removed or entered into the mailslot. Id = NSMex02048 If mount of a tape fails with STATUS_VOLUME_IN_DRIVE, it means that tape is in some other drive. OmniBack doesn't interprete this ACS error code, and the session is aborted. Part of SSPUX300_036 Resolution: Mark the tape as Poor if the result of the tape mount is STATUS_VOLUME_IN_DRIVE , since there is no "Not Ready" mark in OmniBack. Id = NSMbb23166 The problem can be seen in EMASS/GRAU integration if Multiple MA hosts are connected to the drives and each MA client is controling EMASS/GRAU robotics. MA aborts with the Critical message: "Grau DAS error in "aci_init()": error code=19" Part of SSPUX300_043 Resolution: Each MA agent must have a unique DAS client name in order for DAS server to recognize it. This name can now be specified in the /opt/omni/.omnirc file on the MA host(s), using this syntax: DAS_CLIENT= Example: DAS_CLIENT=OMNIBACK_2 This unique name must also be present in the file \das\etc\config on the DAS server in order for the MA host to be able to contact DAS server. Id = HSLco12765 Relative positioning on MO media is limited to 32-bit addresses, which results in 2Gb capacity only. Part of SSPUX300_051 Resolution: Use 64-bit integer for position index on MO platters. Id = NSMex02501 After opening a changer device, controlled by multiple MA hosts, uma returns incorrect result to the media agent, and the session is aborted. Resolution: The function for opening robotics control file now handles return code correctly. Id = NSMex02216 Disk Agent or OB2BAR process started on the same host as a Media Agent (HP-UX 11.x). The DA or OB2BAR process aborts because it can not attach to the Media Agent shared memory. The DA or OB2BAr process reports the message: "IPC Can not Allocate Shared Memory Segment System error: [13] Permission denied." Part of SSPUX300_078. Resolution: Special environemnt variable OB2SHMEM_IPCGLOBAL is introduced to inform media agent to create shared memory accessible by other processes from other memory windows. See 'Special Installation Instructions' on how to use this varaible. PHSS_17303: Id = NSMbb21763 When user aborts a backup with reconnect option, the timing issue could result in the final catalog segment not being written to the medium. The next appended backup reports warning. This can occur on all platforms. Part of SSP30_06. Id = HSLco11087 This can happen only on EMASS/GRAU OmniBack II integration. The user selects more than one tape for ejecting and if EMASS/GRAU has problems ejecting one of them, OmniBack II will incorrectly update ejected tapes and reports that no tapes were ejected. Resolution: For loop used for ejecting tapes rather than calling eject function with the list of tapes as a parameter. Id = HSLco12763 NT Media Agent client doesn't detects dirty drive on tape devices even if dirty drive detection option is selected. Id = NSMbb21763 When using more than one drive in EMASS/GRAU Library, a backup session might successfully dismount the tapes but the drives are left locked. The next backup session will fail because the drives are still locked from previous one. Part of SSP30_32. Resolution: Algorithm changed, so that aci_init is called only once, or only if no tapes are mounted in drives. Id = NSMex01795 The HP SureStore 12000e connected on Sun Solaris can not dismount the tape from drive. The message on HP SureStore's LCD says SemiLoaded. Part of SSP30_05. Id = NSMex01843 Trying to position to the end-of-data, the device gives up too early. This causes the error: "Can not append to medium (Medium error.)" even if verify shows no errors and the backup completed successfully. This can occur on the following Media Agent platforms: HP-UX, Solaris, NT, NetWare. Part of SSP30_06. Id = NSMex01898 When doing an appended backup, the session completes successfully although the tape positions are not correctly updated in database. The problem can only be seen on Solaris MA system, configured with st.conf as proposed in 2.10 Release Notes, and if upgrade to 3.00 was done without changing st.conf the way it is proposed in 3.00 Release Notes. Part of SSP30_12. Resolution: See Special Installation Instructions. Id = NSMex01905 After installing only the ACS or DAS packet the client is not marked as a Media Agent client and no devices can be configured for this client. It also cannot be configured as a device server, and as a result 'single drive' licenses are taken for such system instead of 'multi drive' licenses. Id = NSMex01958 Dirty drive detection has been implemented for DLT4000 drives only, but not for DLT 7000. Resolution: DLT7000 added into internal table of DLT devices with dirty drive detection. Id = NSMex01970 Installation of ACS or DAS agent doesn't update the installation info file properly. It leaves the MA field empty, although the MA packet is actually a part of both packets. Later on this leads into administrator not being able to configure any devices for such system, or not being able to configure it as a 'device server'. Resolution: Installation procedure now updates the MA field in case ACS or DAS agent is installed on a system. SR: 5003461590 1653293829 1653288902 Patch Files: /opt/omni/databases/vendor/ma/hp/s800/hp-ux/A.03.00/packet.Z /opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.03.00/ packet.Z /opt/omni/databases/vendor/ma/siemens/r400/sinix/A.03.00/ packet.Z /opt/omni/databases/vendor/ma/ibm/rs6000/aix/A.03.00/ packet.Z /opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.03.00/ packet.Z /opt/omni/databases/vendor/ma/sun/sparc/solaris/A.03.00/ packet.Z /opt/omni/databases/vendor/das/hp/s800/hp-ux/A.03.00/ packet.Z /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.03.00/ packet.Z /opt/omni/databases/vendor/das/ibm/rs6000/aix-42/A.03.00/ packet.Z /opt/omni/databases/vendor/acs/hp/s800/hp-ux/A.03.00/ packet.Z /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.03.00/ packet.Z what(1) Output: /opt/omni/databases/vendor/ma/hp/s800/hp-ux/A.03.00/ packet.Z: None /opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.03.00/ packet.Z: None /opt/omni/databases/vendor/ma/siemens/r400/sinix/A.03.00/ packet.Z: None /opt/omni/databases/vendor/ma/ibm/rs6000/aix/A.03.00/ packet.Z: None /opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.03.00/ packet.Z: None /opt/omni/databases/vendor/ma/sun/sparc/solaris/A.03.00/ packet.Z: None /opt/omni/databases/vendor/das/hp/s800/hp-ux/A.03.00/ packet.Z: None /opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.03.00/ packet.Z: None /opt/omni/databases/vendor/das/ibm/rs6000/aix-42/A.03.00/ packet.Z: None /opt/omni/databases/vendor/acs/hp/s800/hp-ux/A.03.00/ packet.Z: None /opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.03.00/ packet.Z: None cksum(1) Output: 4179036585 1545685 /opt/omni/databases/vendor/ma/hp/s800/ hp-ux/A.03.00/packet.Z 1775032422 1730053 /opt/omni/databases/vendor/ma/hp/s800/ hp-ux-10/A.03.00/packet.Z 1132353096 1722914 /opt/omni/databases/vendor/ma/siemens/ r400/sinix/A.03.00/packet.Z 1119651976 1253058 /opt/omni/databases/vendor/ma/ibm/rs6000/ aix/A.03.00/packet.Z 1651061607 1386774 /opt/omni/databases/vendor/ma/ibm/rs6000/ aix-42/A.03.00/packet.Z 2491782777 1646275 /opt/omni/databases/vendor/ma/sun/sparc/ solaris/A.03.00/packet.Z 1446206576 1559859 /opt/omni/databases/vendor/das/hp/s800/ hp-ux/A.03.00/packet.Z 1072327517 1744115 /opt/omni/databases/vendor/das/hp/s800/ hp-ux-10/A.03.00/packet.Z 3363527589 1400641 /opt/omni/databases/vendor/das/ibm/ rs6000/aix-42/A.03.00/packet.Z 2084539147 2022751 /opt/omni/databases/vendor/acs/hp/s800/ hp-ux/A.03.00/packet.Z 2447364845 2213273 /opt/omni/databases/vendor/acs/hp/s800/ hp-ux-10/A.03.00/packet.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_17303 Equivalent Patches: PHSS_18702: s700: 11.00 s800: 11.00 Patch Package Size: 17870 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_18701 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_18701.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_18701. 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_18701.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_18701.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_18701: NOTE! Patch has to be installed on all Installation server hosts. * 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! For problem NSMex02216, a special environment variable has been introduced in order to tell the Media Agent to enable other processes from different memory windows accessing its shared memory. The variable name is OB2SHMEM_IPCGLOBAL and it should be set in the file /opt/omni/.omnirc on the Media Agent host, using the following syntax: OB2SHMEM_IPCGLOBAL=1 This way, the flag IPC_GLOBAL is used when creating a shared memory segment. NOTE! From patch PHSS_17303/PHSS_17304 on, OmniBackII supports EMASS/GRAU Integration on IBM AIX 4.2. NOTE! Special notes for problem with Id NSMex01898: The fix in this patch enables restoring corrupted tapes. When the restore fails with "Can not seek to requested position ...", add the option OB2NOSEEK=1 into the file /usr/omni/.omnirc on Sun Solaris MA client and restart restore. After restore has been done, clear the entry from .omnirc.To avoid further producing of corrupted tapes, the customer must also change the configuration in the file /kernel/drv/st.conf according to the explanations given in the OBII 3.0 Installation and Licensing Guide, Chapter 2, Section 'Installing the Solaris Client System'. Patch includes the following Site Specific Patches: SSPUX300_005 SSPUX300_006 SSPUX300_012 SSPUX300_029 SSPUX300_032 SSPUX300_036 SSPUX300_043 SSPUX300_051 SSPUX300_078