<?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: The State of Backup and Cloning Tools under Mac OS X</title>
	<atom:link href="http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/feed/" rel="self" type="application/rss+xml" />
	<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>
	<lastBuildDate>Wed, 24 Feb 2010 06:17:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Xag</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-51079</link>
		<dc:creator>Xag</dc:creator>
		<pubDate>Sun, 23 Aug 2009 23:30:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-51079</guid>
		<description>&lt;p&gt;This can be of interest: automatic back up on a USB key without a click. It&#039;s a do-it-yourself. It uses rsyncx, no other third party app.
http://mogrifiers.blogspot.com/2009/08/quick-usb-backup-from-mac.html&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This can be of interest: automatic back up on a USB key without a click. It&#8217;s a do-it-yourself. It uses rsyncx, no other third party app.
<a href="http://mogrifiers.blogspot.com/2009/08/quick-usb-backup-from-mac.html" rel="nofollow">http://mogrifiers.blogspot.com/2009/08/quick-usb-backup-from-mac.html</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: naechtliches backup auf kleines externes Medium &#124; hilpers</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-45281</link>
		<dc:creator>naechtliches backup auf kleines externes Medium &#124; hilpers</dc:creator>
		<pubDate>Tue, 20 Jan 2009 15:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-45281</guid>
		<description>&lt;p&gt;[...] naechtliches backup auf kleines externes Medium      Hallo,  was waere euer Vorgehen, um z.B. naechtlich mittels cron-job auf einem USB-Stick ein backup laufen zu lassen?  Anwendung ist z.B. ein laptop oder Mac Mini mit z.B. 40 GB Platte und ein externer USB-Stick mit z.B. 8 GB.  Recht einfach ist die Kombination mit einem cron-job und tar, um alle Dateinen der letzten 24 Stunden komprimiert zu archivieren.  Interessanter waere vielleicht rsync u.a. Nach der Lektuere von http://blog.plasticsfuture.org/2006/...nder-mac-os-x/ stelle ich aber fest: MacOSX und HFS+ scheinen doch noch erhebliche &#039;Tricks&#039; auf Lager zu haben, wo resource forks und HFS+ Extended Attributes eher mehr Probleme schaffen, als ein backup zu vereinfachen.  Wichtigere Randbedingung: das backup soll komprimiert werden. Ich vermute, gerade daran scheitern die sonst besten Ansaetze?  ditto und damit CarbonCopyCloner kommen in dem genannten blog recht schlecht weg. SuperDuper war eher auf der Empfehlungsseite.  Ueberhaupt scheint der Finder vielen Programmen gerne ein Bein zu stellen, wenn Daten noch nicht im .DS_Store stehen, sondern noch immer nur im cache vorliegen?   Schoenen Gruss Martin [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] naechtliches backup auf kleines externes Medium      Hallo,  was waere euer Vorgehen, um z.B. naechtlich mittels cron-job auf einem USB-Stick ein backup laufen zu lassen?  Anwendung ist z.B. ein laptop oder Mac Mini mit z.B. 40 GB Platte und ein externer USB-Stick mit z.B. 8 GB.  Recht einfach ist die Kombination mit einem cron-job und tar, um alle Dateinen der letzten 24 Stunden komprimiert zu archivieren.  Interessanter waere vielleicht rsync u.a. Nach der Lektuere von <a href="http://blog.plasticsfuture.org/2006/...nder-mac-os-x/" rel="nofollow">http://blog.plasticsfuture.org/2006/&#8230;nder-mac-os-x/</a> stelle ich aber fest: MacOSX und HFS+ scheinen doch noch erhebliche &#8216;Tricks&#8217; auf Lager zu haben, wo resource forks und HFS+ Extended Attributes eher mehr Probleme schaffen, als ein backup zu vereinfachen.  Wichtigere Randbedingung: das backup soll komprimiert werden. Ich vermute, gerade daran scheitern die sonst besten Ansaetze?  ditto und damit CarbonCopyCloner kommen in dem genannten blog recht schlecht weg. SuperDuper war eher auf der Empfehlungsseite.  Ueberhaupt scheint der Finder vielen Programmen gerne ein Bein zu stellen, wenn Daten noch nicht im .DS_Store stehen, sondern noch immer nur im cache vorliegen?   Schoenen Gruss Martin [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Disk Utility - First Aid Failed - MacNN Forums</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-45150</link>
		<dc:creator>Disk Utility - First Aid Failed - MacNN Forums</dc:creator>
		<pubDate>Sun, 11 Jan 2009 20:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-45150</guid>
		<description>&lt;p&gt;[...] Slowly going insane while waiting for a fix  As for the $28, most people know that SD still does &lt;em&gt;full&lt;/em&gt; clones for &lt;em&gt;free&lt;/em&gt; -- and it always has. The $28 buys incremental (or &quot;differential&quot; if you prefer that terminology) backup features. What else did SD do differently? Well, according to these articles (from 2006), SD was the top cat in the &quot;preserving the most metadata&quot; department: The State of Backup and Cloning Tools under Mac OS X [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Slowly going insane while waiting for a fix  As for the $28, most people know that SD still does <em>full</em> clones for <em>free</em> &#8212; and it always has. The $28 buys incremental (or &quot;differential&quot; if you prefer that terminology) backup features. What else did SD do differently? Well, according to these articles (from 2006), SD was the top cat in the &quot;preserving the most metadata&quot; department: The State of Backup and Cloning Tools under Mac OS X [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Super Flexible File Synchronizer vs SuperDuper - general update on backup universe - MacNN Forums</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-43633</link>
		<dc:creator>Super Flexible File Synchronizer vs SuperDuper - general update on backup universe - MacNN Forums</dc:creator>
		<pubDate>Sat, 22 Nov 2008 13:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-43633</guid>
		<description>&lt;p&gt;[...] I have been a very happy user of SuperDuper for many years - and have recommended it widely but I have run into a limitation that has made me look elsewhere.  To be specific what I was looking for was a detailed way to run backups not just on a schedule (which SD can do if registered) but if a scheduled backup is missed then at the next earliest opportunity.  Furthermore, I wanted to be emailed with a summary of the backup success or failure - and emailed if the backup had not run at all.  All of these items and many more I have found in the app Super Flexible File Synchronizer.  However, and this is the big but - has anyone had any long term experience with this app and what are your thoughts of using it following a restore.  How does it play with large package format files on a Mac such as Aperture &amp; iPhoto Libraries?  Also, does it copy file attributes with anything like the success of SuperDuper - check out this article for an in-depth examination of what I am really trying to get at: plasticsfuture Blog  All thoughts gratefully appreciated... [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] I have been a very happy user of SuperDuper for many years &#8211; and have recommended it widely but I have run into a limitation that has made me look elsewhere.  To be specific what I was looking for was a detailed way to run backups not just on a schedule (which SD can do if registered) but if a scheduled backup is missed then at the next earliest opportunity.  Furthermore, I wanted to be emailed with a summary of the backup success or failure &#8211; and emailed if the backup had not run at all.  All of these items and many more I have found in the app Super Flexible File Synchronizer.  However, and this is the big but &#8211; has anyone had any long term experience with this app and what are your thoughts of using it following a restore.  How does it play with large package format files on a Mac such as Aperture &amp; iPhoto Libraries?  Also, does it copy file attributes with anything like the success of SuperDuper &#8211; check out this article for an in-depth examination of what I am really trying to get at: plasticsfuture Blog  All thoughts gratefully appreciated&#8230; [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Discussions on Mac Backup Strategies and Techniques: My Mac Journal</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-42697</link>
		<dc:creator>Discussions on Mac Backup Strategies and Techniques: My Mac Journal</dc:creator>
		<pubDate>Tue, 04 Nov 2008 16:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-42697</guid>
		<description>&lt;p&gt;[...] The CCC homepage pointed to this article, which is a fantastic resource on how the file metadata system introduced with the Mac OS X operating system introduces a ton of complications for those who think all that is needed to back up a Mac&#8217;s file system is to do a drag files and directories to another volume. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] The CCC homepage pointed to this article, which is a fantastic resource on how the file metadata system introduced with the Mac OS X operating system introduces a ton of complications for those who think all that is needed to back up a Mac&#8217;s file system is to do a drag files and directories to another volume. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: psychotron.net &#187; Blog Archive &#187; Advanced Mac OS X Programming</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-41457</link>
		<dc:creator>psychotron.net &#187; Blog Archive &#187; Advanced Mac OS X Programming</dc:creator>
		<pubDate>Thu, 02 Oct 2008 23:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-41457</guid>
		<description>&lt;p&gt;[...] I tre capitoli sul Filesystem sono poi molto interessanti, perche&#8217; oltre a ripassare le tipiche funzioni per la lettura e scrittura dei files, si parla di tutti gli attributi e metadati che puo&#8217; avere un file. Con Mac OS X siamo ai massimi storici come quantita&#8217; di metadati perche&#8217; oltre ad avere i classici permessi POSIX e proprietari, abbiamo da tener conto di attributi del Finder, Resource Forks, Extended Attributes, ACL e altro. Tutto questo poi purtroppo non puo&#8217; essere gestito da una sola API, ma da un miscuglio di BSD,Carbon e Cocoa. Se si e&#8217; pignoli, fare un backup corretto non e&#8217; proprio un gioco da ragazzi. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] I tre capitoli sul Filesystem sono poi molto interessanti, perche&#8217; oltre a ripassare le tipiche funzioni per la lettura e scrittura dei files, si parla di tutti gli attributi e metadati che puo&#8217; avere un file. Con Mac OS X siamo ai massimi storici come quantita&#8217; di metadati perche&#8217; oltre ad avere i classici permessi POSIX e proprietari, abbiamo da tener conto di attributi del Finder, Resource Forks, Extended Attributes, ACL e altro. Tutto questo poi purtroppo non puo&#8217; essere gestito da una sola API, ma da un miscuglio di BSD,Carbon e Cocoa. Se si e&#8217; pignoli, fare un backup corretto non e&#8217; proprio un gioco da ragazzi. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: rptb1</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-41371</link>
		<dc:creator>rptb1</dc:creator>
		<pubDate>Mon, 29 Sep 2008 18:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-41371</guid>
		<description>&lt;p&gt;See http://www.bombich.com/mactips/rsync.html for updated information on rsync, which now checks all the boxes (except inode) in the table in the article.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>See <a href="http://www.bombich.com/mactips/rsync.html" rel="nofollow">http://www.bombich.com/mactips/rsync.html</a> for updated information on rsync, which now checks all the boxes (except inode) in the table in the article.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: lucidsystems</title>
		<link>http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/comment-page-3/#comment-40973</link>
		<dc:creator>lucidsystems</dc:creator>
		<pubDate>Wed, 17 Sep 2008 10:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-40973</guid>
		<description>&lt;p&gt;&lt;a href=&quot;http://www.lucidsystems.org/tools/lbackup&quot; rel=&quot;nofollow&quot;&gt;LBackup&lt;/a&gt;  uses &lt;a href=&quot;http://www.rsync.samba.org&quot; rel=&quot;nofollow&quot;&gt;rsync&lt;/a&gt; to copy data&lt;/a&gt;. The latest stable version of rsync (version 3.0.4) is capable of preserving a great deal of the Mac OS X  related metadata.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><a href="http://www.lucidsystems.org/tools/lbackup" rel="nofollow">LBackup</a>  uses <a href="http://www.rsync.samba.org" rel="nofollow">rsync</a> to copy data. The latest stable version of rsync (version 3.0.4) is capable of preserving a great deal of the Mac OS X  related metadata.</p>]]></content:encoded>
	</item>
	<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-page-3/#comment-37162</link>
		<dc:creator>n8gray.org: Backup Bouncer is Working, Confusing, Annoying Developers</dc:creator>
		<pubDate>Mon, 02 Jun 2008 20:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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>[...] 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. [...]</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-page-3/#comment-34016</link>
		<dc:creator>Rsyncx to backup Mac &#124; Tongfamily.com</dc:creator>
		<pubDate>Mon, 28 Apr 2008 05:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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>[...] Plasticfutures.org has a good deeper analysis of the various tools. [...]</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-page-3/#comment-25012</link>
		<dc:creator>PG</dc:creator>
		<pubDate>Mon, 24 Mar 2008 19:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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&#039;m aware of your time constraints, so I don&#039;t expect a full update of the test results. But, I think it would be of great benefit if you would add a brief &quot;update&quot; 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:
<a href="http://www.bombich.com/software/ccc.html" rel="nofollow">http://www.bombich.com/software/ccc.html</a></p>

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

<p>maurits &#8211; 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 &#8211; 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-page-2/#comment-22313</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 06 Feb 2008 23:49:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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-page-2/#comment-22294</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 06 Feb 2008 19:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-22294</guid>
		<description>&lt;p&gt;I don&#039;t know why the author is tracking the &quot;locked Flag&quot;.  Mac OS X uses the BSD flag &quot;uchg&quot; 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 &quot;locked&quot; 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-page-2/#comment-22292</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 06 Feb 2008 19:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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-page-2/#comment-21693</link>
		<dc:creator>chipwreck &#124; blog &#187; archive &#187; Backup script using RsyncX</dc:creator>
		<pubDate>Sat, 26 Jan 2008 18:55:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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>[...] More details can be found here: blog.plasticsfuture.org [...]</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-page-2/#comment-20679</link>
		<dc:creator>New Home Server &#124; Robert Accettura&#8217;s Fun With Wordage</dc:creator>
		<pubDate>Wed, 02 Jan 2008 03:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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>[...] 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. [...]</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-page-2/#comment-20024</link>
		<dc:creator>Blog 2</dc:creator>
		<pubDate>Wed, 19 Dec 2007 15:36:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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>[...] The State of Backup and Cloning Tools under Mac OS X [...]</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-page-2/#comment-19819</link>
		<dc:creator>Charles Young</dc:creator>
		<pubDate>Thu, 13 Dec 2007 23:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-19819</guid>
		<description>&lt;p&gt;I&#039;ve had a lot of success with Bacula. [www.bacula.org].&lt;/p&gt;

&lt;p&gt;It&#039;s great if you&#039;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&#039;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 <a href="http://www.haught.org/howto/detail/tag/tech/item/bacula_osx/" rel="nofollow">http://www.haught.org/howto/detail/tag/tech/item/bacula_osx/</a></p>

<p>and a prebuilt binary client at <a href="http://www.pixelchaos.net/" rel="nofollow">http://www.pixelchaos.net/</a></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-page-2/#comment-18585</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Fri, 16 Nov 2007 16:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/the-state-of-backup-and-cloning-tools-under-mac-os-x/#comment-18585</guid>
		<description>&lt;p&gt;You should look at &quot;Unison&quot;
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;
<a href="http://www.cis.upenn.edu/~bcpierce/unison/" rel="nofollow">http://www.cis.upenn.edu/~bcpierce/unison/</a>
I use it to keep my laptop files synced. I used macports to get and install. <a href="http://www.macports.org/" rel="nofollow">http://www.macports.org/</a>
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-page-2/#comment-18318</link>
		<dc:creator>Matt &#38; Jen Simerson &#187; Backing up a Mac</dc:creator>
		<pubDate>Mon, 12 Nov 2007 16:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.plasticsfuture.org/2006/03/04/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>[...] 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. [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->