Patch Name: PHSS_30830

Patch Description: s700_800 11.X OV OB4.10 patch - DA packet

Creation Date: 04/07/13

Post Date: 04/07/16

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

Products:
	OmniBackII A.04.10

Filesets:
	OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP
	OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP

Automatic Reboot?: No

Status: General Release

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

Category Tags:
	defect_repair general_release critical halts_system
	manual_dependencies

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

Symptoms:
	PHSS_30830:
	Change Request: H555012790
	  Total Kbytes file statistics numbers displayed during a
	  backup and restore do not match.

	Change Request: H555012804
	  An error is reported when attempting to perform
	  a restore.

	Change Request: H555013108
	  Volume Backup Disk Agent (VBDA) may end abnormally.

	Change Request: H555013194
	  User ID and group ID of a soft link are not restored
	  correctly.

	PHSS_30330:
	Change Request: H555011415
	  Backup and restore of files ends without warning,
	  but 32-bit file permissions are changed.

	Change Request: H555011790
	  Restore of a file spanning two tapes can fail with an
	  error message about an incorrect sequence number
	  (Missing of data block detected, expecting block x!).

	Change Request: H555011846
	  Restoring a socket with a long path leads to incorrectly
	  restored socket and error messages are reported by the
	  Volume Restore Disk Agent (VRDA):

	   "Cannot set owner: |2| No such file or directory...
	    Cannot set mode...
	    Cannot preserve time attributes: (|2| No such
	    file or directory)."

	Change Request: H555011933
	  Backup of filesystem with lock option enabled reports
	  the following warning even if filesystem is not read
	  only:

	   "Filesystem is mounted read-only => locking disabled."

	Change Request: H555012065
	  When restoring an object with some excluded directories,
	  directories which are selected and should be restored
	  are skipped.

	PHSS_29874:
	Change Request: H555010191
	  During backup minor error is reported:

	   "|Minor| From: VBDA@<host> ""  Time:<time>
	   |81:84|   /<path>
	   Cannot read ACLs: (|2| No such file or directory)."

	Change Request: H555010448
	  When running vbda on Solaris from console with post
	  exec script, vbda sometimes ends abnormally.

	Change Request: H555010763
	  During the JFS 3.3 backup error is reported:

	   "Cannot get VxFS filesystem options
	    (|25| Not a typewriter)=>
	    VxFS extent attributes not backed up."

	Change Request: H555011348
	  During backup error is reported:

	   "Cannot preserve time attributes:
	    (|30| Read-only file system)."

	PHSS_28336:
	Change Request: H555007992
	  Filesystem backup fails with an error:

	  "|Major| From: BSM@<computer> "<object>"  Time: <time>
	   |61:3003| Lost connection to VBDA named <object>
	    on host <host>.
	    Ipc subsystem reports: "IPC Read Error
	    System error: |232| Connection reset by peer"

	Change Request: H555008823
	  ACL checking error reported for infinite symbolic links
	  and symbolic links to NFS mountpoints.

	Change Request: H555009032
	  Option "omit deleted files" replaces existing files on
	  the disk with files from the backup.

	Change Request: H555009141
	  Backup of JFS 3.3 File System reports error:

	    "Cannot read ACLs: (|13| Permission denied)."

	Change Request: H555009249
	  Raw disk restore fails on Tru 64 systems.

	Change Request: H555009425
	  Files are corrupted after restore.

	Change Request: H555009435
	  Restore session on HP-UX with VXFS 3 reports error:

	    "Cannot restore ACLs"

	  for every file restored.

	Change Request: H555009718
	   During the JFS 3.3 backup the following error is
	   reported:

	   "Cannot get VxFS filesystem options (|25| Not a
	    typewriter) => VxFS extent attributes not backed up."

	Change Request: B555014163
	  On Linux Operating Systems with kernel versions
	  2.4.14 - 2.4.18 raw disk backup reports:

	   "cannot compute disk capacity (|22| invalid argument)".

	PHSS_26344:
	Change Request: H555006667
	  Backup of a JFS 3.3 filesystem reports error:

	    "Cannot read ACLs: ([21] Is a directory)".

Defect Description:
	PHSS_30830:
	Change Request: H555012790
	  Total Kbytes calculation in Volume Restore Disk Agent
	  (VRDA) is slightly different than in Volume Backup Disk
	  Agent (VBDA).

	  Resolution:
	  Total Kbytes calculation is corrected.

	Change Request: H555012804
	  "No more media for restore on device" message is
	  displayed and restore session stops responding. This
	  message may appear when restoring hardlinks (pointing to
	  the same file) that are present on more than one tape.

	  Resolution:
	  Problem fixed in Restore Session Manager (RSM). For this
	  fix to work, set the "RepositionWithinRestoredObject"
	  variable in the global options file to 0.

	Change Request: H555013108
	  Two "SIGCHLD" signals are received upon post-exec script
	  exit.

	  Resolution:
	  The child procedure that is processing "SIGCHILD"
	  signals is improved.

	Change Request: H555013194
	  Ownership of a soft link is not treated correctly.

	  Resolution:
	  Ownership of a soft link is treated correctly.

	PHSS_30330:
	Change Request: H555011415
	  32-bit file permissions for Linux are excluded.

	  Resolution:
	  32-bit file permissions for Linux are included.

	Change Request: H555011790
	  If a block on the first tape is written but drive reports
	  a failure, the block is written again on the second tape
	  during a backup. When restoring, both blocks are read
	  and a sequence number checking reports error.

	  Resolution:
	  A sequence number checking is changed and will only
	  report a warning if a duplicated block is encountered
	  and continue with restore.

	Change Request: H555011846
	  Socket path is truncated due to a system limitation
	  of storing socket path only up to 93 charactors.

	  Resolution:
	  Socket can be restored in a socket path only with
	  a socket name.

	Change Request: H555011933
	  Backup reads the "mnttab" file for filesystem options
	  and mistakes the "ioerror" for the "ro" (read only)
	  option.

	  Resolution:
	  Backup reads the "mnttab" file and treats "ro" option as
	  a read only option.

	  Part of SSPUX410_084.

	Change Request: H555012065
	  Comparing directories to be restored with excluded
	  directories can lead to wrong results if directory
	  names are similar but of different length.

	  Resolution:
	  Comparing of similar directory names is reimplemented.

	  Part of SSPUX410_085.

	PHSS_29874:
	Change Request: H555010191
	  When performing backup of non existing soft links
	  in some special cases minor error is reported.

	  Resolution:
	  Minor error is no longer reported for non existing
	  soft links.

	Change Request: H555010448
	  Accessing argv which points to null causes vbda on
	  Solaris to end abnormally.

	  Resolution:
	  Pointer is checked before accessing argv.

	Change Request: H555010763
	  Wrong parameter is passed to ioctl.

	  Part of SSPUX410_079.

	  Resolution:
	  Correct parameter is passed.

	Change Request: H555011348
	  VBDA tries to reset time attributes that do not
	  need to be reset.

	  Resolution:
	  VBDA checking changed.

	PHSS_28336:
	Change Request: H555007992
	  Last message from Disk Agent is sometimes lost. This
	  causes Disk Agent's status reported as "Failed".

	  Resolution:
	  New OmniBack II environment variable:
	    OB2VBDASLEEPBEFORECLOSE
	  is introduced.
	  Its default value is 0. Setting it to a positive
	  number, in /<OMNIBACK_HOME>/.omnirc file specifies
	  number of seconds to pass before Disk Agent completes
	  after sending the last block of data.
	  Sleep time insignificantly influences backup
	  performance.

	Change Request: H555008823
	  These specific errors should be skipped, but they are
	  not.

	  Resolution:
	  Checking for infinite symbolic link and links to NFS
	  added.

	Change Request: H555009032
	  When option "omit deleted files" is enabled for restore
	  it ignores options "no overwrite" and "keep most
	  recent" although it should not.

	  Resolution:
	  "omit deleted files" option is properly interpreted
	  when used together with "no overwrite" and/or "keep
	  most recent" options.

	Change Request: H555009141
	  In case that JFS 3.3 File System has a softlink which
	  points to different File System, read of ACL's can fail.

	  Resolution:
	  Disk Agent ignores such error in case of softlinks.

	Change Request: H555009249
	  Raw disk restore does not work correctly on Tru 64
	  systems if disks are grouped into logical units.

	  Resolution:
	  New OmniBack II environment variable OB2NODIOCWLABEL is
	  introduced. This should be added to the file
	  /<OMNIBACK_HOME>/.omnirc. In case that this variable
	  is set to "1", OmniBack II does not perform disk
	  related ioctl() commands.

	  NOTE: In case that OmniBack II variable is set,
	  and restore is started on the normal raw disk, restore
	  reports that disk is "Read-only file system" and aborts.

	
	Change Request: H555009425
	  In case that OB2ALIGN variable is set backup is
	  corrupt and restore is not possible.

	  Resolution:
	  Backup disk agent is fixed in order to work correctly
	  with OB2ALIGN option.

	Change Request: H555009435
	  If files are backed up on JFS filesystem and restored
	  to VXFS filesystem, minor error is reported for every
	  file restored.

	  Resolution:
	  Message "Destination file system does not support ACLs!"
	  is added and is reported only once, subsequent error
	  messages are suppressed.

	Change Request: H555009718
	   Wrong parameter is passed to "ioctl".

	  Resolution:
	   Parameter passed to "ioctl" is corrected.

	Change Request: B555014163
	  On kernel versions 2.4.14 - 2.4.18, function lseek()
	  fails with errno=EINVAL when seeking past the end of
	  a raw disk section. This is a non-POSIX behaviour and
	  is not expected by Disk Agent PosixCapacity() function.
	  PosixCapacity() often seeks past the end of raw disk
	  section and attempts to read there. Only when the read
	  fails, PosixCapacity() determines that the disk size
	  is smaller than the current offset.

	  Resolution:
	  When lseek() fails with EINVAL, PosixCapacity()
	  immediately assumes that offset is to big.

	PHSS_26344:
	Change Request: H555006667
	  In case that JFS 3.3 filesystem contains LOFS, Disk
	  Agent is not able to get ACL's for such files because
	  they do not exist.

	  Resolution:
	  Disk Agent ignores error in case of LOFS.

Enhancement:
	No

SR:
	H555013194 H555012790 H555013108 H555012804 H555011933
	H555011790 H555011846 H555011415 H555012065 H555011348
	H555010763 H555010448 H555010191 H555009718 B555014163
	H555007992 H555009032 H555009141 H555009425 H555008823
	H555009435 H555009249 H555006667

Patch Files:
	
	OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/opt/omni/databases/vendor/da/hp/s800/hp-ux-11/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/hp/s800/hp-ux-1020/A.04.10/
		packet.Z

	OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/opt/omni/databases/vendor/da/dec/alpha/osf1-4/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/gpl/i386/linux-60/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/ibm/rs6000/aix-42/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/sco/i386/sco_sv/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/sco/i386/unixware/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/sgi/mips/irix-62/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/siemens/r400/sinix/A.04.10/
		packet.Z
	/opt/omni/databases/vendor/da/sun/sparc/solaris-26/A.04.10/
		packet.Z

what(1) Output:
	
	OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/opt/omni/databases/vendor/da/hp/s800/hp-ux-11/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/hp/s800/hp-ux-1020/A.04.10/
		packet.Z:
		None

	OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	/opt/omni/databases/vendor/da/dec/alpha/osf1-4/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/gpl/i386/linux-60/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/ibm/rs6000/aix-42/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/sco/i386/sco_sv/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/sco/i386/unixware/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/sgi/mips/irix-62/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/siemens/r400/sinix/A.04.10/
		packet.Z:
		None
	/opt/omni/databases/vendor/da/sun/sparc/solaris-26/A.04.10/
		packet.Z:
		None

cksum(1) Output:
	
	OMNIBACK-II.OMNI-HPUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	892046950 1239371 /opt/omni/databases/vendor/da/hp/s800/
		hp-ux-11/A.04.10/packet.Z
	555505063 1211623 /opt/omni/databases/vendor/da/hp/s800/
		hp-ux-1020/A.04.10/packet.Z

	OMNIBACK-II.OMNI-OTHUX-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
		v=HP:
	3137220148 981405 /opt/omni/databases/vendor/da/dec/alpha/
		osf1-4/A.04.10/packet.Z
	2503052597 622783 /opt/omni/databases/vendor/da/gpl/i386/
		linux-60/A.04.10/packet.Z
	771949812 690531 /opt/omni/databases/vendor/da/ibm/rs6000/
		aix-42/A.04.10/packet.Z
	1563989970 720583 /opt/omni/databases/vendor/da/sco/i386/
		sco_sv/A.04.10/packet.Z
	96777612 718135 /opt/omni/databases/vendor/da/sco/i386/
		unixware/A.04.10/packet.Z
	1199140296 1325717 /opt/omni/databases/vendor/da/sgi/mips/
		irix-62/A.04.10/packet.Z
	3520734162 1221811 /opt/omni/databases/vendor/da/siemens/
		r400/sinix/A.04.10/packet.Z
	2248006798 793384 /opt/omni/databases/vendor/da/sun/sparc/
		solaris-26/A.04.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_30340:
	CORE packet patch,
	release date: Available
	Change Request: H555009435
	Bad catalog access message is displayed without PHSS_30340.

	PHSS_30344:
	Cell Server (CS) packet patch,
	Release Date: Available
	Change Request: H555012804
	PHSS_30344 is required for these defect fixes.

Supersedes:
	PHSS_30330 PHSS_29874 PHSS_28336 PHSS_26344

Equivalent Patches:
	PHSS_30829:
	s700: 10.20
	s800: 10.20

Patch Package Size: 8970 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_30830

	5. Run swinstall to install the patch:

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

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

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

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

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

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

	The Disk Agent packets must be redistributed to the Cell
	Manager system and client systems afterwards to get the
	fixes into effect.

	Patch includes the following Site Specific Patches:
	   SSPUX410_079
	   SSPUX410_084
	   SSPUX410_085

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