<?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: How-To: Automated Backups to Amazon&#8217;s S3 with Duplicity</title>
	<atom:link href="http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/</link>
	<description>Wasting your precious bandwidth since 1999</description>
	<lastBuildDate>Tue, 09 Feb 2010 00:28:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: gwern</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-612</link>
		<dc:creator>gwern</dc:creator>
		<pubDate>Tue, 09 Feb 2010 00:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-612</guid>
		<description>&lt;p&gt;I don&#039;t think there&#039;s any real need to have a full shell script. This is a one-liner: you can concatenate multiple shell variable definitions, and they will scope only over the one line.&lt;/p&gt;

&lt;p&gt;Here&#039;s an example of what I mean:&lt;/p&gt;

&lt;p&gt;[07:27 PM] 332Mb$ BAR=&quot;bar&quot;
[07:27 PM] 332Mb$ FOO=&quot;foo&quot; ls
....
[07:27 PM] 332Mb$ echo $BAR
bar
[07:27 PM] 332Mb$ echo $FOO&lt;/p&gt;

&lt;p&gt;[07:27 PM] 332Mb$&lt;/p&gt;

&lt;p&gt;The $FOO is gone, but $BAR remains. (And nothing stops one from going &#039;FOO=&quot;foo&quot; BAR=&quot;bar&quot;... ls&#039;)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think there&#8217;s any real need to have a full shell script. This is a one-liner: you can concatenate multiple shell variable definitions, and they will scope only over the one line.</p>

<p>Here&#8217;s an example of what I mean:</p>

<p>[07:27 PM] 332Mb$ BAR=&#8221;bar&#8221;
[07:27 PM] 332Mb$ FOO=&#8221;foo&#8221; ls
&#8230;.
[07:27 PM] 332Mb$ echo $BAR
bar
[07:27 PM] 332Mb$ echo $FOO</p>

<p>[07:27 PM] 332Mb$</p>

<p>The $FOO is gone, but $BAR remains. (And nothing stops one from going &#8216;FOO=&#8221;foo&#8221; BAR=&#8221;bar&#8221;&#8230; ls&#8217;)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-517</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Wed, 21 Oct 2009 23:02:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-517</guid>
		<description>&lt;p&gt;If you&#039;re having trouble with entropy gathering, running ls -lR / in the background (another login, another terminal window, or whatever) will help.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>If you&#8217;re having trouble with entropy gathering, running ls -lR / in the background (another login, another terminal window, or whatever) will help.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Callum</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-510</link>
		<dc:creator>Callum</dc:creator>
		<pubDate>Sun, 28 Jun 2009 20:11:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-510</guid>
		<description>&lt;p&gt;As per my &lt;a href=&quot;#comment-227&quot; rel=&quot;nofollow&quot;&gt;earlier comment&lt;/a&gt;, you can do away with the need for a passphrase altogether. I&#039;d suggest easier and more secure than storing the passphrase anywhere.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>As per my <a href="#comment-227" rel="nofollow">earlier comment</a>, you can do away with the need for a passphrase altogether. I&#8217;d suggest easier and more secure than storing the passphrase anywhere.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: randy</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-509</link>
		<dc:creator>randy</dc:creator>
		<pubDate>Sun, 28 Jun 2009 03:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-509</guid>
		<description>&lt;p&gt;Woodside, I realize that now and I agree that backups of a small time blog like this don&#039;t really need to be ultra strict. This was simply my method (at the time) to &lt;em&gt;automated&lt;/em&gt; backups. On a VPS with no other users, storing your passphrase in a human readable text file is less of an issue (as long as your root password is relatively difficult crack) than someone in a multi-user environment. If security was my ultimate goal, I probably wouldn&#039;t trust my data with a third-party service and use tape backups and store them in an offsite location.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Woodside, I realize that now and I agree that backups of a small time blog like this don&#8217;t really need to be ultra strict. This was simply my method (at the time) to <em>automated</em> backups. On a VPS with no other users, storing your passphrase in a human readable text file is less of an issue (as long as your root password is relatively difficult crack) than someone in a multi-user environment. If security was my ultimate goal, I probably wouldn&#8217;t trust my data with a third-party service and use tape backups and store them in an offsite location.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: S Woodside</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-508</link>
		<dc:creator>S Woodside</dc:creator>
		<pubDate>Sun, 28 Jun 2009 03:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-508</guid>
		<description>&lt;p&gt;Putting your GPG password into a C executable isn&#039;t really going to help since it will be stored in there as text ... basically I would say unless you are storing state secrets don&#039;t worry about it, and if you are, enter your password by hand every time you back up.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Putting your GPG password into a C executable isn&#8217;t really going to help since it will be stored in there as text &#8230; basically I would say unless you are storing state secrets don&#8217;t worry about it, and if you are, enter your password by hand every time you back up.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: thinking sysadmin / Duplicity to Amazon S3 on FreeBSD: Building on the work of others</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-331</link>
		<dc:creator>thinking sysadmin / Duplicity to Amazon S3 on FreeBSD: Building on the work of others</dc:creator>
		<pubDate>Mon, 02 Mar 2009 19:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-331</guid>
		<description>&lt;p&gt;[...] post adds only a couple small details to work described at randys.org and cenolan.com - go there for background on this post and useful scripts for automated Duplicity [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] post adds only a couple small details to work described at randys.org and cenolan.com &#8211; go there for background on this post and useful scripts for automated Duplicity [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Nabeel</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-285</link>
		<dc:creator>Nabeel</dc:creator>
		<pubDate>Tue, 17 Feb 2009 15:58:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-285</guid>
		<description>&lt;p&gt;Nevermind, got the answer to that! Thanks very much!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nevermind, got the answer to that! Thanks very much!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Nabeel</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-284</link>
		<dc:creator>Nabeel</dc:creator>
		<pubDate>Tue, 17 Feb 2009 15:55:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-284</guid>
		<description>&lt;p&gt;Thanks for the reply! 
How many days does this keep a backup? Or is it continuous?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for the reply! 
How many days does this keep a backup? Or is it continuous?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: randy</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-283</link>
		<dc:creator>randy</dc:creator>
		<pubDate>Sat, 14 Feb 2009 05:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-283</guid>
		<description>&lt;p&gt;@Nabeel&lt;/p&gt;

&lt;p&gt;Have a look &lt;a href=&quot;http://www.cenolan.com/2008/12/how-to-incremental-daily-backups-amazon-s3-duplicity/&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;. It&#039;s pretty much like reversing ${SOURCE} and ${DEST} and adding a date in which you want to back up.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Nabeel</p>

<p>Have a look <a href="http://www.cenolan.com/2008/12/how-to-incremental-daily-backups-amazon-s3-duplicity/" rel="nofollow">here</a>. It&#8217;s pretty much like reversing ${SOURCE} and ${DEST} and adding a date in which you want to back up.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Nabeel</title>
		<link>http://www.randys.org/2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity/comment-page-1/#comment-282</link>
		<dc:creator>Nabeel</dc:creator>
		<pubDate>Sat, 14 Feb 2009 03:54:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.randys.org//2007/11/16/how-to-automated-backups-to-amazon-s-s3-with-duplicity#comment-282</guid>
		<description>&lt;p&gt;Great guide, but quick question - I am rather new to this.
How would I then recovery my data in case of the a crash? That&#039;s what I&#039;m rather lost about (now including a key, etc)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great guide, but quick question &#8211; I am rather new to this.
How would I then recovery my data in case of the a crash? That&#8217;s what I&#8217;m rather lost about (now including a key, etc)</p>]]></content:encoded>
	</item>
</channel>
</rss>
