3 ms·
Oh, curious, It's the first backup in clojure I've seen :-) My personal recipe is less sophisticated: - znapzend on all home machines send to a homeserver reg
by kkfx 4y ago
Oh, curious, It's the first backup in clojure I've seen :-)
My personal recipe is less sophisticated:
- znapzend on all home machines send to a homeserver regularly (with enough storage), partially replicated between desktops/laptop
- homeserver backup itself via simple incremental zfs send + mbuffer with one snapshot per day (last 2 days), one per week (last 2 w) and one per month (last 1 month) offsite
- manually triggered offline local backup of the homeserver on external USB drives and a physically mirrored home server, normally on weekly basis
Nothing more, nothing less. On any major NixOS release update I rebuild one homeserver and a month or so later the second one. Desktops and homeserver custom iso are built automatically every Sunday and just left there (I know, it simply took to much time checking so...).
Essentially in case of a fault of a machine I still have data, config and ready iso for a quick reinstall. In case of logical faults (like a direct attack who compromise my data AND zfs itself) there is not much protection beside different sync times (I do NOT use all desktops/latptop at once, when they are powered off they remain behind and I have normally plenty of time to see most casual potential attacks.
Long story short for anyone: when you talk about backups talk about how you restore, or your backups will probably be just useless bits a day...