8 ms·
And for those of us for whom "D'oh, I deleted that!", or "Nooooo....I overwrote that file yesterday!" is more of a danger than "My house just burned down", I st
by meredydd 18y ago
And for those of us for whom "D'oh, I deleted that!", or "Nooooo....I overwrote that file yesterday!" is more of a danger than "My house just burned down", I strongly recommend rdiff-backup:
http://www.nongnu.org/rdiff-backup/ http://www.nongnu.org/rdiff-backup/
It's short, sweet, incremental - and, because it uses diffs, not just hardlinks and new files, it doesn't use an extra 500MB each time you add 2k to the end of a 500MB dataset.
- DougBTX 18y agoThis question doesn't seem to be addressed on the rdiff-backup site, and is the main advantage of the posted solution: How much time do you waste getting a system with a dead main disk back online? Regardless of your backup strategy, you're going to have to replace the physical disk. If the disk you are backing up to is compatible with the broken disk, you 1) already have a disk to put in your computer, and 2) you can already boot off it. So the time wasted is the absolute minimum. Even for people using rdiff, it's probably best to have a ready-to-go backup as described in the article. His recommendation of having a bootable backup is still valid, and is not limited to the "My house just burned down" case. That's what the third disk is for :-)