4c99612258ca2acedc21dbfabbd97a73bc95d630

Author
Leszek Piątek <lpiatek@gmail.com>
Committer
Leszek Piątek <lpiatek@gmail.com>
Date

Message

Added info in readme about --cleanup flag.

Diff

 1diff --git a/README.md b/README.md
 2index 8287f78250de6bc21227962943ed79d22ed5057a..8de10d9581a40cb27dfb08c0acebab9502127ffe 100644
 3--- a/README.md
 4+++ b/README.md
 5@@ -151,6 +151,10 @@ For the [Google Cloud Storage](https://cloud.google.com/storage/) storage backen
 6         -b, --backup               runs an incremental backup
 7         -f, --full                 forces a full backup
 8         -v, --verify               verifies the backup
 9+        -e, --cleanup              cleanup the backup (eg. broken sessions), by default using
10+                                   duplicity --force flag, use --dry-run to actually log what
11+                                   will be cleaned up without removing (see man duplicity
12+                                   > ACTIONS > cleanup for details)
13         -l, --list-current-files   lists the files currently backed up in the archive
14         -s, --collection-status    show all the backup sets in the archive
15 
16@@ -220,15 +224,23 @@ Note that the commands `--restore-file` and `--restore-dir` are equivalent.
17 
18     duplicity-backup.sh [-c config_file] --verify
19 
20+**Clean the backup**
21+
22+    duplicity-backup.sh [-c config_file] --cleanup
23+
24 **Backup the script and gpg key in a encrypted tarfile (for safekeeping)**
25 
26     duplicity-backup.sh [-c config_file] --backup-script
27 
28 
29-## Cron Usage Example
30+## Cron Usage Example (backup)
31 
32     41 3 * * * /absolute/path/to/duplicity-backup.sh -c /etc/duplicity-backup.conf -b
33 
34+## Cron Usage Example (cleanup)
35+
36+    41 4 * * 1 /absolute/path/to/duplicity-backup.sh -c /etc/duplicity-backup.conf -e
37+
38 
39 ## Known issues
40