On Apr 21, 2013, at 08:16 AM, "Edward Ned Harvey (lopser)" <[email protected]> wrote:
At $PREVIOUSJOB, I wrote a Perl frontend for rdiff-backup that I kicked off nightly via cron to backup shared /home (NFS- and samba-mounted on clients) and a few other important data locations. It was a lifesaver when clobbered data needed restoring.
I'm not sure exactly what you mean by this, but I definitely value the commit-style nature of git as a version-tracking mechanism, where rdiff-backup (or duplicity) just copies filesystem snapshots. Version control != backup, no matter how incremental/differential the system.
--
Brad Beyenhof . . . . . . . . . . . . . . . . http://augmentedfourth.com
No, no, you're not thinking; you're just being logical.
~ Niels Bohr
[snip]> From: [email protected] [mailto:[email protected]]
> On Behalf Of Yves Dorfsman
>
> What did this give you that an rdiff-backup wouldn't?
I've never used rdiff-backup before.
Thanks for the suggestion. Will give it a try.
At $PREVIOUSJOB, I wrote a Perl frontend for rdiff-backup that I kicked off nightly via cron to backup shared /home (NFS- and samba-mounted on clients) and a few other important data locations. It was a lifesaver when clobbered data needed restoring.
Although I'm surprised it doesn't have any comment capability.
I'm not sure exactly what you mean by this, but I definitely value the commit-style nature of git as a version-tracking mechanism, where rdiff-backup (or duplicity) just copies filesystem snapshots. Version control != backup, no matter how incremental/differential the system.
--
Brad Beyenhof . . . . . . . . . . . . . . . . http://augmentedfourth.com
No, no, you're not thinking; you're just being logical.
~ Niels Bohr
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
