a backup script to send backups over email when changed #131
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a home-grown backup script that I built for a local HotCRP
installation, but I thought that it may be useful to others as
well. The backup strategy is detailed as follows:
a backups/ directory at the project root with at most two backups saved,
the last one (
new
) and the one before that (old
)whenever the script runs, it moves
new
toold
and creates a newnew
file using thebackupdb.sh
script; then it comparesnew
and
old
, and sends the new backup by email if it differs from theold one
if a
passphrase
file exists in thebackups
directory, thenit is used as a passphrase for
gpg
to encrypt the backup fileImplementation remarks:
--skip-dump-date
tomysqldump
, otherwise the backups would always differcd
to its base directory, so that the script can be invoked directly from a crontab.