File Backup Update (tar)

Simon Bennett 15th December 2020

The following was emailed to all users using the Tar Backup system

We have made a change to the way we deal with errors with Tar Backups. You may have noticed an increase in the number of backups that notify completed with error.

When we recreated the backup system and launched in November, we went to a method of using the backup programs exit code to decide if an error happened. If the process exited with none 0, we would check to see if the file was created and notify completed with error.

This has worked create expect for with TAR that will throw an exit code one if a file changes during the backup process (e.g. a log file changed). These are not issues to backups, we all expect files to change, this is why we backup!

The fix:

  • From today the file backups will accept a TAR exit code equal or less than one as a success
  • Our logs will still show the TAR warnings, but you will receive a success notification, on a 0 or 1 exit code

You can edit your notification settings here

While we think this is an improvement, I wanted to message everyone using the TAR backups to confirm the new behaviour; please reach out if you have questions or concerns.

Get Started Now

Get started with SnapShooter for free!
Backup one droplet, volume or mysql database