Results 1 to 4 of 4

Thread: [SOLVED] Zimbra NE backup?

  1. #1
    Join Date
    May 2007
    Location
    Europe
    Posts
    48
    Rep Power
    8

    Default [SOLVED] Zimbra NE backup?

    Hi

    All informations I could get from an employee is, that he updated the AdAware2007, etc... I don't know what else he did.
    After restarting a computer, he lost all mail in INBOX folder. (SEND folder was OK)
    He uses Thunderbird IMAP account with Zimbra 5.0.1 NE.

    OK, restore was needed. So, today I tryed to restore that individual mail account
    (Zimbra Admin console, with CLI zmrestore, tryed to reindex mail account)
    It didn't work for INBOX folder (it restored SEND folder...).
    The weird thing is that same restore process with other mail account's wend smooth.

    What could be the problem? Is this some kinda bug?

    1 month ago, Zimbra was upgraded from 4.5.10 NE openSUSE 10 (worked OK) to 5.0.1 NE SUSE 10 Enterprise edition.
    The system was from the beginning only SUSE 10 Enterprise edition.
    Restoring back to zimbra 4.5.10 (lucky me, I made a complete backup) was able to restore mail.
    But there is also problem. It's the 1 month gap in mail.

    I would appreciate any help, suggestion...
    Regards

  2. #2
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Did the restore give an error? It will log to /opt/zimbra/log/mailbox.log

  3. #3
    Join Date
    May 2007
    Location
    Europe
    Posts
    48
    Rep Power
    8

    Default

    I tested different accounts. It works fine now. I don't know what went wrong.
    Just to be sure I have deleted backup directory, recreate, check permissions and run full backup.
    Last edited by Aleks; 05-21-2008 at 09:46 AM.

  4. #4
    Join Date
    May 2007
    Location
    Europe
    Posts
    48
    Rep Power
    8

    Default

    Now I have very similar problem with another Zimbra NE server.

    I upgraded Zimbra from 5.0.2 to 5.0.5 (Suse 10) on May 11 2008.
    I don't think this is an upgrade issue.

    When I restore account from admin UI it gives me error after restore is completed. (on all accounts - attachment)
    Mails in account are restored only until May 16 and not to May 21.

    I also tried with CLI
    Code:
    zmrestore -ca -s mail.server.com -a user@server.com -pre restore_ --ignoreRedoErrors
    it did not help. (same result as with admin ui)

    I expect NE backups to be quick, stable and 100% working when needed.

    Here is error on May 11 (output of zmbackupquery -v) all other accounts are OK.
    Code:
     wiki@server.com: completed
    Error: Detected possible redo log sequence reset; expected sequence 150, but found 0 through 1; To avoid future restore problems, discard all existing backups and take a full backup of all accounts; If this error occurred during restore, try the --ignoreRedoErrors option
    com.zimbra.cs.backup.BackupServiceException: Detected possible redo log sequence reset; expected sequence 150, but found 0 through 1; To avoid fut ure restore problems, discard all existing backups and take a full backup of all accounts; If this error occurred during restore, try the --ignoreRedoErrors option
    ExceptionId:btpool0-1:1210546815052:d862bbb985094005
    Code:backup.REDOLOG_RESET_DETECTED
    	at com.zimbra.cs.backup.BackupServiceException.REDOLOG_RESET_DETECTED(BackupServiceException.java:99)
    	at com.zimbra.cs.backup.util.Utils.splitRedoLogsAtSeq(Utils.java:326)
    	at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.backupRedoLogs(FileBackupTarget.java:1085)
    	at com.zimbra.cs.backup.BackupSet.startIncrementalBackup(BackupSet.java:736)
    	at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.startIncrementalBackup(FileBackupTarget.java:883)
    	at com.zimbra.cs.backup.BackupManager.backupIncremental(BackupManager.java:317)
    	at com.zimbra.cs.service.backup.Backup.handleNetworkRequest(Backup.java:150)
    	at com.zimbra.cs.service.NetworkDocumentHandler.handle(Unknown Source)
    	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:391)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:250)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
    	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:266)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:187)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
    	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
    	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:148)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
    	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
    	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:315)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
    	at org.mortbay.jetty.Server.handle(Server.java:313)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
    	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
    Based on post http://www.zimbra.com/forums/adminis...html#post57737
    Code:
    zmrestore -ca -s mail.server.com -a user@server.com -pre restore_ -lb full-20080516.230008.315 -restoreToIncrLabel incr-20080520.230015.171
    I finally did get the mail on May 20.
    Attached Images Attached Images
    Last edited by Aleks; 05-21-2008 at 12:21 PM.

Similar Threads

  1. QUE Failure
    By tbullock in forum Administrators
    Replies: 31
    Last Post: 07-30-2008, 12:17 PM
  2. /tmp filling
    By Nutz in forum Administrators
    Replies: 8
    Last Post: 02-22-2008, 01:00 AM
  3. zimbra-core missing
    By kinaole in forum Developers
    Replies: 1
    Last Post: 10-02-2006, 11:59 AM
  4. Unable to start tomcat
    By chanck in forum Administrators
    Replies: 11
    Last Post: 06-11-2006, 12:58 AM
  5. Monitoring : Data not yet avalaible
    By s3nz3x in forum Installation
    Replies: 7
    Last Post: 11-30-2005, 06:18 PM

Posting Permissions

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