Re: onbar with 7.24

We've run into the same problem, and came up with the same answer. It doesn't appear to be a problem, but I'd appreciate hearing if anyone has experienced any bad side effects of this one. Vic Terry R. Gauchat wrote: > Well, I've seen two things happen: > > 1. OnBar automatically closes the current log file (thus triggering > log_full.sh) when it is done. > 2. The backup process explicitly runs an "onbar -l" after the onbar full > backup. > > It looks like both are happening and one is failing. No big deal though, > since the collision does not hurt. > > Though it bothers me -- since I would like to direct all my logs during a > backup to a different tape pool than not during a backup. So I'd like the > behavior to be predictable. > > Strangely, in my tests, item # 1 above does not happen all the time -- I > think! > > ...Terry. > > Jonathan Myatt wrote in message <357BC0F7.C2270F85@jonners.cix.co.uk>... > >I'm seeing a strange problem with onbar to ADSM under 7.24. When I issue > >onbar -b -L 0 I get the following in the log just after the L0 archive > >completes:> > > ><blah> > >1998-06-08 10:55:59 23500 18850 Completed level 0 backup physdbs. > >1998-06-08 10:56:03 23500 18850 Begin backup logical log 36. > >1998-06-08 10:56:05 23500 18850 Successfully connected to Storage > >Manager. > >1998-06-08 10:56:14 25304 25044 onbar -l > >1998-06-08 10:56:16 25304 25044 WARNING: A log backup is already > >running. Can't start another. > >1998-06-08 10:56:22 23500 18850 Completed backup logical log 36. > > > >I'm not issuing that onbar -l. I presume it's coming from the > >log_full.sh > >script, but what's triggering it? This doesn't happen on my 7.22 > >systems, > >does anyone know if something changed with 7.24? (or 7.23 I guess) > > > >TIA > > > >Jon. -- Vic Goldberg Manager, DBA Team, Acting Manager, Technical Integration Cornell University (607) 254-7441 (Voice) (607) 255-6982 (Fax)