Difference between revisions of "Errors in incremental backups"

(Created page with "===<h1>Errors in incremental backups</h1>=== <hr> <br> <h2>Problem:</h2> When the system performs an automatic incremental backup, indicates the following message: '''Finish...")
 
(Errors in incremental backups)
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
===<h1>Errors in incremental backups</h1>===
+
=Errors in incremental backups=
 
<hr>
 
<hr>
<br>
+
{{KB|{{ZC}}|{{ZCS 8.7}}||||}}
  
<h2>Problem:</h2>
 
  
When the system performs an automatic incremental backup, indicates the following message: '''Finished with errors'''
 
  
This error occurs only when you perform incremental backups. The error message is as follows :
+
====Problem====
 +
 
 +
When automatic incremental backup is executed on the server, following message is displayed in /opt/zimbra/log/mailbox.log file :  
  
 
<pre>
 
<pre>
 
Found gap in redo log sequence; missing 1414 through 1446; 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
 
Found gap in redo log sequence; missing 1414 through 1446; 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: Found gap in redo log sequence; missing 1414 through 1446; 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 ExceptionId:qtp662845511-542373:https://127.0.0.1:7071/service/admin/soap/BackupRequest:1463637618095:568e4f96fbb74864 Code:backup.REDOLOG_OUT_OF_SEQUENCE at com.zimbra.cs.backup.BackupServiceException.REDOLOG_OUT_OF_SEQUENCE(BackupServiceException.java:91) at com.zimbra.cs.backup.util.Utils.splitRedoLogsAtSeq(Utils.java:301) at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.backupRedoLogs(FileBackupTarget.java:1278) at com.zimbra.cs.backup.BackupSet.startIncrementalBackup(BackupSet.java:817) at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.startIncrementalBackup(FileBackupTarget.java:1072) at com.zimbra.cs.backup.BackupManager.backupIncremental(BackupManager.java:335) at com.zimbra.cs.service.backup.Backup.handleNetworkRequest(Backup.java:153) at com.zimbra.cs.service.NetworkDocumentHandler.handle(NetworkDocumentHandler.java:23) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:522) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:385) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:258) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:210) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:207) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:654) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1320) at com.zimbra.cs.servlet.RequestStringFilter.doFilter(RequestStringFilter.java:52) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:57) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82) at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:256) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at com.zimbra.cs.servlet.ETagHeaderFilter.doFilter(ETagHeaderFilter.java:45) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at com.zimbra.cs.servlet.ZimbraQoSFilter.doFilter(ZimbraQoSFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:474) at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:345) at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:316) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1291) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:443) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:556) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:317) at org.eclipse.jetty.server.handler.DebugHandler.handle(DebugHandler.java:81) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:369) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:944) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1005) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SslConnection.handle(SslConnection.java:196) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:744)
+
com.zimbra.cs.backup.BackupServiceException: Found gap in redo log sequence; missing 1414 through 1446; 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  
 +
ExceptionId:qtp662845511-542373:https://127.0.0.1:7071/service/admin/soap/BackupRequest:1463637618095:568e4f96fbb74864  
 +
Code:backup.REDOLOG_OUT_OF_SEQUENCE  
 +
at com.zimbra.cs.backup.BackupServiceException.REDOLOG_OUT_OF_SEQUENCE(BackupServiceException.java:91)  
 +
        at com.zimbra.cs.backup.util.Utils.splitRedoLogsAtSeq(Utils.java:302)
 +
        at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.backupRedoLogs(FileBackupTarget.java:1360)
 +
        at com.zimbra.cs.backup.BackupSet.startIncrementalBackup(BackupSet.java:817)
 +
        at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.startIncrementalBackup(FileBackupTarget.java:1067)
 +
        at com.zimbra.cs.backup.BackupManager.backupIncremental(BackupManager.java:336)
 +
        at com.zimbra.cs.service.backup.Backup.handleNetworkRequest(Backup.java:153)
 +
        at com.zimbra.cs.service.NetworkDocumentHandler.handle(NetworkDocumentHandler.java:23)
 +
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:569)
 +
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:432)
 
</pre>
 
</pre>
  
<h2>Solution:</h2>
+
====Solution====
  
1) During a backup, if the above error is seen, the recommendation is to move the old backups out. The directories in /opt/zimbra/backup/sessions/* . It's advised to keep them somewhere at a different location to be on the safer side and then proceed to do a full backup.
+
* During a backup if the above error is seen, the recommendation is to move the old backups out - the directories in /opt/zimbra/backup/sessions/* .
  
2) Another possibe cause is if the /tmp or /opt/zimbra/redolog/ is filling up. Ensure that there is enough disk  space available.
+
* It's advised to keep them somewhere at a different location to be on the safer side and then proceed to do a full backup.
  
 +
* Another possibe cause is the /tmp or /opt/zimbra/redolog/ filling up. Ensure that there is enough disk space available.
  
  
"Aarti Shah"
+
{| class="wikitable" style="background-color:#d0f0c0;" cellpadding="10"
 +
|'''Submitted by''':  Aarti Shah
 +
|}
  
<ashah@zimbra.com>
+
{{Article Footer|ZCS 8.7|2020-04-13}}

Latest revision as of 07:30, 23 May 2020

Errors in incremental backups


   KB 23304        Last updated on 2020-05-23  




0.00
(0 votes)


Problem

When automatic incremental backup is executed on the server, following message is displayed in /opt/zimbra/log/mailbox.log file :

Found gap in redo log sequence; missing 1414 through 1446; 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: Found gap in redo log sequence; missing 1414 through 1446; 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 
ExceptionId:qtp662845511-542373:https://127.0.0.1:7071/service/admin/soap/BackupRequest:1463637618095:568e4f96fbb74864 
Code:backup.REDOLOG_OUT_OF_SEQUENCE 
	at com.zimbra.cs.backup.BackupServiceException.REDOLOG_OUT_OF_SEQUENCE(BackupServiceException.java:91) 
        at com.zimbra.cs.backup.util.Utils.splitRedoLogsAtSeq(Utils.java:302)
        at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.backupRedoLogs(FileBackupTarget.java:1360)
        at com.zimbra.cs.backup.BackupSet.startIncrementalBackup(BackupSet.java:817)
        at com.zimbra.cs.backup.FileBackupTarget$FileBackupSet.startIncrementalBackup(FileBackupTarget.java:1067)
        at com.zimbra.cs.backup.BackupManager.backupIncremental(BackupManager.java:336)
        at com.zimbra.cs.service.backup.Backup.handleNetworkRequest(Backup.java:153)
        at com.zimbra.cs.service.NetworkDocumentHandler.handle(NetworkDocumentHandler.java:23)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:569)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:432)

Solution

  • During a backup if the above error is seen, the recommendation is to move the old backups out - the directories in /opt/zimbra/backup/sessions/* .
  • It's advised to keep them somewhere at a different location to be on the safer side and then proceed to do a full backup.
  • Another possibe cause is the /tmp or /opt/zimbra/redolog/ filling up. Ensure that there is enough disk space available.


Submitted by: Aarti Shah
Verified Against: ZCS 8.7 Date Created: 2020-04-13
Article ID: https://wiki.zimbra.com/index.php?title=Errors_in_incremental_backups Date Modified: 2020-05-23



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »


Jump to: navigation, search