BAR_MAX_BACKUP - not spawning parallel threads

Version : 10 We are running onbar -b -l with BAR_MAX_BACKUP = 4 and BAR_NB_XPORT_COUNT = 10. But when I check the number of onbar process I just see one onbar_d process. I was expecting atleast 4 processes. Why is it just spawning one process. Is it because our SHMTOTAL is 0.

> Version : 10 > > We are running onbar -b -l with BAR_MAX_BACKUP = 4 and > BAR_NB_XPORT_COUNT = 10. But when I check the number of onbar process > I just see one onbar_d process. I was expecting atleast 4 processes. > Why is it just spawning one process. Is it because our SHMTOTAL is 0. > I don't think BAR_MAX_BACKUP effects the number of backup threads for the logical logs which are backed up one at a time. You should see multiple onbar_d processes when you execute a level 0, 1 or 2 backup. Andrew

On Aug 15, 9:05 pm, "Andrew Ford" <af...@networkip.net> wrote: > > Version : 10 > > > We are running onbar -b -l with BAR_MAX_BACKUP = 4 and > > BAR_NB_XPORT_COUNT = 10. But when I check the number of onbar process > > I just see one onbar_d process. I was expecting atleast 4 processes. > > Why is it just spawning one process. Is it because our SHMTOTAL is 0. > > I don't think BAR_MAX_BACKUP effects the number of backup threads for the > logical logs which are backed up one at a time. > > You should see multiple onbar_d processes when you execute a level 0, 1 or 2 > backup. > > Andrew I think onbar -b -l just does backup of full logical log. It doesn't do who system backup which is done serially. I would expect multiple onbad_d processes for full logical log backup.

Hi, no. Andrew is right. Log backup is a serial operation. Log files fill serially and therefore they are backed up serially. If you set ALARMPROGRAM in the onconfig file so that logs get backed up as soon as the are closed (full or not full), then this will work fine (in most cases). If your log backup is so slow that it cannot keep up with logs filling, then you have to see, how to fix the bottle neck (usually slow I/O on the tape device). Parallel operation is done only for backup of dbspaces. 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-bounces@iiug.org wrote on 16.08.2007 18:29:07: > On Aug 15, 9:05 pm, "Andrew Ford" <af...@networkip.net> wrote: > > > Version : 10 > > > > > We are running onbar -b -l with BAR_MAX_BACKUP = 4 and > > > BAR_NB_XPORT_COUNT = 10. But when I check the number of onbar process > > > I just see one onbar_d process. I was expecting atleast 4 processes. > > > Why is it just spawning one process. Is it because our SHMTOTAL is 0. > > > > I don't think BAR_MAX_BACKUP effects the number of backup threads for the > > logical logs which are backed up one at a time. > > > > You should see multiple onbar_d processes when you execute a level 0, 1 or 2 > > backup. > > > > Andrew > > I think onbar -b -l just does backup of full logical log. It doesn't > do who system backup which is done serially. I would expect multiple > onbad_d processes for full logical log backup. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list

On Aug 16, 9:52 am, Martin Fuerderer <MARTI...@de.ibm.com> wrote: > Hi, > > no. Andrew is right. > > Log backup is a serial operation. > > Log files fill serially and therefore they are backed up serially. > If you set ALARMPROGRAM in the onconfig file so that logs > get backed up as soon as the are closed (full or not full), then > this will work fine (in most cases). If your log backup is so slow > that it cannot keep up with logs filling, then you have to see, > how to fix the bottle neck (usually slow I/O on the tape device). > > Parallel operation is done only for backup of dbspaces. > > Regards, > Martin > -- > Martin Fuerderer > IBMInformixDevelopment 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-boun...@iiug.org wrote on 16.08.2007 18:29:07: > > > > > > > On Aug 15, 9:05 pm, "Andrew Ford" <af...@networkip.net> wrote: > > > > Version : 10 > > > > > We are running onbar -b -l with BAR_MAX_BACKUP = 4 and > > > > BAR_NB_XPORT_COUNT = 10. But when I check the number of onbar > process > > > > I just see one onbar_d process. I was expecting atleast 4 processes. > > > > Why is it just spawning one process. Is it because our SHMTOTAL is > 0. > > > > I don't think BAR_MAX_BACKUP effects the number of backup threads for > the > > > logical logs which are backed up one at a time. > > > > You should see multiple onbar_d processes when you execute a level 0, > 1 or 2 > > > backup. > > > > Andrew > > > I think onbar -b -l just does backup of full logical log. It doesn't > > do who system backup which is done serially. I would expect multiple > > onbad_d processes for full logical log backup. > > > _______________________________________________ > >Informix-list mailing list > >Informix-l...@iiug.org > >http://www.iiug.org/mailman/listinfo/informix-list- Hide quoted text - > > - Show quoted text - Yes Alarm program launches onbar. But, in some exceptional cases there are logs that might have not backed up. What will happen if multiple onbar commands are executed.