The name is short for Backup&Verify.
Bacify looks for files that
- should be in the backup (according to the source file birth time) but are not
- and files that have the same modification timestamp as in the backup but have different content.
Only the fantastic restic is supported at the moment!
Set the RESTIC_REPOSITORY and RESTIC_PASSWORD environment variables and run cargo run.
NOTE: Assuming you cloned Bacify into $HOME/dev/bacify
Create backup and verify the data in the repository:
$ cd $HOME/dev/bacify
$ export RESTIC_REPOSITORY="$HOME/tmp/restic-repo"
$ export RESTIC_PASSWORD="foo"
$ restic init
$ restic backup $HOME/dev/bacify
Verify the backup against the local files:
$ cargo run
Create backup and verify the data in the repository:
$ cd $HOME/dev/bacify
$ export RESTIC_REPOSITORY="$HOME/tmp/restic-repo"
$ export RESTIC_PASSWORD="foo"
$ restic init
$ restic backup .
Verify the backup against the local files:
$ cargo run -- --relative-path
--relative-path is needed as the snapshot metadata lists absolute paths, but the files are actually restored without the leading path components.
Warning
Read this is you get a lot of errors about missing files!
At the moment there is only support for a hard-coded, single exclude file named $HOME/.backup_exclude.
Bacify does NOT (yet) support the full exclude file syntax, only prefixes are compared!
You can use --max-age to make bacify return an error if the backup is too old. Human readable format, e.g. 3d or 2w, should work fine.
MIT