On 2013-04-21 10:34, Edward Ned Harvey (lopser) wrote:
rdiff-backup is more well suited for the former description you've described, although it can certainly be used in the latter. Because rdiff-backup maintains history indefinitely (unless otherwise instructed) you probably don't want to run it frequently. It's well suited to be run manually to record meaningful changes throughout history. It only lacks the ability to store a version comment.
I run rdiff-backup on /etc through cron. It takes very little space (because of the diff and using links. I find once daily is good enough on a stable system, and it allows you to pinpoint what day the change happened.
I personally prefer rdiff-backup for /etc on a prod server that's not under config management, rsnapshot for the home directory of a developer (although if there's money around I'd much prefer a good NAS solution for this).
-- Yves. http://www.SollerS.ca/ Unix/Linux and Python specialist in Calgary. http://blog.zioup.org/ _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
