Patch Name: PHSS_30140

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

Creation Date: 04/01/29

Post Date: 04/02/03

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

Products:
	DATA-PROTECTOR A.05.00

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

Automatic Reboot?: No

Status: General Release

Critical: No

Category Tags:
	defect_repair general_release

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

Symptoms:
	PHSS_30140:
	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: H555010924
	  Volume group on the backup side is created without
	  alternate path.

	Change Request: H555011061
	  During a Oracle integration ZDB backup on HP-UX LVM
	  using the SNAPA agent the following error is reported:

	   "|Minor| From:OB2BAR@<hostname> <barlist> Time:<time>
	    Error:Cannot read object <objectname>(|5| I/O error)"

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

	PHSS_29145:
	Change Request: H555009900
	  Backup using BC fails with error message:

	    "|Critical| From: SNAPA@<host> ""  Time:<time>
	     Unexpected close reading message from the agent on
	     the application system.
	     (Unknown internal error.)

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

	    "|Major| From: SNAPA@<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 SNAPA 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".

	PHSS_28228:
	Change Request: H555008995
	  Snapa backup fails with:

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

Defect Description:
	PHSS_30140:
	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: 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: H555011061
	  There is an error in the way the LVM mirror disks
	  are counted on the R1 side.

	  Resolution:
	  LVM mirror disks are correctly counted on the R1 side.

	  Part of SSPUX500_038.

	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_29145:
	Change Request: H555009900
	  The SNAPA agent abnormally ends while resolving the
	  backup objects on the application system. The buffer
	  which includes information about the rdsks and LUNs
	  is too big, so SNAPA agent can not dump the buffer
	  in the session output.

	  Resolution:
	  The information is dumped in the session output by
	  chunks, taking care that buffer size is within the
	  allowed limits. The array for storing data gathered
	  from the BCAPI_OpenArray API is extended.

	Change Request: H555010044
	  When multiple SNAPA 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 SNAPA
	  sessions at that moment.

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

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

	  Resolution:
	  The DP SNAPA integration includes the PowerPath
	  supportability.

	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.

	PHSS_28228:
	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 SSPUX500_010.

Enhancement:
	No

SR:
	H555010924 8606308890 H555011061 H555010461 H555010044
	H555010272 H555010243 H555009900 H555008995

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

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

cksum(1) Output:
	
	DATA-PROTECTOR.OMNI-SNAPA-P,fr=A.05.00,
		fa=HP-UX_B.11.00_32/64,v=HP:
	2244797758 476779 /opt/omni/databases/vendor/snapa/hp/s800/
		hp-ux-11/A.05.00/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_29145 PHSS_28228

Equivalent Patches: None

Patch Package Size: 480 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_30140

	5. Run swinstall to install the patch:

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

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

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

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

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

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

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

	
	Patch includes the following Site Specific Patches:
	   SSPUX500_010
	   SSPUX500_038

	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.