<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The cost of backups</title>
	<atom:link href="http://sububi.org/2007/02/14/the-cost-of-backups/feed/" rel="self" type="application/rss+xml" />
	<link>http://sububi.org/2007/02/14/the-cost-of-backups/</link>
	<description>Computing, education, and some embedded bits</description>
	<lastBuildDate>Fri, 11 Feb 2011 23:43:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Matt</title>
		<link>http://sububi.org/2007/02/14/the-cost-of-backups/#comment-1229</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 16 Feb 2007 14:54:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.sububi.org/2007/02/14/the-cost-of-backups/#comment-1229</guid>
		<description>Absolutely true. I&#039;m looking for something that is a compromise between simplicity to implement (for the end-user) and a back-end that scales in cost with usage.

As I discover the limitations of the solutions I implement, I&#039;ll find better solutions that are more refined. Ultimately, I want something that &quot;does the right thing&quot; that requires minimal effort to set up, and minimal effort to maintain. I don&#039;t want to be a sysadmin for every machine I touch, just to guarantee a bit of data safety. And ultimately, I have to be able to deploy my solution (largely unattended) on my wife&#039;s laptop, and both her parent&#039;s machine and my parent&#039;s machine. There are no rsync-based solutions for the Mac (that I know of) that I can just &quot;install and walk away from&quot; that will do the job.

So, I keep searching for the compromise that works best.</description>
		<content:encoded><![CDATA[<p>Absolutely true. I&#8217;m looking for something that is a compromise between simplicity to implement (for the end-user) and a back-end that scales in cost with usage.</p>
<p>As I discover the limitations of the solutions I implement, I&#8217;ll find better solutions that are more refined. Ultimately, I want something that &#8220;does the right thing&#8221; that requires minimal effort to set up, and minimal effort to maintain. I don&#8217;t want to be a sysadmin for every machine I touch, just to guarantee a bit of data safety. And ultimately, I have to be able to deploy my solution (largely unattended) on my wife&#8217;s laptop, and both her parent&#8217;s machine and my parent&#8217;s machine. There are no rsync-based solutions for the Mac (that I know of) that I can just &#8220;install and walk away from&#8221; that will do the job.</p>
<p>So, I keep searching for the compromise that works best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://sububi.org/2007/02/14/the-cost-of-backups/#comment-1228</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Fri, 16 Feb 2007 14:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sububi.org/2007/02/14/the-cost-of-backups/#comment-1228</guid>
		<description>Databases are not going to go away just because people are starting to get backup religion.

ID3 information in audio files is another example of the same thing, albeit on a smaller scale. Changing the metadata currently requires the entire file to be backed up again.

The solution to this problem will be better backup tools, which can do binary deltas, like rsync does.</description>
		<content:encoded><![CDATA[<p>Databases are not going to go away just because people are starting to get backup religion.</p>
<p>ID3 information in audio files is another example of the same thing, albeit on a smaller scale. Changing the metadata currently requires the entire file to be backed up again.</p>
<p>The solution to this problem will be better backup tools, which can do binary deltas, like rsync does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://sububi.org/2007/02/14/the-cost-of-backups/#comment-1227</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Thu, 15 Feb 2007 16:19:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.sububi.org/2007/02/14/the-cost-of-backups/#comment-1227</guid>
		<description>Actually, I&#039;m starting to think that way... also for my pile-o-files that I keep for reference. Using a local Subversion repository that gets hit by the S3 sync might be a good solution.

I could also write a script that swaps the SQLite DBs around; they&#039;re just one file, in a fixed location. In fact, using something like Tapir (Google for it; you&#039;ll find it on the same site as Platypus) I could easily make my own drop-down Apple menubar item for this. The point being, I could have one DB for little stuff, and one for big stuff.

So, yeah, there&#039;s a bunch of ways to work around this. :)</description>
		<content:encoded><![CDATA[<p>Actually, I&#8217;m starting to think that way&#8230; also for my pile-o-files that I keep for reference. Using a local Subversion repository that gets hit by the S3 sync might be a good solution.</p>
<p>I could also write a script that swaps the SQLite DBs around; they&#8217;re just one file, in a fixed location. In fact, using something like Tapir (Google for it; you&#8217;ll find it on the same site as Platypus) I could easily make my own drop-down Apple menubar item for this. The point being, I could have one DB for little stuff, and one for big stuff.</p>
<p>So, yeah, there&#8217;s a bunch of ways to work around this. <img src='http://sububi.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave G</title>
		<link>http://sububi.org/2007/02/14/the-cost-of-backups/#comment-1226</link>
		<dc:creator>Dave G</dc:creator>
		<pubDate>Thu, 15 Feb 2007 09:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.sububi.org/2007/02/14/the-cost-of-backups/#comment-1226</guid>
		<description>Here&#039;s a geeky thought. What if... you backed up your Yojimbo file to an SVN repository, and backed up the repository to S3? Presumably when you commit Yojimbo, SVN would only grow by one delta. That way the cost of transfer would be cheap.</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a geeky thought. What if&#8230; you backed up your Yojimbo file to an SVN repository, and backed up the repository to S3? Presumably when you commit Yojimbo, SVN would only grow by one delta. That way the cost of transfer would be cheap.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

