First, some duplicacy terminology:
- I presume each of your “folders” is what Duplicacy calls a repository.
- Each of your 10 repositories is backed up to a different snapshot id (aka backup id) in your local NAS storage.
- You want to maintain a copy of your local storage in a storage on Google.
For maximum flexibility, stick with separate repositories/snaphot ids, because duplicacy commands operate on either individual snapshot ids or all snapshot ids in a storage. If you combine all your folders into a single repository/snapshot id, and you later want to delete one of those folders, or apply different prune
retention policies to various folders, or omit some folders from your Google storage to save space, you’ll be out of luck.
If you’re using the same prune
retention policy for all folders and you want to copy all of them to your Google cloud storage, you can:
- Perform 10 individual backups to local-storage
-
prune -storage
local-storage -all -keep
your retention policy …
-
prune -storage
cloud-storage -all -keep
your retention policy …
-
copy -from
local-storage -to cloud-storage
-
check
local-storage -chunks
-
check
cloud-storage
The two check
commands can be run in parallel, and -chunks
is optional.
You probably don’t need to prune
every day, so that means setting up two schedules: e.g. a schedule without the prune steps to run MTWTFS, and a schedule with the prune steps to run on Sunday.
Yes, it’s a lot of jobs to set up in the Web UI. I also have 10+ repositories (e.g. one per home share, a legal-financial share, a multimedia share, and a repository for system images on each PC). These have different retention policies (e.g.-keep 30:365 -keep 7:90 -keep 1:7
for home and legal-financial, -keep 0:365 -keep 7:90 -keep 1:7
for multimedia, -keep 0:365
for system images), and I don’t want to copy system images to cloud storage. The result is many jobs in the Web UI.
Also note that storages can be initialized with different -encrypt
and -erasure-coding
options and still be copy compatible. E.g. my cloud storage has -encrypt
, I have a normally disconnected cold storage copy on a USB drive with -erasure-coding
, and my local storage has neither option.