Patch Name: PHSS_28020

Patch Description: s700_800 11.X OV OB3.50 patch - EMC packet

Creation Date: 03/01/16

Post Date:  03/01/23

Hardware Platforms - OS Releases:
	s700: 11.00 11.11 11.20
	s800: 11.00 11.11 11.20

Products:
	OmniBackII A.03.50

Filesets:
	OMNIBACK-II.OMNI-EMC-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP

Automatic Reboot?: No

Status: General Release

Critical: No

Category Tags:
	defect_repair general_release manual_dependencies

Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28020

Symptoms:
	PHSS_28020:
	Id = HSLco33557  SR: H555007506
	    File /var/opt/omni/emc/symm.bin is too large.

	Id = HSLco37193  SR: H555008807
	    When backing up SAP integration with EMC split mirror
	    functionality, not all the SAP files are backed up.

	Id = HSLco31734  SR: H555006894
	    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 = HSLco27622  SR: H555005717
	    SSEA backup fails with an error:

	    "Filesystem <path> could not be mounted.".

	Id = HSLco28507  SR: H555006043
	    Restore fails with an error:

	      "[Minor] From: VRDA@<hostname> "SAP"  Time:<time>
	         /oracle/R3E/sapdata2/el46bd_2/el46bd.data2
	         Can not open: ([30] Read-only file system)
	         => not restored."

	PHSS_23469:
	Id = NSMex03739
	    Pre- and post-exec scripts return invalid exit status.

	Id = NSMex03891
	    Disk resolving fails after additional disks are added
	    to volume group.

	Id = NSMex04003, NSMex03695
	    EMC backup fails if there are more than 256 disks.

Defect Description:
	PHSS_28020:
	Id = HSLco33557
	    SymDiscover API appends information to the existing
	    symm.bin file everytime it is called.

	Resolution:
	    File symm.bin is recreated and contains fresh
	    information when "-discovery" option is used in the
	    datalist.

	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 SSPUX350_080.

	Id = HSLco31734
	    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 = HSLco27622
	    Incorrect filesystem options are sent to R2 side.
	    For HFS filesystems the entries in the mnttab file
	    are not updated promptly.

	Resolution:
	    Correct filesystem options are sent to R2 side.
	    /etc/mnttab is promptly updated for HFS filesystem.

	Id = HSLco28507
	    During the restore some file systems are mounted as
	    read-only, so the restore fails.

	Resolution:
	    An additional condition is set for enabling the
	    read-only mode.

	PHSS_23469:
	Id = NSMex03739
	    Pre- and post-exec scripts return invalid exit status
	    because of timing problem.

	Resolution:
	    Environment variable OB2EXECTIMEOUT is introduced.
	    Variable represents timeout (in seconds) after the end
	    of pre- and post-exec script. Default value is 0.
	    Recommended value is between 5 and 10 seconds.

	Id = NSMex03891
	    Message size for resolving information is too small
	    if there are many objects in backup specification or
	    if there are many disks in a single volume group.

	Resolution:
	    Message size is increased.

	    Part of SSPUX350_018.

	Id = NSMex04003, NSMex03695
	    OmniBack II has a limitation of 256 disks for EMC
	    configuration. If there is a configuration with more
	    than 256 disks, backup fails.

	Resolution:
	    Limitation is increased to 1024 disks.

	    Part of SSPUX350_005.

Enhancement:
	No

SR:
	H555007506 H555006894 H555005717 H555006043 H555008807
	H555004394 B554000824 H555004354 B554000869

Patch Files:
	
	OMNIBACK-II.OMNI-EMC-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.03.50/
		packet.Z

what(1) Output:
	
	OMNIBACK-II.OMNI-EMC-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-1020/A.03.50/
		packet.Z:
		None
	/opt/omni/databases/vendor/emc/hp/s800/hp-ux-11/A.03.50/
		packet.Z:
		None

cksum(1) Output:
	
	OMNIBACK-II.OMNI-EMC-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
		v=HP:
	3018644113 531278 /opt/omni/databases/vendor/emc/hp/s800/
		hp-ux-1020/A.03.50/packet.Z
	1783684878 532337 /opt/omni/databases/vendor/emc/hp/s800/
		hp-ux-11/A.03.50/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies:
	If any newer SSP for the Cell Console is installed
	on your system, you must re-apply the SSP after
	installing this Cell Console patch.

	PHSS_28223:
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28223 is required for this defect fix.

	PHSS_28022:
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28022 is required for this defect fix.

	PHSS_28018:
	Release Date: Available
	Id = HSLco37193  SR:H555008807
	PHSS_28018 is required for this defect fix.

Supersedes:
	PHSS_23469 

Equivalent Patches:
	PHSS_28019:
	s700: 10.00 10.01 10.10 10.20
	s800: 10.00 10.01 10.10 10.20

Patch Package Size: 1070 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_28020

	5. Run swinstall to install the patch:

		swinstall -x autoreboot=true -x patch_match_target=true \
			  -s /tmp/PHSS_28020.depot

	By default swinstall will archive the original software in 
	/var/adm/sw/save/PHSS_28020.  If you do not wish to retain a
	copy of the original software, include the patch_save_files
	option in the swinstall command above:

		-x patch_save_files=false

	WARNING: If patch_save_files is false when a patch is installed,
		 the patch cannot be deinstalled.  Please be careful
		 when using this feature.

	For future reference, the contents of the PHSS_28020.text file is 
	available in the product readme:

		swlist -l product -a readme -d @ /tmp/PHSS_28020.depot

	To put this patch on a magnetic tape and install from the
	tape drive, use the command:

		dd if=/tmp/PHSS_28020.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
	PHSS_28020:
	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:
	   SSPUX350_005
	   SSPUX350_018
	   SSPUX350_080