Continuing the discussion from Best Practice: copy from local server to remote and Duplicacy copy confusion/question:
I’d like to confirm something related to the posts above.
I currently have a local server (NAS) that has many directories split across several repositories, that are all encrypted with the same password and all backup to the same offsite storage (B2).
What I’d like to do is set up duplicacy on a local client, and have it backup to the NAS (set up as the storage), then have the NAS “copy” that backup set to B2. So the NAS acts as both a source for a large chunk of data, that goes to B2, and as a destination for a client computer (and I want that destination to also be saved into B2)
My questions are around encryption and deduplication.
- In order for any deduplication to take place in what’s saved at B2, does the repository on the local client need to be encrypted with the same password as the repositories on the NAS? (think answer is yes)
- Similarly, I would have to do a
duplicacy copy
from the NAS to B2 for the local client repository, correct? (in order for it to do deduplication) i.e. I could not just rsync that data to the offsite location into the same bucket, because it wouldn’t know about the other repositories that exist on the NAS (only as source data, not in an already-backed up format). - If the answer the #2 is yes, and given that the repositories on the NAS are already initialized and backing up to B2, where and when do the
copy
andbit-identical
parameters ofduplicacy add
come into play? I am just creating the repository on the client machine now so have flexibility there, but have several TB of data already on B2 from the NAS.
Thanks!