discourse/lib/backup_restore
Gerhard Schlager 220944a38a FIX: Unpause sidekiq before adding uploads to backup
tar exits with status 1 when uploads are modified or deleted by a sidekiq job, so we need to treat it like status 0.

According to the documentation it should be safe to ignore status 1 ("Some files differ"):

> If tar was given `--create', `--append' or `--update' option, this exit code means that some files were changed while being archived and so the resulting archive does not contain the exact copy of the file set.

Status 2 ("Fatal error") still results in an exception.
2019-02-12 13:50:50 +01:00
..
backup_restore.rb FEATURE: Support backup uploads/downloads directly to/from S3. 2018-10-15 09:43:31 +08:00
backup_store.rb FEATURE: Improve backup stats on admin dashboard 2018-12-17 11:35:11 +01:00
backuper.rb FIX: Unpause sidekiq before adding uploads to backup 2019-02-12 13:50:50 +01:00
local_backup_store.rb FIX: Raise or log error when deleting of backup fails 2019-01-24 22:26:50 +01:00
restorer.rb FIX: Allow restore when latest migration is a post_migration 2019-02-08 17:37:05 +01:00
s3_backup_store.rb FEATURE: Use amazon s3 inventory to manage upload stats (#6867) 2019-02-01 10:10:48 +05:30