From 4c99612258ca2acedc21dbfabbd97a73bc95d630 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Leszek=20Pi=C4=85tek?= Date: Wed, 13 Jul 2016 16:41:45 +0200 Subject: [PATCH] Added info in readme about --cleanup flag. --- README.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8287f78..8de10d9 100644 --- a/README.md +++ b/README.md @@ -151,6 +151,10 @@ For the [Google Cloud Storage](https://cloud.google.com/storage/) storage backen -b, --backup runs an incremental backup -f, --full forces a full backup -v, --verify verifies the backup + -e, --cleanup cleanup the backup (eg. broken sessions), by default using + duplicity --force flag, use --dry-run to actually log what + will be cleaned up without removing (see man duplicity + > ACTIONS > cleanup for details) -l, --list-current-files lists the files currently backed up in the archive -s, --collection-status show all the backup sets in the archive @@ -220,15 +224,23 @@ Note that the commands `--restore-file` and `--restore-dir` are equivalent. duplicity-backup.sh [-c config_file] --verify +**Clean the backup** + + duplicity-backup.sh [-c config_file] --cleanup + **Backup the script and gpg key in a encrypted tarfile (for safekeeping)** duplicity-backup.sh [-c config_file] --backup-script -## Cron Usage Example +## Cron Usage Example (backup) 41 3 * * * /absolute/path/to/duplicity-backup.sh -c /etc/duplicity-backup.conf -b +## Cron Usage Example (cleanup) + + 41 4 * * 1 /absolute/path/to/duplicity-backup.sh -c /etc/duplicity-backup.conf -e + ## Known issues