<?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"
	>
<channel>
	<title>Comments on: Backup 3.0: Avoid</title>
	<atom:link href="http://mjtsai.com/blog/2005/10/29/backup-30-avoid/feed/" rel="self" type="application/rss+xml" />
	<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 10:22:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-14640</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 04 Sep 2006 15:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-14640</guid>
		<description>&lt;a href="http://www.stuffonfire.com/2006/09/04/holy-crap-apple-backup-is-dangerous/" rel="nofollow"&gt;Holy Crap, Apple Backup is Dangerous&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://www.stuffonfire.com/2006/09/04/holy-crap-apple-backup-is-dangerous/" rel="nofollow">Holy Crap, Apple Backup is Dangerous</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-11017</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 31 Oct 2005 16:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-11017</guid>
		<description>Forward: store a full copy of the oldest snapshot, then add additional copies of newer files as they're modified.

Backward: store a full copy of the newest snapshot, and keep older versions of files that have been modified.

Forward is nice when using removable backup media, because it works like a log: you can keep adding new versions of files to new discs.

But if you're going to store everything on a big hard disk, backward is nice because because (a) it's easy to recover from the latest backup (which is what you're most likely to want), and (b) it's easy to delete the oldest files to free up disk space.</description>
		<content:encoded><![CDATA[<p>Forward: store a full copy of the oldest snapshot, then add additional copies of newer files as they're modified.</p>
<p>Backward: store a full copy of the newest snapshot, and keep older versions of files that have been modified.</p>
<p>Forward is nice when using removable backup media, because it works like a log: you can keep adding new versions of files to new discs.</p>
<p>But if you're going to store everything on a big hard disk, backward is nice because because (a) it's easy to recover from the latest backup (which is what you're most likely to want), and (b) it's easy to delete the oldest files to free up disk space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jem</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-11016</link>
		<dc:creator>jem</dc:creator>
		<pubDate>Mon, 31 Oct 2005 14:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-11016</guid>
		<description>I'm not sure that I understand what you mean with forward/backward. I switched from Retrospect a couple of year ago (I got really upset when it claimed to backup my data when it actually was trashing my previous backups, when things like that had happened a couple of times I just gave up) and tried many of the programs that was available at that time. Impression was the one that worked the best for me ... but requirements vary. I'm also using ChronoSync for other things and it looks like the latest version could be used for archiving but I haven't had the time to check.</description>
		<content:encoded><![CDATA[<p>I'm not sure that I understand what you mean with forward/backward. I switched from Retrospect a couple of year ago (I got really upset when it claimed to backup my data when it actually was trashing my previous backups, when things like that had happened a couple of times I just gave up) and tried many of the programs that was available at that time. Impression was the one that worked the best for me ... but requirements vary. I'm also using ChronoSync for other things and it looks like the latest version could be used for archiving but I haven't had the time to check.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-11015</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 29 Oct 2005 21:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-11015</guid>
		<description>Impression doesn't seem to match my needs very well. When backing up to a hard disk, I want to be able to quickly restore from the latest backup. I also want to store multiple versions of changed files going &lt;em&gt;backwards&lt;/em&gt; in time. Impression does its incremental backups going &lt;em&gt;forwards&lt;/em&gt;, like Retrospect, which makes managing disk space difficult. Restoring seems to be clunkier than in Retrospect. Of course, Synchronize Pro! doesn't have an interface for restoring, but everything's clearly laid out in the Finder.

For CD/DVD archives, it seems that the only way to get encrypted, catalogable backups would be to tell Impression to save the files in Finder format on disk images. Then I would have to segment the disk images, burn them, and catalog them with CDFinder. It would be a more complicated way of ending up where I am now.</description>
		<content:encoded><![CDATA[<p>Impression doesn't seem to match my needs very well. When backing up to a hard disk, I want to be able to quickly restore from the latest backup. I also want to store multiple versions of changed files going <em>backwards</em> in time. Impression does its incremental backups going <em>forwards</em>, like Retrospect, which makes managing disk space difficult. Restoring seems to be clunkier than in Retrospect. Of course, Synchronize Pro! doesn't have an interface for restoring, but everything's clearly laid out in the Finder.</p>
<p>For CD/DVD archives, it seems that the only way to get encrypted, catalogable backups would be to tell Impression to save the files in Finder format on disk images. Then I would have to segment the disk images, burn them, and catalog them with CDFinder. It would be a more complicated way of ending up where I am now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jem</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-11014</link>
		<dc:creator>jem</dc:creator>
		<pubDate>Sat, 29 Oct 2005 19:34:48 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-11014</guid>
		<description>You could try Impression</description>
		<content:encoded><![CDATA[<p>You could try Impression</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-11013</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 29 Oct 2005 17:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-11013</guid>
		<description>IANAL, but I think the main point is that their patent covers the idea of using a catalog file to keep track of which files were written to the backup media. If anyone knows more, please post a comment/link.</description>
		<content:encoded><![CDATA[<p>IANAL, but I think the main point is that their patent covers the idea of using a catalog file to keep track of which files were written to the backup media. If anyone knows more, please post a comment/link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gus</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-11012</link>
		<dc:creator>gus</dc:creator>
		<pubDate>Sat, 29 Oct 2005 17:16:06 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-11012</guid>
		<description>Is there anywhere that says exactly what the Dantz patent is?  I went to that page and it's really long- I need a cliff notes version :)</description>
		<content:encoded><![CDATA[<p>Is there anywhere that says exactly what the Dantz patent is?  I went to that page and it's really long- I need a cliff notes version :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iacas</title>
		<link>http://mjtsai.com/blog/2005/10/29/backup-30-avoid/#comment-11011</link>
		<dc:creator>iacas</dc:creator>
		<pubDate>Sat, 29 Oct 2005 17:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/?p=1128#comment-11011</guid>
		<description>I use psync. It worked beautifully in the 10.1 to 10.3 era, broke for awhile in 10.4 (I think), but now works great. It creates bootable backups to the second drive in my G5. It's not for everyone, but it could be on the list. Run via a cron job, it seems pretty fast to me. Resource forks, etc. are preserved.</description>
		<content:encoded><![CDATA[<p>I use psync. It worked beautifully in the 10.1 to 10.3 era, broke for awhile in 10.4 (I think), but now works great. It creates bootable backups to the second drive in my G5. It's not for everyone, but it could be on the list. Run via a cron job, it seems pretty fast to me. Resource forks, etc. are preserved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
