Patch Name: PHSS_26363

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

Creation Date: 02/06/06

Post Date:  02/06/13

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

Products:
	OmniBackII A.04.00

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

Automatic Reboot?: No

Status: General Superseded

Critical: No

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

Symptoms:
	PHSS_26363:
	Id = HSLco33370  SR:H555007431
	    Pre-exec script for SSEA reports the following:

	      "[Critical] From: SSEA@<host> ""  Time: <time>
	       [224:509] Cannot stat script "<script name>
	         <parameters>",
	       system reports: "[2] No such file or directory".

	
	Id = HSLco33697  SR:H555007572
	    SSEA Integration backup fails with an error:

	      "[Warning] From: SSEA@<hostname> ""  Time: <time>
	        File system /dev/vx/dsk/<disk-group>/<volume>
	       could not be mounted to /<mountpoint>.
	        ([27] File too large).".

	
	Id = HSLco34238  SR:H555007788
	    SSEA Integration restore fails with an error:

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

	PHSS_25966:
	Id = HSLco31734  SR:H555006894
	    Restore fails with:

	      "[Major] From: SYMA@<hostname> ""  Time: <time>
	       [223:325] Could not activate volume group
	       /dev/sg_sap.

	       [Major] From: SYMA@<hostname> ""  Time: <time>
	       [223:363] Could not prepare mirror disks of object
	       /sg_sap for backup.
	       (Activation of volume group failed.)".

	Id = HSLco30165  SR:H555006563
	    Backup fails with:

	      "[Major] From: SSEA@<host> "" Time: <time>
	       File system <FS> could not be mounted
	       to /var/opt/omni/tmp/<path on host>

	       mount: <FS>: No such file or directory".

	PHSS_24986:
	Id = HSLco27782, SR: H555005757
	    SSEA Integration backup fails with an error:

	      "[Major] From: SSEA@<hostname> ""  Time: <time>
	         File system <path> could not be mounted
	         to <path>. ([16] Device busy).

	Id = HSLco28452, SR: H555006026
	    SSEA Integration backup fails with an error:

	      "[Major] From: SSEA@<hostname> ""  Time: <time>
	         Volume group /dev/<vg-name> could not be
	         activated.

	Id = NSMex04611, SR: H555006245
	    SSEA Integration backup fails with an error:

	      "[Critical] From: SSEA@<hostname> ""  Time:<time>
	         Unexpected close reading message from the agent
	         on the Backup System. (Unknown internal error.)

Defect Description:
	PHSS_26363:
	Id = HSLco33370
	    SSEA does not except parameters in pre-exec script and
	    tries to start the string.

	Resolution:
	    SSEA parameters are now correctly parsed.

	    Part of SSPUX400_028.

	Id = HSLco33697
	    The mount API call does not allow some mount options
	    and combinations of mount options.
	    If the disk groups on the R1 host are owned by an user
	    unknown to the R2 host, then the import of the mapfile
	    from R1 to R2 fails.

	Resolution:
	    From now on CLI mount command is used for all mounting.
	    If mounting is in read only mode then no mount option
	    is used. Mounting is considered successful by checking
	    the status of the CLI command and not the returned
	    value of the 'popen()' function.
	    SSEA now parses a mapfile buffer and searches for
	    "user" and "group" entries. If match is found then both
	    values are set to "root". In this way the import of the
	    mapfile on the R2 host is not problematic in case that
	    the diskgroups on the R1 side are owned by a user who
	    is unknown on the R2 host.

	Id = HSLco34238
	    If, during restore, SSEA fails to unmount the only
	    present mountpoint in the session on the application
	    side, it goes on with syncing and splitting the disks.
	    If the only mountpoint present in the session fails to
	    be unmounted on the application side, then the session
	    should fail immediately.

	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 many mountpoints in
	    the session and not all the mountpoints fail to be
	    unmounted then SSEA skips restore of the disks related
	    to those mountpoints, but proceeds with restore of
	    disks related to the mountpoints that were
	    successfully unmounted.

	PHSS_25966:
	Id = HSLco31734
	    Backup is made in SSEA/split mirror backup environment
	    with the Application host in the cluster. When
	    restoring object on the Backup host (R2), which is not
	    in the cluster the cluster tag (-c y) from the
	    Application host is also restored, so the volume group
	    can not be activated properly.

	Resolution:
	    By default the cluster tag on the Backup host (R2) is
	    disabled with the "vgchange -q n -c n" command. To
	    enable the cluster tag on Backup host, set the new
	    environment variable SMB_CLUS_DEACT=1 in the
	    /opt/omni/.omnirc file.

	Id = HSLco30165
	    During the mapping from logical devices to raw disks
	    the target numbers are incorrectly assigned.

	Resolution:
	    Mapping from logical devices to raw disks
	    is done correctly.

	    Part of SSPUX400_010.

	PHSS_24986:
	Id = HSLco27782
	    Session fails when backup system is left enabled,
	    SSEA_PRESERVE_MOUNTPOINTS is set to 1 in .omnirc
	    file and backup is restarted.

	Resolution:
	    Mountpoint is rechecked becouse it can change.

	Id = HSLco28452
	    If the volume group is located in a cluster on the
	    application side, it is not possible to activate
	    this volume group in "rw" mode on the backup side.

	Resolution:
	    By default volume group on the backup side is activated
	    in read only mode, unless the "Enable the backup system
	    in read/write mode" option is set for the backup.

	Id = NSMex04611
	    Because of the large number of backup volumes agent and
	    backup session manager lost connection to the ssea on
	    the application side in the middle of resolve function.

	Resolution:
	    Buffer concatenation is fixed.

	    Part of SSPUX400_004.

SR:
	H555007572 H555007788 H555007431 H555006894 H555006563
	H555006245 H555006026 H555005757

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

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

cksum(1) Output:
	2444918934 474311 /opt/omni/databases/vendor/ssea/hp/s800/
		hp-ux-1020/A.04.00/packet.Z
	384263882 474585 /opt/omni/databases/vendor/ssea/hp/s800/
		hp-ux-11/A.04.00/packet.Z
	2635439587 223901 /opt/omni/databases/vendor/ssea/sun/sparc/
		solaris-7/A.04.00/packet.Z

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_24986 PHSS_25966

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

Patch Package Size: 1210 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_26363

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

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

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

Special Installation Instructions:
	PHSS_26363:
	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:
	   SSPUX400_004
	   SSPUX400_010
	   SSPUX400_028