On 2012-10-05 04:46, Chris Manly wrote:
In a previous job, I had an epiphany that the most critical database that the
company used was actually not that big. At close of business each day, I did
a full text dump of that database and auto-committed it into svn. This gave
us a history of the database more or less in perpetuity, with a daily
granularity.
The idea was to protect against a situation where some bad data or corruption
crept into the database but didn't get discovered for many moons. (Given the
state of the application that was feeding data in, this was not inconceivable)
This would give us a way to go back and untangle things.
I do that, but with rdiff-backup.
Where I draw the line is:
-is there value to have a diff for every change?
==> yes, then use a VCS, and use it between each changes.
Good candidates for this are ldif files, DNS krb.conf files etc...
-no value, or cannot keep a diff for every change, but still a lot of value to
keep say a daily checkpoint?
==> use rdiff-backup, ddar, netapps snapshots.
Perfect for /etc, small databases' dumps.
Using a distriuted VCS on your home directory is a different case, the
advantage here is not to go back in history, but to be able to work on the
same directory from different machine, merging changing text files etc...
think of it as dropbox on steroid.
--
Yves. http://www.SollerS.ca/
http://ipv6.SollerS.ca
http://blog.zioup.org/
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
