4 ms·
http://www.jwz.org/doc/backups.html http://www.jwz.org/doc/backups.html i've been using the above as a really half assed way of doing backups on a server. usin
by throwawayaway 12y ago
http://www.jwz.org/doc/backups.html http://www.jwz.org/doc/backups.html
i've been using the above as a really half assed way of doing backups on a server. using a nas instead of a usb hdd. very glad to benefit from the experience of others here.
- icebraining 12y agoIf you're using Linux, it's something a lot like that. If you're using Windows, go fuck yourself. : ) jwz's method is fine for disaster recovery, but it doesn't work for recovery from other kinds of errors (including human) since it only saves the last copy of the files. In our case, the most important backups are the databases (servers can be rebuilt from config management), and having past copies definitively helps. With rdiff-backup, we can restore the databases from any day for the past couple of years, and since it's incremental, it doesn't really take up much space.
- wampus 12y agoI use rdiff-backup as my main backup solution. It's efficient and restoring from the latest backup is reasonably fast and simple. But I've found that the further you go back in time, reconstructing the file from all the deltas takes so long I don't consider it useful as an archiving solution. At least that seems to be true for large and/or complex collections of files. Have you actually restored large databases from years ago in less than a few hours?
- icebraining 12y agoWe usually only restore revisions a few weeks old. That said, rdiff-backup works by taking the current mirror file and applying past diffs, so you could probably keep an older mirror (and current_mirror file from the rdiff-backup-data directory) to speed up the process.