3 ms·
I recommend taking a look on borg backup (https://borgbackup.readthedocs.io/ https://borgbackup.readthedocs.io/) or restic (https://github.com/restic/restic htt
by sandreas 9y ago
I recommend taking a look on borg backup (https://borgbackup.readthedocs.io/ https://borgbackup.readthedocs.io/) or restic (https://github.com/restic/restic https://github.com/restic/restic) instead of rsync... and use snapshots for zfs.
- reacharavindh 9y agoI use BorgBackup for backing up my personal website (in the order of a few MBs) to learn. But, my use case in this quest is to build a long-term backup solution that we can rely on. (10 years+). My concern is Borgbackup being updated so frequently and being actively developed to add more features. What is the chance that I can read a backup that I make today 10 years from now? I do NOT want to maintain a directory full of borgbackup binaries of different versions just to be able to access older backups. Same goes with running unupdated version of Borgbackup for 10 years.. Hence my interest to keep things stupidly simple with NFS --> ZFS server.
- sandreas 9y agoWell, that is understandable... but i think, that rsync has major drawbacks: No history - overwriting means destroying (e.g. ransomware) || No deduplication - restic transfers blockwise and only once || No encryption - access to backup means access to all data || No error protection - how to verify backup success? In my opinion a good backup should contain a verified restore strategy :-) You should also consider sending and receiving snapshots, when using zfs (https://docs.oracle.com/cd/E18752_01/html/819-5461/gbchx.html https://docs.oracle.com/cd/E18752_01/html/819-5461/gbchx.htm...). Zfs also supports deduplication, but FreeNAS devs do not recommend using it unless you have a massive amount of RAM and you know what you are doing.