Hi,
sometimes a log backup takes longer for some reasons (external maybe, winding
the tape ...).
Then, a log backup triggers by the alarm program will fail (backup already in
progress).
This can occur with onbar or ontape.
The next call to the alarmprogram will again trigger a backup, which then will
also backup
the skipped logs.
So, it is normal behaviour, when your logs fill up very fast (which they do
according to your log extract).
If your logs fill up very fast not only in peak times, you should consider
using bigger logfiles.
Hope this helps,
Marcus Haarmann
----- Ursprüngliche Mail -----
Von: "FRANK"<yunyaoqu@gmail.com>
An: ids@iiug.org
Gesendet: Freitag, 20. Dezember 2013 17:47:31
Betreff: Logical log backup [32162]
Folks,
IDS11.50FC8 , Linux
We have a couple of boxes , all are setup to do automatic logical
backup. Once the current log is full, it triggers the alarm procedure
to start a backup. It works great.
But, The interesting thing is, some servers do not always backup a full
logical log immediately, instead they backup them in sort of batch mode
( attached log can show you that sort of info), i.e., they can wait
and backup logical logs until there are a number of logs are full.
Any clue or comments?
Thanks,
Frank
15:56:48 Maximum server connections 210
15:56:48 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
3, Plog used 7504, Llog used 47209
16:00:13 Logical Log 86460 Complete, timestamp: 0xa8b2cfa5.
16:00:13 Logical Log 86458 - Backup Started
16:00:19 Logical Log 86458 - Backup Completed
16:00:20 Logical Log 86459 - Backup Started
16:00:24 Logical Log 86459 - Backup Completed
16:00:25 Logical Log 86460 - Backup Started
16:00:29 Logical Log 86460 - Backup Completed
16:01:48 Checkpoint Completed: duration was 0 seconds.
16:01:48 Fri Dec 20 - loguniq 86461, logpos 0x26f712c, timestamp:
0xa8b71f15 Interval: 299248
--14dae93405f9f4ae6704edfa0760
*******************************************************************************
To post a response via email (IIUG members only):
1. Address it to ids@iiug.org
2. Include the bracketed message number in the subject line: [32171]
*******************************************************************************
↧