<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Slacy's Blog &#187; backup</title>
	<atom:link href="http://slacy.com/blog/tag/backup/feed/" rel="self" type="application/rss+xml" />
	<link>http://slacy.com/blog</link>
	<description>This site is solar powered!</description>
	<lastBuildDate>Tue, 07 Sep 2010 23:45:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Best remote backup solution for Linux?</title>
		<link>http://slacy.com/blog/2009/12/best-remote-backup-solution-for-linux/</link>
		<comments>http://slacy.com/blog/2009/12/best-remote-backup-solution-for-linux/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 18:08:46 +0000</pubDate>
		<dc:creator>slacy</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[remote]]></category>
		<category><![CDATA[rsync]]></category>
		<category><![CDATA[scp]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://slacy.com/blog/?p=1049</guid>
		<description><![CDATA[I&#8217;m running my own hand-crafted remote backup (rsync++) script to back up data from one machine to another.  But, it has some serious drawbacks, and I&#8217;m still looking for something better.  Here are my requirements: Runs on Ubuntu Is either: &#8230; <a href="http://slacy.com/blog/2009/12/best-remote-backup-solution-for-linux/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m running my own hand-crafted remote backup (rsync++) script to back up data from one machine to another.  But, it has some serious drawbacks, and I&#8217;m still looking for something better.  Here are my requirements:</p>
<ul>
<li>Runs on Ubuntu</li>
<li>Is either:
<ul>
<li>Available in the standard distro (i.e. via apt-get)</li>
<li>A simple self-contained script (Python, Perl, Bash, etc.)</li>
</ul>
</li>
<li>Uses ssh/scp/rsync to transport files</li>
<li>Is incremental (i.e. does &#8220;what&#8217;s changed from last time&#8221;, and only backs up that much)</li>
<li><strong>Handles file renames &amp; moves without re-transmitting the underlying data</strong>.</li>
<li>Puts files in a simple &#8220;directory by date&#8221; format.  No fancy databases, no fancy metadata required for restoring.</li>
<li>Preserves file permissions &amp; modification dates.</li>
<li>Correctly handles both hard &amp; soft symbolic links.</li>
<li>Is client-side only.  In other words, I don&#8217;t want to have to maintain 2 copies of this script, one for the server, and one for the client.</li>
</ul>
<p>Is there anything out there that meets these requirements?</p>
]]></content:encoded>
			<wfw:commentRss>http://slacy.com/blog/2009/12/best-remote-backup-solution-for-linux/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
	
	</item>
		<item>
		<title>Archiving GMail without using fetchmail</title>
		<link>http://slacy.com/blog/2009/07/archiving-gmail-without-using-fetchmail/</link>
		<comments>http://slacy.com/blog/2009/07/archiving-gmail-without-using-fetchmail/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 18:27:04 +0000</pubDate>
		<dc:creator>slacy</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[archiving]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[getmail]]></category>
		<category><![CDATA[gmail]]></category>
		<category><![CDATA[libgmail]]></category>

		<guid isPermaLink="false">http://slacy.com/blog/?p=891</guid>
		<description><![CDATA[Thanks Paul and Greg for the advice on backing up my GMail account.  Although fetchmail seems to work for some users, there are a couple of easier to use scripts out there. Paul pointed me at Matt Cutts&#8217; great blog &#8230; <a href="http://slacy.com/blog/2009/07/archiving-gmail-without-using-fetchmail/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Thanks Paul and Greg for the advice on backing up my GMail account.  Although fetchmail seems to work for some users, there are a couple of easier to use scripts out there.</p>
<p>Paul pointed me at <a href="http://www.mattcutts.com/blog/backup-gmail-in-linux-with-getmail/">Matt Cutts&#8217; great blog post about using the getmail script to archive GMail.</a></p>
<p>Greg pointed me at libgmail which comes with some simple driver scripts to download all your content.  You can get it from <a href="http://libgmail.sourceforge.net">the sourceforge.net page</a>, and read more on the <a href="http://words.rancidbacon.com">libgmail author&#8217;s website</a>.</p>
<p>I&#8217;m running a big batch getmail run now, and putting all the messages in MailDir format.  The thing that I&#8217;m actually looking for is a way to preserve GMail&#8217;s label structure using hard or soft links in a MailDir-like format, for easy searching.   I suspect that libgmail will allow this, but I haven&#8217;t dug into it enough to know for sure.</p>
]]></content:encoded>
			<wfw:commentRss>http://slacy.com/blog/2009/07/archiving-gmail-without-using-fetchmail/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
	</item>
		<item>
		<title>Archiving your Google Apps for your domain mail.</title>
		<link>http://slacy.com/blog/2009/07/archiving-your-google-apps-for-your-domain-mail/</link>
		<comments>http://slacy.com/blog/2009/07/archiving-your-google-apps-for-your-domain-mail/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 01:12:32 +0000</pubDate>
		<dc:creator>slacy</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[fetchmail]]></category>
		<category><![CDATA[gmail]]></category>
		<category><![CDATA[google apps]]></category>
		<category><![CDATA[google apps for your domain]]></category>
		<category><![CDATA[mail backup]]></category>

		<guid isPermaLink="false">http://slacy.com/blog/?p=879</guid>
		<description><![CDATA[There are many guides to using fetchmail to backup your gmail account, but I use Google Apps For Your Domain to host my mail.  So, I needed to craft up a slightly modified version of the fetchmail commandline: $ fetchmail &#8230; <a href="http://slacy.com/blog/2009/07/archiving-your-google-apps-for-your-domain-mail/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>There are many guides to using fetchmail to backup your gmail account, but I use Google Apps For Your Domain to host my mail.  So, I needed to craft up a slightly modified version of the fetchmail commandline:</p>
<blockquote><p>$ fetchmail &#8211;ssl -p pop3 -vk &#8211;user slacy@slacy.com pop.gmail.com</p></blockquote>
<p>The funny thing is that within a few minutes of running this script, I got e-mails from my friends saying &#8220;Hey, did you mean to send this to me&#8221; and &#8220;I got this weird message about delivery failure from you&#8221;.</p>
<p>Reading the fetchmail man page in more detail, it says that after fetching the mail, it delivers it via the local delivery agent.  In my case, I suspect that what&#8217;s happening is that it&#8217;s going to my local SMTP server, which is set up to forward back to GMail, and I think that somehow created the re-sending.</p>
<p>If you have any other ideas how or why a fetchmail run would re-send old messages to other recipeients, let me know.  I&#8217;m going to have to do a fair amount of digging before I re-run the script.</p>
]]></content:encoded>
			<wfw:commentRss>http://slacy.com/blog/2009/07/archiving-your-google-apps-for-your-domain-mail/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
	</item>
	</channel>
</rss>
