Results 1 to 3 of 3

Thread: PostStartupCrashRecovery

  1. #1
    Petter Ramme is offline New Member
    Join Date
    Oct 2007
    Location
    Stockholm, Sweden
    Posts
    4
    Rep Power
    7

    Default PostStartupCrashRecovery

    When I start the Zimbra server it logs in the mailbox.log this log several thousands of rows like this, it seems to be one line per message in the system.


    What does it mean, and what could be done so that it's not necessary for the server to RedoLogManager?

    2007-11-06 15:01:28,260 INFO [PostStartupCrashRecovery] []RedoLogManager - REDOING: txn 1194311376.46443 [IndexItem] ver=1.12, tstamp=1194313303409, mailbox=9, id=2565, type=11
    2007-11-06 15:01:28,320 INFO [PostStartupCrashRecovery] [] RedoLogManager - REDOING: txn 1194311376.46444 [IndexItem] ver=1.12, tstamp=1194313303445, mailbox=9, id=2561, type=11
    2007-11-06 15:01:28,352 INFO [PostStartupCrashRecovery] [] RedoLogManager - REDOING: txn 1194311376.46445 [IndexItem] ver=1.12, tstamp=1194313303482, mailbox=9, id=2563, type=11

    I also want to thank The Zimbra Team for a great product, that really is nothing less than great!

    I hope I will get some answer on my question!

    Thanks
    Petter

  2. #2
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    20

    Default

    Welcome to the forums,

    Each Zimbra server generates redo logs that contain every transaction processed by that server. If an unexpected shutdown occurs to the server, the redo logs are used for the following:
    • To ensure that no uncommitted transactions remain, the server rereads the redo logs upon startup.
    • During NE restore, to recover data written since the last backup in the event of a server failure.
    When the current redo log file size reaches 100MB, it rolls over to an archive directory. At that point, the server starts a new redo log. All uncommitted transactions from the previous redo log are preserved. In the case of a crash, when the server restarts, the current redo log and the archived logs are read to re-apply any uncommitted transactions.
    If you're on NE, when an incremental backup is run, the redo logs are moved from the archive to the backup directory.

    You can see them in your /opt/zimbra/redolog/

    Are you ok now however?

    If you don't already know that the problem was external to zimbra (power loss etc) I would suggest that you dig through your system logfiles and then the zimbra related logfiles: /docs/ne/latest/administration_guide/9_Monitoring.12.1.html#1075561
    Last edited by mmorse; 11-06-2007 at 08:48 AM.

  3. #3
    Petter Ramme is offline New Member
    Join Date
    Oct 2007
    Location
    Stockholm, Sweden
    Posts
    4
    Rep Power
    7

    Default

    Thanx Mike,

    Do I understand you right, I can't do this manually, unless i do a backup on NE?

    I'm only asking since I today run Open Source version and do a backup with a full directory dump with rsync and rotations, the redo logs takes lots of performance and time on restart after the backup.

    Is there no way to comit the logs while I have the Zimbra server down and have done the backup?

    //Petter

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •