Errors in incremental backups: Difference between revisions
Line 40: | Line 40: | ||
|} | |} | ||
{{Article Footer|ZCS 8. | {{Article Footer|ZCS 8.7|2020-04-13}} |
Revision as of 07:14, 15 May 2020
Errors in incremental backups
- This article is a Work in Progress, and may be unfinished or missing sections.
Problem
When automatic incremental backup is executed on the server, following message is displayed :
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 |