Oninit cdi / Archive
Talk to an expert →

Logical log backup

Posted in 2013

Topics: Triggers, Constraints & Referential Integrity, Logging & Checkpoints

FRANK — — source: IIUG Forums & Mailing Lists

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

↪ replying to FRANK
Art Kagel — — source: IIUG Forums & Mailing Lists

If you are using onbar that can happen if the storage manager is busy or slow to respond. It's not that the backup doesn't start, it's just that it takes so long for the onbar to make contact with the storage manager and get a response that multiple logs have completed. Art Art S. Kagel, Principal Consultant Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Fri, Dec 20, 2013 at 11:47 AM, FRANK <yunyaoqu@gmail.com> wrote: > 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 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7bdc94ca71ffcb04edfa55b0

↪ replying to FRANK
Habichtsberg, Reinhard — — source: IIUG Forums & Mailing Lists

For me it looks like you have a procedure in the background that waits until a couple of logs are full and then starts to backup. We do the same to avoid the tape-streamer to start and stop to often. Do verify have a look to onconfig parameter ALARMPROGRAM. Then have a look in the shell-script which is referred by this paramter. The value of BACKUP_CMD there shows you the command which is started when a Logical Logs fills up. Perhaps it is a shell-scripts counting the full logical logs until a certain value is reached. HTH, Reinhard > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of FRANK > Sent: Friday, December 20, 2013 5:48 PM > To: ids@iiug.org > Subject: 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 > > > ************************************************************************ ******* > Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to FRANK
Marcus Haarmann — — source: IIUG Forums & Mailing Lists

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 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Glossary