<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The State of Backup and Cloning Tools under Mac OS X</title>
	<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/</link>
	<description>Mac OS X Gordian Knots Smashed</description>
	<pubDate>Thu, 24 Jul 2008 01:13:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: n8gray.org: Backup Bouncer is Working, Confusing, Annoying Developers</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-37162</link>
		<pubDate>Mon, 02 Jun 2008 20:06:20 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-37162</guid>
					<description>&lt;p&gt;[...] The FIFO/device file tests are not included in either the &#8220;critical&#8221; or &#8220;important&#8221; set of tests. So I&#8217;m saying (and have always said) that most users, even most power users, won&#8217;t care about them. So why test for them at all? Consider the situation before Maurits&#8217; blogged on backups and BB existed. Most people, myself included, didn&#8217;t even know what the full set of OS X filesystem object types and metadata was. Maurits filled us in on what existed, but knowing how to test for preservation was still a black art. BB was meant to democratize that testing, but also to act as an exhaustive test set. (I don&#8217;t claim to have achieved even close to 100% coverage, but that&#8217;s the goal.) So it&#8217;s important to me that BB include tests for any metadatum or filesystem object that can conceivably have a reason to be backed up. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] The FIFO/device file tests are not included in either the &#8220;critical&#8221; or &#8220;important&#8221; set of tests. So I&#8217;m saying (and have always said) that most users, even most power users, won&#8217;t care about them. So why test for them at all? Consider the situation before Maurits&#8217; blogged on backups and BB existed. Most people, myself included, didn&#8217;t even know what the full set of OS X filesystem object types and metadata was. Maurits filled us in on what existed, but knowing how to test for preservation was still a black art. BB was meant to democratize that testing, but also to act as an exhaustive test set. (I don&#8217;t claim to have achieved even close to 100% coverage, but that&#8217;s the goal.) So it&#8217;s important to me that BB include tests for any metadatum or filesystem object that can conceivably have a reason to be backed up. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: best back up for a mac</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-37071</link>
		<pubDate>Fri, 30 May 2008 05:11:43 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-37071</guid>
					<description>&lt;p&gt;[...]  [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;]  [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rsyncx to backup Mac &#124; Tongfamily.com</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-34016</link>
		<pubDate>Mon, 28 Apr 2008 05:39:20 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-34016</guid>
					<description>&lt;p&gt;[...] Plasticfutures.org has a good deeper analysis of the various tools. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] Plasticfutures.org has a good deeper analysis of the various tools. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: PG</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-25012</link>
		<pubDate>Mon, 24 Mar 2008 19:00:43 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-25012</guid>
					<description>&lt;p&gt;Carbon Copy Cloner  3.1 has now been released:
http://www.bombich.com/software/ccc.html&lt;/p&gt;

&lt;p&gt;According to an independent backup-integrity testing tool (Backup-Bouncer: http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/ ), it successfully preserves ALL metadata. &lt;/p&gt;

&lt;p&gt;maurits - I saw your posts on the Backup-Bouncer site: I'm aware of your time constraints, so I don't expect a full update of the test results. But, I think it would be of great benefit if you would add a brief "update" note, simply saying that (a) some of the tools (e.g. CCC) have been updated, with much better results, and (b) a link to Backup-Bouncer.&lt;/p&gt;

&lt;p&gt;Otherwise, people coming across this page are going to be misinformed about the current state of affairs, and might spend a fair amount of time tracking current information down.&lt;/p&gt;

&lt;p&gt;Thanks for this great work - you really started something, and a lot of good results have come from it!&lt;/p&gt;

&lt;p&gt;PG&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Carbon Copy Cloner  3.1 has now been released:
http://www.bombich.com/software/ccc.html</p>

<p>According to an independent backup-integrity testing tool (Backup-Bouncer: http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/ ), it successfully preserves ALL metadata. </p>

<p>maurits - I saw your posts on the Backup-Bouncer site: I&#8217;m aware of your time constraints, so I don&#8217;t expect a full update of the test results. But, I think it would be of great benefit if you would add a brief &#8220;update&#8221; note, simply saying that (a) some of the tools (e.g. CCC) have been updated, with much better results, and (b) a link to Backup-Bouncer.</p>

<p>Otherwise, people coming across this page are going to be misinformed about the current state of affairs, and might spend a fair amount of time tracking current information down.</p>

<p>Thanks for this great work - you really started something, and a lot of good results have come from it!</p>

<p>PG</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rob</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-22313</link>
		<pubDate>Wed, 06 Feb 2008 23:49:02 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-22313</guid>
					<description>&lt;p&gt;P.S.  Carbon Copy Cloner 3.0.1 is now based on asr.  But even though asr does not always preserve metadata, Carbon Copy Cloner does copy  metadata including BSD Flags, Locked, Extended Attributes, Symlink Ownership, etc.  &lt;/p&gt;

&lt;p&gt;But there may be a bug in 3.0.1.  If the file is locked, CCC may not always copy extended attributes.  I hope that gets fixed soon.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>P.S.  Carbon Copy Cloner 3.0.1 is now based on asr.  But even though asr does not always preserve metadata, Carbon Copy Cloner does copy  metadata including BSD Flags, Locked, Extended Attributes, Symlink Ownership, etc.  </p>

<p>But there may be a bug in 3.0.1.  If the file is locked, CCC may not always copy extended attributes.  I hope that gets fixed soon.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rob</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-22294</link>
		<pubDate>Wed, 06 Feb 2008 19:34:47 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-22294</guid>
					<description>&lt;p&gt;I don't know why the author is tracking the "locked Flag".  Mac OS X uses the BSD flag "uchg" to lock or unlock a file.  &lt;/p&gt;

&lt;p&gt;All you need to do is check to see whether the BSD flags are being copied.  If they are, then the "locked" status of the file will also be copied.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know why the author is tracking the &#8220;locked Flag&#8221;.  Mac OS X uses the BSD flag &#8220;uchg&#8221; to lock or unlock a file.  </p>

<p>All you need to do is check to see whether the BSD flags are being copied.  If they are, then the &#8220;locked&#8221; status of the file will also be copied.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rob</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-22292</link>
		<pubDate>Wed, 06 Feb 2008 19:31:55 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-22292</guid>
					<description>&lt;p&gt;I can confirm that asr in its file-copy mode is still badly broken in Tiger 10.4.11. (The asr version is 72).&lt;/p&gt;

&lt;p&gt;I created two disk images and put some files in the first. Then I used asr to copy the files from the first disk image to the second.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;No extended attributes were copied.&lt;/li&gt;
&lt;li&gt;No BSD flags were copied.&lt;/li&gt;
&lt;li&gt;No locked flags were copied (which are just a type of BSD flag).&lt;/li&gt;
&lt;li&gt;Symlink ownership was not copied.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;And it really messed up the Symlink ownership. One of symlinks had the owner of rob:dummy. When the symlink was copied, it became root:rob. How it did this is beyond my comprehension.&lt;/p&gt;

&lt;p&gt;Come on Apple. Why don’t you fix these long-standing bugs!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I can confirm that asr in its file-copy mode is still badly broken in Tiger 10.4.11. (The asr version is 72).</p>

<p>I created two disk images and put some files in the first. Then I used asr to copy the files from the first disk image to the second.</p>

<ol>
<li>No extended attributes were copied.</li>
<li>No BSD flags were copied.</li>
<li>No locked flags were copied (which are just a type of BSD flag).</li>
<li>Symlink ownership was not copied.</li>
</ol>

<p>And it really messed up the Symlink ownership. One of symlinks had the owner of rob:dummy. When the symlink was copied, it became root:rob. How it did this is beyond my comprehension.</p>

<p>Come on Apple. Why don’t you fix these long-standing bugs!</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: chipwreck &#124; blog &#187; archive &#187; Backup script using RsyncX</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-21693</link>
		<pubDate>Sat, 26 Jan 2008 18:55:23 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-21693</guid>
					<description>&lt;p&gt;[...] More details can be found here: blog.plasticsfuture.org [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] More details can be found here: blog.plasticsfuture.org [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: New Home Server &#124; Robert Accettura&#8217;s Fun With Wordage</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-20679</link>
		<pubDate>Wed, 02 Jan 2008 03:30:19 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-20679</guid>
					<description>&lt;p&gt;[...] Next I wanted to replicate data across the drives on a cron. Initially I was thinking rsync, since as of 10.4, it&#8217;s resource-fork aware. It turns out that&#8217;s not really true. I ended up going back to SuperDuper to copy between the drives. It only copies changed files, and once a week will delete removed files (so if you accidentally delete something, there&#8217;s still a chance to recover, unless you do it at the wrong time). Not a bad solution IMHO. Still would prefer rsync more. Initial backup took less than 1/2 hour. Just a few minutes should be enough to keep the disks in sync. I briefly considered setting up RAID, but decided against it since RAID is not backup. It doesn&#8217;t protect against things like corruption. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] Next I wanted to replicate data across the drives on a cron. Initially I was thinking rsync, since as of 10.4, it&#8217;s resource-fork aware. It turns out that&#8217;s not really true. I ended up going back to SuperDuper to copy between the drives. It only copies changed files, and once a week will delete removed files (so if you accidentally delete something, there&#8217;s still a chance to recover, unless you do it at the wrong time). Not a bad solution IMHO. Still would prefer rsync more. Initial backup took less than 1/2 hour. Just a few minutes should be enough to keep the disks in sync. I briefly considered setting up RAID, but decided against it since RAID is not backup. It doesn&#8217;t protect against things like corruption. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Blog 2</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-20024</link>
		<pubDate>Wed, 19 Dec 2007 15:36:46 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-20024</guid>
					<description>&lt;p&gt;[...] The State of Backup and Cloning Tools under Mac OS X [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] The State of Backup and Cloning Tools under Mac OS X [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Charles Young</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-19819</link>
		<pubDate>Thu, 13 Dec 2007 23:54:02 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-19819</guid>
					<description>&lt;p&gt;I've had a lot of success with Bacula. [www.bacula.org].&lt;/p&gt;

&lt;p&gt;It's great if you've got a few machines to backup and can spare a few hours to configure it.&lt;/p&gt;

&lt;p&gt;There is a good resource for bacula for OSX at http://www.haught.org/howto/detail/tag/tech/item/bacula_osx/&lt;/p&gt;

&lt;p&gt;and a prebuilt binary client at http://www.pixelchaos.net/&lt;/p&gt;

&lt;p&gt;As for most backup applications (as opposed to DR), it is predicated on the idea of saving your data rather than your machine, but there is some flexibility to recover from bare metal if you want to go down that path. Personally I wouldn't generally bother.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had a lot of success with Bacula. [www.bacula.org].</p>

<p>It&#8217;s great if you&#8217;ve got a few machines to backup and can spare a few hours to configure it.</p>

<p>There is a good resource for bacula for OSX at http://www.haught.org/howto/detail/tag/tech/item/bacula_osx/</p>

<p>and a prebuilt binary client at http://www.pixelchaos.net/</p>

<p>As for most backup applications (as opposed to DR), it is predicated on the idea of saving your data rather than your machine, but there is some flexibility to recover from bare metal if you want to go down that path. Personally I wouldn&#8217;t generally bother.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anders</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18585</link>
		<pubDate>Fri, 16 Nov 2007 16:01:34 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18585</guid>
					<description>&lt;p&gt;You should look at "Unison"
http://www.cis.upenn.edu/~bcpierce/unison/
I use it to keep my laptop files synced. I used macports to get and install. http://www.macports.org/
enjoy!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You should look at &#8220;Unison&#8221;
http://www.cis.upenn.edu/~bcpierce/unison/
I use it to keep my laptop files synced. I used macports to get and install. http://www.macports.org/
enjoy!</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matt &#38; Jen Simerson &#187; Backing up a Mac</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18318</link>
		<pubDate>Mon, 12 Nov 2007 16:14:25 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18318</guid>
					<description>&lt;p&gt;[...] I owned Synchronize! Pro years ago but gave up on it during the switch to OS X. CCC was the perfect (and only) tool for duplicating OS X drives for quite a while. I used and recommended it for a few years. It&#8217;s so good and cheap that I paid the suggested donation for it several times. It &#8220;just works.&#8221; However, CCC has grown rather long in the tooth. As new versions of OS X arrived, it has been slow to get updated and even the latest version today does not support all of OS X&#8217;s file metadata features. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] I owned Synchronize! Pro years ago but gave up on it during the switch to OS X. CCC was the perfect (and only) tool for duplicating OS X drives for quite a while. I used and recommended it for a few years. It&#8217;s so good and cheap that I paid the suggested donation for it several times. It &#8220;just works.&#8221; However, CCC has grown rather long in the tooth. As new versions of OS X arrived, it has been slow to get updated and even the latest version today does not support all of OS X&#8217;s file metadata features. [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Articles</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18265</link>
		<pubDate>Sun, 11 Nov 2007 15:53:32 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18265</guid>
					<description>&lt;p&gt;I am very grateful for your efforts. I have just tried, for the first time, to creat a bootable copy of my internal disc on an external drive, using Disk Utility. &lt;/p&gt;

&lt;p&gt;It failed because my copy of Disk Utility (Mac OS X version 10.4.10) cannot drag-and-drop the source and destination devices!&lt;/p&gt;

&lt;p&gt;A known but unfixed bug, apparently:-(&lt;/p&gt;

&lt;p&gt;I started searching for alternatives and uncovered your can of worms! I am rather surprised that such a basic requirement as backing up bootable versions of the filestore is in such a mess:&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am very grateful for your efforts. I have just tried, for the first time, to creat a bootable copy of my internal disc on an external drive, using Disk Utility. </p>

<p>It failed because my copy of Disk Utility (Mac OS X version 10.4.10) cannot drag-and-drop the source and destination devices!</p>

<p>A known but unfixed bug, apparently:-(</p>

<p>I started searching for alternatives and uncovered your can of worms! I am rather surprised that such a basic requirement as backing up bootable versions of the filestore is in such a mess:</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dp</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18031</link>
		<pubDate>Tue, 06 Nov 2007 15:39:33 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18031</guid>
					<description>&lt;p&gt;any thoughts on synk  pro?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>any thoughts on synk  pro?</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Keith Dancey</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-13479</link>
		<pubDate>Thu, 02 Aug 2007 22:01:53 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-13479</guid>
					<description>&lt;p&gt;I am very grateful for your efforts.  I have just tried, for the first time, to creat a bootable copy of my internal disc on an external drive, using Disk Utility.   &lt;/p&gt;

&lt;p&gt;It failed because my copy of Disk Utility (Mac OS X version 10.4.10) cannot drag-and-drop the source and destination devices!&lt;/p&gt;

&lt;p&gt;A known but unfixed bug, apparently:-(&lt;/p&gt;

&lt;p&gt;I started searching for alternatives and uncovered your can of worms!  I am rather surprised that such a basic requirement as backing up bootable versions of the filestore is in such a mess:-(&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am very grateful for your efforts.  I have just tried, for the first time, to creat a bootable copy of my internal disc on an external drive, using Disk Utility.   </p>

<p>It failed because my copy of Disk Utility (Mac OS X version 10.4.10) cannot drag-and-drop the source and destination devices!</p>

<p>A known but unfixed bug, apparently:-(</p>

<p>I started searching for alternatives and uncovered your can of worms!  I am rather surprised that such a basic requirement as backing up bootable versions of the filestore is in such a mess:-(</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mark_usha</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-13180</link>
		<pubDate>Sun, 29 Jul 2007 23:56:47 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-13180</guid>
					<description>&lt;p&gt;@ Peter da Silva
Some of SuperDuper's features you're missing are available after registering. It's has some shortcomings, agreed, but it copies all metadata.&lt;/p&gt;

&lt;p&gt;I think maurits recommendations are based on "how good are they at metadata preservation". If someone can do without BSD-Flags, Extended Attributes or ACL (ACL-support in TIger is normally turned off) he'll be happy with old RsyncX' rsync (which preserves the creation date!!) and find workarounds for known bugs (e.g. avoiding uappnd-flags on directories).&lt;/p&gt;

&lt;p&gt;Someone here asked for a report on rdiff-backup: the development version of rdiff-backup (1.1.12) loses the Z-Finderflag (busy-flag), the "locked" or BSD-ish "uchg"-flag, all BSD-flags, extended attributes on symlinks (&lt;em&gt;attributes elsewhere are preserved&lt;/em&gt;, if py-xattr 0.4 is installed!!) and ACLs (1). rdiff-backup cannot copy device files and fifos.&lt;/p&gt;

&lt;p&gt;This is promising for a development version, and rdiff-backup offers some "time machine" functions (restore to any given date of hour in the past)!&lt;/p&gt;

&lt;p&gt;(1) rdiff-backup actually does support ACLs on other platforms, but not (yet??) on MacOS X (pylibacl refuses to install on a Mac).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@ Peter da Silva
Some of SuperDuper&#8217;s features you&#8217;re missing are available after registering. It&#8217;s has some shortcomings, agreed, but it copies all metadata.</p>

<p>I think maurits recommendations are based on &#8220;how good are they at metadata preservation&#8221;. If someone can do without BSD-Flags, Extended Attributes or ACL (ACL-support in TIger is normally turned off) he&#8217;ll be happy with old RsyncX&#8217; rsync (which preserves the creation date!!) and find workarounds for known bugs (e.g. avoiding uappnd-flags on directories).</p>

<p>Someone here asked for a report on rdiff-backup: the development version of rdiff-backup (1.1.12) loses the Z-Finderflag (busy-flag), the &#8220;locked&#8221; or BSD-ish &#8220;uchg&#8221;-flag, all BSD-flags, extended attributes on symlinks (<em>attributes elsewhere are preserved</em>, if py-xattr 0.4 is installed!!) and ACLs (1). rdiff-backup cannot copy device files and fifos.</p>

<p>This is promising for a development version, and rdiff-backup offers some &#8220;time machine&#8221; functions (restore to any given date of hour in the past)!</p>

<p>(1) rdiff-backup actually does support ACLs on other platforms, but not (yet??) on MacOS X (pylibacl refuses to install on a Mac).</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Peter da Silva</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-13055</link>
		<pubDate>Fri, 27 Jul 2007 23:12:57 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-13055</guid>
					<description>&lt;p&gt;OK, here's the deal. You never did explain what the basis of your comparisons are. You "partially recommend" a program that I &lt;em&gt;know&lt;/em&gt; preserves less of what I would have thought was genuinely critical metadata than one you "don't recommend", but you do make one point... you really recommend SuperDuper. Since it &lt;em&gt;is&lt;/em&gt; free for basic use, it can't hurt to try it.&lt;/p&gt;

&lt;p&gt;Of course... it's not really a backup program, it's a mirroring program, but given the price of backup media these days that seems to be what you're stuck with.&lt;/p&gt;

&lt;p&gt;So I go to make a backup using SuperDuper.&lt;/p&gt;

&lt;p&gt;You know what?&lt;/p&gt;

&lt;p&gt;It's missing what I would have thought was totally basic functionality for a mirroring program. You can't select the folder the mirror is going to be rooted in. You either have to blow away the whole destination disk, or create a disk image (which uses more disk space and memory). You can't select the folder you're going to back up, it's the whole disk or nothing.&lt;/p&gt;

&lt;p&gt;Is this what they consider advanced functionality? It doesn't seem like it.&lt;/p&gt;

&lt;p&gt;PLEASE, could you go into more detail &lt;em&gt;why&lt;/em&gt; you recommend some programs over others? What metadata are you considering essential, and what metadata are you letting slide, and why? And what basic functionality are you assuming any program should have... because SuperDuper is about the most basic non-functional backup program I've ever fired up.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>OK, here&#8217;s the deal. You never did explain what the basis of your comparisons are. You &#8220;partially recommend&#8221; a program that I <em>know</em> preserves less of what I would have thought was genuinely critical metadata than one you &#8220;don&#8217;t recommend&#8221;, but you do make one point&#8230; you really recommend SuperDuper. Since it <em>is</em> free for basic use, it can&#8217;t hurt to try it.</p>

<p>Of course&#8230; it&#8217;s not really a backup program, it&#8217;s a mirroring program, but given the price of backup media these days that seems to be what you&#8217;re stuck with.</p>

<p>So I go to make a backup using SuperDuper.</p>

<p>You know what?</p>

<p>It&#8217;s missing what I would have thought was totally basic functionality for a mirroring program. You can&#8217;t select the folder the mirror is going to be rooted in. You either have to blow away the whole destination disk, or create a disk image (which uses more disk space and memory). You can&#8217;t select the folder you&#8217;re going to back up, it&#8217;s the whole disk or nothing.</p>

<p>Is this what they consider advanced functionality? It doesn&#8217;t seem like it.</p>

<p>PLEASE, could you go into more detail <em>why</em> you recommend some programs over others? What metadata are you considering essential, and what metadata are you letting slide, and why? And what basic functionality are you assuming any program should have&#8230; because SuperDuper is about the most basic non-functional backup program I&#8217;ve ever fired up.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: MacUser</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-11012</link>
		<pubDate>Fri, 22 Jun 2007 14:42:03 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-11012</guid>
					<description>&lt;p&gt;Latest version of Personal Backup X4 worked flawlessly for me, preserving all metadata (except inodes number)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Latest version of Personal Backup X4 worked flawlessly for me, preserving all metadata (except inodes number)</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mickintosh</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-9352</link>
		<pubDate>Mon, 28 May 2007 13:14:09 +0000</pubDate>
		<guid>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-9352</guid>
					<description>&lt;p&gt;Regarding BruClone desktop version (http://www.tolisgroup.com/products/macosx/bruclone/) worked flawlessly, even with the incremental cloning&lt;/p&gt;

&lt;p&gt;While other apps like Intego Personnal Backup, fails to deliver even on a simple cloning.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Regarding BruClone desktop version (http://www.tolisgroup.com/products/macosx/bruclone/) worked flawlessly, even with the incremental cloning</p>

<p>While other apps like Intego Personnal Backup, fails to deliver even on a simple cloning.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
