Yeah - very similar, except it wasnt 20 mins. Here's a scrubbed snip from our logs:
Code:
2009-10-02 09:55:00,331 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] backup - redo log file sequence is 912 at full backup for --------@-----.com
2009-10-02 09:55:00,366 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] backup - Full backup started for account --------@-----.com (64eb000e-20d3-44af-9065-df4ae8971abd) mailbox 63
2009-10-02 09:55:00,366 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] mailbox - Locking mailbox 63 for maintenance.
2009-10-02 09:55:01,607 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] backup - Number of blobs to backup for mailbox 63: 24804
2009-10-02 09:55:01,608 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] mailbox - Ending maintenance on mailbox 63.
2009-10-02 09:55:01,608 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] mbxmgr - Mailbox 63 account 64eb000e-20d3-44af-9065-df4ae8971abd AVAILABLE
2009-10-02 09:55:16,411 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] backup - Account --------@-----.com in backup set full-20091002.163124.235: All pending file IO completed (23905 out of 23905)
2009-10-02 09:55:16,580 INFO [FullBackupThread] [name=--------@-----.com;mid=63;] mailbox - Locking mailbox 63 for maintenance.
this was the account we had to re-index...
Some additional, possibly non-sequitur details:
I recently got samba/posix ldap integration working on our NE 5.18 installation. Our full backups begain failing after that, however, they weren't hanging like the one above...after I got the integration working, I added two test accounts, which were the only ones with the samba/posix ldap attributes populated. Looking through the logs, the fullback ups would hit only those two test accounts, and then finish, exiting normally. Then a day or so later we had the "locked in maintenance mode" issue which brought it to our attention.
Again, unsure if this is related, but strangely enough the full backups began working normally again once we re-indexed that one account that was locked in maintenance mode. Let me know if you see anything else you'd like me to check.