Patch Name: PHSS_30564

Patch Description: s700_800 11.X OV DP5.10 patch - SSEA packet

Creation Date: 04/05/10

Post Date: 04/05/12

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

Products:
	DATA-PROTECTOR A.05.10

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

Automatic Reboot?: No

Status: General Release

Critical:
	No (superseded patches were critical)
	PHSS_29411: ABORT

Category Tags:
	defect_repair enhancement general_release critical
	halts_system manual_dependencies

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

Symptoms:
	PHSS_30564:
	Change Request: H555012230
	  Business Copy (BC) backups fail with the following
	  error message:

	   "|Critical| From: SSEA@<hostname> "<object>" Time:
	    <time> |225:1012| Failed to get pairs for all LDEVs."

	Change Request: H555012715
	  Split pre-exec script fails with the exit code 1, but
	  the backup does not fail.

	PHSS_30326:
	Change Request: 8606308890
	  In StorageWorks XP Agent (SSEA) environments with
	  multiple host bus adapters only one is used,
	  so the backup performance is poor.

	Change Request: H555011701
	  StorageWorks XP integration backup fails with
	  the following error:

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

	Change Request: H555011747
	  The following error is reported by "ob2smbsplit"
	  during a backup:

	   "|Major| From: OB2BAR_SMB_Split@<hostname> Time: <time>
	    Preparing of backup host failed (error=-14)

	    |Major| From: OB2BAR_SMB_Split@<hostname> Time: <time>
	    Preparing of backup host failed (error=-14)."

	Change Request: H555011950
	  The following error is reported during a backup:

	   "|Major| From: SSEA@<hostname> "<object>" Time: <time>
	    Mapping from character device file of disk to LDEV
	    failed forcXtYdZ.(|16| Device busy)."

	
	Change Request: H555012038
	  The following error is reported during a backup:

	   "|Critical| From: SSEA@<hostname> "<object>"
	    Time: <time> Cannot find command device."

	PHSS_29872:
	Change Request: H555009003
	  SSEA backup session fails with:

	    "|Critical| From: BSM@<hostname> "<barlist>"
	     Time: <time>
	     None of the Disk Agents completed successfully.
	     Session has failed."

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

	    "|Major| From: SSEA@<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: H555010751
	  Backup fails with the following error reported:

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

	Change Request: H555011015
	  SSEA integration backup fails with:

	   "|Major| From: SSEA@<host name> ""  Time: <time>
	   |225:109| Mapping from character device file
	   of disk to LDEV failed for .
	   (|2| No such file or directory)"

	Change Request: H555011053
	  The backup session intermittently fails with
	  the following error reported:

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

	  More detailed error message is reported in SSEA
	  debug file:

	   "| -2| |SseXPairSplit| pairsplit failed!
	   [EL_CMDIOE] Control command I/O error, or rejected.
	   ...
	   ...
	   |Major| From: SSEA@<hostname> ""  Time:<time>
	    Failed to split the BC pair of LDEV <LDEV NUMBER>,
	    SEQ# <SEQ NUMBER>, MU# <MU NUMBER>."

	Change Request: H555011149
	  Volume group on backup system skips mount and dismount
	  procedure and backup fails.

	Change Request: H555011275
	  Wrong volume groups are deactivated during the backup.

	Change Request: 8606257980
	  Data Protector XP Integration backup using split-mirror
	  fails with:

	    "|Major| From: SSEA@<hostname> "" Time: <time>
	    File system for / object not mounted or local
	    disk is in backup."

	Change Request: H555011457
	  During SSEA backup the following error is shown in
	  the session report:

	    "[Normal] From: SSEA@<R1_hostname> "" Time:<time>

	    The following BC pairs will be used in current
	    session:  SEQ# LDEV  Port TID LUN MU#  Status SEQ#
	    LDEV---------------------------------------------
	    -------<more then 10 BC pairs reported>----------
	    -------------------------------------------------

	    [Normal] From: SSEA@<R2_hostname> ""  Time:<time>
	    ABORTED SSEA-Backup Agent on <R2_hostname>.

	Change Request: H555011461
	  SSEA backup fails with:

	    "[Critical] From: SSEA@<host> ""  Time:<time>
	     Failed to find T-VOL/R-Vol of LDEVs."

	Change Request: H555011475
	  Backup sessions using large number of split-mirror
	  disk resources (more than 450) fail with following
	  error message:

	    "[Critical] From: SSEA@<hostname> "" Time:<time>
	     Cannot lock mirror disk(s).
	     [Critical] From: SSEA@<hostname> "" Time:<time>
	     Failed to find T-VOL/R-Vol of LDEVs.".

	PHSS_29411:
	Change Request: H555009899
	  Data Protector SSEA backup fails with error:

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

	Change Request: H555010306
	  Using the SSEA Zero Downtime Backup agent, if the
	  option "After the backup, keep the version on mirror
	  disk" is not selected and backup is aborted after the
	  split, mirror is not resynchronized.

	Change Request: H555010436
	  SSEA integration backup fails with:

	    "|Major| From: OB2BAR@<backup_hostname>  Time:<time>
	        Resolve of the disks fails.

	    "|Major| From: OB2BAR@<backup_hostname> Time:<time>
	        Resolving to disk level failed (error=-14)".

	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: H555010480
	   The following error is reported at the end of backup:

	   "61:3003 Lost connection to Split Mirror Agent
	   COMPLETED Media Agent. |Major| From: BSM@<hostname>
	   <object>" Time: <time> |61:3003| Lost connection to
	   Split Mirror Agent named <object> on host <hostname>.
	   Ipc subsystem reports: "IPC Read ErrorSystem error:
	   |238| Connection timed out."

	Change Request: H555010508
	  Direct backup solution is not supported.

	Change Request: H555010528
	  After the LDEVs are resolved and the BC pairs are
	  correctly identified, SSEA checks for LDEVs info
	  in the xpdb in order to find out if the current LDEVs
	  have already been used in the previous SSEA backup
	  sessions. The SSEA agent on the R1 side ends abnormally
	  when browsing LDEVs info in the xpdb. After several
	  reallocations of the LDEVs list, the new realloc call
	  fails. Backup fails with:

	   "|Major| From: BSM@<hostname> <object>  Time: <time>
	   |61:3003| Lost connection to Split Mirror Agent named
	   <object> on host <hostname>. Ipc subsystem reports:
	   "IPC Read ErrorSystem error: |10054| Connection reset
	   by peer."

	   "|Critical| From: SSEA@<hostname> <object>  Time:
	   <time> IPC failure reading message from the agent
	   on the application system. (IPC Read ErrorSystem
	   error: |10054| Connection reset by peer.)"

	Change Request: H555010664
	  Backup is failing with the following error:

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

Defect Description:
	PHSS_30564:
	Change Request: H555012230
	  The StorageWorks XP Agent (SSEA) calls to the RAID
	  Manager Library API are using LUNs that are greater
	  than the 0-255 range (XP1024 box). With the RAID
	  Manager Library version 1.07, the truncating feature
	  has been removed. SSEA was not able to resolve the
	  disks.

	  Resolution:
	  Execution of the "getdkclimit()" Raid Manger Library
	  API function will ensure that calls to the XP box only
	  use the LUNs from the 0-255 range.

	  Part of SSPUX510_026.

	Change Request: H555012715
	  Return code 1 from a split pre-exec script on a BC split
	  mirror backup is being ignored.

	  Resolution:
	  Correction in error handling. The backup fails when the
	  stop/quiesce script returns an error code greater than
	  zero.

	PHSS_30326:
	Change Request: 8606308890
	  Data Protector 5.10 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 "SSEA_BACKUP_VG_EXIST"
	  is introduced to disable 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;).

	Change Request: H555011701
	  Table of XP ports is not appropriate for the 01.07.00
	  and higher versions of "rmlib" api.

	  Resolution:
	  Special table of XP ports is defined for the 01.07.00
	  and higher versions of "rmlib" api.

	Change Request: H555011747
	  SSEA cannot resolve softlinks of the mountpoints.
	  The softlink checking exists only for the backup object.

	  Resolution:
	  The softlink checking is added for the mountpoints too.

	Change Request: H555011950
	  For the "multipath" configuration of the veritas disks,
	  SSEA cannot switch to the secondary (alternate) paths
	  of the disks.

	  Resolution:
	  Finding and storing alternate paths of all the disks
	  involved in the backup and making mechanism for switching
	  to the alternate path when primary disk is disabled.

	  Part of SSPUX510_021.

	Change Request: H555012038
	  If a hostname used in a XP backup specification
	  is a substring of a hostname that is already present
	  in the command devices list, then a new entry for
	  the new hostname will not be added in the command devices
	  list.

	Resolution:
	  Hostnames comparing functions correctly.

	PHSS_29872:
	Change Request: H555009003
	  The data structure that holds information used for
	  calling the pairvolstat() API is not re-initialized
	  before a new pairvolstat() call.

	  Resolution:
	  The data structure that holds information used for
	  calling the pairvolstat() API is re-initialized
	  before a new pairvolstat() call.

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

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

	Change Request: H555010751
	  Buffer which holds information from the map file for
	  vgimport command is not big enough.

	  Resolution:
	  Buffer which holds information about VG mapfile is
	  increased.

	  Part of SSPUX510_003.

	Change Request: H555011015
	  Veritas filesystem dmp nodes can be in different
	  format than physical discs (cXtYdZ). Because of
	  this disc resolving fails.

	  Resolution:
	  Mapping from different dmp node names to physical
	  disk names (cXtYdZ) is done before resolving.

	Change Request: H555011053
	  pairsplit() API call occasionally fails with no
	  obvious reason.

	  Resolution:
	  Call of pairsplit() is put in a loop that will repeat
	  the call if pairsplit() fails. If pairsplit() fails 10
	  times, error message will be displayed.

	Change Request: H555011149
	  During backup system preparation MountFs and DismountFs
	  functions are only supported on Solaris 7 and 8.

	  Resolution:
	  Solaris 9 mount and dismount functionality is added.

	Change Request: H555011275
	  When backup and application host are in cluster and
	  integration backup is performed, volume groups with
	  same name on application and backup side are exported
	  during the cleanup of the volume group by
	  name (autoconfiguration).

	  Resolution:
	  New .omnirc variable ZDB_CLUSTER_CONFIG is added.
	  When set to 1 on the backup host, name of volume
	  group on the backup side will not be the same as on
	  the application side (during the integration backup)
	  and before importing of the vg on the backup side
	  vgchgid command is called to change the volume group
	  header information on all mirrored disks in the
	  volume group.

	Change Request: 8606257980
	  SSEA agent cannot handle "/" (root) mountpoint when
	  performing a split-mirror backup.

	  Resolution:
	  Mountpoint "/" (root) can be used in SSEA split-mirror
	  backup if following is satisfied:

	  1. Root mountpoint is located on an XP disk.
	  2. SSEA_PRESERVE_MOUNTPOINT environment variable is not
	    set to 1 on Backup host.
	  3. SSEA_BACKUP_ROOT_MOUNTPOINT environment variable is
	    set to 1 on Application side.

	  Note: Such backup cannot be used for Instant Recovery!

	Change Request: H555011457
	  If the volume groups seen from the application host
	  include more than 10 Logical Volume Manager (LVM)
	  mirror pairs, then the Business Copy (BC) pair
	  report dumped to the session report is not displayed
	  by chunks, causing the buffer to overflow.

	  Resolution:
	  The counter for the displayed BC pairs takes into account
	  also LVM mirror primary disks that do not need to be
	  displayed in the BC pairs report. This way, the BC pairs
	  report is dumped to the session report by chunks.

	  Part of SSPUX510_018.

	Change Request: H555011461
	  SSEA searches for the file systems by scanning
	  "/etc/mnttab" file. Scan fails if one of the rows
	  in /etc/mnttab is unreadable.

	  Resolution:
	  unreadable parts in /etc/mntab are skipped.

	  Part of SSPUX510_019.

	Change Request: H555011475
	  Locking buffer is part of the shared memory and has a
	  maximum length of 100KB. Large number of lock requests
	  from SSEA exceed this maximum length causing locking
	  to crash and session consequently fails.

	  Resolution:
	  Workaround resolution is to disable the SSEA resource
	  locking to prevent locking buffer overflow. By setting
	  .omnirc variable OB2FORCENOSSEALOCK=1 locking of
	  split-mirror disks is disabled for the client. Multiple
	  sessions which use the same split-mirror disk resources
	  should not be run simultaneously.

	  Part of SSPUX510_020.

	PHSS_29411:
	Change Request: H555009899
	  The disk group information is not parsed correctly.

	  Resolution:
	  The disk group information is parsed correctly.

	Change Request: H555010306
	  If the option "After the backup, keep the version on
	  mirror disk" is not selected, and no more than one
	  first level mirror is set by the MU Number(s) option,
	  then the mirrors should be resynchronized after the
	  backup. This should also be the case if the split has
	  been made successfully but the backup is aborted.

	  Resolution:
	  If the option "After the backup, keep the version on
	  mirror disk" is not selected, and no more than one
	  first level mirror is set by the MU Number(s) option,
	  then the mirrors are resynchronized even if the split
	  has been made successfully but the backup is aborted.

	Change Request: H555010436
	  HP-UX LVM Mirroring configuration looks for BC PVOLs
	  on all involved XP boxes instead of only on the XP
	  box(es) where the BC is configured.

	  Resolution:
	  PVOLs are sought only on the XP box(es) where BC is
	  configured.

	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 the "/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 synching the "mnttab" file.

	Change Request: H555010480
	  SSEA ignores the "OB2IPCKEEPALIVE"
	  environment variable.

	  Resolution:
	  Checking for the "OB2IPCKEEPALIVE" environment
	  variable is implemented for a Solaris platform.

	Change Request: H555010508
	  Direct backup solution is not supported.

	  Resolution:
	  Direct backup is supported. For supported
	  configurations, refer to the Direct backup support
	  matrix available at:

	  http://www.openview.hp.com/products/
	  storage_data_protector/device_matrices/
	  Direct_Backup_Support_Matrix_DP51.pdf.

	  For more information, refer to the HP OpenView Storage
	  Data Protector Administration Guide, chapters 2 and 5,
	  HP OpenView Storage Data Protector Concepts Guide,
	  chapter 9, and online Help. The updated version of
	  these guides are available with DOC patches PHSS_29143
	  and DPSOL_00027 or subsequent DOC patches.

	Change Request: H555010528
	  Invalid access to memory location during the creation
	  of the session list for removing from the IDB.

	  Resolution:
	  Access to memory location during the creation of the
	  session list for removing from the IDB is corrected.

	Change Request: H555010664
	  Process is terminated with an access violation error
	  because of memory overflow caused by a recursion.

	  Resolution:
	  Backup completes successfully.

Enhancement:
	No (superseded patches contained enhancements)
	PHSS_29411:
		General release patch PHSS_29411
		introduces Data Protector A.05.10 Direct
		backup solution.

		For more information about the above
		functionality, install the Documentation
		Patch PHSS_29143 on the Cell Manager system
		and read the respective changes in the
		Release Notes, chapters 2 and 6.

SR:
	H555012715 H555012230 H555012038 8606308890 H555011747
	H555011950 H555011701 H555011475 H555011149 H555011015
	H555010044 H555011461 H555011275 8606257980 H555010751
	H555011457 H555011053 H555009003 H555009899 H555010508
	H555010436 H555010461 H555010528 H555010480 H555010306
	H555010664

Patch Files:
	
	DATA-PROTECTOR.OMNI-SSEA-P,fr=A.05.10,
		fa=HP-UX_B.11.00_32/64,v=HP:
	/opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.05.10/
		packet.Z
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.05.10/
		packet.Z

what(1) Output:
	
	DATA-PROTECTOR.OMNI-SSEA-P,fr=A.05.10,
		fa=HP-UX_B.11.00_32/64,v=HP:
	/opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.05.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.05.10/
		packet.Z:
		None

cksum(1) Output:
	
	DATA-PROTECTOR.OMNI-SSEA-P,fr=A.05.10,
		fa=HP-UX_B.11.00_32/64,v=HP:
	1545744434 505767 /opt/omni/databases/vendor/ssea/hp/s800/
		hp-ux-11/A.05.10/packet.Z
	1864758006 503343 /opt/omni/databases/vendor/ssea/sun/sparc/
		solaris-7/A.05.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_30336:
	CORE packet patch,
	release date: Available
	Change Request: H555010508
	PHSS_30336 is required for this enhancement.

	PHSS_30327:
	Cell Console (CC) packet patch,
	release date: Available
	Change Request: H555010508
	PHSS_30327 is required for this enhancement.

	PHSS_30328:
	Cell Server (CS) packet patch,
	release date: Available
	Change Request: H555010508
	PHSS_30328 is required for this enhancement.

	PHSS_30134:
	Documentation packet patch,
	release date: Available
	Change Request: H555010508
	PHSS_30134 is required for this enhancement.

	PHSS_29863:
	Oracle8 packet patch,
	release date: Available
	Change Request: H555010508
	PHSS_29863 is required for this enhancement.

	PHSS_29869:
	Media Agent (MA) packet patch,
	release date: Available
	Change Request: H555010508
	PHSS_29869 is required for this enhancement.

Supersedes:
	PHSS_30326 PHSS_29872 PHSS_29411

Equivalent Patches: None

Patch Package Size: 990 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_30564

	5. Run swinstall to install the patch:

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

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

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

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

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

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

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

	For distribution of the SSEA agent, refer to
	the Data Protector Installation guide.

	Patch includes the following Site Specific Patches:
	   SSPUX510_003
	   SSPUX510_018
	   SSPUX510_019
	   SSPUX510_020
	   SSPUX510_021
	   SSPUX510_026

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