Re: Question regarding restore of a full (but not "Whole-system") onbar backup

On Nov 9, 8:59 pm, "da...@smooth1.co.uk" <da...@smooth1.co.uk> wrote: > > Then you should do normal archvie (level 0/1/2) and log archives.and > use parallel backups with onconfig parameter BAR_MAX_BACKUP > controlling parallelism from the database server side. > > You can then restore to current time (onbar -r) or a given point in > time (onbar -r -t time). > > If however your database are unlogged or you do not take log backups > then you will need to run level 0/1/2 with -w (whole system) option > and log backups will not be required for restores > (as you do not have any!). Ignoring version 11.10 then prior to > version 11.50 your backups with -w option will be single threaded and > NOT be parallel. > > Assuming you backup logs then what is stoppiing you from allowing > processing whilst the backup runs? Thanks, David. All databases are log mode B or U; we stop processing for a few minutes either side of the backup start point but once we've confirmed it's started, processing begins again. What I was concerned with is whether a -f <spacelist> backup is consistent to the start time of the entire backup, i.e. the point where onbar -b -L 0 -f <list> was issued. Using the -f method, backups (to disk) take 4 hours, using -w it takes 6 hours. We'd rather take the shorter option But SB above said that using -f, we can't restore to the time we issued onbar -b -L 0 if logs are being filled and some dbspaces start backing up later than rootdbs; whereas the training notes and the BAR manual imply differently, as I wrote earlier. e.g. Time zero: issue onbar -b -L 0 -f <dbspacelist> (where <spacelist> is created by the initiating process as an SQL on sysmaster and lists all the dbspaces) T0+1: rootdbs backs up, processing is allowed to restart T0+2: space1 backs up T0+3: log log fills and gets backed up by ALARMPROGRAM T0+4: space 2 backs up T0+4 to T0+5: several more log logs fill up and get backed up by ALARMPROGRAMT0+6: space 3 backs up T0+7: onbar ends We only ever would do a COLD restore. Can we restore the database, using the data written by the above processes, to Time zero? I know we can, using -w. I'm asking if the -f version allows the same, or can we only restore to the point where space 3 was backed up? Simple as that. Remember our versions - IDS9.30HC5 on HP-UX11.11. Not negotiable.

Hello Malc, --> I know we can, using -w. I'm asking if the -f version allows the same, --> or can we only restore to the point where space 3 was backed up? --> Simple as that. No you can not. The onbar -b -w -L 0 does backup the content of your logical logs too simular as an ontape would do. So the restore can do a fast recovery after a physical restore. onbar -b -L 0 does not backup the content of your logs;(believe me i have been there you need your trx log to restore which means that you can not restore to the point in time the archive starts. this you can only do with an archive taken before and using trx logs.) Besides that collecting before images of a dbspace starts when the backup for that dbspace starts. There is a FEA out there to allow this; however this got implemented in onbar -b -w -L 0 as Martin said to be in paralel which is more thenacceptable. Superboer. You could try and tune a bit in upping BAR_NB_XPORT_COUNT make sure BAR_XFER_BUF_SIZE is 31 make a not if you change BAR_XFER_BUF_SIZE because you may not be able to restore an older archive taken with a different BAR_XFER_BUF_SIZE size.

On Nov 10, 10:32 am, Superboer <superbo...@t-online.de> wrote: > Hello Malc, > > --> I know we can, using -w. I'm asking if the -f version allows the > same, > --> or can we only restore to the point where space 3 was backed up? > --> Simple as that. > > No you can not. The onbar -b -w -L 0 does backup the content of your > logical logs too simular as an > ontape would do. So the restore can do a fast recovery after a > physical restore. > > onbar -b -L 0 does not backup the content of your logs;> (believe me i have been there you need your trx log to restore which > means that you can not restore > to the point in time the archive starts. this you can only do with an > archive taken before and using trx logs.) Ta. Shame the manuals and training material don't state this explicitly. The impression from the training manual is that this is in fact possible. > > You could try and tune a bit in  upping BAR_NB_XPORT_COUNT > make sure BAR_XFER_BUF_SIZE is 31 make a not if you change > BAR_XFER_BUF_SIZE because you may not be able to restore an older > archive taken with a different BAR_XFER_BUF_SIZE size. BAR_NB_EXPORT_COUNT is 10, BUF_SIZE 31 already.

Hello Malc, you could try BAR_NB_EXPORT_COUNT 1000 means 31 MB extra claimed. Superboer. On 10 nov, 11:51, Malc <mal...@googlemail.com> wrote: > On Nov 10, 10:32 am, Superboer <superbo...@t-online.de> wrote: > > > > > Hello Malc, > > > --> I know we can, using -w. I'm asking if the -f version allows the > > same, > > --> or can we only restore to the point where space 3 was backed up? > > --> Simple as that. > > > No you can not. The onbar -b -w -L 0 does backup the content of your > > logical logs too simular as an > > ontape would do. So the restore can do a fast recovery after a > > physical restore. > > > onbar -b -L 0 does not backup the content of your logs;> > (believe me i have been there you need your trx log to restore which > > means that you can not restore > > to the point in time the archive starts. this you can only do with an > > archive taken before and using trx logs.) > > Ta. Shame the manuals and training material don't state this > explicitly. The impression from the training manual is that this is in > fact possible. > > > > > You could try and tune a bit in  upping BAR_NB_XPORT_COUNT > > make sure BAR_XFER_BUF_SIZE is 31 make a not if you change > > BAR_XFER_BUF_SIZE because you may not be able to restore an older > > archive taken with a different BAR_XFER_BUF_SIZE size. > > BAR_NB_EXPORT_COUNT is 10, BUF_SIZE 31 already.

Hi, The "Backup and Restore Guide" of IDS 10 () said (just to pick one place): ---excerpt start---------------------- ON-Bar Backup Examples The following sections contain examples of ON?Bar syntax for backing up storage spaces. Performing a Level-0 Backup of All Storage Spaces To perform a standard, level-0 backup of all online storage spaces and used logical logs, use one of the following commands: onbar -b onbar -b -L 0 ON?Bar never backs up offline storage spaces, temporary dbspaces, or temporary sbspaces. Important: Save your logical logs so that you can restore from this backup. ---excerpt end---------------------- I think what you are missing is mentioned with the keyword "Important" ... it may be for a reason ... :) Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management IBM Deutschland Research & Development GmbH Chairman of the Supervisory Board: Martin Jetter Board of Management: Dirk Wittkopp Corporate Seat: Boeblingen, Germany Reg.-Gericht: Amtsgericht Stuttgart, HRB 243294 > On Nov 10, 10:32 am, Superboer <superbo...@t-online.de> wrote: > > Hello Malc, > > > > --> I know we can, using -w. I'm asking if the -f version allows the > > same, > > --> or can we only restore to the point where space 3 was backed up? > > --> Simple as that. > > > > No you can not. The onbar -b -w -L 0 does backup the content of your > > logical logs too simular as an > > ontape would do. So the restore can do a fast recovery after a > > physical restore. > > > > onbar -b -L 0 does not backup the content of your logs;> > (believe me i have been there you need your trx log to restore which > > means that you can not restore > > to the point in time the archive starts. this you can only do with an > > archive taken before and using trx logs.) > > Ta. Shame the manuals and training material don't state this > explicitly. The impression from the training manual is that this is in > fact possible. > > > > > You could try and tune a bit in upping BAR_NB_XPORT_COUNT > > make sure BAR_XFER_BUF_SIZE is 31 make a not if you change > > BAR_XFER_BUF_SIZE because you may not be able to restore an older > > archive taken with a different BAR_XFER_BUF_SIZE size. > > BAR_NB_EXPORT_COUNT is 10, BUF_SIZE 31 already. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list