After much gnashing of teeth we got the archive to work.
Now we find that logical logs fail. Running onbar -b -l works fine,
running onmode -l fails. It gets a BSACreateObject error with a return
code of 3.
There were no configuration changes in onconfig or anywhere else.
The BAR_BSALIB_PATH is set to /usr/lib/sparcv9/ibsad001.so
We have also turned on BAR_DEBUG but haven't seen anything.
The Commvault staff are "working" on it.
Anyone have any suggestions
Thanks
Doug McAllister.
Err... onmode -l? This "just" moves to another log... Do you have the
ALARMPROGRAM configured to do automatic backup? Don't you have to change
anything in it's environment to work with the new storage manager?
Regards.
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
> >
> > We have also turned on BAR_DEBUG but haven't seen anything.
> >
> > The Commvault staff are "working" on it.
> >
> > Anyone have any suggestions
> >
> > Thanks
> >
> > Doug McAllister.
>
> Err... onmode -l? This "just" moves to another log... Do you have the
> ALARMPROGRAM configured to do automatic backup? Don't you have to
> change anything in it's environment to work with the new storage
> manager?
>
> Regards.
--
Andreas Breitfeld; Informix Development Munich
IBM Deutschland GmbH; Vorsitzender des Aufsichtsrats: Hans Ulrich
Maerki; Geschäftsführung: Martin Jetter (Vorsitzender), Rudolf Bauer,
Christian Diedrich, Christoph Grandpierre, Matthias Hartmann, Thomas
Fell, Michael Diemer; Sitz der Gesellschaft: Stuttgart;
Registergericht: Amtsgericht Stuttgart, HRB 14562 WEEE-Reg.-Nr. DE
99369940
I think Fernando has a point. :)
The difference when doing "onmode -l" is that it triggers
the IDS server to execute the ALARMPROGRAM, which then
in turn executes the log backup command "onbar -b -l".
For that reason the environment (i.e. settings of environment
variables) usually is different.
I don't know Commvault SM, but e.g. with some other SM
I saw that environment settings influence how the SM works.
And this caused some pain.
Another difference can be the userid, with which the command
"onbar -b -l" is executed. When run via the ALARMPROGRAM,
I think "onbar -b -l" will be executed as user "informix". Usually
this should not cause XBSA or SM errors, but again I don't
know the Commvault SM.
Is return code 3 really the return directly from the function
BSACreateObject() (as seen in the BAR debug log, i.e. not
mapped from something else)?
Then it means "system error" - which of course can have
many causes. In this case it may be helpful to have some
tracing inside the XBSA library and possibly from the
Commvault SM itself.
>The BAR_BSALIB_PATH is set to /usr/lib/sparcv9/ibsad001.so
This somehow "disturbs" me a bit.
It looks very much like the default XBSA library that we ship
with IDS and that is good for the ISM.
It would surprise me if this really works for this Commvault SM.
I thought they would have to supply their own XBSA lib, no?
Also the path seems to hint, that this either is an old IDS version
(9.40 or older?) or at least the configuration stems from an old
IDS version. In newer versions, this XBSA library would be
located in directory "$INFORMIXDIR/lib".
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland GmbH
Chairman of the Supervisory Board: Hans Ulrich Märki
Board of Management: Martin Jetter (Chairman), Rudolf Bauer, Christian
Diedrich, Christoph Grandpierre, Matthias Hartmann, Thomas Fell, Michael
Diemer
Corporate Seat: Stuttgart, Germany; Reg.-Gericht: Amtsgericht Stuttgart,
HRB-Nr.: 14 562 WEEE-Reg.-Nr. DE 99369940
> _______________________________________________
> Informix-list mailing list
> Inform...@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
I am backing up 9.40.FC8 (Solaris 8) to Commvault without issues. My
BAR_BSALIB_PATH is set as above, but /usr/lib/sparcv9/ibsad001.so is
simply a link to /opt/galaxy/Base64/ibsad001.so. So yes - Commvault
has their own XBSA library.
The one issue I have is on a Solaris Veritas clustering box. Informix
is running in a virtual machine, and when I do command line log
backups (onbar -b -l from log_full.sh), Commvault somehow gets
confused between the physical and virtual ip addresses and errors
out. So I am forced to schedule hourly log backups from the Commvault
console... not the most ideal but it works.
My non-virtual servers are working just fine with Commvault (vers 5.9
and now 6.1). Let me know if you want more details of how I have it
setup.
Nick