How to fix a Full Backup error

Revision as of 18:50, 11 July 2015 by Jorge de la Cruz (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

How to fix a Full Backup error

   KB 21933        Last updated on 2015-07-11  

(0 votes)


Fix a problem with Full Backup:

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

ERRORS system failure: backing up table: mboxgroup45.tagged_item
com.zimbra.common.service.ServiceException: system failure: backing up table: mboxgroup45.tagged_item
at com.zimbra.common.service.ServiceException.FAILURE(
at com.zimbra.cs.db.DbBackup.saveTable(
at com.zimbra.cs.backup.BackupAccountSession.storeTablesToLocalFile(
at com.zimbra.cs.backup.FileBackupTarget$BackupAcctSession.storeTablesStage(
at com.zimbra.cs.backup.FileBackupTarget$
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(
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
at java.lang.reflect.Constructor.newInstance(
at com.mysql.jdbc.Util.handleNewInstance(
at com.mysql.jdbc.Util.getInstance(
at com.mysql.jdbc.SQLError.createSQLException(
at com.mysql.jdbc.MysqlIO.checkErrorPacket(
at com.mysql.jdbc.MysqlIO.checkErrorPacket(
at com.mysql.jdbc.MysqlIO.sendCommand(
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(
at com.mysql.jdbc.ConnectionImpl.execSQL(
at com.mysql.jdbc.PreparedStatement.executeInternal(
at com.mysql.jdbc.PreparedStatement.execute(
at com.zimbra.cs.db.DebugPreparedStatement.execute(
at org.apache.commons.dbcp.DelegatingPreparedStatement.execute(
at org.apache.commons.dbcp.DelegatingPreparedStatement.execute(
at com.zimbra.cs.db.StatTrackingPreparedStatement.execute(
at com.zimbra.cs.db.DbBackup.saveTable(
... 3 more

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


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.

Verified Against: Zimbra Collaboration 8.6, 8.5, 8.0 Date Created: 05/05/2015
Article ID: Date Modified: 2015-07-11

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 »

Wiki/KB reviewed by SME1 SME2 Copyeditor Last edit by Jorge de la Cruz
Jump to: navigation, search