How to fix a Full Backup error

 - This article is a Work in Progress, and may be unfinished or missing sections.

Article Information
This article applies to the following ZCS versions. ZCS 8.6 ZCS 8.5 ZCS 8.0

How to fix a Full Backup error

Purpose

Fix a problem with Full Backup:

Label: full-20150315.230242.839
Type: full
Status: completed (with errors)

ERRORS

jessamine.dirain-20140718@sbgk.com.archive: system failure: backing up table: mboxgroup45.tagged_item
com.zimbra.common.service.ServiceException: system failure: backing up table: mboxgroup45.tagged_item
ExceptionId:BackupSetWorkerThread-DB:1426466884964:23a033919a9f4478
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:260)
at com.zimbra.cs.db.DbBackup.saveTable(DbBackup.java:128)
at com.zimbra.cs.backup.BackupAccountSession.storeTablesToLocalFile(BackupAccountSession.java:317)
at com.zimbra.cs.backup.FileBackupTarget$BackupAcctSession.storeTablesStage(FileBackupTarget.java:1639)
at com.zimbra.cs.backup.FileBackupTarget$BackupSetWorkerThread.run(FileBackupTarget.java:2993)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'INTO OUTFILE '/mnt/backup/backup/tmp/full-20150315.230242.839/accounts/10c/6a2/1' at line 1

Query being executed when exception was thrown:
SELECT INTO OUTFILE '/mnt/backup/backup/tmp/full-20150315.230242.839/accounts/10c/6a2/10c6a2b7-b60f-447d-8fa6-82809dd75dca/db/tagged_item.dat' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY 'n' FROM mboxgroup45.tagged_item WHERE mailbox_id = 45

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4237)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4169)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2617)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2778)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2834)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2156)
at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:1379)
at com.zimbra.cs.db.DebugPreparedStatement.execute(DebugPreparedStatement.java:308)
at org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:172)
at org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:172)
at com.zimbra.cs.db.StatTrackingPreparedStatement.execute(StatTrackingPreparedStatement.java:475)
at com.zimbra.cs.db.DbBackup.saveTable(DbBackup.java:125)
... 3 more

Full backup errors out because of a corrupted table for one user ( can be multiple users)

Resolution

Follow the next steps to fix the issue:

• Stop mailbox

zmmailboxdctl stop

• Dump that specific table, in your case the table name is tagged_item

source ~/bin/zmshutil ; zmsetvars
~/mysql/bin/mysqldump mboxgroup38 --table tagged_item -S $mysql_socket -u root  --password=$mysql_root_password > /tmp/tagged_item.sql

• Drop existing table tagged_item

$ mysql mboxgroup38
mysql>drop table tagged_item

• Restore tagged_item.sql file

mysql mboxgroup38 < /tmp/tagged_item.sql

• Restart services and run full backup again.

Additional Content

• No related content.