Patch Name: PHSS_28742

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

Creation Date: 03/06/23

Post Date: 03/06/24

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

Products:
	OmniBackII A.04.10

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

Automatic Reboot?: No

Status: General Superseded

Critical: No

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

Symptoms:
	PHSS_28742:
	Id = HSLco38904  SR: H555009231
	    OmniBack II A.04.10 does not support XP1024 split
	    mirror box.

	Id = HSLco39583  SR: H555009456
	    SSEA backup session report displays messages:

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

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

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

	Id = HSLco40897  SR: H555010044
	    During multiple SSEA sessions running at the same time
	    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".

	Id = HSLco41311  SR: H555010251
	    Volume group activation fails during Instant Recovery.

	Id = HSLco41923  SR: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)".

	PHSS_28338:
	Id = HSLco38493  SR: H555009140
	    Aborting SSEA Integration backup session after the
	    mirror disks have been split, leaves backup system
	    enabled.

	Id = HSLco39063  SR: H555009270
	    SSEA Integration backup occasionally fails with:

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

	Id = HSLco39896  SR: H555009573
	    Instant Recovery fails reporting an invalid BC pairs
	    status.

	PHSS_27593:
	Id = HSLco36407  SR:H555008644
	    During an OmniBack II XP Integration restore
	    following error message is reported:

	     "[Major] From: SSEA@<hostname> ""  Time: <time>
	      Filesystem /dev/vx/dsk/<disk_group>/<lvol>
	      could not be dismounted from /<mountpoint>
	      (Details unknown.)".

	Id = HSLco36669  SR:H555008685
	    In some cases SSEA takes a long time to resolve
	    all the objects on the backup side.

	Id = HSLco37123  SR:H555008788
	    SSEA backup fails with:

	     "/usr/sbin/vgchange -q n -a y /dev/<vg_name>
	      [Major] From: SSEA@<hostname> ""  Time: <time>
	      Volume group /dev/<vg_name> could not be activated.".

	Id = HSLco37703  SR:H555008886
	    SSEA agent abnormally ends on the application side
	    after Disk Agents are completed successfully.

	Id = HSLco37704  SR:H555008887
	    The connection with the host running SSEA agent is
	    broken.

	PHSS_26883:
	Id = HSLco32243  SR: H555006991
	    OmniBack II XP split-mirror backup fails with:

	      "[Critical] From: SSEA@<hostname> ""  Time: <time>
		Failed to attach to the command device <device>.
		(Bad catalog access for message #10822 in set 12!)"

	Id = HSLco32969  SR: H555007253
	    OmniBack II XP split-mirror backup fails with:

	      "[Major] From: SSEA@<hostname> ""  Time: <time>
	       Failed to split the BC pair of
	       LDEV <ldev#>, SEQ# <seq#>, MU# <mu#>."

	Id = HSLco33105  SR: H555007298
	    SSEA agent dies ungracefully right after the last
	    medium is unloaded at the end of backup.

	Id = HSLco33681  SR: H555007572
	    OmniBack II XP integration sessions fail with:

	      "[Major] From: SSEA@<hostname> ""  Time: <time>
	       Failed to split the <BC or CA> pair of
	       LDEV <ldev#>, SEQ# <seq#>, MU# <mu#>."

	Id = HSLco33697  SR: H555007572
	    OmniBack II XP Integration backup reports:

	      "[Warning] From: SSEA@<hostname> ""  Time: <time>
	       File system <filesystem_path> could not be mounted
	        to <mountpoint>. ([27] File too large)."

	Id = HSLco34841  SR: H555008141
	    Pre- and post-exec scripts are improperly executed under
	    shell or "sh -c" type.

	Id = HSLco35984  SR: H555008573
	    During an OmniBack II XP Integration backup following
	    error message is reported:

	      "[Critical] From: SSEA@<hostname> ""  Time: <time>
	       Failed to attach to the command device <device>.
	       (Raid Manager LIB Error: [2] Can't attach to the
	       command device.)"

	Id = HSLco36041  SR: H555008585
	    A warning:

	      "[Warning] From: SSEA@<hostname> ""  Time: <time>
	       Failed to get a BC pair for LDEV 0, MU# 0
	       in RAID <num>. (Details unknown.)"

	    is reported during an OmniBack II XP Integration
	    backup.

	Id = JAGae22283  SR: 8606257980
	    OmniBack II 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."

Defect Description:
	PHSS_28742:
	Id = HSLco38904
	    OmniBack II A.04.10 does not support XP1024 split
	    mirror box.

	Resolution:
	    OmniBack II A.04.10 supports XP1024 split mirror box.

	Id = HSLco39583
	    pairvolstat () API call fails for some disks.

	Resolution:
	    Three parameters (linenumber, detailerrno and
	    sourcename)of pCmd data structure which holds
	    information used forcalling the pairvolstat() API are
	    re-initialized beforea new pairvolstat() call. Call of
	    ErrClearError is addedin SarQuery function.

	    Part of SSPUX410_063.

	Id = HSLco40897
	    In the situation when multiple SSEA backups are running,
	    and the R2 host is being prepared by two or more
	    sessions at the same time, the mount system command
	    might fail because the /etc/mnttab is refreshed by one
	    of the other SSEA sessions at rightthat m-oment.

	Resolution:
	    A retry/sleep is introduced for the problematic mount
	    system command.

	Id = HSLco41311
	    When the OmniBack II mounts the data from the primary
	    server to the backup server in order to move data to
	    tape, it turns off the cluster bit for the volume
	    group. The problem appears during reactivation of the
	    volume groups after the Instant Recovery disk
	    resynchronization is completed. Data is resynchronized
	    onto the original volume group, but the cluster bit is
	    still turned off. As a result, volume group activation
	    fails.

	Resolution:
	    If SSEA_IR_VGCHANGE_A in .omnirc file is set to
	    "vgchange -a e", "vgchange -c y <volume group name>" is
	    executed before "vgchange -a e <volume group name>" in
	    order to turn on the cluster bit of the volume group
	    after instant recovery.

	Id = HSLco41923  SR: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.

	    Part of SSPUX410_073.

	PHSS_28338:
	Id = HSLco38493
	    Clean-up procedure is not executed after backup session
	    is aborted. Volume groups on backup host are left
	    activated with the filesystems mounted.

	Resolution:
	    Proper clean-up procedure (deactivation of volume
	    groups, umounting the filesystems and re-synching the
	    mirror) is executed after backup session is aborted.

	    Part of SSPUX410_055.

	Id = HSLco39063
	    Backup session fails because of incorrect information
	    sent to pairvolstat() API.

	Resolution:
	    The data structure carrying the information to be
	    provided to pairvolstat() API is re-initialized before
	    executing new pairvolstat() call.

	Id = HSLco39896
	    If only one BC pair target disk is configured for
	    Instant Recovery, then the session fails due to
	    incorrect checking for more target disks.

	Resolution:
	    Status checking for target disks is improved in a
	    manner that it correctly recognizes what disks are
	    going to be used for Instant Recovery.

	PHSS_27593:
	Id = HSLco36407
	    If during the restore SSEA fails to unmount the
	    only  mountpoint present in the session on the
	    application side, agent proceeds with synching
	    and splitting the disks although it should abort
	    the session.

	Resolution:
	    If the only mountpoint present in the session fails
	    to be unmounted on the application side, then the
	    session fails immediately.
	    If there are multiple mountpoints in the session,
	    and some of the mountpoints fail to be unmounted
	    then SSEA skips the restore of the disks related
	    to those mountpoints, but proceeds the restore of
	    disks related to the mountpoints that were
	    successfully unmounted.

	Id = HSLco36669
	    Resolving of objects from Business Copy XP on backup
	    host proceeds very slowly if some (out of backup)
	    objects are in PAIR state:
	    -CA PAIR are in PSUS/SUSU: resolving takes less
	    then <x> minutes,
	    -CA PAIR are in PAIR state: resolving takes more
	    then <6*x> minutes.
	    The resolving algorithm has a very bad performance
	    in this case.

	Resolution:
	    The resolving algorithm is improved.

	    Part of SSPUX410_041.

	Id = HSLco37123
	    If the application side is configured in a MC/SG
	    cluster then the volume groups on the backup side
	    can not be activated in the read/write mode with
	    "vgchange -q n -a y" command.

	Resolution:
	    The volume group on the backup side is marked as
	    "not clustered" with the "vgchange -q n -c n" command
	    before the activation in the read/write mode happens.
	    To change this behavior set the SMB_CLUS_DEACT=1
	    environment variable in the .omnirc file on the R2 host.

	    Part of SSPUX410_044.

	Id = HSLco37703
	    The allocated buffer size is too small.

	Resolution:
	    The allocated buffer size is increased.

	Id = HSLco37704
	    In environments where the firewall between Cell Server
	    and client(s) with firewall idle timeout of <x>
	    minutes is present, it can happen that an agent is in
	    idle state for the amount of time longer than mentioned
	    timeout. In such cases, firewall breaks the connection
	    between Cell Server and the client(s).

	Resolution:
	    New environment variable OB2IPCKEEPALIVE is introduced.
	    Setting its value to any of YES, TRUE, ON or 1 in
	    /opt/omni/.omnirc file on Cell Server causes sending a
	    dummy package from time to time in order to keep the
	    connection open.

	    Part of SSPUX410_046.

	PHSS_26883:
	Id = HSLco32243
	    SSEA agent tries to attach to the first command device
	    it finds. In cases when first command device is busy,
	    SSEA fails to attach.

	Resolution:
	    A list of command devices is created and if one of them
	    is busy, SSEA agent tries to attach to the next one.

	Id = HSLco32969
	    SSEA agent collects physical volume names from
	    "vgdisplay" output. In environments where physical
	    volumes are configured their names are collected as
	    well although they are not needed for resolving
	    process. This causes backup to fail.

	Resolution:
	    SSEA agent skips parsing of "vgdisplay" command as
	    soon as "PVG name" token is encountered.

	    Part of SSPUX410_010.

	Id = HSLco33105
	    SSEA agent dies when updating XP database because of
	    buffering problem.

	Resolution:
	    Buffer holding logical devices information is extended.

	    Part of SSPUX410_011.

	Id = HSLco33681
	    A "Major" message is displayed instead of "Warning" is
	    environments with LVM mirroring on application side.

	Resolution:
	    Message level is lowered to the level documented in
	    XP Integration Guide.

	Id = HSLco33697
	    Some combinations of mount API options and ownerships
	    of disk groups cause failures when import mapfile from
	    Application to Backup host.

	Resolution:
	    Command line mount is used instead of mount API.

	Id = HSLco34841
	    Scripts are executed with ".%s" which is "sh" instead of
	    script name.

	Resolution:
	    The dot is removed from function that executes the
	    scripts.

	Id = HSLco35984
	    Attaching fails in environments where alternate links
	    are used because of incorrect instance number counting.

	Resolution:
	    Instance numbers are properly counted if alternate links
	    are used.

	Id = HSLco36041
	    SSEA agent improperly handles "LDEV 0" (unknown logical
	    device).

	Resolution:
	    Logical device resolution is improved by adding
	    additional checking in cases where "LDEV 0" is
	    encountered.

	    Part of SSPUX410_032.

	Id = JAGae22283
	    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!

SR:
	H555010251 H555010044 H555010436 H555009231 H555009456
	H555009270 H555009140 H555009573 H555008685 H555008644
	H555008886 H555008788 H555008887 H555006991 H555008585
	H555007298 H555007748 8606257980 H555008141 H555007253
	H555007572 H555007564 H555008573

Patch Files:
	/opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.04.10/
		packet.Z

what(1) Output:
	/opt/omni/databases/vendor/ssea/sun/sparc/solaris-7/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.04.10/
		packet.Z:
		None

cksum(1) Output:
	1759720013 251779 /opt/omni/databases/vendor/ssea/sun/sparc/
		solaris-7/A.04.10/packet.Z
	1300315943 523865 /opt/omni/databases/vendor/ssea/hp/s800/
		hp-ux-1020/A.04.10/packet.Z
	960820909 539177 /opt/omni/databases/vendor/ssea/hp/s800/
		hp-ux-11/A.04.10/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

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

	PHSS_28731:
	Cell Server (CS) packet patch,
	Release Date: Available
	Id = HSLco37704  SR:H555008887
	PHSS_28731 is required for this defect fix.

Supersedes:
	PHSS_26883 PHSS_27593 PHSS_28338

Equivalent Patches:
	PHSS_28743:
	s700: 11.00 11.11 11.20
	s800: 11.00 11.11 11.20

Patch Package Size: 1300 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_28742

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

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

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

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

	The OB2 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 OmniBackII Installation guide.


	Patch includes the following Site Specific Patches:
	   SSPUX410_010
	   SSPUX410_011
	   SSPUX410_032
	   SSPUX410_041
	   SSPUX410_044
	   SSPUX410_046
	   SSPUX410_055
	   SSPUX410_063
	   SSPUX410_073