Patch Name: PHSS_32032

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

Creation Date: 04/12/13

Post Date: 05/01/10

Hardware Platforms - OS Releases:
	s700: 10.20
	s800: 10.20

Products:
	OmniBackII A.04.10

Filesets:
	OMNIBACK-II.OMNI-SNAPA-P,A.04.10

Automatic Reboot?: No

Status: General Release

Critical: No

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

Symptoms:
	PHSS_32032:
	Change Request: H555009900
	  The "SNAPA" agent ends abnormally while resolving
	  backup objects on the application system.

	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: H555011233
	  If the "use existing snapshot" option is used, the backup
	  session reports to be completed successfully, but the
	  data is not actually backed up from the application host.

	PHSS_28230:
	Change Request: H555008604
	  Disk resolving on backup host is very slow.

	Change Request: H555008788
	  Some of the volume groups cannot be activated.

	Change Request: H555008995
	  Snapa backup fails with:

	    "[Normal] From: SNAPA@<backup_host> ""  Time: <time>
		ABORTED SNAPA-Backup Agent on <backup_hostname>."

	PHSS_27450:
	Change Request: H555006949
	  SNAPA agent has poor resolving performance.

	Change Request: H555007503
	  debug.log file gets filled with messages:

	    "mm/dd/yy hh:mm:ss  SNAPA.10149.0
	     ["<source file, version>":<line>] A.04.10 <VERSION>
	     [<function>] /dev/rdsk/c?t?d? is not a VA disk!"

	Change Request: H555008436
	  SNAPA agent abnormally ends while resolving backup
	  objects on application system.

	Change Request: H555008538
	  Backup using VA integration fails with:

	    "[Major] From: SNAPA@<hostname> ""
	     Time: mm/dd/yy hh:mm:ss
	     Failed to split the BC pair of LDEV
	     <ldev#>, SEQ# , MU#"

Defect Description:
	PHSS_32032:
	Change Request: H555009900
	  The buffer for "rdsks" and "LUNs" information is too
	  big. When the "SNAPA" agent tries to transfer the
	  buffer to the session output, it ends abnormally.

	  Resolution:
	  The information is transferred to the session output in
	  chunks, keeping the buffer size within the allowed
	  limits.

	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: H555011233
	  Due to an improper parameter read, the
	  BCAPI_CopyFromParent() API function is never called,
	  which causes the data from the application host never
	  to be updated to the backup host.

	  Resolution:
	  Proper parameter read before the
	  BCAPI_CopyFromParent() API function is called.

	PHSS_28230:
	Change Request: H555008604
	  All devices on backup host are being queried.

	  Resolution:
	  Only VA disks are queried when gathering disk
	  information.

	Change Request: H555008788
	  If the application host is MC/SG system, then volume
	  groups on the backup host cannot be activated in
	  read/write mode.

	  Resolution:
	  Volume groups on backup side are marked "not-clustered"
	  before activation in read/write mode. To prevent such
	  marking set SMB_CLUS_DEACT=1 in /opt/omni/.omnirc file.
	  Note: SMB_CLUS_DEACT=1 means the volume group is marked
	  as clustered.

	Change Request: H555008995
	  New HP17 VA firmware is not working with the API v.2.2.

	  Resolution:
	  Snapa agent is rebuilt with new API v.2.3.

	  Part of SSPUX410_051.

	PHSS_27450:
	Change Request: H555006949
	  One of the API's called during resolving takes up
	  to 45 seconds to complete. Calling this API multiple
	  times causes poor performance.

	  Resolution:
	  Resolving algorithm is improved.

	  Part of the SSPUX410_003.

	Change Request: H555007503
	  Every time SNAPA agent encounters non-VA disk during
	  resolving phase, a message is logged in debug.log file.

	  Resolution:
	  Debug range for message is changed and the message is
	  not logged.

	Change Request: H555008436
	  When SNAPA agent tries to dump buffer containing
	  information about rawdisks and LUN's to session output,
	  it ends abnormally if buffer is too big.

	  Resolution:
	  Information about rawdisks and LUN's is being dumped to
	  session output in pieces keeping the buffer within
	  prescribed size.

	  Part of SSPUX410_026.

	Change Request: H555008538
	  SNAPA agent parses the output of "vgdisplay -v <vgname>"
	  and collects logical volume names. It collects physical
	  volume name as well in environments where PVG's are
	  configured.

	  Resolution:
	  Parsing is terminated when "PVG name" token is
	  encountered.

SR:
	H555011233 H555010044 H555010461 H555009900
	H555008604 H555008995 H555008788 H555006949
	H555008436 H555007503 H555008538

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

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

cksum(1) Output:
	527211566 482637 /opt/omni/databases/vendor/snapa/hp/s800/
		hp-ux-11/A.04.10/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_27450 PHSS_28230

Equivalent Patches:
	PHSS_32033:
	s700: 11.00 11.11
	s800: 11.00 11.11

Patch Package Size: 520 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_32032

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

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

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

Special Installation Instructions:
	PHSS_32032:
	NOTE!
	This Patch has to be installed on the Installation
	Server host.

	The OB2 SNAPA agent must be redistributed to the SNAPA
	client system(s) after the installation of the patch
	in order to get the fixes into effect.

	For distribution of the SNAPA agent, refer to
	the OmniBackII Installation guide.

	
	Patch includes the following Site Specific Patches:
	   SSPUX410_003
	   SSPUX410_026
	   SSPUX410_051

	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 SNAPA agent
	is installed on your system, then you
	must re-apply this SSP after installing
	this SNAPA patch.