Patch Name: PHSS_25954

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

Creation Date: 02/03/08

Post Date:  02/03/11

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.10

Filesets:
	OMNIBACK-II.OMNI-CS,A.03.10

Automatic Reboot?: No

Status: General Release

Critical: No

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

Symptoms:
	PHSS_25954:
	Id = HSLco31295 SR: H555006799
	    OmniBack reports that medium copy session finished
	    successfully although it failed.

	Id = JAGad70771 SR: 8606201597
	    Post-exec script specified for a virtual hostname does
	    not start if pre-exec script fails.

	Id = JAGad86475 SR: 8606217323
	    Cell Request Server and session managers frequently
	    abort.

	Id = HSLco24755 SR: B555011718
	    OmniBack II issues a mount request for tape during
	    the restore session.

	Id = HSLco27714 SR: H555005732
	    OmniBack II issues mount request, but it can not be
	    confirmed because the tape drive is busy.

	Id = HSLco28279 SR: H555005975
	    Purge of fnames aborts daily.

	Id = HSLco28271 SR: H555005973
	    Restore session fails with error:

	      "Can not load exchanger medium.".

	PHSS_23689:
	Id = JAGad36093
	    Session status indicates "Completed" although one of the
	    agents failed.

	Id = NSMbb37729
	    Devbra reports:

	    "[90:11] Unrecognized option "/" => ignored".

	Id = NSMex02631
	    Backup of Informix logs fails with an error:

	    "Can not read BSM message (IPC Read Error)".

	Id = NSMex03425
	    Backup of SAP archive logs fails with:

	      "[Major] From: OB2BAR@<hostname> <ORASID> Time:<time>
	           Can not read BSM message (IPC Read Error
	           System error: [232] Connection reset by peer.)".

	Id = NSMex03486
	    Backup Session Manager is started with Purge
	    Session Manager parameters.

	Id = NSMex03711
	    Error:

	      "Hostname is not in IP range."

	    is reported after service guard fails over to a
	    secondary host.

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

	Id = NSMex03894
	    Host backup fails if host has more than 600
	    mountpoints.

	Id = NSMex03991
	    Full Oracle backup can be appended to a medium in a
	    pool with "append incremental only" property.

	Id = NSMex04149
	    If CRS is restarted in cluster aware mode, error:

	    "-2 starting omnidbutil -clear!"

	    occurred in cluster.log file.

	Id = NSMex03621
	    Restore does not work correctly after the mount
	    request confirmation.

	Id = NSMex04283
	    Licensing fails with an error:

	    "Cell Server host IP is not in IP range"

	Id = HSLco20414
	    Device maintenance from command line is not sufficient.

	Id = NSMex04332
	    Load balancing does not use all expected devices.

	Id = NSMex03705
	    "omnidbutil -purge" fails with error no 227.

	PHSS_22166:
	Id = JAGad17029
	    "List from media" ignores "See private objects" option.

	Id = NSMex02584
	    RDS dies due to lack of memory.

	Id = NSMex03493
	    Omnitrig does not pass debugging parameters to omnirpt.

	Id = NSMex03419
	    After importing a tape from 2.55 to 3.x cell some of
	    the files can not be restored.

	Id = NSMex03356
	    Permanent license shows up as out of IP range.

	Id = NSMex03365
	    Backup session is not logged in the database if file
	    pattern search is performed in parallel.

	Id = NSMex03466
	    After the upgrade from OmniBack II 3.00 to 3.10, a
	    warning

	      "Received connect from BAR backup DA on host
	       <hostname> that is not specified in CLIENT statement
	       in barlist."

	    appears on a client with multiple lan cards.

	Id = NSMex03481
	    A backup of MC/SG can not be aborted after the switch.

	Id = NSMex03663
	    "-dev_server" entry is removed from cell_info file
	    whenever an update of device server is performed.

	Id = NSMex03417
	    Upgrading OmniBack II from version 2.55 to 3.10 fails.

	Id = NSMex03246
	    Backup Session Manager is sending wrong SNMP messages to
	    ITO Management server.

	Id = JAGad13634
	    Informix barlists are not converted into a OmniBack II
	    3.10 format after an upgrade from OmniBack II 2.55.

	Id = NSMex03583
	    OmniBack II ignores the tape loaded after the mount
	    request for SCSI-II changer device.

	Id = NSMex03702
	    RDS dies during a SAP restore.

	Id = NSMex03289
	    Sessions are disappearing from OmniBack II database.

	Id = NSMex03521
	    OmniBack II database gets corrupted.

	PHSS_21650:
	Id = NSMex03001
	    Sessions are disappearing from the database.

	Id = NSMex03294
	    Restarting of a failed backup session results in an
	    error message:

	        "Expecting new option when parsing."

	Id = NSMex03346
	    Omnidbutil -readascii fails with the error message:

	        "ascii file is corrupted."

	PHSS_21234:
	Id = NSMex02885
	    BSM reports unexpected close message during backup
	    preview.

	Id = NSMex02929
	    Bad performance of Informix logical logs restore.

	Id = NSMex03097
	    Copy session of write-protected tape is aborted and
	    cleaning tape is requested in the source tape drive.

	Id = NSMex02931
	    Too many backup sessions running in parallel.

	Id = NSMex02964
	    License is not recognized on a Cell Manager system
	    with multiple lan cards although it has been prepared
	    for one of the lan cards IP address.

	Id = NSMex03110
	    Backup fails with an error:

	      "Could not connect to inet in order to start BMA".

	Id = NSMex02738
	    Bad backup performance after upgrade from OmniBack II
	    2.55 or 3.00.

	Id = NSMex02639, NSMex03017
	    "omnirpt -report fs_not_conf" gives incorrect output.

	Id = NSMex03144
	    Mounting of media fails with an error:

	      "Volume not found of this type".

	Id = NSMex03052, JAGac40383
	    Filesystem disk agents of a host backup are not
	    started until the pre/post-exec of the host object
	    is completed.

	PHSS_19519:
	Id = HSLco16368
	    HP SureStoreE Disk Array XP256 is not supported by
	    OmniBack II to perform a split mirror backup. This
	    patch does not fix any other problem.

Defect Description:
	PHSS_25954:
	Id = HSLco31295
	    Media Session Manager does not send abort message to
	    Backup Media Agent started after Copy Media Agent
	    failed.

	Resolution:
	    Media Session Manager properly handles abort message
	    from Copy Media Agent.

	Id = JAGad70771
	    OmniBack II improperly recognizes post-exec script as a
	    start request if pre-exec script fails in cluster
	    environment.

	Resolution:
	    OB2FORCEPOSTEXEC environment variable is added.
	    Setting its value to 1 in the .omnirc file causes
	    post-exec scripts to be started regardless of pre-exec
	    script exit code.

	    Part of SSPUX310_057.

	Id = JAGad86475
	    Cell Request Server and session managers abort
	    because of an accept() command failure on some
	    HP-UX 11.x systems.

	Resolution:
	    accept() command is re-executed in case of
	    ENOBUFS failure.

	    Part of SSPUX310_059.

	Id = HSLco24755
	    Rescan before backup option incorrectly deletes locked
	    slots information from OmniBack II database.

	Resolution:
	    Locked slots are not updated during any rescan.

	Id = HSLco27714
	    When there is no more media available for the running
	    session, mount request is issued. This mount request
	    can not be confirmed because the drive is locked
	    by Backup Session Manager.

	Resolution:
	    Media Session Manager ignores Backup Session Manager
	    lock making the slot free for mount request
	    confirmation.

	Id = HSLco28279
	    In some special cases it is possible for purge of
	    fnames to fail with error written in the debug.log:

	    "DB[9] internal error [-16]
	    record not connected to set."

	Resolution:
	   Purge is improved in order to correctly remove
	   such records.

	Id = HSLco28271
	    After the mount request during restore from SCSI-II
	    library, Omniback tries to load "" medium into drive.

	Resolution:
	    Restore session manager rechecks the configuration
	    after the mount request is confirmed.

	PHSS_23689:
	Id = JAGad36093
	    If one of the agent fails session status should
	    indicate "Completed/Errors" instead of "Completed".

	Resolution:
	    Session status is correct.

	Id = NSMbb37729
	    Database Session Manager starts Device Browser with
	    incorrect options.

	Resolution:
	    Structure containing Device Browser options is
	    initialized before it is filled with the parameters.

	Id = NSMex02631
	    If new backup of logical logs is started at the time
	    when BSM is waiting for the tape to be ejected,
	    the backup of Informix logs fails with an error:

	    "Can not read BSM message (IPC Read Error)"

	    after the SmWaitForNewClient timeout occurs.

	Resolution:
	    Fix is implemented in BSM.

	Id = NSMex03425
	    Backup of SAP archive logs fails if a backup request
	    for next archive log comes when Backup Session Manager
	    is already exiting.

	Resolution:
	    Datalist entries for BAR session are removed.

	Id = NSMex03486
	    Purge Session Manager parameters are passed to Backup
	    Session Manager without freeing the options string.

	Resolution:
	    Options string is cleaned before any session
	    manager starts.

	Id = NSMex03711
	    Licensing is not working properly for systems with
	    more than 20 LAN cards, due to an OmniBack limitation.

	Resolution:
	    Number of LAN cards on a single system can be up to 100.

	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 = NSMex03894
	    OmniBack II has a 600 mountpoints limitation. Host
	    backup fails if there are more than 600 mountpoints.

	Resolution:
	    Number of mountpoints per host increased to 50000.

	Id = NSMex03991
	    Backup Session Manager incorrectly appends full
	    Oracle backups.

	Resolution:
	    Backup Session Manager correctly checks properties
	    of pool.

	Id = NSMex04149
	    "omnidbutil -clear" return invalid exit status.

	Resolution:
	     Omnidbutil is improved.

	Id = NSMex03621
	    When restoring the data from STK or GRAU library,
	    wrong medium is loaded into drive after the mount
	    request confirmation.

	Resolution:
	    Mount request is properly handled.

	    Part of SSPUX310_046.

	Id = NSMex04283
	    Ioctl function cannot list all interfaces.

	Resolution:
	    Interfaces limitation is increased to 1000.

	Id = HSLco20414
	    Device enabling, disabling and status report cannot be
	    performed using OmniBack II command line.

	Resolution:
	    New options "-disable_device", "-enable_device" and
	    "-device" are added to omnimm, omniupload and
	    omnidownload.

	    Please see Special Installation Instructions for details
	    about the usage of mentioned options.

	    Part of SSPUX310_055.

	Id = NSMex04332
	    During backup not all devices are locked and used.

	Resolution:
	    Backup Session Manager is improved.

	Id = NSMex03705
	    IpcConnectToProcess() is called incorrectly with
	    the port 0.

	Resolution:
	    Cell Request Server is changed.

	PHSS_22166:
	Id = JAGad17029
	    Using "List from media" option in restore context
	    ignores "See private objects" option. Objects that are
	    backed up as "Private" are not listed.

	Resolution:
	    Option parsing in restore context is improved.

	Id = NSMex02584
	    Execution of command

	      "omnidb -filesystem <FS_Object> -file <File_Name>"

	    causes a memory leak in RDS (approx. 300 bytes). If the
	    command is started more than 100000 times, it can cause
	    RDS to die due to a lack of memory.

	Resolution:
	    Fix is implemented in libob2ecdb.sl.

	Id = NSMex03493
	    Scheduled reports are not started with "-debug" option
	    although omnitrig is.

	Resolution:
	    Command line option parsing is implemented for omnirpt.

	Id = NSMex03419
	    OmniBack II 3.10 objects are case insensitive which is
	    not true for the SAP objects backed up with 2.55
	    version. Object tape format is changed with 3.10 as
	    well. These changes caused some SAP objects not to be
	    displayed in the Restore GUI after importing the tape
	    with SAP objects from 2.55 to 3.10.

	Resolution:
	    Names are tape format are converted into OmniBack II
	    3.10 format after tape import from 2.55.

	    Part of SSPUX310_028.
	    See Special Installation Instructions.

	Id = NSMex03356
	    If there are more than 100 network interfaces, ioctl()
	    call fails.

	Resolution:
	    Buffer for SIOCGIFCONF is increased to support up to
	    1000 network interfaces.

	Id = NSMex03365
	    When backup and file search sessions are started in
	    parallel, file search session locks the database.
	    Backup Session Manager tries to write backup
	    information into locked database. Since this action can
	    not be performed, the following messages are logged
	    in the rds.log:

	      "11740  [10-Apr-00 17:37:07]  error status=5
	       11741  [10-Apr-00 17:37:07]  GROUPLOCK ELEMENT:
	        userID=4, LockType=6, LockMode= *, RecSetType=10002,
	        dba=[0:0], odnum=1"

	Resolution:
	    File pattern search is optimized to minimize the
	    possibilities of group locks.

	Id = NSMex03466
	    System name checking is not performed for systems with
	    multiple LAN cards. Backup Session Manager is checking
	    the system names only when looking for clusters.

	Resolution:
	    System name checking is performed when looking for
	    clusters and systems with multiple LAN cards.

	Id = NSMex03481
	    Aborting backup session is not possible because
	    Backup Session Manager incorrectly aborts Disk Agents
	    after the package switch.

	Resolution:
	    Disk Agents are properly aborted.

	Id = NSMex03663
	    A few entries are deleted from cell_info file upon
	    update.

	Resolution:
	    Existing entries are preserved.

	Id = NSMex03417
	    Some files are not converted to OmniBack II A.03.10
	    format because of an upgrade script failure.

	Resolution:
	    Fix is implemented in upgrade script.

	    Part of the SSPUX310_031.

	Id = NSMex03246
	    Normal, Warning and Minor messages can be seen on ITO
	    Management server even though OVfilter is set up to
	    forward only Critical messages.

	Resolution:
	    Messages are forwarded according to OVfilter setup.

	    Part of the SSPUX310_032.

	Id = JAGad13634
	    File /opt/omni/sbin/nb_informix is missing.

	Resolution:
	    File /opt/omni/sbin/nb_informix is added to OMNI-CS
	    fileset.

	    Part of the SSPUX310_035.

	Id = NSMex03583
	    Mount request is not properly implemented for SCSI-II
	    changer devices.

	Resolution:
	    OmniBack II properly handles mount requests.

	    Part of the SSPUX310_037.

	Id = NSMex03702
	    RDS dies during a large SAP restore due to memory leak
	    described in NSMex02584.

	Resolution:
	    Fix is implemented in libob2ecbd.sl.

	Id = NSMex03289
	    Media sync does not work properly when table of
	    exported/recycled media gets too big (>3000 media).
	    Some new sessions disappear from database. No error is
	    reported.

	Resolution:
	    Improved error handling logs this event in debug.log.

	    Part of the SSPUX310_036.

	Id = NSMex03521
	    Database stays in the hot mode after issuing an
	    "omnidbcheck" command. If a large amount of data is
	    written before OmniBack II daemons are stopped, it can
	    happen that hot files are not properly flushed. This
	    causes corruption of database.

	Resolution:
	    omnidbcheck flushes hot files immediately after
	    database check.

	    Part of the SSPUX310_036.

	PHSS_21650:
	Id = NSMex03001
	    When exporting tapes from a cell, wrong sessions are
	    purged.
	Resolution:
	    Sessions not residing on the exported tape are not
	    purged.

	Id = NSMex03294
	    Additional protection option is not recognized at
	    session restart.
	Resolution:
	    Bsm now recognizes the option "-protect days <days>".

	Id = NSMex03346
	    Omnidbutil -writeascii does not handle 2GB limit of
	    ascii files properly. If any ascii file during
	    writeascii procedure exceeds 2 GB, the file is not
	    completed properly. Because of that "omnidbutil
	    -readascii" fails with an error message that ascii
	    file is corrupted.
	Resolution:
	    When a file exceeds 2GB during the writeascii procedure
	    then an additional ascii file is created.
	    Part of SSPUX310_026.

	PHSS_21234:
	Id = NSMex02885
	    BSM reports unexpected close message during backup
	    preview even if Disk Agent was completed successfully.

	Resolution:
	    Counting of processed data size improved.

	Id = NSMex02929
	    There is a consistent delay of 30 seconds between
	    each logical log restore.

	Resolution:
	    Fix is implemented in Restore Session Manager.

	Id = NSMex03097
	    Copy session is aborted when copying a write-protected
	    tape. When write-protected tape in the source drive is
	    checked, the cleaning tape for that drive is requested
	    and the following message appears:

	      "Cleaning tape requested by device <device_name>.
	       Please clean the drive.".

	Resolution:
	    The cleanme signal is now processed correctly.

	Id = NSMex02931
	    It is not possible to have more than 50 sessions
	    running in parallel with OmniBAck II 3.10.

	Resolution:
	    The maximum number of session running in parallel is
	    set to 200.

	    Part of the SSPUX310_004.

	Id = NSMex02964
	    On some systems ioctl command returns 0 as the IP
	    address of some of the lan cards. This value has been
	    used as the end of IP address list and OmniBack II
	    rejects the license if it is prepared for an IP address
	    that is listed after "0" address.

	Resolution:
	    "0" addresses are not added to the list of valid system
	    IP addresses. This way license checking searches
	    complete IP address list until if finds the IP address
	    that the license has been prepared for.

	Id = NSMex03110
	    If more than one Media Agent is used in one session
	    and they are located on the same Novell NetWare
	    client, then the backup fails with an error:

	      "Could not connect to inet in order to start BMA".

	Resolution:
	    Delay for starting Media Agents increased.

	Id = NSMex02738
	    Performance degrated by up to 50% after upgrade from
	    OmniBack II 2.55 or 3.10.

	Resolution:
	    Redundant update of the objects removed.

	Id = NSMex02639, NSMex03017
	    "omnirpt -report fs_not_conf" gives incorrect output.

	Resolution:
	    Processing of "allbdf" output changed.

	Id = NSMex03144
	    After the confirmation of mount request for GRAU DAS or
	    Storage Tek ACS Library, OmniBack II tries to load ""
	    (empty string) medium. Library returns an error that
	    such a volume does not exist.

	Resolution:
	    BSM rechecks medium allocation after the mount request
	    confirmation.

	Id = NSMex03052, JAGac40383
	    If a datalist contains a host object with pre/post-exec
	    script, disk agents for the filesystem objects of that
	    host will not start until the script execution is
	    complete. This is not suitable if the script doesn't
	    need to be started for all filesystems.

	Resolution:
	    A new global option is introduced in order to control
	    the behaviour of the pre/post-exec script execution.
	    See 'Special Installation Instructions' for details
	    on setting the global option.

	    Part of SSPUX310_018.

	PHSS_19519:
	Id = HSLco16368
	    Currently OmniBack II only supports the Split Mirror
	    Backup concept with EMC Symmetrix. After the
	    introduction of the new HP SureStoreE Disk Array
	    XP256, it was requested that OmniBack II also
	    supports this disk array with the split mirror backup
	    concept.  This requires to support Oracle 8.0.x and
	    SAP R/3 in this concept as well and in addition a new
	    manual is needed.

	Resolution:
	    The SureStoreE Agent (SSEA) was developed for
	    HP-UX to control the SureStoreE disk array.
	    The Backup Session Manager, INET on HP-UX,
	    and the NT GUI were enhanced and in addition
	    Oracle 8.0.x and SAP integrations are
	    supported. Also the manual "HP OpenView
	    OmniBack II HP SureStore E Disk Array XP256
	    Configuration Guide" will be released.

SR:
	H555005732 H555005975 B555011718 8606201597 8606217323
	H555006799 H555005973 H555005697 H555004061 H555003134
	H555004027 B555002953 B555008272 H555003831 H555005821
	B554000869 H555005149 H555004475 B554000616 B554000841
	B554000834 8606144294 8606147687 3100069193 3100205011
	8606110994

Patch Files:
	/opt/omni/lbin/bsm
	/opt/omni/lbin/crs
	/opt/omni/lbin/rsm
	/opt/omni/lbin/dbsm
	/opt/omni/lbin/msm
	/opt/omni/lbin/mmd
	/opt/omni/lib/libob2ecdb.sl
	/opt/omni/lib/libob2eadm.sl
	/opt/omni/lib/libob2ecmn.sl
	/opt/omni/lib/libob2emmdb.sl
	/opt/omni/sbin/omnidbutil
	/opt/omni/sbin/omnitrig
	/opt/omni/sbin/nb_informix
	/opt/omni/sbin/upgrade_from_2.55.sh
	/opt/omni/sbin/omnidbcheck

what(1) Output:
	/opt/omni/lbin/bsm:
		[TZ=GMT0  /opt/omni/lbin/bsm  -version]
		HP OpenView OmniBack II A.03.10: BSM, internal build
			 PHSS_25954/PHSS_25955, built on Tue Feb 12
			16:19:40 2002
	/opt/omni/lbin/crs:
		[TZ=GMT0  /opt/omni/lbin/crs  -version]
		HP OpenView OmniBack II A.03.10: CRS, internal build
			 PHSS_25954/PHSS_25955, built on Tue Feb 12
			16:42:29 2002
	/opt/omni/lbin/rsm:
		[TZ=GMT0  /opt/omni/lbin/rsm  -version]
		HP OpenView OmniBack II A.03.10: RSM, internal build
			 PHSS_25954/PHSS_25955, built on Tue Feb 12
			16:21:43 2002
	/opt/omni/lbin/dbsm:
		[TZ=GMT0  /opt/omni/lbin/dbsm  -version]
		HP OpenView OmniBack II A.03.10: DBSM, internal buil
			d PHSS_25954/PHSS_25955, built on Tue Feb 12
			 15:54:34 2002
	/opt/omni/lbin/msm:
		[TZ=GMT0  /opt/omni/lbin/msm  -version]
		HP OpenView OmniBack II A.03.10: MSM, internal build
			 PHSS_25954/PHSS_25955, built on Tue Feb 12
			15:28:09 2002
	/opt/omni/lbin/mmd:
		[TZ=GMT0  /opt/omni/lbin/mmd  -version]
		HP OpenView OmniBack II A.03.10: MMD, internal build
			 PHSS_22166/PHSS_22167, built on Mon Sep 18
			14:26:26 2000
	/opt/omni/lib/libob2ecdb.sl:
		None
	/opt/omni/lib/libob2eadm.sl:
		None
	/opt/omni/lib/libob2ecmn.sl:
		None
	/opt/omni/lib/libob2emmdb.sl:
		None
	/opt/omni/sbin/omnidbutil:
		[TZ=GMT0  /opt/omni/sbin/omnidbutil  -version]
		HP OpenView OmniBack II A.03.10: OMNIDBUTIL, interna
			l build PHSS_21650, built on Thu May 18 14:1
			2:35 2000
	/opt/omni/sbin/omnitrig:
		[TZ=GMT0  /opt/omni/sbin/omnitrig  -version]
		HP OpenView OmniBack II A.03.10: OMNITRIG, internal
			build PHSS_22166/PHSS_22167, built on Thu Se
			p  7 15:06:12 2000
	/opt/omni/sbin/nb_informix:
		None
	/opt/omni/sbin/upgrade_from_2.55.sh:
		None
	/opt/omni/sbin/omnidbcheck:
		[TZ=GMT0  /opt/omni/sbin/omnidbcheck  -version]
		HP OpenView OmniBack II A.03.10: OMNIDBCHECK, intern
			al build PHSS_22166/PHSS_22167, built on Mon
			 Sep 18 14:15:32 2000

cksum(1) Output:
	4251315514 1166298 /opt/omni/lbin/bsm
	2101932918 706368 /opt/omni/lbin/crs
	1032402225 862632 /opt/omni/lbin/rsm
	1233821896 1219055 /opt/omni/lbin/dbsm
	1402629428 686053 /opt/omni/lbin/msm
	246603417 517732 /opt/omni/lbin/mmd
	2765462869 881364 /opt/omni/lib/libob2ecdb.sl
	843626451 692720 /opt/omni/lib/libob2eadm.sl
	1160727023 804257 /opt/omni/lib/libob2ecmn.sl
	2630151782 651912 /opt/omni/lib/libob2emmdb.sl
	188065716 677437 /opt/omni/sbin/omnidbutil
	2570520288 394475 /opt/omni/sbin/omnitrig
	2755861046 353611 /opt/omni/sbin/nb_informix
	1359022427 28086 /opt/omni/sbin/upgrade_from_2.55.sh
	3452850420 464149 /opt/omni/sbin/omnidbcheck

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHSS_19519 PHSS_21234 PHSS_21650 PHSS_22166 PHSS_23689

Equivalent Patches:
	PHSS_25955:
	s700: 11.00
	s800: 11.00

Patch Package Size: 9940 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_25954

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

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

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

Special Installation Instructions:
	PHSS_25954:
	NOTE!
	Fix for HSLco20414 introduces new options for device
	maintenance. The usage of new options is listed below:

	To disable/enable specific device and all other devices
	with the same lockname, run:
	    omnimm -disable_device {device name}
	    omnimm -enable_device {device name}

	To disable/enable all devices with the same lockname, run:
	    omnimm -disable_lockname {lock name}
	    omnimm -enable_lockname {lock name}

	To check if specific device is enabled/disabled, run:
	    omnidownload -device {device name}

	To obtain complete functionality one has to install
	PHSS_24423/PHSS_24424 (CORE) and PHSS_23109/PHSS_23110
	(Cell Console) or later patches as well.


	NOTE!
	This Patch has to be installed on the Cell Manager host.
	OmniBack II server must be shutdown before installing
	the patch. Use the following command for shutting down
	the server:

	   "/opt/omni/sbin/omnisv.sh stop".

	After the installation is complete, restart OmniBack II
	server using "/opt/omni/sbin/omnisv.sh start".


	NOTE!

	Fix NSMex03419 is also part of the OMNIBACK_00014
	(Windows NT) and PHSS_21644/PHSS_21645 (Cell Console)
	general release patch. Its functionality will be
	fully available when the mentioned patches that include
	this fix are released.


	NOTE!
	New global option has been introduced with earlier
	patches PHSS_21234/PHSS_21235 for solving the problem
	NSMex03052 & JAGac40383. With this option, the backup
	administrator can decide whether the pre/post-exec script
	will be started for one filesystem on the host only, or
	should all the filesystem disk agents wait for the
	pre/post-exec script to finish before starting up the
	filesystem backup.

	The option must be set on the Cell Manager system, in the
	file /etc/opt/omni/options/global. This is the syntax:

	   PrePostExecOnEveryVolumeForHostBackup=<0 or 1>

	      default: 0

	   If this option is set (=1), Backup Disk Agent (BDA)
	   for each volume of host object will execute the
	   pre/post-exec script specified. If this option is not
	   set (=0), the Backup  Session  Manager (BSM) will
	   execute preexec just prior to starting first volume
	   BDA and postexec after last volume BDA finished.
	   Note that for the duration of pre/post-exec scripts,
	   the BSM will not be responding.


	NOTE!
	The patches PHSS_19519/PHSS_19520 introduce support for
	HP SureStore E XP256 disk array.

	In order to enable the HP SureStoreE Agent (SSEA)
	functionality,a license-to-use (B7023AA) must be
	installed. In addition, the following OB2 patches
	are required:

	   PHSS_19523/PHSS_19524 - Core patch
	   PHSS_20111/PHSS_20112 - Oracle8 integration patch
	   PHSS_19525/PHSS_19526 - SSEA integration patch
	   PHSS_21236/PHSS_21237 - SAP integration patch
	   OMNIBACK_00010        - Windows NT

	Some of the patches mentioned above may be superseded
	by a newer patch.  Please check the HP Electronic
	Support Center web page for latest patches available.

	For more information regarding the installation procedure
	refer to the "HP OpenView OmniBack II HP SureStore E Disk
	Array XP256 Configuration Guide"



	Patch includes the following Site Specific Patches:
	   SSPUX310_004
	   SSPUX310_018
	   SSPUX310_026
	   SSPUX310_028
	   SSPUX310_031
	   SSPUX310_032
	   SSPUX310_035
	   SSPUX310_036
	   SSPUX310_037
	   SSPUX310_046
	   SSPUX310_055
	   SSPUX310_057
	   SSPUX310_059