Patch Name: PHSS_32030

Patch Description: s700_800 10.20 OV OB4.10 patch - EMC packet

Creation Date: 04/12/08

Post Date: 05/01/12

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 Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHSS_32030

Symptoms:
	PHSS_32030:
	Change Request: H555010044
	  Error is reported during multiple split mirror sessions
	  running simultaneously.

	Change Request: H555010461
	  An error is reported during multiple split mirror
	  sessions on HP-UX running simultaneously.

	Change Request: H555010893
	  After split, some disks from the volume group are still
	  synchronized.

	PHSS_28341:
	Change Request: 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.)".

	Change Request: H555008807
	  When backing up SAP integration with EMC split mirror
	  functionality, not all the SAP files are backed up.

Defect Description:
	PHSS_32030:
	Change Request: H555010044
	  When multiple split mirror backups are running and
	  backup system is being prepared by two or more sessions
	  at the same time, the mount system command can fail
	  because the "/etc/mnttab" is refreshed by one of the
	  other split mirror sessions at that moment.

	  Resolution:
	  A retry/sleep is introduced to prevent mount system
	  command.

	Change Request: H555010461
	  When multiple split mirror backup sessions are running,
	  and the backup system is being prepared by two or more
	  sessions simultaneously, the mount system command fails
	  because the "/etc/mnttab" is being refreshed by one of
	  the other split mirror sessions at the same time.

	  Resolution:
	  The system level umount(1M) command is used instead of
	  the program level umount(2) command in order to avoid
	  problems with synching the "mnttab" file.

	Change Request: H555010893
	  The Symmetrix Agent (Syma) uses the "lvdisplay" command
	  to obtain information about disks in the volume group.

	  Resolution:
	  The "vgdisplay" command is used instead of "lvdisplay"
	  to obtain information about disks in the volume group.

	PHSS_28341:
	Change Request: H555008778
	  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.

	Change Request: H555008807
	  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:
	H555010044 H555010893 H555010461 H555008778
	H555008807

Patch Files:
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.04.10/
		packet.Z

what(1) Output:
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.04.10/
		packet.Z:
		None

cksum(1) Output:
	3706760247 270888 /opt/omni/databases/vendor/emc/hp/s800/
		hp-ux-1020/A.04.10/packet.Z
	1216406177 275511 /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:
	Some of the defect fixes contained in this patch
	depend on the following other patches or their
	successors in order to completely resolve the problem:

	PHSS_31956:
	Cell Console (CC) packet patch,
	Release Date: Available
	Change Request: H555008807
	PHSS_31956 is required for this defect fix.

	PHSS_32015:
	Core packet patch,
	Release Date: Available
	Change Request: H555008807
	Bad catalog access message is displayed without PHSS_32015.

	PHSS_30568:
	SAP packet patch,
	Release Date: Available
	Change Request: H555008807
	PHSS_30568 is required for this defect fix.

	PHSS_32019:
	Cell Server (CS) packet patch,
	Release Date: Available
	Change Request: H555008807
	PHSS_32019 is required for this defect fix.

Supersedes:
	PHSS_28341

Equivalent Patches:
	PHSS_32031:
	s700: 11.00 11.11
	s800: 11.00 11.11

Patch Package Size: 570 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_32030

	5a. For a standalone system, run swinstall to install the
	    patch:

		swinstall -x autoreboot=true -x match_target=true \
			-s /tmp/PHSS_32030.depot

	By default swinstall will archive the original software in 
	/var/adm/sw/patch/PHSS_32030.  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_32030.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_32030.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	PHSS_32030:
	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

	A Site Specific Patch is a temporary hotfix that
	you might have received from HP Support if you
	have encountered a problem with Data Protector
	for which no General Release patch was or is
	available yet.

	If any newer Site Specific Patch - that is
	one with a higher number - for the EMC agent
	is installed on your system, then you
	must re-apply this SSP after installing
	this EMC patch.