using onbar from two different instances

Hello, we have a configuration problem with automatic logical log backup (using alarmprogram.sh). We have a cluster (2 nodes) and on node1 -> IDS 9.40, on node2 -> IDS 10.00, (this one recently installed). Backup Server is Netbackup 5.1 is installed on a 3rd machine. The problem comes when a logical log fills and the alarmprogram.sh launches a backup, or either when we launch an onbar -b -l manually: the bar_act.log reports: 2008-02-14 13:20:18 2280 2278 /opt/informix_2/bin/onbar_d -b -l 2008-02-14 13:20:19 2280 2278 Working with veritas-netbackup as generic storage manager. 2008-02-14 13:20:19 2280 2278 Begin backup logical log 32. 2008-02-14 13:20:19 2280 2278 Successfully connected to Storage Manager. but we get a timeout. The Netbackup Server logs report that it is trying to perform a logical log backup from IDS9.40 which is on node1, although the backup was launched from node2 with IDS10.00. Because both informix installations can be on either node1 or node2, on both we define 2 different $INFORMIXDIR, each with a different bp.conf file (specific for Netbackup). On the other hand, the daily backup (launched from Netbackup server using a defined policy) works fine. I'm pretty sure it has something to do with environment variables, but we cannot find the right configuration. Any clues? Thanks in advance.

Hi, if I re-call correctly it is (Veritas) Netbackup that requires an environment variable to be set to determine the destination pool for the backup objects. Usually this is different for dbspaces and logs. So maybe that setting for the log backup is missing on the second node? Unfortunately I don't recall what the name of this environment variable is ... :-( 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), Christian Diedrich, Matthias Hartmann, Thomas Fell, Christoph Grandpierre, 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 14.02.2008 13:39:45: > Hello, > we have a configuration problem with automatic logical log backup (using > alarmprogram.sh). We have a cluster (2 nodes) and on node1 -> IDS 9.40, on > node2 -> IDS 10.00, (this one recently installed). Backup Server is Netbackup > 5.1 is installed on a 3rd machine. > The problem comes when a logical log fills and the alarmprogram.sh launches a > backup, or either when we launch an onbar -b -l manually: the bar_act.log > reports: > 2008-02-14 13:20:18 2280 2278 /opt/informix_2/bin/onbar_d -b -l > 2008-02-14 13:20:19 2280 2278 Working with veritas-netbackup as generic > storage manager. > 2008-02-14 13:20:19 2280 2278 Begin backup logical log 32. > 2008-02-14 13:20:19 2280 2278 Successfully connected to Storage Manager. > > but we get a timeout. The Netbackup Server logs report that it is trying to > perform a logical log backup from IDS9.40 which is on node1, although the > backup was launched from node2 with IDS10.00. > Because both informix installations can be on either node1 or node2, on both > we define 2 different $INFORMIXDIR, each with a different bp.conf file > (specific for Netbackup). > On the other hand, the daily backup (launched from Netbackup server using a > defined policy) works fine. > I'm pretty sure it has something to do with environment variables, but we > cannot find the right configuration. Any clues? > Thanks in advance. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > See you at the IIUG Informix 2008 Conference > The Power Conference for Informix Professionals > April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas > http://www.iiug.org/conf > Registration Now Open!!

Hi guys... My buddy Martin is correct.... Environment, environment, environment... Here is some information from my environment that you may find helpful. I am on solaris 9, with IDS 9.4, and netbackup (forgot version). Our netbackup is on a separate machine. Netbackup does have to handshake with multiple informix engines on the same server. The informix environment variables important to netbackup are, for example, from my SAP TRG system: NFXBSA_SERVER=3Dsapbkup INFXBSA_POLICY=3Dsaptrg_trg_onbar0_ifmx INFXBSA_SCHED=3Dtrg_dbspaces INFXBSA_LOGICAL_POLICY=3Dsaptrg_trg_dblogs_ifmx INFXBSA_LOGICAL_SCHED=3Dtrg_dblogs INFXBSA_CLIENT=3Dsaptrg I do not have a bp.conf file in my informix directories (home or otherwise). In other words, I do not override the default netbackup bp.conf file in /usr/openv/netbackup. My bp.conf file from /user/openv/netbackup is as follows.... Notice it has multiple clients in it because it is supporting multiple logical systems on one server. =20 Actual unix server name is sap46 this is how netbackup sees the server for unix level file backups. =20 The handshake between netbackup and informix TRG database on this server goes through client name "saptrg". The handshake between netbackup and informix QA2 database on this server goes through client name "sapqa2". sap46% cat bp.confSERVER =3D sapbkup SERVER =3D sapbkup2 SERVER =3D hsapbkup SERVER =3D backup1 SERVER =3D ebackup01 SERVER =3D ilnv3w80562d SERVER =3D usnvw330359d SERVER =3D usnvw310177d SERVER =3D usnvw32s3brd SERVER =3D usnvw37z3brd VERBOSE =3D 0 #VERBOSE =3D 5 CLIENT_READ_TIMEOUT =3D 2100 CLIENT_NAME =3D saptrg CLIENT_NAME =3D sapqa2 CLIENT_NAME =3D sap46 Hopefully this information helps you see your missing piece or prompt you to provide more info/ask more questions. Thanks, Norma Jean Sebastian =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Sorry for the messy previous post...Sometimes "plain text" posts nicely, sometimes not. Anyway, you can contact me directly regarding this netbackup/informix issue or the least ignore the "3D" and "=3D20" characters that are seen in posted message but not part of what I sent. Sorry for the mess. Norma Jean > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On=20 > Behalf Of Sebastian, Norma J. > Sent: Thursday, February 14, 2008 9:04 AM > To: ids@iiug.org > Subject: RE: using onbar from two different instances [11311] >=20 > Hi guys...=20 >=20 > My buddy Martin is correct.... Environment, environment,=20 > environment...=20 >=20 > Here is some information from my environment that you may=20 > find helpful.=20 > I am on solaris 9, with IDS 9.4, and netbackup (forgot version). Our=20 > netbackup is on a separate machine. Netbackup does have to handshake=20 > with multiple informix engines on the same server.=20 >=20 > The informix environment variables important to netbackup are, for=20 > example, from my SAP TRG system:=20 >=20 > NFXBSA_SERVER=3D3Dsapbkup=20 > INFXBSA_POLICY=3D3Dsaptrg_trg_onbar0_ifmx=20 > INFXBSA_SCHED=3D3Dtrg_dbspaces=20 > INFXBSA_LOGICAL_POLICY=3D3Dsaptrg_trg_dblogs_ifmx=20 > INFXBSA_LOGICAL_SCHED=3D3Dtrg_dblogs=20 > INFXBSA_CLIENT=3D3Dsaptrg=20 >=20 > I do not have a bp.conf file in my informix directories (home or=20 > otherwise). In other words, I do not override the default netbackup=20 > bp.conf file in /usr/openv/netbackup.=20 > My bp.conf file from /user/openv/netbackup is as follows....=20 > Notice it=20 > has multiple clients in it because it is supporting multiple logical=20 > systems on one server. =3D20=20 > Actual unix server name is sap46 this is how netbackup sees=20 > the server=20 > for unix level file backups. =3D20=20 > The handshake between netbackup and informix TRG database on=20 > this server=20 > goes through client name "saptrg". The handshake between=20 > netbackup and=20 > informix QA2 database on this server goes through client name=20 > "sapqa2".=20 >=20 > sap46% cat bp.conf=20> SERVER =3D3D sapbkup=20 > SERVER =3D3D sapbkup2=20 > SERVER =3D3D hsapbkup=20 > SERVER =3D3D backup1=20 > SERVER =3D3D ebackup01=20 > SERVER =3D3D ilnv3w80562d=20 > SERVER =3D3D usnvw330359d=20 > SERVER =3D3D usnvw310177d=20 > SERVER =3D3D usnvw32s3brd=20 > SERVER =3D3D usnvw37z3brd=20 > VERBOSE =3D3D 0=20 > #VERBOSE =3D3D 5=20 > CLIENT_READ_TIMEOUT =3D3D 2100=20 > CLIENT_NAME =3D3D saptrg=20 > CLIENT_NAME =3D3D sapqa2=20 > CLIENT_NAME =3D3D sap46=20 >=20 > Hopefully this information helps you see your missing piece or prompt=20 > you to provide more info/ask more questions.=20 > Thanks,=20 > Norma Jean Sebastian=20 > =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3 > D=3D3D=3D3D=3D3D=3D3D=3D=20 > =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3 > D=3D3D=3D3D=3D3D=3D3D=3D=20 > =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=20 > The information contained in this message may be privileged=20 > and confidential and protected from disclosure. If the reader=20 > of this message is not the intended recipient, or an employee=20 > or agent responsible for delivering this message to the=20 > intended recipient, you are hereby notified that any reproduction,=20 > dissemination or distribution of this communication is strictly=20 > prohibited. If you have received this communication in error,=20 > please notify us immediately by replying to the message and=20 > deleting it from your computer. Thank you. Tellabs=20 > =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3 > D=3D3D=3D3D=3D3D=3D3D=3D=20 > =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D= 3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3 > D=3D3D=3D3D=3D3D=3D3D=3D=20 > =3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=3D3D=20 >=20 >=20 > ************************************************************** > *****************=20 > Forum Note: Use "Reply" to post a response in the discussion forum.=20 >=20 > See you at the IIUG Informix 2008 Conference > The Power Conference for Informix Professionals > April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas > http://www.iiug.org/conf > Registration Now Open!!=20 >=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Hi, thanks a lot for the clues, we almost got the answer: if fact, there're 2 bp.conf files on each node: one in the $INFORMIXDIR, an a second one on / directory (don't ask me why), which is identical (in the case that only one INFORMIXDIR is needed), to the one on INFORMIXDIR. But the point is, we found out today while we were configuring a different 3-node cluster, that the bp.conf file must go on / directory; we placed it firstly in the $INFORMIXDIR (there we got only one IDS installed, so only one INFORMIXDIR is needed), and forcing an onbar -b -l by doing: onmode -l (option: next log)so alarmprogram.sh lanuches the backup, but it failed ...until we placed the bp.conf file in /. In fact, the bp.conf file in INFORMIXDIR is not needed, not even read (we removed it and it still worked). Unfortunately, this seems to makes the desired solution quite impossible: having two different IDS installed that can work on either cluster-node if needed, which do launch automatic logical log backups through the alarmprogram.sh connecting to the same backup-server (using Netbackup). We still haven't tried out the points you stated: the specific environment variables and tuning the bp.conf file on /usr/openv/netbackup, but we will soon. Thannks, and regards. Gerardo Padierna

Gerardo, That's good news. Keep testing. I bet the extra bp.conf was from someone's attempt to override the netbackup bp.conf file. This can be done (the override). I am currently doing bp.conf overrides on db2, and I know I did it for informix/netbackup as well. I had to override the bp.conf file for informix every time I did a DB refresh from, for example, production to a test system (in netbackup terms an "alternate client restore"). What you desire can be done with informix and netbackup. You may have to get the bp.conf override file in the right location, meaning a directory that swings with your database if it changes nodes. If you are certain your "local informix" bp.conf needs to go in /, perhaps you can change it to be a LINK to the bp.conf in your $INFORMIXDIR, that way the /bp.conf link will point to whatever active informix is on the node?.... Just some thinking off the top of my tired brain.... I will try to find the documentation I have for this (some homemade doc), it may help. If I forget, please remind me on Monday/Tuesday. Good luck, Norma Jean -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of GERARDO PADIERNA Sent: Friday, February 15, 2008 4:15 AM To: ids@iiug.org Subject: Re: RE: using onbar from two different instances [11322] Hi,=20 thanks a lot for the clues, we almost got the answer:=20 if fact, there're 2 bp.conf files on each node: one in the $INFORMIXDIR, an a=20 second one on / directory (don't ask me why), which is identical (in the case=20 that only one INFORMIXDIR is needed), to the one on INFORMIXDIR. But the point=20 is, we found out today while we were configuring a different 3-node cluster,=20 that the bp.conf file must go on / directory; we placed it firstly in the=20 $INFORMIXDIR (there we got only one IDS installed, so only one INFORMIXDIR is=20 needed), and forcing an onbar -b -l by doing:=20 onmode -l (option: next log)=20so alarmprogram.sh lanuches the backup, but it failed ...until we placed the=20 bp.conf file in /. In fact, the bp.conf file in INFORMIXDIR is not needed, not=20 even read (we removed it and it still worked).=20 Unfortunately, this seems to makes the desired solution quite impossible:=20 having two different IDS installed that can work on either cluster-node if=20 needed, which do launch automatic logical log backups through the=20 alarmprogram.sh connecting to the same backup-server (using Netbackup).=20 We still haven't tried out the points you stated: the specific environment=20 variables and tuning the bp.conf file on /usr/openv/netbackup, but we will=20 soon.=20 Thannks, and regards.=20 Gerardo Padierna=20 ************************************************************************ *******=20 Forum Note: Use "Reply" to post a response in the discussion forum.=20 See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!!=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

We got it! Thanks a lot Norma J. Sebastian, we followed your indications about the bp.conf file and included some lines identifying the possible clients and that's it! Befere the changes, our bp.conf file in / was just the three lines from our first IDS installation/instance: SERVER = pessback-gestion CLIENT_NAME = pessids-gestion REQUIRED_INTERFACE = pessids-gestion We added some lines identifying the second backup client, which has the hostname 'pessids2-gestion': SERVER = pessback-gestion CLIENT_NAME = pessids-gestion CLIENT_NAME = pessids2-gestion REQUIRED_INTERFACE = pessids-gestion REQUIRED_INTERFACE = pessids2-gestion and now it works. I'm still wondering why it doesn't work at all if we place just a bp.conf file in the INFORXDIR, for it is quite contrary to what is stated in the Netbackup documentation for the 5.1 version. This second instance is still not in production, but it will be from tomorrow on (it there're no last minunte changes ;)) so thanks a lot for the fast answering!! Regards

We got it! Thanks a lot Norma J. Sebastian, we followed your indications about the bp.conf file and included some lines identifying the possible clients and that's it! Before the changes, our bp.conf file in / was just the three lines from our first IDS installation/instance: SERVER = pessback-gestion CLIENT_NAME = pessids-gestion REQUIRED_INTERFACE = pessids-gestion We added some lines identifying the second backup client, which has the hostname 'pessids2-gestion': SERVER = pessback-gestion CLIENT_NAME = pessids-gestion CLIENT_NAME = pessids2-gestion REQUIRED_INTERFACE = pessids-gestion REQUIRED_INTERFACE = pessids2-gestion and now it works. I'm still wondering why it doesn't work at all if we place just a bp.conf file in the INFORXDIR, for it is quite contrary to what is stated in the Netbackup documentation for the 5.1 version. This second instance is still not in production, but it will be from tomorrow on (if there're no last minute changes ;)) so thanks a lot for the fast answering!! Regards

Gerardo, That is awesome news! You may need to put in a support ticket with netbackup to understand why their documentation is not working with regards to the bp.conf file in INFORMIXDIR. I can add that when we do a netbackup "alternate client restore", we change the INFXBSA_CLIENT informix environment variable. I thought perhaps we had to play with bp.conf, but we don't. Once you get it working, it just keeps working :) I wish I could say the same for DB2/netbackup (I am currently "learning" my way through that relationship). Enjoy, Norma Jean -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of GERARDO PADIERNA Sent: Monday, February 18, 2008 12:33 PM To: ids@iiug.org Subject: Re: RE: RE: using onbar from two different instanc [11326] We got it! Thanks a lot Norma J. Sebastian, we followed your indications about the bp.conf file and included some lines identifying the possible clients and that's it! Before the changes, our bp.conf file in / was just the three lines from our first IDS installation/instance: SERVER = pessback-gestion CLIENT_NAME = pessids-gestion REQUIRED_INTERFACE = pessids-gestion We added some lines identifying the second backup client, which has the hostname 'pessids2-gestion': SERVER = pessback-gestion CLIENT_NAME = pessids-gestion CLIENT_NAME = pessids2-gestion REQUIRED_INTERFACE = pessids-gestion REQUIRED_INTERFACE = pessids2-gestion and now it works. I'm still wondering why it doesn't work at all if we place just a bp.conf file in the INFORXDIR, for it is quite contrary to what is stated in the Netbackup documentation for the 5.1 version. This second instance is still not in production, but it will be from tomorrow on (if there're no last minute changes ;)) so thanks a lot for the fast answering!! Regards ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum. See you at the IIUG Informix 2008 Conference The Power Conference for Informix Professionals April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas http://www.iiug.org/conf Registration Now Open!! ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================