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. -- Christopher Manly Coordinator, Library Systems Cornell University Library Information Technologies [email protected] 607-255-3344 From: Aaron McCaleb <[email protected]<mailto:[email protected]>> Date: Wednesday, October 3, 2012 5:59 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [lopsa-discuss] Question: Unorthodox applications of version control Hello, all. I'm suffering a bout of unsatisfied curiosity: What are some un-orthodox, but useful applications for version control systems (VCS) that you have employed or heard of others employing in day-to-day work? My own un-original example: importing my home directory into a VCS repository to essentially provide an archive solution with considerable "backup" history. (This was something I remember being suggested in a magazine article, possibly by David Blank-Edelman [ http://goo.gl/jJwiP ]. He also suggested this in one of his "Over-the-edge System Administration" talks at LISA'07, I think.) Cheers! --Aaron
_______________________________________________ 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/
