OnBar to HP Data Protector - XBSA API error codes?
A weekly OnBar whole-system backup (IDS 9.30HC5, HP-UX 11i, Data Protector 5.1) started failing: bar_act.log showed "XBSA Error: BSACreateObject" with code 0x03 (BSA_RC_ABORT_SYSTEM_ERROR), while Data Protector logged "Unable to create OB2BAR set /itshm/rootdbs/0 ... OB2 API error is = 5[0]". The poster could find no documentation for the OB2 error. Replies asked about BAR_MAX_BACKUP, dbspace count and the onbar command, noted that failure was always a DP timeout on the first dbspace (rootdbs) while a near-identical instance on the same box worked, and argued the OB2 code is Data Protector-specific, so HP support (or the separate Unix/backup team) should be engaged; other suggestions covered checking for full target media, OS patches, and alternative backup methods. No resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Afternoon all
IDS 9.30HC5, HP-UX 11i, Data Protector 5.1
We're getting errors on a backup of a test system lately, nothing's
changed at all recently but the weekly backup is failing with code
0x03, which translates (Thanks hugely to Maury Tiller's wonderful
Informix On-Bar information page) to "BSA_RC_ABORT_SYSTEM_ERROR".
bar_act.log shows us "XBSA Error: BSACreateObject", info from Maury as
before: "-Creates an XBSA object. This basically tells that storage
manager to make room for a new backup. The storage manager passes back
the copyid (inside the objectdescriptor) that is the unique identifier
that onbar uses when it need to get that back/object. ".
What we CAN'T translate is that in the Data Protector runlog we get
"02:12:22 : (26918): IBK-bsa : [Critical] Unable to create OB2BAR set
"/itshm/rootdbs/0
(dbspace)".
OB2 API error is = 5[0]"
Now, we can't find any reference for the "OB2 API error" - can anyone
help? What is error 5[0]?
We're pushing the onbar debug level to 9 for the next run, should be
fun.............
Puzzled of Kent.
iiug@perrior.net wrote:
> Afternoon all
> IDS 9.30HC5, HP-UX 11i, Data Protector 5.1
>
> We're getting errors on a backup of a test system lately, nothing's
> changed at all recently but the weekly backup is failing with code
> 0x03, which translates (Thanks hugely to Maury Tiller's wonderful
> Informix On-Bar information page) to "BSA_RC_ABORT_SYSTEM_ERROR".
>
> bar_act.log shows us "XBSA Error: BSACreateObject", info from Maury as
> before: "-Creates an XBSA object. This basically tells that storage
> manager to make room for a new backup. The storage manager passes back
> the copyid (inside the objectdescriptor) that is the unique identifier
> that onbar uses when it need to get that back/object. ".
>
> What we CAN'T translate is that in the Data Protector runlog we get
> "02:12:22 : (26918): IBK-bsa : [Critical] Unable to create OB2BAR set
> "/itshm/rootdbs/0
> (dbspace)".
> OB2 API error is = 5[0]"
>
> Now, we can't find any reference for the "OB2 API error" - can anyone
> help? What is error 5[0]?
>
> We're pushing the onbar debug level to 9 for the next run, should be
> fun.............
>
> Puzzled of Kent.
>
What are your settings in your $ONCONFIG for BAR_MAX_BACKUP?
What onbar command are you issuing to backup?
How many dbspaces have you got?
What do Data Protector say :-/
On 24 Nov, 15:23, i...@perrior.net wrote:
> Afternoon all
> IDS 9.30HC5, HP-UX 11i, Data Protector 5.1
>
> We're getting errors on a backup of a test system lately, nothing's
> changed at all recently but the weekly backup is failing with code
> 0x03, which translates (Thanks hugely to Maury Tiller's wonderful
> Informix On-Bar information page) to "BSA_RC_ABORT_SYSTEM_ERROR".
>
> bar_act.log shows us "XBSA Error: BSACreateObject", info from Maury as
> before: "-Creates an XBSA object. This basically tells that storage
> manager to make room for a new backup. The storage manager passes back
> the copyid (inside the objectdescriptor) that is the unique identifier
> that onbar uses when it need to get that back/object. ".
>
> What we CAN'T translate is that in the Data Protector runlog we get
> "02:12:22 : (26918): IBK-bsa : [Critical] Unable to create OB2BAR set
> "/itshm/rootdbs/0
> (dbspace)".
> OB2 API error is = 5[0]"
>
> Now, we can't find any reference for the "OB2 API error" - can anyone
> help? What is error 5[0]?
>
> We're pushing the onbar debug level to 9 for the next run, should be
> fun.............
>
> Puzzled of Kent.
"OB2 API error" would be something specific to Data Protector so read
the DataProtector manuals or raise a support call
with the DataProtector vendor.
On 24 Nov, 15:36, TBP <th...@Usenet-News.Net> wrote:
> i...@perrior.net wrote:
> > Afternoon all
> > IDS 9.30HC5, HP-UX 11i, Data Protector 5.1
>
> > We're getting errors on a backup of a test system lately, nothing's
> > changed at all recently but the weekly backup is failing with code
> > 0x03, which translates (Thanks hugely to Maury Tiller's wonderful
> > Informix On-Bar information page) to "BSA_RC_ABORT_SYSTEM_ERROR".
>
> > bar_act.log shows us "XBSA Error: BSACreateObject", info from Maury as
> > before: "-Creates an XBSA object. This basically tells that storage
> > manager to make room for a new backup. The storage manager passes back
> > the copyid (inside the objectdescriptor) that is the unique identifier
> > that onbar uses when it need to get that back/object. ".
>
> > What we CAN'T translate is that in the Data Protector runlog we get
> > "02:12:22 : (26918): IBK-bsa : [Critical] Unable to create OB2BAR set
> > "/itshm/rootdbs/0
> > (dbspace)".
> > OB2 API error is = 5[0]"
>
> > Now, we can't find any reference for the "OB2 API error" - can anyone
> > help? What is error 5[0]?
>
> > We're pushing the onbar debug level to 9 for the next run, should be
> > fun.............
>
> > Puzzled of Kent.
>
> What are your settings in your $ONCONFIG for BAR_MAX_BACKUP?
> What onbar command are you issuing to backup?
> How many dbspaces have you got?
> What do Data Protector say :-/
BAR_MAX_BACKUP is 0 but that's irrelevant because the backup command
is wholesystem (-b -w -L 0); we have 30 dbspaces but the failure mode
is always a timeout from Data Protector after receiving the request
for the first (always rootdbs). We have another similar instance on
the same machine with a near-identical backup strategy (all that's
different is the instance name and related info) which always works.
I have spent some time trawling round the HP support pages for Data
Protector and found nothing, next stage is a support call but being as
we practise apartheid here between the IT team (including me as DBA)
and the Unix boys (who control anything to do with the backups and
Data Protector etc) that's gonna generate several days frustration and
communication path issues!
More anon.....
We had On-Bar, too, but later switched to cold backups of all chunk
files because it was more reliable and easy to maintain. If your
backups have to be "hot" then ontape, dbexport or onunload might suit
your needs.
But if you are going to stay with On-Bar, here are some things to
check:
1. Are the identifiers truly unique? Check the source vs. target's
identifier lists.
2. Is the error message correct? Maybe the target location is full,
etc.
3. Are you sure nothing has changed? Maybe an operating system
patch, etc.
4. Is the setup correct? Double check everything on Informix & Data
Protector.
5. Call Data Protector support. The problem is usually NOT informix.
-L.S.
"LIGHT SCANS" <light_scans@yahoo.com> wrote in message
news:2d2707e5-2e14-4d91-bccc-61631f178bba@w35g2000yqm.googlegroups.com...
> We had On-Bar, too, but later switched to cold backups of all chunk
> files because it was more reliable and easy to maintain. If your
> backups have to be "hot" then ontape, dbexport or onunload might suit
> your needs.
In what way is a dbexport a "hot" backup of a database?
And in what way does onunload provide a consistent database image suitable
for restoring?
On 25 Nov, 20:54, LIGHT SCANS <light_sc...@yahoo.com> wrote:
> We had On-Bar, too, but later switched to cold backups of all chunk
> files because it was more reliable and easy to maintain. If your
> backups have to be "hot" then ontape, dbexport or onunload might suit
> your needs.
>
> But if you are going to stay with On-Bar, here are some things to
> check:
> 1. Are the identifiers truly unique? Check the source vs. target's
> identifier lists.
> 2. Is the error message correct? Maybe the target location is full,
> etc.
> 3. Are you sure nothing has changed? Maybe an operating system
> patch, etc.
> 4. Is the setup correct? Double check everything on Informix & Data
> Protector.
> 5. Call Data Protector support. The problem is usually NOT informix.
>
> -L.S.
In our 8 years of using OnBar via HP's Omniback (now Data Protector),
the problem is NEVER with Informix..........
Nothing's changed at the database server end whatsoever so once again
whatever the Unix bods have done behind their Iron Curtain is
suspected.They of course differ in their assessment but they would say
that, wouldn't they.
We are a 24-hours-per-day OLTP system so other options are not viable,
thanks anyway!
Neil is right. The "onmode -c block/unblock" logic is needed. Just
brainstorm and you will probably come up with something.
But since you need a backup method for a 24-hour OLTP system, I would
recommend snap, ontape, HDR, ER or OnBar. Again, brainstorm around
any shortcomings.
Otherwise call HP Data Potector support and have them talk to their
own unix people. That ought to get your unix people's attention!