809cc5bf28
Previously, a failed backup would always overwrite ${db}.sql.gz,
because the bash `>` redirect truncates the file; even if the
backup was going to fail.
On the next run, the ${db}.prev.sql.gz backup would be
overwritten by the bad ${db}.sql.gz.
Now, if the backup fails, the ${db}.in-progress.sql.gz is in an
unknown state, but ${db}.sql.gz will not be written.
On the next run, ${db}.prev.sql.gz (our only good backup) will
not be overwritten because ${db}.sql.gz does not exist.
(cherry picked from commit 81c8189a841728a813bcde8604b80427fcf33522)
|
||
|---|---|---|
| .. | ||
| automysqlbackup.nix | ||
| bacula.nix | ||
| borgbackup.nix | ||
| borgbackup.xml | ||
| borgmatic.nix | ||
| duplicati.nix | ||
| duplicity.nix | ||
| mysql-backup.nix | ||
| postgresql-backup.nix | ||
| postgresql-wal-receiver.nix | ||
| restic-rest-server.nix | ||
| restic.nix | ||
| rsnapshot.nix | ||
| sanoid.nix | ||
| syncoid.nix | ||
| tarsnap.nix | ||
| tsm.nix | ||
| zfs-replication.nix | ||
| znapzend.nix | ||
| zrepl.nix | ||