IDS Forum

Re: onbar Logical restore cannot complete beca....

Posted By: Lyubomir Grigorov
Date: Thursday, 12 November 2015, at 2:38 a.m.

In Response To: RE: onbar Logical restore cannot complete beca.... (Lyubomir Grigorov)

One question:

If I change the backups from Whole system (with -w flag) to Parralel
(without -w flag) backup, and I differentiate the specifications so that
logs only go to log specification, and not the full backup specification,
will this work correctly?

I mean, during L0 backup, will Informix require to backup the current log
together with the L0 backup, or this can be done afterwards with Log
backups from ALARMPROGRAM? Because as far as I know we can't have two
backups running at a time :)

Thanks a lot for the information!

2015-11-11 21:04 GMT+02:00 Lyubomir Grigorov <lgrigorlu1@gmail.com>:

> I forgot to mention that we take whole-system backups, sorry.
>
> So as they are based on a checkpoint time including the logs,maybe these
> two logs were needed to satisfy the checkpoint.
>
> I am aware that whole system backups do not require to restore additional
> logs,but it is written in the docs as option for roll forward recovery
> if/when needed.
>
> So basically I can't remove the Logs being backed up by the whole backup
> specification,because it will fail to complete.
>
> So basically I can't do much if I understand it right?
>
> Thanks for your time!
>
> BR,
> Lyubomir
> On Nov 11, 2015 6:44 PM, "Alexandre Marini" <alexandre@briug.org> wrote:
>
> > Hello.
> > This kind of errors are common to DP, if you are using 2 separate jobs
> (one
> > for archives, and the other for logs through alarmprogram).
> > I just don't understand what job did backup the 2 logs you've mentioned.
> > Did
> > any onbar process hang in your filesystem?? If so, were they killed
> > manually???
> > As the error log description says, the next logical log backup should
> > automatically include the 2 (or more) missed logs. No magic.
> >
> > Just make sure your archive job in DP does not have a L checked in your
> > Resource type configuration, and also the opposite (your logical logs job
> > must
> > only have the L checkbox marked, in its Resource Type configuration).
> >
> > That should separate and not start logical logs backups by the archive
> job.
> >
> > Alexandre Marini
> > IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10
> >
> > IBM Information Management Informix Technical Professional
> >
> > IBM Certified Developer - Informix Genero
> > BRIUG website administrator
> > Informix independent consultant
> >
> > > To: ids@iiug.org
> > > From: lgrigorlu1@gmail.com
> > > Subject: onbar Logical restore cannot complete because .... [36046]
> > > Date: Wed, 11 Nov 2015 10:50:51 -0500
> > >
> > > Hello all,
> > >
> > > OS: Windows Server 2008 R2
> > > DB: Informix IDS 11.70 FC8GE
> > > SM: HP Data Protector 9
> > >
> > > We have two separate backup specifications - one for full backups, one
> > for
> > > log backups. The instance is configured with environment variable
> > parameter
> > > OB2BARLIST poining to the log specification in the instance .cmd
> console
> > > file and in ALARMPROGRAM.
> > > The full backups are being run by Scheduler of Data protector each day
> > > using the Full backup specifications. The log backups are being
> triggered
> > > by ALARMPROGRAM when a log fills up.
> > >
> > > During our monthly restore tests, we've hit an error which prevents us
> > from
> > > performing Logical restore of the instance. The problem is that onbar
> > > cannot find two logs from the Storage manager, which are the first two
> > logs
> > > after the time Full backup was taken. The problem is that when Full
> > backup
> > > started, ALARMPROGRAM started trying to backup current log log 5525
> (the
> > > current log by the time when Full started). Then, another log 5526 was
> > > filled up and also was backed up by the Full backup session. In the
> > > meantime, ALARMPROGRAM caused error 43395 An logical log backup is
> > already
> > > running - cannot start another.
> > >
> > > So at the end we have the Full backup specification holding all the
> > > dbspaces, critical files, and logs 5525 and 5526 and the Log
> > specification
> > > holding up all logical logs besides these.
> > >
> > > The Physical restore (onbar -r -p) using the Full backup specification
> > > succeeds without worries, but after when we try logical restore (onbar
> -r
> > > -l) onbar complains it can't find log 5525:
> > >
> > > 2015-11-11 15:19:02 180 180 Begin reserved pages restore (level 0 of
> > > rootdbs,
> > > Storage Manager copy ID: 2866 2015011010).
> > > 2015-11-11 15:19:03 180 180 Completed reserved pages restore (level 0
> of
> > > rootd
> > > bs).
> > > 2015-11-11 15:19:04 180 180 Successfully connected to Storage Manager.
> > > 2015-11-11 15:19:39 180 180 Begin cold level 0 restore rootdbs (Storage
> > > Manage
> > > r copy ID: 2866 2015011010).
> > > 2015-11-11 15:19:59 180 180 Completed cold level 0 restore rootdbs.
> > > 2015-11-11 15:20:35 180 180 Begin cold level 0 restore
> > > ona2aqifx030p0dbs01 (St
> > > orage Manager copy ID: 2866 2015011010).
> > > 2015-11-11 15:52:02 180 180 Completed cold level 0 restore
> > > ona2aqifx030p0dbs01
> > > ..
> > > 2015-11-11 15:52:38 180 180 Begin cold level 0 restore sbspace01
> (Storage
> > > Mana
> > > ger copy ID: 2866 2015011010).
> > > 2015-11-11 15:52:40 180 180 Completed cold level 0 restore sbspace01.
> > > 2015-11-11 15:53:16 180 180 Begin cold level 0 restore logdbs01
> (Storage
> > > Manag
> > > er copy ID: 2866 2015011010).
> > > 2015-11-11 15:53:18 180 180 Completed cold level 0 restore logdbs01.
> > > 2015-11-11 15:53:53 180 180 Begin cold level 0 restore physdbs (Storage
> > > Manage
> > > r copy ID: 2866 2015011010).
> > > 2015-11-11 15:53:56 180 180 Completed cold level 0 restore physdbs.
> > > 2015-11-11 15:53:58 180 180 Successfully connected to Storage Manager.
> > > 2015-11-11 15:53:58 180 180 XBSA Error: (BSAGetObject) Backup object
> does
> > > not
> > > exist in Storage Manager.
> > > 2015-11-11 15:53:58 180 180 Object information: bar_objdesc
> > >
> > > obj_id 0 obj_name '5525' obj_type 'L' act_id 0 act_type 2 act_status 0
> > >
> > > act_start '2015-11-11 15:53:58' act_end '2015-11-10 21:39:49'
> > >
> > > ins_time 0 rsam_time 0 seal_time 1447187988 prev_seal_time 1447155921
> > > level
> > > 0 copyid hi:lo 2866:2015011010 req_act_id 7150
> > >
> > > logstream 0 est_pages hi:lo 0:0 first_log 0 chpt_log 5525 last_log 0
> > >
> > > partial_flag 0 do_query 0 ins_sm_id 0 ins_sm_name ''
> > >
> > > ins_verify 0 ins_verify_date '' restore order 0:0
> > >
> > > objInfo ''
> > >
> > > retry 0 in_catalog 1 in_bootfile 0 child_pid 0 child_state 0
> > >
> > > bkup_host '' backup_order 0
> > > * 2015-11-11 15:53:58 180 180 (-43258) ON-Bar could not get logical log
> > > 5525 fro*
> > > *m the storage manager.*
> > > 2015-11-11 15:54:21 180 180 (-43168) ON-Bar suspended the logical
> restore
> > > on l
> > > og 5525 (expected to
> > > restore to 2147483647).
> > > 2015-11-11 15:54:27 180 180 C:\PROGRA~1\IBM\Informix\11.70\bin\onbar_d
> > > complet
> > > e, returning 100 (0x64)
> > >
> > > I tried manually to PITR to log 5525 using either of the
> > specifications(set
> > > OB2BARLIST), but again onbar can't find the logs :(
> > >
> > > So my question is: besides my attempts to reschedule the full backup
> in a
> > > time with lowest workload possible, is there something else I can try
> to
> > do
> > > to prevent this situation happens in the future?
> > >
> > > Or this is limitation of the Data protector integration for Informix?
> > >
> > > Thanks in advance for any comments!
> > >
> > > --001a114daacc33c074052445ca1e
> > >
> > >
> > >
> >
> >
>
> *******************************************************************************
> > > Forum Note: Use "Reply" to post a response in the discussion forum.
> > >
> >
> >
> >
> >
>
> *******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --001a114e4d7cd96a2d0524487e7e
>
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>

--001a11427b60bc17730524530511

Messages In This Thread

• onbar Logical restore cannot complete because of e
  Lyubomir Grigorov -- Wednesday, 11 November 2015, at 10:50 a.m.
  • RE: onbar Logical restore cannot complete because
    Alexandre Marini -- Wednesday, 11 November 2015, at 11:43 a.m.
    • RE: onbar Logical restore cannot complete beca....
      Lyubomir Grigorov -- Wednesday, 11 November 2015, at 2:04 p.m.
      • Re: onbar Logical restore cannot complete beca....
        Lyubomir Grigorov -- Thursday, 12 November 2015, at 2:38 a.m.
        • RE: onbar Logical restore cannot complete beca....
          Alexandre Marini -- Thursday, 12 November 2015, at 5:49 a.m.
          • RE: onbar Logical restore cannot complete beca....
            Lyubomir Grigorov -- Thursday, 12 November 2015, at 7:40 a.m.
            • RE: onbar Logical restore cannot complete beca....
              Alexandre Marini -- Thursday, 12 November 2015, at 8:09 a.m.
  • Re: onbar Logical restore cannot complete because
    BRYCE STENBERG -- Monday, 16 November 2015, at 4:48 p.m.
    • Re: onbar Logical restore cannot complete because
      Lyubomir Grigorov -- Tuesday, 17 November 2015, at 2:34 a.m.
      • Re: onbar Logical restore cannot complete because
        Art Kagel -- Tuesday, 17 November 2015, at 7:10 a.m.
      • RE: onbar Logical restore cannot complete because
        Alexandre Marini -- Tuesday, 17 November 2015, at 2:09 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.