There are many other good backup programs (Arq, restic, borg) so I’m not being duplicacy fanboy here. I don’t shit on it because we are on different backup program forum, I genuinely hate it with passion. I’ve tested it before, and it failed miserably. It’s a flaky crap, with no official stabile version, mind you. I have no idea why people still use Duplicati, or why is it so high in google search results. While I’ve saved my Duplicati configurations to B2, Duplicacy manages filesystem snapshots on its own (on Mac and windows on Linux you have to write pre- and post- backup script yourself) Running duplicacy on each client is straightforward, eliminates extra copy, and all that synchronization work. take filesystem snapshot) then copy, then wait for copy to be done, then backup, and what if backup takes longer than time between copies? Then you need to create another local snapshot…. But why have this extra copy in the first place? On each client you would need to ensure atomicity (e.g. I think that implies everything in the staging area should actually be a copy. What would be the recommendation for how to set this up? What sorts of things should I be keeping in mind as I create a recovery plan? Should I backup the entire staging area to a single Duplicacy storage to a single B2 bucket? Should I backup each client to individual Duplicacy storages to a single B2 bucket? Use individual B2 buckets for each client? But, that 1) feels overly complex and 2) appears to fly in the face of Duplicacy’s de-duplication. The thought here is I can quickly see how much space is taken by each client. I like the idea of having three separate storage locations one for each client. However, I’m struggling a bit on the proper way to configure Duplicacy. Use Duplicacy to store the staged backups at a remote storage provider. ![]() Have each client run it’s own backup targeting a staging area on the unRAID server. My thought process is to have two lines of defense: For anything critical, I have a local git repository to retain versions, etc… Instead, I want to protect against the catastrophic failure. I’m less interested in protecting against an “oopsie” day-to-day. I have three clients I want to protect: a personal PC, a server, and a router.
0 Comments
Leave a Reply. |