Backups/restores fail after 4.5.5->4.5.6 upgrade?

[gkra]

we're running the NE trial and upgraded from 4.5.5 to 4.5.6 last night.

The incremental backup last night failed, though subsequent full backups claimed to succeed. However, I'm getting the following error when trying to restore a user's mailbox from the most recent (successful) full backup via the admin web console:

Message: system failure: Restore encountered redo log sequence error: Found gap in redo log sequence; missing 8 through 164; 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
Error code: service.FAILURE
Method: ZmCsfeCommand.prototype.invoke
Details:soap:Receiver

The nightly incremental restore that happened automatically last night post-upgrade completed with this error:

system
Detected possible redo log sequence reset; expected sequence 379, but found 0 through 5; 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 379, but found 0 through 5; 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 at com.zimbra.cs.backup.BackupServiceException.REDOLO G_RESET_DETECTED(BackupServiceException.java:101) at com.zimbra.cs.backup.util.Utils.splitRedoLogsAtSeq (Utils.java:403) at com.zimbra.cs.backup.FileBackupTarget$FileBackupSe t.backupRedoLogs(FileBackupTarget.java:1034) at com.zimbra.cs.backup.BackupSet.startIncrementalBac kup(BackupSet.java:636) at com.zimbra.cs.backup.FileBackupTarget$FileBackupSe t.startIncrementalBackup(FileBackupTarget.java:836 ) at com.zimbra.cs.backup.BackupManager.backupIncrement al(BackupManager.java:324) at com.zimbra.cs.service.backup.Backup.handleNetworkR equest(Backup.java:116) at com.zimbra.cs.service.NetworkDocumentHandler.handl e(Unknown Source) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:270) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:168) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:90) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223) at javax.servlet.http.HttpServlet.service(HttpServlet .java:709) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet .java:802) at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541) at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)

Any ideas what to do?

[mmorse]

Are you testing the restore of this mailbox to see if it's working properly or is this critical for someone?
Schema changes in upgrades tend to invalidate old backups...
If you were just testing:
Pretty much do what it says...so in some downtime window - zmcontrol stop, move the redolog & prior backups to a safe place (just for insurance), zmcontrol start, & run a full backup.

[gkra]

Well, it was a test restore. Doing the restore from the command line and using the --ignoreRedoErrors option got me the data.

However, during an opportunity for downtime, I move the existing backups and redolog aside and let Zimbra start from scratch. After restarting, though, backups just disappear without an error message.

zmbackupquery reports no backups, and I find a full backup in /opt/zimbra/backups/tmp.

Attempts to perform any backups at this point fail silently, and leave carcasses in /opt/zimbra/backup/tmp. This is, as you might understand, undesirable.

I'd really like to get the backups working again.

[mmorse]

You do have free support during your trial period: support.zimbra.com/supportlogin.php