Patch Name: PHSS_28578

Patch Description: s700_800 10.X OV OB3.50 patch - SSEA packet

Creation Date: 03/03/24

Post Date: 03/04/04

Hardware Platforms - OS Releases:
	s700: 10.00 10.01 10.10 10.20
	s800: 10.00 10.01 10.10 10.20

Products:
	OmniBackII A.03.50

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

Automatic Reboot?: No

Status: General Release

Critical: No

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

Symptoms:
	PHSS_28578:
	Id = HSLco37090  SR:H555008776
	    SSEA LVM BC backup fails with:

	      "[Critical] From: SSEA@<hostname> ""  Time:<time>
	       Command "/usr/bin/raidscan -p <port>"
	       failed with exit code 238.
	       For details check the following log directories:
	       Log file directory in operation:
	       /var/opt/omni/log/<session_ID>/curlog<num>Log
	       file directory for automatic storing:
	       /var/opt/omni/log/<session_ID>/tmp<num>"

	Id = HSLco37449  SR:H555008860
	    When resolving ssea reports all of its data for every
	    single object to be backed up.

	Id = HSLco40537  SR:H555009863
	    When backing up very large SAP databases with SSEA
	    split mirror, backups can fail with error:

	      "BR280I Time stamp <time>
	       BR296I Split of mirror disks successful
	       BR274E File /<sapdata_path>/system.data1 not found"

	PHSS_27591:
	Id = HSLco32398  SR:H555007043
	    When there is a firewall between the application and
	    the backup host, the split mirror backup fails.

	Id = HSLco32470  SR:H555007071
	    Resolving performance is poor.

	Id = HSLco33214  SR:H555007361
	    SSEA backup fails with:

	      "[Major] From: SSEA@<hostname> "" Time: <time>
	       [224:106] Resolving of object <object_path> has
	       failed. (Search for backup logical volume failed.)"

	Id = HSLco35074  SR:H555008259
	    SSEA backup fails with:

	      "[Critical] From: SSEA@<hostname> "" Time:<time>
	       Failed to get pair for LDEV <ldev#> in RAID <seq#>.
	                (Details unknown.)"

	Id = HSLco36105  SR:H555008599
	    SSEA backup fails with:

	      "[Critical] From: SSEA@<host> <mailto:SSEA@<host>
	       "" Time:<time>
	       Command "/usr/bin/pairdisplay -g" failed with exit
	       code 242."

	Id = HSLco36476  SR:H555008656
	    SSEA backup fails with:

	      "[Major] From: SSEA@<hostname> "" Time:<time>
	       [224:106] Resolving of object <object_name> has
	       failed. (Search for backup logical volume failed.)"

	Id = HSLco36975  SR:H555008750
	    The SSEA SMB session on the backup host abnormally ends
	    when trying to activate backup volume group after the
	    paired LDEVs have been split.

	PHSS_26215:
	Id = HSLco32218  SR: H555006986
	    Horc instance number is not configurable.

	Id = HSLco32253  SR: H555006993
	    SSEA agent reports disks in SIMPLEX state although
	    they are in PAIR state in HORCM.

	Id = HSLco32264  SR: H555006994
	    OmniBack II SSEA Integration does not work with
	    logical devices with XP LUN number greater than 128.

	Id = HSLco32274  SR: H555006996
	    Performance of SSEA integration drastically decreases
	    after the installation of PHSS_25817/PHSS_25818.

	PHSS_25817:
	Id = JAGad48627  SR:8606179403
	    If preexec script fails OmniBack II by default just
	    aborts the agent and exits. It does not run post-exec
	    script or clean up.

	Id = NSMex04226
	    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 = HSLco30300  SR:H555006603
	    Split mirror backup fails with:

	      "[Critical] From: SSEA@<host> ""  Time: <time>
	        Command "/etc/horcmgr" failed with exit code 3.
	        For details please check log directories:
	        Log file directory in operation:
	                /var/opt/omni/log/yyyy-mm-dd-xx/curlogxx
	        Log file directory for automatic storing:
	                /var/opt/omni/log/yyyy-mm-dd-xx/tmpxx".

	Id = HSLco31032  SR:H555006753
	    Split mirror backup session fails with:

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

	       [SseMapLdevToRdsk] Unable to found /dev/rdsks
	       file for LDEV = <number>".

	Id = HSLco31434  SR:H555006835
	    Unexpected close reading message from the agent on the
	    Backup System (SSEA abnormally ends on R2).

	Id = HSLco30701  SR:H555006685
	    Resolving fails on the Application host. The spt inq
	    structure returns corrupted results.

	Id = HSLco31490  SR:H555006844
	    SSEA integration backup fails with:

	      "[Critical] From: SSEA@<host_name> ""  Time: <time>
	        Command "/etc/horcmgr" failed with exit code 3.
	       [Critical] From: SSEA@<host_name> ""  Time: <time>
	        Failed to start RAID Manager instance.
	            (Command /etc/horcmgr failed.)".

	PHSS_24425:
	Id = NSMex04086
	    Session status is "Completed/Failures" although there
	    is no any indication of errors.

	Id = NSMex04209
	    SSEA Integration backup fails with an error:

	      "[Critical] From: SSEA@<hostname> "" Time: <time>
	         Failed to find <volume/volume No.> of LDEVs.".

	Id = NSMex04216
	    SSEA Integration backup reports the following warning:

	      "[Warning] Cascading structure of BC pairs found
	        (THIS IS UNSUPPORTED).".

	Id = NSMex04392
	    SSEA Integration backup fails with an error:

	      "Filesystem <path> could not be mounted.".

	Id = NSMex04267
	    SSEA Integration backup fails with an error:

	      "[61:1005] Got unexpected close from Split Mirror
	       Agent.".

	Id = HSLco23886
	    LVM Mirror (XP Campus Cluster) is not supported
	    within OmniBack II SSEA Integration.

	PHSS_22436:
	Id = NSMex03360
	    SSEA Integration split does not appear to mount some
	    filesystems.

	Id = NSMex03700
	    Disk resolving failed on Backup Host.

	Id = NSMex03717
	    a) SSEA integration backup fails with an error:

	       "[Major] From: SSEA@<hostname> ""  Time: <time>
	        [224:106] Resolving of object "filename" has failed.
	    	(Cannot find block device path name of a logical
	         volume)"

	    b) SSEA Integration backup fails with an error:

	       "[Major] From: SSEA@<hostname> ""  Time: <time>
	        File system <filesystem> could
	        not be mounted to . (Invalid filesystem type.)"

	Id = NSMex03482
	    Disk synchronization messages are incorrect.

	Id = HSLco22201
	    OmniBack II SSEA integration is not supported on Sun
	    Solaris operating system.

	Id = NSMex03651
	    Disk synchronization fails with:

	      "[Critical] From: SSEA@<hostname> "" Time: <time>
	       [225:110] Mapping from LDEV to character device
	         file or disk failed for LDEV <dev> on
	         array <array>. (Unable to find character device
	         file for SureStoreE XP256 disk (LDEV))."

	Id = NSMex03673
	    Backup fails with the following message:

	      "[Critical] From: SSEA@<hostname> "" Time: <time>
	       Command "/usr/bin/pairdisplay -g" failed with
	       exit code 242.".

	Id = NSMbb39679
	    OmniBack II aborts Business Copy split mirror
	    backup because one of the disks in a pair is in
	    status COPY.

	Id = NSMex03547
	    SSEA Agent intermittently fails to resolve objects.

	Id = NSMex03739
	    Pre- and post-exec scripts return invalid exit status.

	Id = NSMex03913
	    SSEA backup fails with the following message:

	      "[Critical] From: SSEA@<hostname> "" Time: <time>
	       Command "/usr/bin/pairdisplay -g" failed with
	       exit code 221.".

	Id = NSMex03960
	    SSEA backup fails with the following error:

	      "Failed to start RAID Manager instance.
	       (Unable to find SureStoreE XP256 COMMAND device
	        file.)".

	Id = NSMex03850
	    Sometimes volumes cannot be mounted on JFS 3.3
	    filesystem.

	Id = NSMex03749
	    Mount function does not restore mount options.

	Id = NSMex03563
	    Mounting of a filesystem fails.

	Id = NSMex03931
	    OmniBack II SSEA Integration does not work on XP 512
	    for LDEVs with XP LUN addresses above 128.

Defect Description:
	PHSS_28578:
	Id = HSLco37090
	    If the LVM mirroring is done between two XP boxes with
	    the BC configuration on the second XP box and the BC
	    license present only on the second XP box, the raidscan
	    command fails on the first XP box causing the session
	    to fail.

	Resolution:
	    BC license on the first XP is not needed. When
	    executing the raidscan command, the SSEA session does
	    not fail if the raidscan command fails, but just marks
	    the rdsks and LDEVs from the first XP box with an
	    error. The marked rdsks and LDEVs are skipped later in
	    the session.

	Id = HSLco37449
	    Extensive reporting is only needed in case of errors,
	    so reporting data for every object can mean a lot of
	    unwanted information, especially in big environments.

	Resolution:
	    New environment variable is introduced:
	    SSEA_RESOLVING_DISPLAY. Its default value is 1. Set
	    it to 0 if you want to switch off extensive object
	    data reporting.

	Id = HSLco40537
	    In split mirror environment with very large SAP
	    databases, it can happen that the size of the message
	    buffer that OmniBack II uses is too small to fit in
	    for the complete list of SAP files to be backed up.

	Resolution:
	    New environment variable is introduced: OB2IPCBUFSIZE.
	    In order to solve this problem, the buffer size can
	    be increased by setting the OB2IPCBUFSIZE environment
	    variable in the .omnirc file on CM, R1 and R2 hosts,
	    specifying the desired amount of memory to be used
	    for the buffer.
	    Please read the following instructions and make sure
	    that the patches listed in "Other Dependencies" section
	    (see below) are installed and the environment
	    variable is set on Cell Server, R1 and R2 systems before
	    running the backup!

	    How to determine the buffer size?
	    ---------------------------------

	    N_obj:       number of objects (files)
	    N_fs:        number of file systems
	    N_lvmvg:     number of volume groups
	    N_dg:        number of disk groups
	    N_rdsk:      number of rawdisks
	    Obj:         Object Name
	    ObjBack:     Object Backup Name
	    MntPathLen:  Path name on backup (R2) host
	                 (example: /var/opt/omni/tmp/App_host)
	    fsmnt:       File System Mount Point
	    fsdev:       File System Device File
	                 (example: /dev/dsk/[c0t1d1,lvol1])
	    vg:          Volume group
	                 (ex: /dev/vg01)
	    dg:          Disk group (VxVM) - dependence on mapfile
	                 which is required for creating disk group
	                 (example:/dev/vx/dsk/dg01)
	    rdsk:        Raw disk file name
	                 (example: /dev/rdsk/c1t1d1)
	    AvgLen_<xxx> average length of <xxx>


	    There are two different buffers used:

	    1. BSM <-> R1
	    2. R1 <-> R2

	    Calculating the BSM <-> R1 buffer size
	    --------------------------------------
	    MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen)

	    Calculating the R1 <-> R2 buffer size
	    -------------------------------------
	    MsgSize_R1_R2 =
	      N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) +
	      N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+
	      N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) +
	      N_rdsk*(AvgLen_rdsk*2)

	    Calculating the OB2IPCBUFSIZE value
	    -----------------------------------
	    OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)

	    RESTORE NOTE:
	    -------------
	    If restore is started using the sapbda utility,
	    the variable OB2IPCBUFSIZE must be exported to
	    environment prior to starting sapbda.

	    Part of SSPUX350_088.

	PHSS_27591:
	Id = HSLco32398
	    OmniBack II selects by random the port to use and than
	    checks if it is free. When there is a firewall between
	    the application and the backup host, not all the ports
	    can be used, but just those in a specified range.

	Resolution:
	    Two environment variables are added to set the port
	    range in .omnirc file that can be used by OmniBack II:

	    SSEA_RM_PORT_LOW
	    SSEA_RM_PORT_HIGH

	Id = HSLco32470
	    In the resolving phase SSEA executes two ioscan
	    commands in the SseXIoScanRdsk and ScsiIquiry
	    functions. Since these two functions are called
	    several times the resolving performance decreases,
	    especially in big environments.

	Resolution:
	    SSEA executes just one ioscan command in the
	    SseXIoScanRdsk and ScsiIquiry functions. The ioscan
	    output is cached into a buffer and parsed for
	    information twice.

	Id = HSLco33214
	    In case of non-XP rdsk, SSEA can not find the volume
	    group belonging to this rdsk and resolving can not
	    be done.

	Resolution:
	    SSEA finds and checks all the rdsks belonging to an LDEV
	    on the R2 side. Than it uses only those rdsks which are
	    included in a volume group, in this way skips the non-XP
	    rdsks.

	Id = HSLco35074
	    When there are more than one smb sessions running
	    simultaneously, horcm instances could be attached to
	    the same command device.

	Resolution:
	    SSEA retries the getldev() call for 10 times. The
	    timeout before calling the getldev() API again is
	    randomly set. From now on SSEA tries to attach up
	    to 5 command devices if necessary.

	Id = HSLco36105
	    A time out occurs on remote communication, and HORC
	    manager fails to re-execute.

	Resolution:
	    A new environment variable SSEA_RM_TIMEOUT is
	    introduced. Its default value is 6000 milliseconds.

	Id = HSLco36476
	    When mapping the LDEVs to the appropriate rdsks,
	    rdsks statuses are not correctly updated.

	Resolution:
	    Mapping is done correctly.

	    Part of SSPUX350_083.

	Id = HSLco36975
	    When the LDEVs belonging to a volume group are in PAIR
	    status and the SSEA smb session is started on some of
	    these LDEVs, the vgchange command on this volume group
	    takes a long time. After splitting the disks on on the
	    R2 side, the LDEVs included in the SMB session are in
	    PSUS state, the rest of the LDEVs are still in PAIR
	    state and vgchange command can not proceed, which
	    causes the session to ends abnormally.

	Resolution:
	    If the SMB_SPLIT_ENTIRE_VG environment variable is set
	    to 1 in the .omnirc file on both hosts, then all the
	    LDEV pairs included in the backup volume group are
	    synchronized and split.

	    Part of SSPUX350_084.

	PHSS_26215:
	Id = HSLco32218
	    Horc instance number is not configurable.

	Resolution:
	    Horc instance number can be configured using new
	    environment variables, SSEA_RMINST_LOW and
	    SSEA_RMINST_HIGH. When set in ${OMNI_HOME}/.omnirc
	    file, these variables set instance number range. Default
	    values for SSEA_RMINST_LOW and SSEA_RMINST_HIGH
	    are 50 and 80, respectively.

	    Part of SSPUX350_070.

	Id = HSLco32253
	    Incorrect comparison of the strings causes incorrect
	    state of the disks reported.

	Resolution:
	    SSEA agent properly reports disk state.

	Id = HSLco32264
	    SSEA agent creates invalid configuration files for
	    logical devices exported to LUN's above 128.

	Resolution:
	    New environment variable is introduced: SSEA_XP_PORTS.
	    Setting the variable to the value "FC" in
	    ${OMNI_HOME}/.omnirc file enables OmniBack II SSEA
	    Integration to work properly with logical devices
	    exported to XP LUN's greater than 128.

	Id = HSLco32274
	    Multiple ioscan calls when extracting needed data
	    cause bad performance.


	Resolution:
	    Scripts for obtaining data needed by OmniBack II SSEA
	    Integration are improved.

	PHSS_25817:
	Id = JAGad48627
	    If pre-exec script fails, cleanup does not start
	    post-exec script.

	Resolution:
	    New environment variable is introduced. When
	    SSEA_ALWAYS_POST_SCRIPT in .omnirc file on
	    application host is set to 1, post-exec script
	    is always executed.

	Id = NSMex04226
	    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 = HSLco30300
	    The command /etc/horcmgr fails if the command
	    device is used by another split mirror session.

	Resolution:
	    New environment variables are introduced
	    SSEA_RM_RETRY and SSEA_RM_SLEEP.

	    SSEA_RM_RETRY defines the number of retries.
	    SSEA_RM_SLEE defines sleeping time in seconds,
	    before new retry is started.


	Id = HSLco31032
	    The resolving from LDEVs to rdsks on the backup host
	    fails due to incorrect reporting of LDEVs to rdsks.

	Resolution:
	    The resolving from LDEVs to rdsks is corrected.

	Id = HSLco31434
	    SSEA agent on R2 does not read the number of rdsk
	    from the R1. Bug is produced while fixing the
	    NSMex04787 case on NT platform, but affected the
	    SSEA agent on the HP-UX platform.

	Resolution:
	    The correct number of strings is read from the SSEA
	    agent on the R2 side.

	Id = HSLco30701
	    The SCTL_InquiryDisk function returns empty or
	    corrupted inq structure.

	Resolution:
	    The ioctl system function writes its output directly
	    to the inq structure. The "mapping from rdsks to LDEVs"
	    and the ScsiInquiry are enhanced.

	    Part of SSPUX350_057.

	Id = HSLco31490
	    SSEA can not start the selected HORCMINST instance
	    number. It is already started by another RaidManager
	    process.

	Resolution:
	    SSEA tries to start the instance with different
	    instance number up to five times.

	PHSS_24425:
	Id = NSMex04086
	    Message level of a resolving failure in XP environment
	    is set to "Normal" instead of "Major".

	Resolution:
	    Message level is corrected.

	Id = NSMex04209
	    If backup devices are exported to more than one port
	    and original devices have more than two mirrors, when
	    session is started and two of these ports are used for
	    that session, SSEA Integration detects more mirrors
	    than it is allowed.

	Resolution:
	    Parsing of raidscan() output is improved.

	Id = NSMex04216
	    If there are two or three mirror disks to source
	    disk, OmniBack II reports that cascading structure is
	    found although cascading structure is present only
	    when there are mirror disks to targer disk.

	Resolution:
	    Searching for cascading structure is excluded as
	    this feature is not supported with OmniBack II
	    A.03.50 version.

	Id = NSMex04392
	    Incorrect filesystem options are sent to R2 side.
	    For HFS filesystems the entries in the mnttab file
	    are not updated promptly.

	Resolution:
	    Correct filesystem options are sent to R2 side.
	    /etc/mnttab is promptly updated for HFS filesystem.

	Id = NSMex04267
	    SSEA API fails after 60 seconds during the change of
	    volume groups. SMB_TIMEOUT is hardcoded to 60 seconds.

	Resolution:
	    SMB_TIMEOUT can be configured in .omnirc file for
	    situations where the changing of volume groups takes
	    more than one minute.

	    Part of SSPUX350_037.

	Id = HSLco23886
	    LVM Mirror (XP Campus Cluster) is not supported within
	    OmniBack II SSEA Integration.

	Resolution:
	    LVM Mirror (XP Campus Cluster) is supported within
	    OmniBack II SSEA Integration.

	PHSS_22436:
	Id = NSMex03360
	    XP256 Raid Manager's pairdisplay command returns
	    invalid status which causes some raw disks to fail
	    during resolving.

	Resolution:
	    Status checking changed to ignore invalid status from
	    pairdisplay command.

	Id = NSMex03700
	    If there is a lot of backup objects (usually case with
	    SAP databases) and these objects are placed in volume
	    group with a lot of stripped disks, then the size of
	    the internal message sent from SSEA-R1 to SSEA-R2 can
	    overflow hardcoded 100k limit.

	Resolution:
	    New message format reduces message size significantly.

	    Part of the SSPUX350_007.

	Id = NSMex03717
	    a) OmniBack II does not handle soft links correctly.

	    b) SSEA integration backup does not work properly in
	       case that a single session contains both filesystem
	       and rawdisk objects.

	Resolution:
	    Fixes are implemented in ssea.

	    Part of the SSPUX350_007.

	Id = NSMex03482
	    Disk synchronization failure reported as "Normal".

	Resolution:
	    Message statuses are properly reported.

	Id = HSLco22201
	    OmniBack II SSEA integration is not supported on Sun
	    Solaris operating system.

	Resolution:
	    OmniBack II SSEA integration is supported on Sun
	    Solaris 7 and 8 operating systems.
	    Please find the integration manual in the
	    /usr/omni/bin/utilns directory after the patch is
	    installed.

	Id = NSMex03651
	    IPC buffer for communication between SSEA Agents on
	    backup and application host is too small.

	Resolution:
	    IPC buffer increased.

	Id = NSMex03673
	    Pairdisplay command fails in ServiceGuard environment.

	Resolution:
	    Hostname resolving is improved.

	Id = NSMbb39679
	    OmniBack II does not treat status COPY as a valid
	    status.

	Resolution:
	    OmniBack II waits (for configurable timeout) for the
	    second disk to change the status to PAIR.

	    Environment variables are:

	      SSEA_SYNC_SLEEP_TIME = <time in seconds>
	      SSEA_SYNC_RETRY = <number of retries>

	    Default values are 5 for SSEA_SYNC_SLEEP_TIME and
	    10 for SSEA_SYNC_RETRY.

	Id = NSMex03547
	    Resolving of objects fails if stat() function reports
	    error for any entry in /etc/mnttab.

	Resolution:
	    Irrelevant errors are skipped during the resolving.

	Id = NSMex03739
	    Pre- and post-exec scripts return invalid exit status
	    because of timing problem.

	Resolution:
	    Environment variable OB2EXECTIMEOUT is introduced.
	    Variable represents timeout (in seconds) after the end
	    of pre- and post-exec script. Default value is 0.
	    Recommended value is between 5 and 10 seconds.

	Id = NSMex03913
	    Pairdisplay command fails if two sessions are started
	    at the same time.

	Resolution:
	    SSEA Agent correctly detects service port numbers
	    availability.

	Id = NSMex03960
	    SSEA Agent uses only those disks for which ioscan
	    reports state CLAIMED. Backup fails due to a fact that
	    some of the disks needed for session are in state SCAN.

	Resolution:
	    Disks in state SCAN are reported as well as those in
	    state CLAIMED.

	Id = NSMex03850
	    Changes made for JFS 3.3 support cause mount problems
	    on HP-UX 10.20 platform.

	Resolution:
	    Code now properly works also for the HP-UX 10.20
	    platform.

	    Part of SSPUX350_016.

	Id = NSMex03749
	    Filesystem is not mounted with the options that were
	    used before split mirror backup was performed.

	Resolution:
	    Command line mount command is used instead of mount
	    function for vxfs filesystem.

	Id = NSMex03563
	    Mount operation does not work properly on systems
	    with Online JFS 3.3 installed.

	Resolution:
	    Mount API uses proper arguments.

	Id = NSMex03931
	    Invalid configuration files are created for LDEVs
	    exported to LUN addresses above 128.

	Resolution:
	    New environment variable SSEA_XP_PORTS is introduced.
	    Its value has to be set to "FC" when using Fibre channel
	    and LUN addresses greater than 128.

	    Part of SSPUX350_032.

SR:
	H555009863 H555008776 H555008860 H555008656 B554000692
	H555007043 H555008599 H555007071 B554000869 B554000879
	H555007361 H555008750 H555008259 H555006993 H555006994
	H555006986 H555006996 H555006685 H555006753 8606179403
	H555006844 H555006835 H555006603 H555005488 H555005717
	H555005689 H555005681 H555004065 H555005289 H555003697
	B554000781 B554000676 B554000847 B554000829 H555004533
	H555004741 H555003490 H555003716 B554000521 B554000612
	H555003817 H555004474 B554000803 B554000491 H555004919

Patch Files:
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.03.50/
		packet.Z
	/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
		A.03.50/packet.Z
	/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
		A.03.50/require.dat

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

cksum(1) Output:
	1343273602 2050307 /opt/omni/databases/vendor/ssea/hp/s800/
		hp-ux-1020/A.03.50/packet.Z
	3097561959 2059081 /opt/omni/databases/vendor/ssea/hp/s800/
		hp-ux-11/A.03.50/packet.Z
	3903783657 1550093 /opt/omni/databases/vendor/ssea/sun/
		sparc/solaris-26/A.03.50/packet.Z
	1830950196 19 /opt/omni/databases/vendor/ssea/sun/sparc/
		solaris-26/A.03.50/require.dat

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_28727:
	Release date: Late April
	Id = HSLco40537  SR:H555009863
	PHSS_28727 is required for this defect fix.

	PHSS_28725:
	Release date: Late April
	Id = HSLco40537  SR:H555009863
	PHSS_28725 is required for this defect fix.

	PHSS_28570:
	Release date: Available
	Id = HSLco40537  SR:H555009863
	Bad catalog access message is displayed without PHSS_28570.

	PHSS_28017:
	Release Date: Available
	Id = HSLco40537  SR:H555009863
	PHSS_28017 is required for this defect fix.

Supersedes:
	PHSS_22436 PHSS_24425 PHSS_25817 PHSS_26215 PHSS_27591

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

Patch Package Size: 5590 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_28578

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

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

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

Special Installation Instructions:
	PHSS_28578:
	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:
	   SSPUX350_007
	   SSPUX350_016
	   SSPUX350_032
	   SSPUX350_037
	   SSPUX350_057
	   SSPUX350_070
	   SSPUX350_083
	   SSPUX350_084
	   SSPUX350_088