Informix backup fails.
Hi,
I am trying to take backup of my Informix database using the Onbar but the
backup fails, I cheked the bar_act.log file I found the following :-
BACKUP & VERIFICATION
=====================
For IBM Informix Dynamic Server:
-b [-L <level>] [-w | -f <filename> | <spaces>] [-O]
-b -F
-b -l [-c | -C | -s] [-O]
-v [-w] [-p] [-t <time>] [-f <filename> | <spaces>]
-b backup
-c backup current logical log
-C continuous logical log backup
-f pathname of file containing list of storage spaces
-F fake backup
-l backup full logical logs (no spaces)
-L backup level: 0, 1, or 2, defaults to 0
-O override internal error checks - enforce policy strictly
-p backup spaces only (no logs)
-w whole system backup
-s salvage logs
-v verify consistency of most recent backups
<spaces> list of storage spaces to backup
2008-01-10 01:41:35 4888 4888 onbar usage
RESTORE
========
For IBM Informix Dynamic Server:
-r [-e] [-O] [-f <filename> | <spaces>]
-r [-e] [-t <time> | -n <log>] [-O]
-r -p [-e] [-t <time>] [-O] [-f <filename> | <spaces>]
-r -l [-t <time> | -n <log>]
-r -w [-e] [[-p] [ -t <time>] | -n <log>] [-O]
-RESTART
-r -rename -f <filename> [-w] [-p] [-t <time> | -n <log>]
[-f <filename> | <spaces>]
-r {-rename -p <old path> -o <old offset> -n <new path>
-o <new offset>...} [-w] [-p] [-t <time> | -n <log>]
[-f <filename> | <spaces>]
-e external restore
-f pathname of file containing list of storage spaces
-l logical log only restore (no spaces)
-n last logical log to restore
-O override internal error checks - enforce policy strictly
-p physical only restore (no logs)
-r restore
-t point in time to stop restore
-w whole system to restore
-RESTART restart an interrupted restore
<spaces> list of storage spaces to restore
-rename rename chunks during cold restore
With -rename option:
-rename -f <filename> pathname of file containing list of mapped
chunk pathnames and offsets
-p old pathname of chunk
-o old offset of chunk
-n new pathname of chunk
-o new offset of chunk
2008-01-10 01:41:35 4888 4888 d:\\\\informix\\\\prd\\\\bin\\\\onbar_d complete, returning
149 (0x95)
2008-01-10 01:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 02:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 02:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 03:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 03:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 04:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 04:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 05:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 05:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 06:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 06:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 07:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 07:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 08:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 08:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-10 09:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager Progress may
be stalled.
2008-01-11 13:19:18 4420 4420 d:\\\\informix\\\\prd\\\\bin\\\\onbar_d -b -L 0
2008-01-11 13:19:18 4420 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 13:19:20 4420 4420 Begin level 0 backup rootdbs.
2008-01-11 13:19:23 4420 4420 Successfully connected to Storage Manager.
2008-01-11 13:31:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager Progress
may be stalled.
2008-01-11 14:01:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager Progress
may be stalled.
2008-01-11 14:31:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager Progress
may be stalled.
2008-01-11 15:01:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager Progress
may be stalled.
2008-01-11 15:31:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager Progress
may be stalled.
2008-01-11 16:01:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager Progress
may be stalled.
2008-01-11 16:31:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager Progress
may be stalled.
2008-01-11 16:55:43 4420 4420 Completed level 0 backup rootdbs (Storage
Manager copy ID: 37572 0).
2008-01-11 16:55:43 4480 4420 onbar_d -b logdbs
2008-01-11 16:55:43 4480 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:43 552 4420 onbar_d -b physdbs
2008-01-11 16:55:43 4232 4420 onbar_d -b psapclu
2008-01-11 16:55:43 552 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed limit.
Changing buffer size to 61440.
2008-01-11 16:55:43 4232 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 4340 4420 onbar_d -b psapel620
2008-01-11 16:55:44 5068 4420 onbar_d -b psapbtab
2008-01-11 16:55:44 4340 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 5068 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 4552 4420 onbar_d -b psappool
2008-01-11 16:55:44 4552 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 900 4420 onbar_d -b psapprot
2008-01-11 16:55:44 3528 4420 onbar_d -b psapsource
2008-01-11 16:55:44 900 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed limit.
Changing buffer size to 61440.
2008-01-11 16:55:44 3528 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 4184 4420 onbar_d -b psapes620
2008-01-11 16:55:44 4632 4420 onbar_d -b psapload
2008-01-11 16:55:44 4656 4420 onbar_d -b psapel40b
2008-01-11 16:55:44 4248 4420 onbar_d -b psapes40b
2008-01-11 16:55:44 4564 4420 onbar_d -b psapuser1
2008-01-11 16:55:44 4184 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 4632 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 1528 4420 onbar_d -b psapstab
2008-01-11 16:55:44 4248 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 4656 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 4564 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01-11 16:55:44 1528 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
limit. Changing buffer size to 61440.
2008-01
Hi,
I'm no Windows expert. So I can't tell why you can't start IDS
after the change of LTAPEDEV parameter.
LTAPEDEV parameter set to NUL (or nul ?) on Windows means
that IDS will not backup logical logs. (On UNIX/Linux this special
value is /dev/null.)
With this special value set no log backup will be done. The IDS
Server marks logs as "Backed Up" even though they are not
backed up. The rational is that the backup would go to the
trash bin (/dev/null) anyway, so why bother with an actual
backup, just mark it as backed up and we are done quickly.
But when you do your onbar backup command, you are
doing a parallel backup of your dbspaces. And for that it
is necessary to have a real backup of the logical logs.
Because these logical logs will be needed for restore in
order to synchronize the restored dbspaces. (The dbspaces
are backed up at different times when parallel backup is
done.) For your safety the onbar is detecting the NUL/nul
setting of LTAPEDEV and therefore tells you that the backup
failed, because it will not be usable for restore. (Newer
versions of IDS are improved in that they detect this first
and provide corresponding error more verbose before
starting the backup.)
So you either need to backup the logs (i.e. set
LTAPEDEV to something other than NUL or nul). Or you
have to do a "whole system backup", which is not parallel.
Thus it does not need logs for restore. The command for
backup includes the "-w" option, like "onbar -b -w -L 0".
Also, you seem to have the onconfig parameter
BAR_MAX_BACKUP set to 0, which means that
onbar will do all dbspaces (except rootdbs) in
parallel at the same time. This can slow down the
storage manager (SM) considerably if it can not
handle so many parallel requests with true
parallelism. So you may want to set
BAR_MAX_BACKUP to a more reasonable value
(between 3 and 10 maybe?).
Other than that I'm not sure why, but your SM seems
to be a bit slow. At least too slow for the many
dbspaces to be backed up in parallel.
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), Christian Diedrich,
Matthias Hartmann, Thomas Fell, Christoph Grandpierre, Michael Diemer
Corporate Seat: Stuttgart, Germany; Reg.-Gericht: Amtsgericht Stuttgart,
HRB-Nr.: 14 562 WEEE-Reg.-Nr. DE 99369940
ids-bounces@iiug.org wrote on 07.02.2008 09:44:57:
> Hi,
>
> I am trying to take backup of my Informix database using the Onbar but
the
> backup fails, I cheked the bar_act.log file I found the following :-
>
> BACKUP & VERIFICATION
> =====================
> For IBM Informix Dynamic Server:
>
> -b [-L <level>] [-w | -f <filename> | <spaces>] [-O]
>
> -b -F
>
> -b -l [-c | -C | -s] [-O]
>
> -v [-w] [-p] [-t <time>] [-f <filename> | <spaces>]
>
> -b backup
>
> -c backup current logical log
>
> -C continuous logical log backup
>
> -f pathname of file containing list of storage spaces
>
> -F fake backup
>
> -l backup full logical logs (no spaces)
>
> -L backup level: 0, 1, or 2, defaults to 0
>
> -O override internal error checks - enforce policy strictly
>
> -p backup spaces only (no logs)
>
> -w whole system backup
>
> -s salvage logs
>
> -v verify consistency of most recent backups
>
> <spaces> list of storage spaces to backup
> 2008-01-10 01:41:35 4888 4888 onbar usage
>
> RESTORE
> ========
> For IBM Informix Dynamic Server:
>
> -r [-e] [-O] [-f <filename> | <spaces>]
>
> -r [-e] [-t <time> | -n <log>] [-O]
>
> -r -p [-e] [-t <time>] [-O] [-f <filename> | <spaces>]
>
> -r -l [-t <time> | -n <log>]
>
> -r -w [-e] [[-p] [ -t <time>] | -n <log>] [-O]
>
> -RESTART
>
> -r -rename -f <filename> [-w] [-p] [-t <time> | -n <log>]
>
> [-f <filename> | <spaces>]
>
> -r {-rename -p <old path> -o <old offset> -n <new path>
>
> -o <new offset>...} [-w] [-p] [-t <time> | -n <log>]
>
> [-f <filename> | <spaces>]
>
> -e external restore
>
> -f pathname of file containing list of storage spaces
>
> -l logical log only restore (no spaces)
>
> -n last logical log to restore
>
> -O override internal error checks - enforce policy strictly
>
> -p physical only restore (no logs)
>
> -r restore
>
> -t point in time to stop restore
>
> -w whole system to restore
>
> -RESTART restart an interrupted restore
>
> <spaces> list of storage spaces to restore
>
> -rename rename chunks during cold restore
>
> With -rename option:
>
> -rename -f <filename> pathname of file containing list of mapped
>
> chunk pathnames and offsets
>
> -p old pathname of chunk
>
> -o old offset of chunk
>
> -n new pathname of chunk
>
> -o new offset of chunk
> 2008-01-10 01:41:35 4888 4888 d:\\\\informix\\\\prd\\\\bin\\\\onbar_d complete,
returning
> 149 (0x95)
> 2008-01-10 01:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 02:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 02:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 03:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 03:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 04:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 04:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 05:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 05:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 06:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 06:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 07:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 07:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 08:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 08:59:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-10 09:29:03 792 792 Warning: BAR_TIMEOUT Storage Manager
Progress may
> be stalled.
> 2008-01-11 13:19:18 4420 4420 d:\\\\informix\\\\prd\\\\bin\\\\onbar_d -b -L 0
> 2008-01-11 13:19:18 4420 4420 BAR_XFER_BUF_SIZE exceeded maximum allowed
> limit. Changing buffer size to 61440.
> 2008-01-11 13:19:20 4420 4420 Begin level 0 backup rootdbs.
> 2008-01-11 13:19:23 4420 4420 Successfully connected to Storage Manager.
> 2008-01-11 13:31:18 4420 4420 Warning: BAR_TIMEOUT Storage Manager
Progress
> may be stalled.
> 2008-01