Oninit cdi / Archive
Talk to an expert →

ONBAR not working

Posted in 2007

Summary

A user setting up ON-Bar with Informix Storage Manager (ISM) on IDS 9.40 under Linux couldn't get disk backups to work: onbar -b -w produced only a zero-byte 'volume' file, then XBSA errors (BSACreateObject system error) and later BAR_TIMEOUT 'Storage Manager may be stalled' warnings. Suggestions included adding devices with ism_add -device ... -type file, using the correct disk pools (ISMDiskData/ISMDiskLogs or ISMData/ISMLogs), checking BAR_BSALIB_PATH, re-initialising /nsr with a clean ism_startup -init script, verifying with ism_show -devices, and raising BAR_DEBUG to 6 to find a non-zero function return. No confirmation of a fix is recorded in the thread.

Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.

Topics: Backup & Restore, Server Administration, Versions, Editions & End-of-Life

GULSHAN KUMAR — — source: IIUG Forums & Mailing Lists

I have IDS 9.40 UC2 on linux. This is the first time i am trying to configure onbar with ISM. I did follow all the steps mentioned in backup and restore pdf. One thing that i need is i need to take the backup on disk, so i have changed the parameters in onconfig file. Please see below the parameters i have configured for ISM and onbar in onconfig file: ALARMPROGRAM /software/ids/etc/log_full.sh TAPEDEV /informix_backup/data LTAPEDEV /informix_backup/logs BAR_ACT_LOG /software/ids/logs/bar_act.log BAR_DEBUG_LOG /software/ids/logs/bar_dbug.log BAR_MAX_BACKUP 0 BAR_RETRY 1 BAR_NB_XPORT_COUNT 10 BAR_XFER_BUF_SIZE 31 RESTARTABLE_RESTORE on BAR_PROGRESS_FREQ 0 BAR_BSALIB_PATH /usr/lib/ibsad001.so BAR_WORKER_MAX 1ISM_DATA_POOL ISMData ISM_LOG_POOL ISMLogs I have followed the below commands for the through root: 1. ./ism_startup -init 2. mkdir /informix_backup cd /informix_backup mkdir data logs Change the user and group to informix for the above directories. 3. Added a volume; ./ism_op -label /informix_backup/data -pool ISMData -volume ISMData001 ./ism_op -label /informix_backup/logs -pool ISMLogs -volume ISMLogs001 ./ism_op -mount /informix_backup/data ./ism_op -mount /informix_backup/logs Now when i am trying to take the backup through onbar -b -w command then it is not creating any file at /informix_backup/data directory. Even it is not showing any error. Please suggest if anything missing and how can i crosscheck that whether Informix Storage Manager (ISM) is configured correctly and onbar is also configured correctly. Thanks Gulshan

↪ replying to GULSHAN KUMAR
Veronica Gomes — — source: IIUG Forums & Mailing Lists

Hello, From the ism commands below, we cannot tell what type of ISM device is this one (tape or file?). I think that, one of the steps missing here, before labeling the ISM device, is to add the device and indicate its type (file, in this case?), using the 'ism_add -device' command. This article explains all the steps for setting up the ISM on Unix the first time, and provides examples: Setting up Informix Storage Manager (ISM) on UNIX http://www-1.ibm.com/support/docview.wss?uid=swg21105298 Hope this helps! Regards, Veronica. > To: ids@iiug.org > From: gulshank@infotechsw.com > Subject: ONBAR not working [10408] > Date: Mon, 19 Nov 2007 07:04:19 -0500 > > I have IDS 9.40 UC2 on linux. This is the first time i am trying to configure > onbar with ISM. I did follow all the steps mentioned in backup and restore > pdf. > One thing that i need is i need to take the backup on disk, so i have changed > the parameters in onconfig file. > Please see below the parameters i have configured for ISM and onbar in > onconfig file: > > ALARMPROGRAM /software/ids/etc/log_full.sh > TAPEDEV /informix_backup/data > LTAPEDEV /informix_backup/logs > BAR_ACT_LOG /software/ids/logs/bar_act.log > BAR_DEBUG_LOG /software/ids/logs/bar_dbug.log > BAR_MAX_BACKUP 0 > BAR_RETRY 1 > BAR_NB_XPORT_COUNT 10 > BAR_XFER_BUF_SIZE 31 > RESTARTABLE_RESTORE on > BAR_PROGRESS_FREQ 0 > BAR_BSALIB_PATH /usr/lib/ibsad001.so > BAR_WORKER_MAX 1> ISM_DATA_POOL ISMData > ISM_LOG_POOL ISMLogs > > I have followed the below commands for the through root: > > 1. ./ism_startup -init > 2. mkdir /informix_backup > cd /informix_backup > mkdir data logs > Change the user and group to informix for the above directories. > 3. Added a volume; > ../ism_op -label /informix_backup/data -pool ISMData -volume ISMData001 > ../ism_op -label /informix_backup/logs -pool ISMLogs -volume ISMLogs001 > > ../ism_op -mount /informix_backup/data > ../ism_op -mount /informix_backup/logs > > Now when i am trying to take the backup through onbar -b -w command then it is > not creating any file at /informix_backup/data directory. Even it is not > showing any error. > > Please suggest if anything missing and how can i crosscheck that whether > Informix Storage Manager (ISM) is configured correctly and onbar is also > configured correctly. > > Thanks > Gulshan > > > ******************************************************************************* > Forum Note: Use 'Reply' to post a response in the discussion forum. > _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

↪ replying to Veronica Gomes
GULSHAN KUMAR — — source: IIUG Forums & Mailing Lists

I forgot to mentioned the two more commands that i followed: ./ism_add -admin informix@test ./ism_add -device /informix_backup/data -type file ./ism_add -device /informix_backup/logs -type file After running the onbar -b -l -c command i have checked at the below path: cd /informix_backup/data and found that there is one file with the name volume created with read-write permission and having "Zero bytes size" Please suggest Thanks Gulshan

↪ replying to Veronica Gomes
Andreas.KUTSCHE@spar.at — — source: IIUG Forums & Mailing Lists

Hi, look at the mentioned document > Setting up Informix Storage Manager (ISM) on UNIX > http://www-1.ibm.com/support/docview.wss?uid=swg21105298 I think you have missed two things: ism_add -device device_name -type Media_type_name AND for backups to disk you have to change the onconfig file: ISM_DATA_POOL ISMDiskData ISM_LOG_POOL ISMDiskLogs Regards, Andreas Kutsche > ------------------------------------------- SPAR Österreichische Warenhandels-AG Hauptzentrale A - 5015 Salzburg, Europastrasse 3 FN 34170 a Tel: +43 662 4470 24223 Mobile: +43 664 6259575 E-Mail: Andreas.KUTSCHE@spar.at Internet: http://www.spar.at Wichtiger Hinweis: Der Inhalt dieser E-Mail kann vertrauliche und rechtlich geschützte Informationen, insbesondere Betriebs- oder Geschäftsgeheimnisse, enthalten, zu deren Geheimhaltung der Empfänger verpflichtet ist. Die Informationen in dieser E-Mail sind ausschließlich für den Adressaten bestimmt. Sollten Sie die E-Mail irrtümlich erhalten haben so ersuchen wir Sie, die Nachricht von Ihrem System zu löschen und sich mit uns in Verbindung zu setzen. Über das Internet versandte E-Mails können leicht manipuliert oder unter fremdem Namen erstellt werden. Daher schließen wir die rechtliche Verbindlichkeit der in dieser Nachricht enthaltenen Informationen aus. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er von uns schriftlich bestätigt und gezeichnet wird. Sollte trotz der von uns verwendeten Virus-Schutzprogramme durch die Zusendung von E-Mails ein Virus in Ihre Systeme gelangen, haften wir nicht für evtl. hieraus entstehende Schäden. Wir danken für Ihr Verständnis. Important notice: The contents of this e-mail may contain confidential and legally protected information that is in particular related to operational and trade secrets, which the recipient is obliged to treat as confidential. The information in this e-mail is made available exclusively for use by the addressee. In the event that the e-mail may have been sent to you in error, we would ask you to kindly delete this communication from your system and to contact us. E-mails sent via the Internet can be easily manipulated or sent out under someone else's name. We therefore do not accept legal liability for the information contained in this communication. The contents of the e-mail are only legally binding if they have been confirmed and signed by us in writing. If, in spite of our using Antivirus protection software, a virus may have penetrated your system through the sending of this e-mail, we do not accept liability for any damage that may possibly arise as a result of this. We trust that you appreciate our position. ------------------------------------------- -----Ursprüngliche Nachricht----- > Von: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] Im Auftrag von > Veronica Gomes > Gesendet: Montag, 19. November 2007 13:20 > An: ids@iiug.org > Betreff: RE: ONBAR not working [10410] > > Hello, > > >From the ism commands below, we cannot tell what type of ISM device is > this > one (tape or file?). I think that, one of the steps missing here, before > labeling the ISM device, is to add the device and indicate its type (file, > in > this case?), using the 'ism_add -device' command. > > This article explains all the steps for setting up the ISM on Unix the > first > time, and provides examples: > > Setting up Informix Storage Manager (ISM) on UNIX > http://www-1.ibm.com/support/docview.wss?uid=swg21105298 > > Hope this helps! > Regards, > Veronica. > > > To: ids@iiug.org > > From: gulshank@infotechsw.com > > Subject: ONBAR not working [10408] > > Date: Mon, 19 Nov 2007 07:04:19 -0500 > > > > I have IDS 9.40 UC2 on linux. This is the first time i am trying to > configure > > onbar with ISM. I did follow all the steps mentioned in backup and > restore > > pdf. > > One thing that i need is i need to take the backup on disk, so i have > changed > > the parameters in onconfig file. > > Please see below the parameters i have configured for ISM and onbar in > > onconfig file: > > > > ALARMPROGRAM /software/ids/etc/log_full.sh > > TAPEDEV /informix_backup/data > > LTAPEDEV /informix_backup/logs > > BAR_ACT_LOG /software/ids/logs/bar_act.log > > BAR_DEBUG_LOG /software/ids/logs/bar_dbug.log > > BAR_MAX_BACKUP 0 > > BAR_RETRY 1 > > BAR_NB_XPORT_COUNT 10 > > BAR_XFER_BUF_SIZE 31 > > RESTARTABLE_RESTORE on > > BAR_PROGRESS_FREQ 0 > > BAR_BSALIB_PATH /usr/lib/ibsad001.so > > BAR_WORKER_MAX 1> > ISM_DATA_POOL ISMData > > ISM_LOG_POOL ISMLogs > > > > I have followed the below commands for the through root: > > > > 1. ./ism_startup -init > > 2. mkdir /informix_backup > > cd /informix_backup > > mkdir data logs > > Change the user and group to informix for the above directories. > > 3. Added a volume; > > ../ism_op -label /informix_backup/data -pool ISMData -volume ISMData001 > > ../ism_op -label /informix_backup/logs -pool ISMLogs -volume ISMLogs001 > > > > ../ism_op -mount /informix_backup/data > > ../ism_op -mount /informix_backup/logs > > > > Now when i am trying to take the backup through onbar -b -w command then > it > is > > not creating any file at /informix_backup/data directory. Even it is not > > showing any error. > > > > Please suggest if anything missing and how can i crosscheck that whether > > Informix Storage Manager (ISM) is configured correctly and onbar is also > > configured correctly. > > > > Thanks > > Gulshan > > > > > > > ************************************************************************** > ***** > > Forum Note: Use 'Reply' to post a response in the discussion forum. > > > > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's FREE! > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > > ************************************************************************** > ***** > Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Andreas.KUTSCHE@spar.at
GULSHAN KUMAR — — source: IIUG Forums & Mailing Lists

I have changed the parameters in onconfig file: ISM_DATA_POOL ISMDiskData ISM_LOG_POOL ISMDiskLogs and run the below command ./ism_op -label /informix_backup/data -pool ISMDiskData -volume ISMDiskData001 ./ism_op -label /informix_backup/logs -pool ISMdISKlOGS -VOLUME ismdISKlOGS001 ./ism_op -mount /informix_backup/data ./ism_op -mount /informix_backup/logs Then i shutdown and start the ISM: ./ism_shutdown ./ism_startup Then i run the below command for testing: onbar -b -w then i checked the output in /informix_backup/data directory: [informix@test data]$ pwd /informix_backup/data [informix@test data]$ ls -la total 12 drwxrwxr-x 2 informix informix 4096 Nov 19 17:48 . drwxr-xr-x 4 informix informix 4096 Nov 19 16:49 .. -rw------- 1 root root 47 Nov 19 17:48 .nsr -rw------- 1 root root 0 Nov 19 17:48 volume Please suggest the same as still i am not able to take the backup. Thanks Gulshan

↪ replying to GULSHAN KUMAR
Andreas Breitfeld — — source: IIUG Forums & Mailing Lists

On Tuesday 20 November 2007 06:23, GULSHAN KUMAR wrote: > I have changed the parameters in onconfig file: > > ISM_DATA_POOL ISMDiskData > ISM_LOG_POOL ISMDiskLogs > > and run the below command > > ../ism_op -label /informix_backup/data -pool ISMDiskData -volume > ISMDiskData001 > ../ism_op -label /informix_backup/logs -pool ISMdISKlOGS -VOLUME > ismdISKlOGS001 > ../ism_op -mount /informix_backup/data > ../ism_op -mount /informix_backup/logs > > Then i shutdown and start the ISM: > > ../ism_shutdown > > ../ism_startup > > Then i run the below command for testing: > > onbar -b -w> > then i checked the output in /informix_backup/data directory: > > [informix@test data]$ pwd > /informix_backup/data > [informix@test data]$ ls -la > total 12 > drwxrwxr-x 2 informix informix 4096 Nov 19 17:48 . > drwxr-xr-x 4 informix informix 4096 Nov 19 16:49 .. > -rw------- 1 root root 47 Nov 19 17:48 .nsr > -rw------- 1 root root 0 Nov 19 17:48 volume > > Please suggest the same as still i am not able to take the backup. Whats printed in your BAR_ACT_LOG /software/ids/logs/bar_act.log ? Andreas > > Thanks > Gulshan > > > ********************************************************************* >********** Forum Note: Use "Reply" to post a response in the > discussion forum. -- 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

↪ replying to GULSHAN KUMAR
GULSHAN KUMAR — — source: IIUG Forums & Mailing Lists

The below error found in /software/ids/logs/bar_act.log file 2007-11-21 17:11:58 4568 4566 /software/ids/bin/onbar_d -b -w 2007-11-21 17:11:59 4568 4566 Begin level 0 backup rootdbs. 2007-11-21 17:11:59 4568 4566 Successfully connected to Storage Manager. 2007-11-21 17:12:19 4568 4566 XBSA Error: (BSACreateObject) A system error occurred. Aborting XBSA session. 2007-11-21 17:12:30 4568 4566 /software/ids/bin/onbar_d complete, returning 3 (0x03) And the below are the contents of online.log file 17:11:59 Maximum server connections 0 17:11:59 Level 0 Archive started on rootdbs, dbs01, llogdbs01, plogdbs01, dbs02, dbs03 17:12:20 Archive on rootdbs, dbs01, llogdbs01, plogdbs01, dbs02, dbs03 ABORTED. 17:12:20 Aborted by client. 17:17:19 Fuzzy Checkpoint Completed: duration was 0 seconds, 1 buffers not flushed, timestamp: 172449003. 17:17:19 Checkpoint loguniq 61, logpos 0x1904c, timestamp: 172449003 17:17:19 Maximum server connections 0 I have checked on google and found a document and then i followed the below steps: 1. ./ism_shutdown 2. mv /nsr/index/tifetl/db /nsr/index/tifetl/db.old 3. ./ism_start 4. ./nsrck -c test 5. onbar -b -w But still the result is same. Please suggest. Thanks Gulshan

↪ replying to GULSHAN KUMAR
Shweta Sinha — — source: IIUG Forums & Mailing Lists

Generally this "XBSA error" comes when BAR_BSA_LIB is not set properly in ur config file.Just check it once and set it to $INFORMIXDIR/lib/libbsa.so .here $INFORMIXDIR means dir where u have installed the IDS. Thanks Shweta "GULSHAN KUMAR" <gulshank@infotechsw.com> Sent by: ids-bounces@iiug.org 11/21/2007 05:26 PM Please respond to ids To ids@iiug.org cc Subject Re: AW: ONBAR not working [10426] The below error found in /software/ids/logs/bar_act.log file 2007-11-21 17:11:58 4568 4566 /software/ids/bin/onbar_d -b -w 2007-11-21 17:11:59 4568 4566 Begin level 0 backup rootdbs. 2007-11-21 17:11:59 4568 4566 Successfully connected to Storage Manager. 2007-11-21 17:12:19 4568 4566 XBSA Error: (BSACreateObject) A system error occurred. Aborting XBSA session. 2007-11-21 17:12:30 4568 4566 /software/ids/bin/onbar_d complete, returning 3 (0x03) And the below are the contents of online.log file 17:11:59 Maximum server connections 0 17:11:59 Level 0 Archive started on rootdbs, dbs01, llogdbs01, plogdbs01, dbs02, dbs03 17:12:20 Archive on rootdbs, dbs01, llogdbs01, plogdbs01, dbs02, dbs03 ABORTED. 17:12:20 Aborted by client. 17:17:19 Fuzzy Checkpoint Completed: duration was 0 seconds, 1 buffers not flushed, timestamp: 172449003. 17:17:19 Checkpoint loguniq 61, logpos 0x1904c, timestamp: 172449003 17:17:19 Maximum server connections 0 I have checked on google and found a document and then i followed the below steps: 1. ./ism_shutdown 2. mv /nsr/index/tifetl/db /nsr/index/tifetl/db.old 3. ./ism_start 4. ./nsrck -c test 5. onbar -b -w But still the result is same. Please suggest. Thanks Gulshan ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to Shweta Sinha
GULSHAN KUMAR — — source: IIUG Forums & Mailing Lists

I have set the BAR_BSA_LIB to /software/ids/lib/ibsad001.so. ibsad001.so is a symbolic link of libbsa.so. And also set the below parameters: BAR_DEBUG 4 BAR_DEBUG_LOG /software/ids/logs/bar_dbug.log Now when i run onbar -b -w command. It throws some errors and warnings in logs. The below error are in bar_act.log: 2007-11-22 09:48:50 5361 5359 /software/ids/bin/onbar_d -b -w 2007-11-22 09:48:51 5361 5359 Begin level 0 backup rootdbs. 2007-11-22 09:48:51 5361 5359 Successfully connected to Storage Manager. 2007-11-22 09:58:51 5361 5359 Warning: BAR_TIMEOUT Storage Manager Progress may be stalled. Also the below errors found in bar_debug.log; 2007-11-22 09:48:51 5361 5359 buildObjName: output objectSpaceName /ol_tifetl01, pathName /ol_tifetl01/rootdbs/0 2007-11-22 09:48:51 5361 5359 buildObjName: return 0 (0x00) 2007-11-22 09:48:51 5361 5359 initObjDesc: output: object owner name createTime 2007-11-22 09:48:51 5361 5359 initObjDesc: output: INFORMIX informix /ol_tifetl01 /ol_tifetl01/rootdbs/0 0 0 0 0 0 0 2007-11-22 09:48:51 5361 5359 initObjDesc: output: copytype copyid restoreOrder size resource type status desc objectInfo 2007-11-22 09:48:51 5361 5359 initObjDesc: output: 3 0 0 0 0 0 0 4 2 2007-11-22 09:48:51 5361 5359 initObjDesc: return 2007-11-22 09:48:51 5361 5359 BSACreateObject: enter 2007-11-22 09:48:51 5361 5359 BSACreateObject: object owner name createTime 2007-11-22 09:48:51 5361 5359 BSACreateObject: INFORMIX informix /ol_tifetl01 /ol_tifetl01/rootdbs/0 0 0 0 0 0 0 2007-11-22 09:48:51 5361 5359 BSACreateObject: copytype copyid restoreOrder size resource type status desc objectInfo 2007-11-22 09:48:51 5361 5359 BSACreateObject: 3 0 0 0 0 1 2191728640 R 4 2 2007-11-22 09:50:51 5361 5359 bar_sighdlr: enter 2007-11-22 09:50:51 5361 5359 bar_sighdlr: input signo: 14 2007-11-22 09:50:51 5361 5359 get_pid: enter 2007-11-22 09:50:51 5361 5359 bar_alarm: enter 2007-11-22 09:50:51 5361 5359 bar_alarm: input 120 seconds 2007-11-22 09:50:51 5361 5359 bar_alarm: return 0 (0x00) 2007-11-22 09:50:51 5361 5359 bar_sighdlr: return 2007-11-22 09:52:51 5361 5359 bar_sighdlr: enter 2007-11-22 09:52:51 5361 5359 bar_sighdlr: input signo: 14 2007-11-22 09:52:51 5361 5359 get_pid: enter 2007-11-22 09:52:51 5361 5359 bar_alarm: enter 2007-11-22 09:52:51 5361 5359 bar_alarm: input 120 seconds 2007-11-22 09:52:51 5361 5359 bar_alarm: return 0 (0x00) 2007-11-22 09:52:51 5361 5359 bar_sighdlr: return 2007-11-22 09:54:51 5361 5359 bar_sighdlr: enter 2007-11-22 09:54:51 5361 5359 bar_sighdlr: input signo: 14 I am trying to take the backup on disk but again and again it failed. Please suggest. Thanks Gulshan

↪ replying to GULSHAN KUMAR
Martin Fuerderer — — source: IIUG Forums & Mailing Lists

Hi, a) the onconfig file parameter name is BAR_BSALIB_PATH. Just to make sure that this is not the problem (though I don't think so). b) in the excerpt of bar_dbug.log file that you sent, there is no error contained. Signal 14 (ALARM) is issued three times, but that only means that the timer (set internally by onbar) has expired three times. And this is why in the bar_act.log file you get the message about "SM may be stalled ...". This points to some problem in the SM, possibly a setup/configuration problem. Following is a simple (bare-bones) setup for ISM that I usually do on my development machine: echo "y" | ism_shutdown # in case ISM running rm -rf /nsr/* rm -rf /nsr ism_startup -init ism_add -admin informix@mymachine ism_add -device /work/martinfu/nsr_data -type file ism_add -device /work/martinfu/nsr_logs -type file ism_op -label /work/martinfu/nsr_data -volume data1 -pool ISMData ism_op -label /work/martinfu/nsr_logs -volume logs1 -pool ISMLogs ism_op -mount /work/martinfu/nsr_data ism_op -mount /work/martinfu/nsr_logs This script is to be run as user root. Prerequisite is that the 2 directories /work/martinfu/nsr_data /work/martinfu/nsr_logs exist. After running this script you can do "ism_show -devices" which should show the two devices mounted and writable. In the onconfig file the corresponding settings of the ISM parameters are: ISM_DATA_POOL ISMData ISM_LOG_POOL ISMLogs If this still doesn't work, increase the BAR_DEBUG value to 6 (from currently 4). Then look for a function return other than 0 (zero). That would indicate a real error. 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 ids-bounces@iiug.org wrote on 22.11.2007 05:42:59: > I have set the BAR_BSA_LIB to /software/ids/lib/ibsad001.so. ibsad001.so is a > symbolic link of libbsa.so. And also set the below parameters: > > BAR_DEBUG 4 > BAR_DEBUG_LOG /software/ids/logs/bar_dbug.log> > Now when i run onbar -b -w command. It throws some errors and warnings in > logs. > The below error are in bar_act.log: > > 2007-11-22 09:48:50 5361 5359 /software/ids/bin/onbar_d -b -w > 2007-11-22 09:48:51 5361 5359 Begin level 0 backup rootdbs. > 2007-11-22 09:48:51 5361 5359 Successfully connected to Storage Manager. > 2007-11-22 09:58:51 5361 5359 Warning: BAR_TIMEOUT Storage Manager Progress > may be stalled. > > Also the below errors found in bar_debug.log; > > 2007-11-22 09:48:51 5361 5359 buildObjName: output objectSpaceName > /ol_tifetl01, pathName /ol_tifetl01/rootdbs/0 > 2007-11-22 09:48:51 5361 5359 buildObjName: return 0 (0x00) > 2007-11-22 09:48:51 5361 5359 initObjDesc: output: object owner name > createTime > 2007-11-22 09:48:51 5361 5359 initObjDesc: output: INFORMIX informix > /ol_tifetl01 /ol_tifetl01/rootdbs/0 0 0 0 0 0 0 > 2007-11-22 09:48:51 5361 5359 initObjDesc: output: copytype copyid > restoreOrder size resource type status desc objectInfo > 2007-11-22 09:48:51 5361 5359 initObjDesc: output: 3 0 0 0 0 0 0 4 2 > 2007-11-22 09:48:51 5361 5359 initObjDesc: return > 2007-11-22 09:48:51 5361 5359 BSACreateObject: enter > 2007-11-22 09:48:51 5361 5359 BSACreateObject: object owner name createTime > 2007-11-22 09:48:51 5361 5359 BSACreateObject: INFORMIX informix /ol_tifetl01 > /ol_tifetl01/rootdbs/0 0 0 0 0 0 0 > 2007-11-22 09:48:51 5361 5359 BSACreateObject: copytype copyid restoreOrder > size resource type status desc objectInfo > 2007-11-22 09:48:51 5361 5359 BSACreateObject: 3 0 0 0 0 1 2191728640 R 4 2 > 2007-11-22 09:50:51 5361 5359 bar_sighdlr: enter > 2007-11-22 09:50:51 5361 5359 bar_sighdlr: input signo: 14 > 2007-11-22 09:50:51 5361 5359 get_pid: enter > 2007-11-22 09:50:51 5361 5359 bar_alarm: enter > 2007-11-22 09:50:51 5361 5359 bar_alarm: input 120 seconds > 2007-11-22 09:50:51 5361 5359 bar_alarm: return 0 (0x00) > 2007-11-22 09:50:51 5361 5359 bar_sighdlr: return > 2007-11-22 09:52:51 5361 5359 bar_sighdlr: enter > 2007-11-22 09:52:51 5361 5359 bar_sighdlr: input signo: 14 > 2007-11-22 09:52:51 5361 5359 get_pid: enter > 2007-11-22 09:52:51 5361 5359 bar_alarm: enter > 2007-11-22 09:52:51 5361 5359 bar_alarm: input 120 seconds > 2007-11-22 09:52:51 5361 5359 bar_alarm: return 0 (0x00) > 2007-11-22 09:52:51 5361 5359 bar_sighdlr: return > 2007-11-22 09:54:51 5361 5359 bar_sighdlr: enter > 2007-11-22 09:54:51 5361 5359 bar_sighdlr: input signo: 14 > > I am trying to take the backup on disk but again and again it failed. > Please suggest. > > Thanks > Gulshan > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Glossary