<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Søren Vind &#187; s3fs</title>
	<atom:link href="http://sorenvind.dk/tag/s3fs/feed/" rel="self" type="application/rss+xml" />
	<link>http://sorenvind.dk</link>
	<description>For the sake of everybody in the band</description>
	<lastBuildDate>Thu, 11 Mar 2010 07:55:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
		<item>
		<title>Backing up to Amazon S3 (Part 1)</title>
		<link>http://sorenvind.dk/2009/04/20/backing-up-to-amazon-s3-part-1/</link>
		<comments>http://sorenvind.dk/2009/04/20/backing-up-to-amazon-s3-part-1/#comments</comments>
		<pubDate>Mon, 20 Apr 2009 21:43:47 +0000</pubDate>
		<dc:creator>Søren Vind</dc:creator>
				<category><![CDATA[Software]]></category>
		<category><![CDATA[amazon s3]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[dropbox]]></category>
		<category><![CDATA[duplicity]]></category>
		<category><![CDATA[encfs]]></category>
		<category><![CDATA[jungle disk]]></category>
		<category><![CDATA[s3fs]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://sorenvind.dk/?p=111</guid>
		<description><![CDATA[Backing up your files can obviously be done in many ways. Some prefer a USB-disk located somewhere to which backups can be made with irregular intervals, while others prefer the backups to be made by some automated process which backs up to some remote location. It is probably apparent from the last sentence that I [...]]]></description>
			<content:encoded><![CDATA[<p>Backing up your files can obviously be done in many ways. Some prefer a USB-disk located somewhere to which backups can be made with irregular intervals, while others prefer the backups to be made by some automated process which backs up to some remote location. It is probably apparent from the last sentence that I prefer to back up to some remote location &#8211; preferably completely automatic.</p>
<p>Moving my online-presence to another server, I now have a lot less space to store my backups on than I had before. Thus, a simple rsync-via-ssh is not really an option any more. This forced me to look for another solution. Luckily, there is a great abundance of online backup services, most of which use <a href="http://aws.amazon.com/s3/">Amazon S3</a> as the backend storage. I seemed to have two options to use S3 as the backup provider:</p>
<ol>
<li>Use some commercial and complete software for making, transferring and organizing the backups. A couple of solutions seemed mature enough to real-world usage: <a href="http://www.getdropbox.com/">Dropbox</a> and <a href="http://www.jungledisk.com/">Jungle Disk</a>. Several user reports recommend both solutions, which should be quite stable and easy to use. Also, they are not that expensive compared to the raw cost of S3. Both commersial solutions have disadvantages, though &#8211; Dropbox adds a lot of cost if you want to store more than 2GB but a lot less than 50GB (compared to S3), and Jungle Disk apparantly stores the backed up files in some odd way, making it hard to recover files without Jungle Disk. Also, they share the disadvantage of being commercial (it is non-free and the source code is not available). An advantage of both solutions is that they are multiplatform.</li>
<li>Use some combination of open source software to back up my files directly to Amazon S3. The open source software available for communicating more or less directly with S3 seems quite mature at this time. Browsing the blogosphere gave me a lot of documentation on how to do this using varying tools ranging from <a href="http://duplicity.nongnu.org/">duplicity</a> through two (different) projects called <a href="https://fedorahosted.org/s3fs/">s3fs</a> and <a href="http://code.google.com/p/s3fs/">s3fs</a> (??) to <a href="http://www.arg0.net/encfs">encFS</a>. Using these tools, it is possible to customize the backup of files in exactly the way the user wants, and they do not present the user with any extra cost besides the raw cost for the S3 storage.</li>
</ol>
<p>I chose the second option, using a bit more time in setting up the backup but in return getting a completely customized and free backup toolchain. In the next couple of posts I will document how I did it, but to get an idea (and to get some inspiration), here is the resources I used when setting up the backup:</p>
<p><a href="http://blog.eberly.org/2008/10/27/how-i-automated-my-backups-to-amazon-s3-using-rsync/">http://blog.eberly.org/2008/10/27/how-i-automated-my-backups-to-amazon-s3-using-rsync/</a><br />
<a href="http://www.cenolan.com/2008/12/how-to-incremental-daily-backups-amazon-s3-duplicity/">http://www.cenolan.com/2008/12/how-to-incremental-daily-backups-amazon-s3-duplicity/</a><br />
<a href="http://www.brainonfire.net/blog/remote-encrypted-backup-duplicity-amazon-s3/">http://www.brainonfire.net/blog/remote-encrypted-backup-duplicity-amazon-s3/</a><br />
<a href="http://sharph.net/2008/12/encrypted-offsite-backup-with-encfs-amazon-s3-and-s3cmd/">http://sharph.net/2008/12/encrypted-offsite-backup-with-encfs-amazon-s3-and-s3cmd/</a><br />
<a href="http://markusthielmann.com/blog/use_amazon_s3_with_ubuntu_hardy">http://markusthielmann.com/blog/use_amazon_s3_with_ubuntu_hardy</a><br />
<a href="http://www.sharms.org/blog/?p=137">http://www.sharms.org/blog/?p=137</a></p>
]]></content:encoded>
			<wfw:commentRss>http://sorenvind.dk/2009/04/20/backing-up-to-amazon-s3-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
