Patch Name: PHSS_30137

Patch Description: s700_800 11.X OV DP5.00 patch - EMC packet

Creation Date: 04/02/17

Post Date: 04/02/18

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

Products:
	DATA-PROTECTOR A.05.00

Filesets:
	DATA-PROTECTOR.OMNI-EMC-P,fr=A.05.00,fa=HP-UX_B.11.00_32/64,v=HP

Automatic Reboot?: No

Status: General Release

Critical:
	Yes
	PHSS_30137: ABORT

Category Tags:
	defect_repair general_release critical halts_system

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

Symptoms:
	PHSS_30137:
	Change Request: H555010461
	  During multiple ZDB sessions on HP-UX running at the
	  same time, the following is reported in the session
	  report:

	   "|Major| From: SSEA@<hostname> <object>  Time: <time>
	   Filesystem <object> could not be mounted to <object>.
	   /usr/sbin/mount -Fv xfs -r <object> <object>
	   2>&1mount: file system table may be corrupt."

	Change Request: H555010512
	  In environments with very large number of Physical
	  Volumes in one Volume Group backup can fail with
	  following error message:

	   "|Major| From: BSM@<hostname> ""  Time:<time>
	    |61:3003| Lost connection to Split Mirror Agent
	    named "noname"on host <hostname>.
	    Ipc subsystem reports: "Details unknown."
	    |Critical| From: SYMA@<hostname> ""  Time:<time>
	    Unexpected close reading SYMA-R2 message
	    (Unknown internal error.) => aborting.
	    |Major| From: OB2BAR_SMB_Split@<hostname> Time:<time>
	    Received ABORT request from RSM (ERR: Error
	    starting backup/restore
	    (BMA cannot be started or similar).)
	    |Normal| From: SYMA@<hostname> ""  Time:<time>
	    ABORTED SYMA-R1 Agent on <hostname>.
	    BR278E Command output of
	    '/opt/omni/lbin/ob2smbsplit
	    /oracle/PM1/sapbackup/.bdkpwibp.lst':
	    |Major| From: OB2BAR_SMB_Split@<hostname> Time:<time>
	    Received ABORT request from RSM
	    (ERR: Error starting backup/restore
	    (BMA cannot be started or similar).)
	    |Major| From: OB2BAR_SMB_Split@<hostname> Time:<time>
	    Preparing of backup host failed (error=-2)
	    |Major| From: OB2BAR_SMB_Split@<hostname> Time:<time>
	    Preparing of backup host failed (error=-2)A
	    syma core file is written on the backup system:
	    file syma_coresyma_core:core file from
	    'syma' - received SIGSEGV."

	Change Request: H555010744
	  Backup is failing with the following error reported:

	    "|Major| From: SYMA@<host name> ""  Time:<time>
	     Volume group <volume group name> could not
	     be activated."

	Change Request: H555010924
	  Volume group on the backup side is created without
	  alternate path.

	Change Request: 8606308890
	  In Split Mirror Backup environments with multiple
	  host bus adapters only one is used, so the backup
	  performance is poor.

	PHSS_28744:
	Change Request: H555008827
	  Mounting of VxFS on VxVM volume fails on the backup
	  host.

	Change Request: H555010044
	  During multiple EMC sessions running at the same time,
	  the following is reported in the session report:

	    "|Major| From: SYMA@<R2_hostname> ""  Time: <time>
	    Filesystem <fs_name> could not be mounted
	    to <mountpoint>.

	    /usr/sbin/mount -F vxfs -r <fs_name> 2>&1
	    mount: file system table may be corrupt".

	Change Request: H555010243
	  Mount command on VxVM EMC integration backup is failing
	  with error:

	    "mount: /dev/<path>: No such file or directory".

	Change Request: H555010272
	  If softlinks are configured on raw disks or raw logical
	  volumes, the following error message appears in the
	  Zero Downtime Backup agent's debugs:

	    "| -2| |ResolveR1| Object type UNKNOWN (0140144)of
	     /dev/<vg_name>/r<lvol_name> is not supported".

	Change Request: H555010341
	  After upgrading from OmniBack II A.04.10 to Data
	  Protector A.05.00 SAP/EMC backup is failing with
	  the following errors reported:

	    "|Major| From: BSM@<host> ""  Time: <time>
	     |61:3003|  Lost connection to Split Mirror
	    Agent named "name" on host <hostname>.
		Ipc subsystem reports: "Details unknown."

	     |Critical| From: SYMA@<host> ""  Time: <time>
	    Unexpected close reading SYMA-R2 message (Unknown
	    internal error.) => aborting.

	     |Major| From: OB2BAR_SMB_Split@<host> Time: <time>
		Received ABORT request from RSM (ERR: Error
	    starting backup/restore (BMA cannot be started
	    or similar).)

	     |Normal| From: SYMA@<hostname> ""  Time: <time>
		ABORTED SYMA-R1 Agent on <hostname>".

Defect Description:
	PHSS_30137:
	Change Request: H555010461
	  When multiple ZDB backup sessions are running and the
	  R2 host is being prepared by two or more sessions at
	  the same time, the mount system command fails because
	  "/etc/mnttab" is being refreshed by one of the other
	  ZDB 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 synchronizing the "mnttab" file.

	Change Request: H555010512
	  The buffer tsCmd is too short to hold the command
	  line that is prepared to be executed.

	  Resolution:
	  The tsCmd buffer in HpuxCreateVolumeGroup ()
	  function is increased.

	Change Request: H555010744
	  "vgimport" command failed because /usr/symcli/bin/symdev
	  show command took the disks from a different EMC frames.

	  Resolution:
	  Symmetrix ID is included in "symdev show" command.

	  Part of SSPUX500_032.

	Change Request: H555010924
	  Because strtok function is used in a wrong way,
	  alternate paths for volume groups are not created.

	  Resolution:
	  Temporary structure is used for parsing information
	  from alternate_paths structure.

	Change Request: 8606308890
	  Data Protector 5.00 Split Mirror Backup is using
	  volume group auto configuration on the backup host
	  and the first path is configured. This feature is
	  causing problems in environments, where multiple
	  host bus adapters are used on the backup host.
	  Reading data from disk across the multiple paths
	  to balance backup load is not possible.

	  Resolution:
	  New .omnirc variable ZDB_BACKUP_VG_EXIST is
	  introduced which disables auto configuration.
	  If set to 1 backup VG that already exists is used.
	  With other agents this variable is set to 0
	  (inf.backup_vg_exist = 0;).

	PHSS_28744:
	Change Request: H555008827
	  Disk group importing procedure is incorrectly
	  implemented on the backup side.

	  Resolution:
	  Disk group importing procedure in corrected.

	Change Request: H555010044
	  When multiple SYMA backups are running and R2 host
	  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 SYMA
	  sessions at that moment.

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

	Change Request: H555010243
	  The DP EMC integration on Data Protector A.05.00 does
	  not include the PowerPath supportability.

	  Resolution:
	  The DP EMC integration includes the PowerPath
	  supportability.

	  Part of SSPUX500_015.

	Change Request: H555010272
	  Backup fails after all the operations handled by
	  Data Protector agents and ob2smbsplit are completed
	  because object type inquiry is not recognized.

	  Resolution:
	  Object type inquiry is changed.

	Change Request: H555010341
	  Buffer in function "HpuxCreateVolumeGroup ()" is not big
	  enough for "vgimport" command containing large number of
	  disks as parameters which causes "syma" to end
	  abnormally.

	  Resolution:
	  Buffer is increased.

Enhancement:
	No

SR:
	H555010924 H555010512 8606308890 H555010744 H555010461
	H555010044 H555010272 H555008827 H555010243 H555010341

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

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

cksum(1) Output:
	
	DATA-PROTECTOR.OMNI-EMC-P,fr=A.05.00,fa=HP-UX_B.11.00_32/64,
		v=HP:
	1630881874 316437 /opt/omni/databases/vendor/emc/hp/s800/
		hp-ux-1020/A.05.00/packet.Z
	1282397488 324271 /opt/omni/databases/vendor/emc/hp/s800/
		hp-ux-11/A.05.00/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_28744 

Equivalent Patches: None

Patch Package Size: 640 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_30137

	5. Run swinstall to install the patch:

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

	By default swinstall will archive the original software in 
	/var/adm/sw/save/PHSS_30137.  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_30137.text file is 
	available in the product readme:

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

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

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

Special Installation Instructions:
	PHSS_30137:
	NOTE!

	This patch has to be installed on the Installation
	Server host.

	The DP 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 Data
	Protector Installation guide.

	Patch includes the following Site Specific Patches:
	    SSPUX500_015
	    SSPUX500_032

	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.