{"id":2474,"date":"2005-04-18T12:56:26","date_gmt":"2005-04-18T12:56:26","guid":{"rendered":"http:\/\/www.soulhuntre.com\/items\/date\/2005\/04\/18\/its-all-under-version-control\/"},"modified":"2005-04-18T12:56:26","modified_gmt":"2005-04-18T12:56:26","slug":"its-all-under-version-control","status":"publish","type":"post","link":"http:\/\/legacyiamsenseiken.local\/2005\/04\/18\/its-all-under-version-control\/","title":{"rendered":"It&#8217;s all under (version) control&#8230;"},"content":{"rendered":"<p>After a lot of looking around, I have currently settled on <a href=\"\/\/\/sh_external\">Subversion<\/a> as a core part of my backup strategy. For the most part it is going to operate like this:<\/p>\n<blockquote>\n<p>important &#8220;controlled&#8221; data &lt;-&gt; repository server &lt;-&gt; versioning &#8220;hot&#8221; backup server &lt;-&gt; offline storage<\/p>\n<p>important &#8220;non controlled&#8221; data &lt;-&gt; repository server &lt;-&gt; versioning &#8220;hot&#8221; backup server &lt;-&gt; offline storage<\/p>\n<\/blockquote>\n<p>This is true for &gt;all&lt; the important data. There are really two different types of versioning servers in my worldview and each have their place. <\/p>\n<ul>\n<li><u><b>repository servers<\/b><\/u>: these are the traditional &#8220;source code control&#8221; servers. In a repository server when you &#8220;check in&#8221; or &#8220;commit&#8221; a change you are asked to supply a comment or explanation of the change. It handles grouping multiple files at a particular point in time into a &#8220;release&#8221; and so on. This allows me to batch up all the files form a web site or programming project and say &#8220;this is release 1.0&#8221; and so on. Very useful stuff for the right kind of data. Currently I am using <a href=\"\/\/\/sh_external\">Subversion<\/a> for this.<\/li>\n<li><u><b>versioning hot backup servers<\/b><\/u>: these are systems that monitor activity for specific files, folders and make backups of those changes in close to real time. No specific action is necessary to &#8220;check in&#8221; a file, as soon as you save it it is backed up. You can &#8220;roll back&#8221; to any previous version fo the file you might need. At the moment I am probably going to wait for &#8220;<a href=\"\/\/\/sh_external\">Microsoft Data Protection Manager<\/a>&#8221; to handle this part.<\/li>\n<\/ul>\n<p>The important difference is that repositories know about your data&#8217;s logical history and organization. They understand what files go together, can show you the commented history of a file and do a good job of merging changes made by multiple people. Versioned backups don&#8217;t always have that.<\/p>\n<p>For me this means that data that is part of an organized, incremental development process (websites, software, artwork, etc.) where you might want to gather and put out &#8220;releases&#8221; or have multiple people working on them at the same time should go in repositories. Data that is not part of a formalized incremental development process (email data files, the &#8220;My Documents&#8221; folder, even the <i>repositories themselves<\/i>) should just go straight to the hot backups.<\/p>\n<p>So far, stage one complete. I have my repositories in place and I am also using them as a limited &#8220;hot backup&#8221; system. For example my email files are in a &#8220;soulhuntre&#8221; repository, and I check them in ever day or so. Eventually I will take the next step.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After a lot of looking around, I have currently settled on Subversion as a core part of my backup strategy. For the most part it is going to operate like this: important &#8220;controlled&#8221; data &lt;-&gt; repository server &lt;-&gt; versioning &#8220;hot&#8221; backup server &lt;-&gt; offline storage important &#8220;non controlled&#8221; data &lt;-&gt; repository server &lt;-&gt; versioning &#8220;hot&#8221; [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"aside","meta":{"footnotes":""},"categories":[278],"tags":[],"_links":{"self":[{"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/posts\/2474"}],"collection":[{"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/comments?post=2474"}],"version-history":[{"count":0,"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/posts\/2474\/revisions"}],"wp:attachment":[{"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/media?parent=2474"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/categories?post=2474"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/legacyiamsenseiken.local\/wp-json\/wp\/v2\/tags?post=2474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}