Manual or scheduled full backup shows a failed for large backups
Last Updated December 19, 2017
When running a manual or schedule backup you are receiving an alert that the backup failed. In the Graphical Interface you notice the that the backup is shown as failed. Db-backup is the process generating the error.
While generating an error the backup is valid and can be restored.
When running the backup manually in debug you'll see the following error type:
ERROR: Failed to run: '/bin/tar -rf /data/tmp/db-backup.10.6.1-3.brightmail.<date>.tar /data/tmp/mysql_dump_file /data/tmp/sms-appliance-release-10.6.1-3.noarch
/data/tmp/db-backup-type': /bin/tar: Removing leading `/' from members names /bin/tar: /data/tmp/mysql_dump_file: file changed as we read it.
This is a known issue with the "tar" command we are using when dealing with large-size files.
This issue has been addressed with the SMG 10.6.4 release.
For earlier releases, this is a false alarm given by the tar facility, the backup file will still be valid and can be restored.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe