onbar -v

IDS 11.50FC6 on AIX 5.3. I've taken over management of a newly-migrated system. It's not that big, perhaps 300GB distributed across a bumper 106 dbspaces. It's backed up with onbar using Netbackup. A level 0 takes about an hour. We're required to run a "verify". This is taking 7-10 hours. The administrator of the previous system tells me it used to take about 1h 20m on the old system, about the same as the level 0 time, which was my expectation for this system. I've never used onbar -v/archecker and has no idea what it does. Can anyoner suggest where I can look for clues on what's taking all the time? There are no issues in the onbar log (see below). Thanks Neil ... 2013-09-26 22:05:23 10707156 6901828 Begin backup verification of level 0 for db34 (Storage Manager copy ID: 1 1379748129). 2013-09-26 22:13:16 10707156 6901828 Begin backup verification of level 0 for db35 (Storage Manager copy ID: 1 1379746776). 2013-09-26 22:23:07 10707156 6901828 Begin backup verification of level 0 for db36 (Storage Manager copy ID: 1 1379748024). 2013-09-26 22:35:19 10707156 6901828 Begin backup verification of level 0 for db38 (Storage Manager copy ID: 1 1379750181). 2013-09-26 22:38:28 10707156 6901828 Begin backup verification of level 0 for db39 (Storage Manager copy ID: 1 1379747807). 2013-09-26 22:47:18 10707156 6901828 Begin backup verification of level 0 for db4 (Storage Manager copy ID: 1 1379749423). 2013-09-26 22:52:52 10707156 6901828 Begin backup verification of level 0 for db40 (Storage Manager copy ID: 1 1379746508). 2013-09-26 23:02:56 10707156 6901828 Begin backup verification of level 0 for db41 (Storage Manager copy ID: 1 1379748436). 2013-09-26 23:10:46 10707156 6901828 Begin backup verification of level 0 for db42 (Storage Manager copy ID: 1 1379746038). ...

Hi Neil Can you spot in the log any dbspace that is taking longer (ie that is taking most of the 7 to 10 hours that you mentioned). You ca use the date of the message "Begin backup verification" to calculate the time it took to retrieve the dbspace before that one. If you cannot spot any single dbspace that takes most of the time, then for some reason your storage manager is taking too much time retrieving the dbspaces from the media. You should check this situation with your SM vendor ASAP because it could also be that if you need to restore, it will be equally long. On the informix side, check that BAR_DEBUG in the $ONCONFIG file is set to 0 Also that AC_DEBUG is set to 0 or not set in the $AC_CONFIG file. Gustavo On 9/26/2013 6:19 PM, NEIL TRUBY wrote: > IDS 11.50FC6 on AIX 5.3. > > I've taken over management of a newly-migrated system. It's not that big, > perhaps 300GB distributed across a bumper 106 dbspaces. > > It's backed up with onbar using Netbackup. A level 0 takes about an hour. > > We're required to run a "verify". This is taking 7-10 hours. The administrator > of the previous system tells me it used to take about 1h 20m on the old > system, about the same as the level 0 time, which was my expectation for this > system. > > I've never used onbar -v/archecker and has no idea what it does. Can anyoner > suggest where I can look for clues on what's taking all the time? There are no > issues in the onbar log (see below). > > Thanks > Neil > > .... > 2013-09-26 22:05:23 10707156 6901828 Begin backup verification of level 0 for > db34 (Storage Manager copy ID: 1 1379748129). > 2013-09-26 22:13:16 10707156 6901828 Begin backup verification of level 0 for > db35 (Storage Manager copy ID: 1 1379746776). > 2013-09-26 22:23:07 10707156 6901828 Begin backup verification of level 0 for > db36 (Storage Manager copy ID: 1 1379748024). > 2013-09-26 22:35:19 10707156 6901828 Begin backup verification of level 0 for > db38 (Storage Manager copy ID: 1 1379750181). > 2013-09-26 22:38:28 10707156 6901828 Begin backup verification of level 0 for > db39 (Storage Manager copy ID: 1 1379747807). > 2013-09-26 22:47:18 10707156 6901828 Begin backup verification of level 0 for > db4 (Storage Manager copy ID: 1 1379749423). > 2013-09-26 22:52:52 10707156 6901828 Begin backup verification of level 0 for > db40 (Storage Manager copy ID: 1 1379746508). > 2013-09-26 23:02:56 10707156 6901828 Begin backup verification of level 0 for > db41 (Storage Manager copy ID: 1 1379748436). > 2013-09-26 23:10:46 10707156 6901828 Begin backup verification of level 0 for > db42 (Storage Manager copy ID: 1 1379746038). > .... > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

Hi Gustavo No, the check seems to take consistently longer for all dbspaces. I had the same concern as you about restore times but in fact during non-functional testing the restore from a Level 0 was about as long as the Level 0 backup, or about 55m. By comparison the current onbar -v has done about 50 of the 100 dbspaces after 4 hours. regards Neil

Maybe you should contract the work to Oninit UK :-) Paul Watson Oninit www.oninit.com +1 913 387 7529 On Sep 26, 2013, at 17:19, "NEIL TRUBY" <neil.truby@ardenta.com> wrote: > IDS 11.50FC6 on AIX 5.3. > > I've taken over management of a newly-migrated system. It's not that big, > perhaps 300GB distributed across a bumper 106 dbspaces. > > It's backed up with onbar using Netbackup. A level 0 takes about an hour. > > We're required to run a "verify". This is taking 7-10 hours. The administrator > of the previous system tells me it used to take about 1h 20m on the old > system, about the same as the level 0 time, which was my expectation for this > system. > > I've never used onbar -v/archecker and has no idea what it does. Can anyoner > suggest where I can look for clues on what's taking all the time? There are no > issues in the onbar log (see below). > > Thanks > Neil > > .... > 2013-09-26 22:05:23 10707156 6901828 Begin backup verification of level 0 for > db34 (Storage Manager copy ID: 1 1379748129). > 2013-09-26 22:13:16 10707156 6901828 Begin backup verification of level 0 for > db35 (Storage Manager copy ID: 1 1379746776). > 2013-09-26 22:23:07 10707156 6901828 Begin backup verification of level 0 for > db36 (Storage Manager copy ID: 1 1379748024). > 2013-09-26 22:35:19 10707156 6901828 Begin backup verification of level 0 for > db38 (Storage Manager copy ID: 1 1379750181). > 2013-09-26 22:38:28 10707156 6901828 Begin backup verification of level 0 for > db39 (Storage Manager copy ID: 1 1379747807). > 2013-09-26 22:47:18 10707156 6901828 Begin backup verification of level 0 for > db4 (Storage Manager copy ID: 1 1379749423). > 2013-09-26 22:52:52 10707156 6901828 Begin backup verification of level 0 for > db40 (Storage Manager copy ID: 1 1379746508). > 2013-09-26 23:02:56 10707156 6901828 Begin backup verification of level 0 for > db41 (Storage Manager copy ID: 1 1379748436). > 2013-09-26 23:10:46 10707156 6901828 Begin backup verification of level 0 for > db42 (Storage Manager copy ID: 1 1379746038). > .... > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum.

Couldn't afford that kind of money! ;-)

I just had a chat with John Miller, He correctly pointed out that the backup occurs in parallel whereas the verification is done serially. IF you add the time to do the backup of each dbspace that is probably close to 7 hours..... The questions then is to know how come is was a lot faster before..... or maybe that was a misunderstanding? On 9/26/2013 7:03 PM, NEIL TRUBY wrote: > Hi Gustavo > > No, the check seems to take consistently longer for all dbspaces. > > I had the same concern as you about restore times but in fact during > non-functional testing the restore from a Level 0 was about as long as the > Level 0 backup, or about 55m. > > By comparison the current onbar -v has done about 50 of the 100 dbspaces after > 4 hours. > > regards > Neil > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >