2 ms·
Are there any pros/cons to this approach versus rdiff-backup?: http://www.nongnu.org/rdiff-backup/ http://www.nongnu.org/rdiff-backup/
by _delirium 17y ago
Are there any pros/cons to this approach versus rdiff-backup?: http://www.nongnu.org/rdiff-backup/ http://www.nongnu.org/rdiff-backup/
- andrewcooke 17y agordiff-backup does (more or less) the same thing, but is simpler to use, as far as i can tell (i switched from rsync to rdiff-backup about a year ago, and haven't looked back).
- barrkel 17y agoI use rdiff-backup too, and since it stores the diffs, you can go back in time. I also backup the rdiff-backup tree itself to a remote location.
- andrewvc 17y agoI use rsnapshot and rdiff-backup, the big difference is rdiff-backup chokes on larger file volumes. I have a backup with a million+ video and image files, at around 600 gigs. rdiff-backup doesn't like this very much, and spends way more time backing it up than rsnapshot. There were other more serious problems, but I made the switch a year or two ago and I can't remember what they were. Additionally, the braindead simplicity of rsnapshot makes it much easier to verify backups without having to do a restore first. That said, I use rdiff-backup to back up /etc on all my systems to a local backup directory for quick access if anything gets accidentally fucked up while reconfiguring a service. It really is better for small datasets. My backup hierarchy, in terms of complexity / size of the job, generally goes: rdiff-backup (small stuff) -> rsnapshot (bigger stuff) -> bacula (mammoth stuff)