<?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 for damontimm.com</title>
	<atom:link href="http://blog.damontimm.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.damontimm.com</link>
	<description>Where I go to remember what I did</description>
	<lastBuildDate>Wed, 28 Jul 2010 21:33:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on How to: Mount a SFTP Folder (SSH + FTP) on Ubuntu Linux using SSHFS &amp; Fuse by Sheely</title>
		<link>http://blog.damontimm.com/how-to-mount-a-sftp-folder-ssh-ftp-on-ubuntu-linux-using-sshfs-fuse/comment-page-1/#comment-20162</link>
		<dc:creator>Sheely</dc:creator>
		<pubDate>Wed, 28 Jul 2010 21:33:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.damontimm.com/blog/how-to-mount-a-sftp-folder-ssh-ftp-on-ubuntu-linux-using-sshfs-fuse/#comment-20162</guid>
		<description>Fucking love you, this works amazingly!! Saved me a lot of hassle, thank you!</description>
		<content:encoded><![CDATA[<p>Fucking love you, this works amazingly!! Saved me a lot of hassle, thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) by links for 2010-07-22 &#8211; Magpiebrain</title>
		<link>http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/comment-page-1/#comment-19932</link>
		<dc:creator>links for 2010-07-22 &#8211; Magpiebrain</dc:creator>
		<pubDate>Thu, 22 Jul 2010 21:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=131#comment-19932</guid>
		<description>[...] Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) « damontimm.com (tags: s3 aws duplicity backup incremental sysadmin) [...]</description>
		<content:encoded><![CDATA[<p>[...] Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) « damontimm.com (tags: s3 aws duplicity backup incremental sysadmin) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How To: Automated Encrypted Incremental Backups on Amazon S3 with Duplicity (OS X or Ubuntu) by Amazon News</title>
		<link>http://blog.damontimm.com/how-to-automated-secure-encrypted-incremental-backups-amazon-s3-duplicity-os-x-or-ubuntu/comment-page-1/#comment-19894</link>
		<dc:creator>Amazon News</dc:creator>
		<pubDate>Wed, 21 Jul 2010 00:52:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=107#comment-19894</guid>
		<description>I searched around for various S3 backup solutions and found a handy utility called duplicity. Even more handy that it is available for most distributions (Archlinux, the debs, and Fedora anyway).</description>
		<content:encoded><![CDATA[<p>I searched around for various S3 backup solutions and found a handy utility called duplicity. Even more handy that it is available for most distributions (Archlinux, the debs, and Fedora anyway).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How To: Automated Encrypted Incremental Backups on Amazon S3 with Duplicity (OS X or Ubuntu) by Looking for the best way to keep data on servers safe</title>
		<link>http://blog.damontimm.com/how-to-automated-secure-encrypted-incremental-backups-amazon-s3-duplicity-os-x-or-ubuntu/comment-page-1/#comment-19777</link>
		<dc:creator>Looking for the best way to keep data on servers safe</dc:creator>
		<pubDate>Fri, 16 Jul 2010 10:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=107#comment-19777</guid>
		<description>[...] A variant of it can be used to backup to Amazon S3 too, and there&#039;s a helpful blog post to show how to do this here, if you use Ubuntu or OSX. [...]</description>
		<content:encoded><![CDATA[<p>[...] A variant of it can be used to backup to Amazon S3 too, and there&#039;s a helpful blog post to show how to do this here, if you use Ubuntu or OSX. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) by Peter</title>
		<link>http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/comment-page-1/#comment-19590</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Fri, 09 Jul 2010 16:40:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=131#comment-19590</guid>
		<description>This would be a really useful addition to the code, and allows me to forget the Duplicity commands a bit more ;)</description>
		<content:encoded><![CDATA[<p>This would be a really useful addition to the code, and allows me to forget the Duplicity commands a bit more ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) by Damon</title>
		<link>http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/comment-page-1/#comment-19268</link>
		<dc:creator>Damon</dc:creator>
		<pubDate>Tue, 29 Jun 2010 21:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=131#comment-19268</guid>
		<description>Hey Patrick - right now, we don&#039;t have an option to restore from a specific time period built in yet ... you can, of course, just run a normal duplicity command to get the file ... that would be a nice feature, actually.  I will open a &lt;a href=&quot;http://github.com/thornomad/dt-s3-backup/issues#issue/2&quot; rel=&quot;nofollow&quot;&gt;ticket&lt;/a&gt; and see if we can get to it at some point.  If you want to contribute the code, I am happy to include it. --Damon</description>
		<content:encoded><![CDATA[<p>Hey Patrick &#8211; right now, we don&#8217;t have an option to restore from a specific time period built in yet &#8230; you can, of course, just run a normal duplicity command to get the file &#8230; that would be a nice feature, actually.  I will open a <a href="http://github.com/thornomad/dt-s3-backup/issues#issue/2" rel="nofollow">ticket</a> and see if we can get to it at some point.  If you want to contribute the code, I am happy to include it. &#8211;Damon</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) by Patrick</title>
		<link>http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/comment-page-1/#comment-19258</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Tue, 29 Jun 2010 14:33:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=131#comment-19258</guid>
		<description>Great script, thank you very much! I&#039;m happily running my daily backups with it.
Since the backup is incremental: Is it possible to restore a certain version of a file (e.g. not the latest version, but the version it was a few days/weeks ago)?</description>
		<content:encoded><![CDATA[<p>Great script, thank you very much! I&#8217;m happily running my daily backups with it.<br />
Since the backup is incremental: Is it possible to restore a certain version of a file (e.g. not the latest version, but the version it was a few days/weeks ago)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) by Damon</title>
		<link>http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/comment-page-1/#comment-18834</link>
		<dc:creator>Damon</dc:creator>
		<pubDate>Mon, 14 Jun 2010 11:44:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=131#comment-18834</guid>
		<description>Glad you got it working - you can always troubleshoot your script by un-commenting the &lt;code&gt;ECHO&lt;/code&gt; portion ... and reading the output.</description>
		<content:encoded><![CDATA[<p>Glad you got it working &#8211; you can always troubleshoot your script by un-commenting the <code>ECHO</code> portion &#8230; and reading the output.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) by Samuel</title>
		<link>http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/comment-page-1/#comment-18814</link>
		<dc:creator>Samuel</dc:creator>
		<pubDate>Sun, 13 Jun 2010 21:17:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=131#comment-18814</guid>
		<description>Forget about my latest comment, I found it was a permission problem, so sorry ;)

Finally I get it working in the local test.

Thank you very much for this great script and your kindly support :)</description>
		<content:encoded><![CDATA[<p>Forget about my latest comment, I found it was a permission problem, so sorry ;)</p>
<p>Finally I get it working in the local test.</p>
<p>Thank you very much for this great script and your kindly support :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bash Script: Incremental Encrypted Backups with Duplicity (Amazon S3) by Samuel</title>
		<link>http://blog.damontimm.com/bash-script-incremental-encrypted-backups-duplicity-amazon-s3/comment-page-1/#comment-18812</link>
		<dc:creator>Samuel</dc:creator>
		<pubDate>Sun, 13 Jun 2010 20:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.damontimm.com/?p=131#comment-18812</guid>
		<description>Thank you very much for your fast reply Damon ;)

Well, I tried with a fresh new copy like you suggest, and the previous problem dissapear. But now I have another error message, this one:

&lt;pre class=&quot;brush: bash;&quot;&gt;Specified archive directory &#039;/home/samuel/.cache/duplicity/daedb76a93a9a5c65793185c65874bc3&#039; does not exist, or is not a directory
Specified archive directory &#039;/home/samuel/.cache/duplicity/daedb76a93a9a5c65793185c65874bc3&#039; does not exist, or is not a directory&lt;/pre&gt;

I can&#039;t figure why is telling this, I tried to exclude that directory from the backup but it says the same even doing that :(

This is my script configuration:

&lt;pre class=&quot;brush: bash;&quot;&gt;
# AMAZON S3 INFORMATION
export AWS_ACCESS_KEY_ID=&quot;my_access_key&quot;
export AWS_SECRET_ACCESS_KEY=&quot;my_secret_key&quot;

# If you aren&#039;t running this from a cron, comment this line out
# and duplicity should prompt you for your password.
export PASSPHRASE=&quot;my_passphrase&quot;

# Specify which GPG key you would like to use (even if you have only one).
GPG_KEY=&quot;my_key&quot;

# The ROOT of your backup (where you want the backup to start);
# This can be / or somwhere else -- I use /home/ because all the 
# directories start with /home/ that I want to backup.
ROOT=&quot;/home/samuel/backups-mysql&quot;

# BACKUP DESTINATION INFORMATION
# In my case, I use Amazon S3 use this - so I made up a unique
# bucket name (you don&#039;t have to have one created, it will do it
# for you).  If you don&#039;t want to use Amazon S3, you can backup 
# to a file or any of duplicity&#039;s supported outputs.
#
# NOTE: You do need to keep the &quot;s3+http:///&quot; format
# even though duplicity supports &quot;s3:///&quot;.
#DEST=&quot;s3+http://backup-bucket/backup-folder/&quot;
DEST=&quot;file:///home/samuel/new-backup-test/&quot;

# INCLUDE LIST OF DIRECTORIES
# Here is a list of directories to include; if you want to include 
# everything that is in root, you could leave this list empty (I think).
#INCLIST=( &quot;/home/*/Documents&quot; \ 
#    	  &quot;/home/*/Projects&quot; \
#	      &quot;/home/*/logs&quot; \
#	      &quot;/home/www/mysql-backups&quot; \
#        ) 

INCLIST=( &quot;/home/samuel/backups-mysql&quot; ) # small dir for testing

# EXCLUDE LIST OF DIRECTORIES
# Even though I am being specific about what I want to include, 
# there is still a lot of stuff I don&#039;t need.           
EXCLIST=( &quot;/home/*/Trash&quot; \
	      &quot;/home/*/Projects/Completed&quot; \
	      &quot;/**.DS_Store&quot; &quot;/**Icon?&quot; &quot;/**.AppleDouble&quot; &quot;/home/samuel/.cache&quot; &quot;/home/samuel/.*&quot; \ 
           ) 

# STATIC BACKUP OPTIONS
# Here you can define the static backup options that you want to run with
# duplicity.  I use both the `--full-if-older-than` option plus the
# `--s3-use-new-style` option (for European buckets).  Be sure to separate your
# options with appropriate spacing.
STATIC_OPTIONS=&quot;--full-if-older-than 14D --s3-use-new-style&quot;

# FULL BACKUP &amp; REMOVE OLDER THAN SETTINGS
# Because duplicity will continue to add to each backup as you go,
# it will eventually create a very large set of files.  Also, incremental 
# backups leave room for problems in the chain, so doing a &quot;full&quot;
# backup every so often isn&#039;t not a bad idea.
#
# You can either remove older than a specific time period:
#CLEAN_UP_TYPE=&quot;remove-older-than&quot;
#CLEAN_UP_VARIABLE=&quot;31D&quot;

# Or, If you would rather keep a certain (n) number of full backups (rather 
# than removing the files based on their age), you can use what I use:
CLEAN_UP_TYPE=&quot;remove-all-but-n-full&quot;
CLEAN_UP_VARIABLE=&quot;2&quot;

# LOGFILE INFORMATION DIRECTORY
# Provide directory for logfile, ownership of logfile, and verbosity level.
# I run this script as root, but save the log files under my user name -- 
# just makes it easier for me to read them and delete them as needed. 

LOGDIR=&quot;/home/samuel/logs/test2/&quot;
LOG_FILE=&quot;duplicity-`date +%Y-%m-%d-%M`.txt&quot;
LOG_FILE_OWNER=&quot;samuel:samuel&quot;
VERBOSITY=&quot;-v3&quot;
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>Thank you very much for your fast reply Damon ;)</p>
<p>Well, I tried with a fresh new copy like you suggest, and the previous problem dissapear. But now I have another error message, this one:</p>
<pre class="brush: bash;">Specified archive directory '/home/samuel/.cache/duplicity/daedb76a93a9a5c65793185c65874bc3' does not exist, or is not a directory
Specified archive directory '/home/samuel/.cache/duplicity/daedb76a93a9a5c65793185c65874bc3' does not exist, or is not a directory</pre>
<p>I can&#8217;t figure why is telling this, I tried to exclude that directory from the backup but it says the same even doing that :(</p>
<p>This is my script configuration:</p>
<pre class="brush: bash;">
# AMAZON S3 INFORMATION
export AWS_ACCESS_KEY_ID="my_access_key"
export AWS_SECRET_ACCESS_KEY="my_secret_key"

# If you aren't running this from a cron, comment this line out
# and duplicity should prompt you for your password.
export PASSPHRASE="my_passphrase"

# Specify which GPG key you would like to use (even if you have only one).
GPG_KEY="my_key"

# The ROOT of your backup (where you want the backup to start);
# This can be / or somwhere else -- I use /home/ because all the
# directories start with /home/ that I want to backup.
ROOT="/home/samuel/backups-mysql"

# BACKUP DESTINATION INFORMATION
# In my case, I use Amazon S3 use this - so I made up a unique
# bucket name (you don't have to have one created, it will do it
# for you).  If you don't want to use Amazon S3, you can backup
# to a file or any of duplicity's supported outputs.
#
# NOTE: You do need to keep the "s3+http:///" format
# even though duplicity supports "s3:///".
#DEST="s3+http://backup-bucket/backup-folder/"
DEST="file:///home/samuel/new-backup-test/"

# INCLUDE LIST OF DIRECTORIES
# Here is a list of directories to include; if you want to include
# everything that is in root, you could leave this list empty (I think).
#INCLIST=( "/home/*/Documents" \
#    	  "/home/*/Projects" \
#	      "/home/*/logs" \
#	      "/home/www/mysql-backups" \
#        ) 

INCLIST=( "/home/samuel/backups-mysql" ) # small dir for testing

# EXCLUDE LIST OF DIRECTORIES
# Even though I am being specific about what I want to include,
# there is still a lot of stuff I don't need.
EXCLIST=( "/home/*/Trash" \
	      "/home/*/Projects/Completed" \
	      "/**.DS_Store" "/**Icon?" "/**.AppleDouble" "/home/samuel/.cache" "/home/samuel/.*" \
           ) 

# STATIC BACKUP OPTIONS
# Here you can define the static backup options that you want to run with
# duplicity.  I use both the `--full-if-older-than` option plus the
# `--s3-use-new-style` option (for European buckets).  Be sure to separate your
# options with appropriate spacing.
STATIC_OPTIONS="--full-if-older-than 14D --s3-use-new-style"

# FULL BACKUP &amp; REMOVE OLDER THAN SETTINGS
# Because duplicity will continue to add to each backup as you go,
# it will eventually create a very large set of files.  Also, incremental
# backups leave room for problems in the chain, so doing a "full"
# backup every so often isn't not a bad idea.
#
# You can either remove older than a specific time period:
#CLEAN_UP_TYPE="remove-older-than"
#CLEAN_UP_VARIABLE="31D"

# Or, If you would rather keep a certain (n) number of full backups (rather
# than removing the files based on their age), you can use what I use:
CLEAN_UP_TYPE="remove-all-but-n-full"
CLEAN_UP_VARIABLE="2"

# LOGFILE INFORMATION DIRECTORY
# Provide directory for logfile, ownership of logfile, and verbosity level.
# I run this script as root, but save the log files under my user name --
# just makes it easier for me to read them and delete them as needed. 

LOGDIR="/home/samuel/logs/test2/"
LOG_FILE="duplicity-`date +%Y-%m-%d-%M`.txt"
LOG_FILE_OWNER="samuel:samuel"
VERBOSITY="-v3"
</pre>
]]></content:encoded>
	</item>
</channel>
</rss>
