From 6d96b400385e5e650c91ecb6c7705e72e67dd438 Mon Sep 17 00:00:00 2001 From: Adam Weinberger Date: Sat, 28 Mar 2020 11:19:46 -0600 Subject: [PATCH] Add FAQ about separate targets, calsnap link (#44) --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 9450118..803f547 100644 --- a/README.md +++ b/README.md @@ -73,6 +73,14 @@ to wherever you put this script: tarsnap --dry-run --quiet --print-stats --humanize-numbers -C / -c $backuptargets 2>&1 ``` +* **Why does `acts` create a separate backup for each target?** This is the +original recommended paradigm for `tarsnap`, the idea being that you save +bandwidth (and therefore money) by only retrieving the pieces you need. If +`/etc` gets damaged, why download the entirety of `/home`? If this paradigm +doesn't fit your needs and workflow, there is a fork of `acts` +called [calsnap](https://github.com/bannmann/calsnap) that produces one +backup containing all targets. + Help ----