Patch Name: PHSS_28341 Patch Description: s700_800 10.20 OV OB4.10 patch - EMC packet Creation Date: 03/01/17 Post Date: 03/01/22 Hardware Platforms - OS Releases: s700: 10.20 s800: 10.20 Products: OmniBackII A.04.10 Filesets: OMNIBACK-II.OMNI-EMC-P,A.04.10 Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_28341 Symptoms: PHSS_28341: Id = HSLco37092 SR: H555008778 Restore fails with: "|Major| From: SYMA@<hostname> "" Time: <time> |223:325| Could not activate volume group /dev/sg_sap. |Major| From: SYMA@<hostname> "" Time: <time> |223:363| Could not prepare mirror disks of object /sg_sap for backup. (Activation of volume group failed.)". Id = HSLco37193 SR: H555008807 When backing up SAP integration with EMC split mirror functionality, not all the SAP files are backed up. Defect Description: PHSS_28341: Id = HSLco37092 Backup is made in SSEA/split mirror backup environment with the Application host in the cluster. When restoring object on the Backup host (R2), which is not in the cluster the cluster tag (-c y) from the Application host is also restored, so the volume group can not be activated properly. Resolution: By default the cluster tag on the Backup host (R2) is disabled with the "vgchange -q n -c n" command. To enable the cluster tag on Backup host, set the new environment variable SMB_CLUS_DEACT=1 in the /opt/omni/.omnirc file. Id = HSLco37193 In split mirror environment with huge SAP databases it can happen that the size of the message buffer OmniBack II uses is too small to receive complete list of SAP files to be backed up. Resolution: Setting the OB2IPCBUFSIZE environment variable in the /opt/omni/.omnirc file on Cell Server, R1 and R2 hosts, specifying the desired amount of memory to be used for the buffer solves the described problem. Please read the following instructions and make sure that the patches listed in "Other Dependencies" section (see below) are installed and the environment variable is set on Cell Server, R1 and R2 systems before running the backup! How to determine the buffer size? --------------------------------- N_obj: number of objects (files) N_fs: number of file systems N_lvmvg: number of volume groups N_dg: number of disk groups N_rdsk: number of rawdisks Obj: Object Name ObjBack: Object Backup Name MntPathLen: Path name on backup (R2) host (example: /var/opt/omni/tmp/App_host) fsmnt: File System Mount Point fsdev: File System Device File (example: /dev/dsk/|c0t1d1,lvol1|) vg: Volume group (ex: /dev/vg01) dg: Disk group (VxVM) - dependence on mapfile which is required for creating disk group (example:/dev/vx/dsk/dg01) rdsk: Raw disk file name (example: /dev/rdsk/c1t1d1) AvgLen_<xxx> average length of <xxx> There are two different buffers used: 1. BSM <-> R1 2. R1 <-> R2 Calculating the BSM <-> R1 buffer size -------------------------------------- MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen) Calculating the R1 <-> R2 buffer size ------------------------------------- MsgSize_R1_R2 = N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) + N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+ N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) + N_rdsk*(AvgLen_rdsk*2) Calculating the OB2IPCBUFSIZE value ----------------------------------- OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2) RESTORE NOTE: ------------- If restore is started using the sapbda utility, the variable OB2IPCBUFSIZE must be exported to environment prior to starting sapbda. Known problems: --------------- If the calculated variable OB2IPCBUFSIZE is correctly set, but is still too small for the file list to fit into the message buffer, the session will fail with the following error seen in the report: BR295I Splitting mirror disks... BR280I Time stamp <time> BR279E Return code from '/opt/omni/lbin/ob2smbsplit /<sap_homedir_path>/.<filename>.lst': 2 BR299E Split/resynchronization of mirror disks failed In this case the variable OB2IPCBUFSIZE must be recalculated to appropriate value. See above how to determine it. Part of SSPUX410_033. SR: H555008778 H555008807 Patch Files: /opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.04.10/ packet.Z /opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.04.10/ packet.Z what(1) Output: /opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.04.10/ packet.Z: None /opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.04.10/ packet.Z: None cksum(1) Output: 599085285 263939 /opt/omni/databases/vendor/emc/hp/s800/ hp-ux-1020/A.04.10/packet.Z 316652955 275030 /opt/omni/databases/vendor/emc/hp/s800/ hp-ux-11/A.04.10/packet.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: If any newer SSP for the EMC is installed on your system, you must re-apply the SSP after installing this EMC patch. PHSS_28331: Release Date: Mid February 2003 Id = HSLco37193 SR:H555008807 PHSS_28331 is required for this defect fix. PHSS_28232: Release Date: Early February 2003 Id = HSLco37193 SR:H555008807 Bad catalog access message is displayed without PHSS_28232. PHSS_28343: Release Date: Early February 2003 Id = HSLco37193 SR:H555008807 PHSS_28343 is required for this defect fix. PHSS_27602: Release Date: Available Id = HSLco37193 SR:H555008807 PHSS_27602 is required for this defect fix. Supersedes: None Equivalent Patches: PHSS_28342: s700: 11.00 11.11 11.20 s800: 11.00 11.11 11.20 Patch Package Size: 580 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_28341 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_28341.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_28341. 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_28341.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_28341.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_28341: NOTE! This patch has to be installed on the Installation Server host. The OB2 EMC agent must be redistributed to the EMC client system(s) after the installation of the patch in order to get the fixes into effect. For distribution of the EMC agent, refer to the OmniBackII Installation guide. Patch includes the following Site Specific Patches: SSPUX410_033