<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"  xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">
	<channel>
		<title>TidBITS: Comments on Clone Wars, or How My Backups Ate My Photos</title>
		<link>http://www.tidbits.com/</link>
		<description>Public confession time—a part of Adam’s backup strategy wasn’t fully thought out, and the end result was a situation that caused him to lose photos imported into iPhoto for two months. Read on for the gory details and for how to avoid your own clone wars.</description>
		<language>en-us</language>
		<copyright>Copyright 2010 TidBITS Publishing Inc.</copyright>
		<pubDate>Thu, 30 Dec 2010 09:13:15 PST</pubDate>
		<lastBuildDate>Thu, 30 Dec 2010 09:13:15 PST</lastBuildDate>
		<managingEditor>editors@tidbits.com (TidBITS Editors)</managingEditor>
		<webMaster>editors@tidbits.com (TidBITS Editors)</webMaster>
		<creativeCommons:license><![CDATA[http://www.tidbits.com/terms/]]></creativeCommons:license>
		<image>
			<title>TidBITS</title> 
			<url>http://www.tidbits.com/images/tb_logo_152x55.png</url> 
			<link>http://www.tidbits.com/</link> 
			<height>55</height>
			<width>152</width>
			<description>TidBITS badge</description> 
		</image>
		
		<item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_7011</link>
			<pubDate>Thu, 30 Dec 2010 09:13:15 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_7011</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Jolin Warren just gave me a good tip - to prevent a partition from mounting at login, the Unix way would be to add a line to the /etc/fstab file. See this writeup for more info:<br><br><a href="http://hints.macworld.com/article.php?story=20060930150059172">http://hints.macworld.com/article.php?story=20060930150059172</a>]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6960</link>
			<pubDate>Wed, 15 Dec 2010 14:20:56 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6960</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Yes, it's really too bad that iPhoto presents a list, rather than a standard Open dialog, which would have made clear where I was in the disk hierarchy. It's a case of trying to make something easier and making it worse in the process.]]></description>
		</item><item>
			<title><![CDATA[Comment from Christian Kaatmann]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6959</link>
			<pubDate>Wed, 15 Dec 2010 14:06:44 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6959</guid>
			<author><![CDATA[comments@tidbits.com (Christian Kaatmann)]]></author>
			<description><![CDATA[Dear Adam, I know exactly how you felt (that horrible sinking feeling..) from times when I succeeded in deleting important files from my harddrive with no recovery possible. The core of your problem is, I think, the non-transparent way in which iPhoto selects its photo library.<br>I can totally support the modus of using a disconnectable external harddrive. I keep one Carbon Copy clone on a Freecom drive and a Time Machine backup on another drive in our weekend home. CCC + Time Machine is a very sensible double backup strategy.]]></description>
		</item><item>
			<title><![CDATA[Comment from Curtis Wilcox]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6955</link>
			<pubDate>Tue, 14 Dec 2010 19:44:33 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6955</guid>
			<author><![CDATA[comments@tidbits.com (Curtis Wilcox)]]></author>
			<description><![CDATA[I knew $4 was a variable and assumed it represented the disk you want unmounted but I wasn't clear where the data inside that variable was coming from. Then I looked at the screenshot again, understood SuperDuper would run it and guessed $4 was the 4th parameter passed to this shell script. Sure enough, on pg. 43 of the SuperDuper manual, there's a list of parameters passed to pre- and post- scripts and the full path to the destination disk (e.g. /Volumes/DoppleZeus) was the 4th parameter.]]></description>
		</item><item>
			<title><![CDATA[Comment from Glenn Fleishman]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6952</link>
			<pubDate>Tue, 14 Dec 2010 09:47:55 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6952</guid>
			<author><![CDATA[comments@tidbits.com (Glenn Fleishman)]]></author>
			<description><![CDATA[We'll look into it. It hasn't been our experience among many users here at TidBITS and our colleagues, but that doesn't mean that our experience invalidates everyone else's! Thanks for the information.]]></description>
		</item><item>
			<title><![CDATA[Comment from Simon]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6951</link>
			<pubDate>Tue, 14 Dec 2010 09:18:43 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6951</guid>
			<author><![CDATA[comments@tidbits.com (Simon)]]></author>
			<description><![CDATA[You'll read about a ton of problems if you frequent Mac-related forums. Just google for issues with clones created with CCC and SD. Supposedly "bootable clones" not booting users' Macs is the most common but by far not the most serious.<br><br>In the end you get what ask for. If you want a reliable clone, don't fiddle (i.e, increment, etc.) with it. If you want to fiddle, make sure you use another backup method and another backup volume in addition.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6950</link>
			<pubDate>Tue, 14 Dec 2010 08:12:44 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6950</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[The $4 refers to the just-backed-up disk, as I understand it.]]></description>
		</item><item>
			<title><![CDATA[Comment from Glenn Fleishman]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6949</link>
			<pubDate>Tue, 14 Dec 2010 08:08:07 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6949</guid>
			<author><![CDATA[comments@tidbits.com (Glenn Fleishman)]]></author>
			<description><![CDATA[I haven't heard about these problems, either. Can you point to where people are having difficulties? I've used smart clones from Super Duper to boot and restore drives several times.]]></description>
		</item><item>
			<title><![CDATA[Comment from Jeff]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6948</link>
			<pubDate>Tue, 14 Dec 2010 08:01:38 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6948</guid>
			<author><![CDATA[comments@tidbits.com (Jeff)]]></author>
			<description><![CDATA[Regarding the interim method of getting SuperDuper! to unmount a volume after backup (a GREAT idea), the command in the article<br><br>nohup /bin/bash -c "sleep 30; diskutil unmount \"$4\"" &<br><br>seems a bit cryptic.  Does this command indirectly always refer to the volume that SuperDuper has just backed up, or does it have to be changed in some manner for other peoples' backups?]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6947</link>
			<pubDate>Tue, 14 Dec 2010 08:01:36 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6947</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[I guess I simply haven't heard from people using CCC and SD and suffering notable problems.]]></description>
		</item><item>
			<title><![CDATA[Comment from Simon]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6946</link>
			<pubDate>Tue, 14 Dec 2010 07:29:59 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6946</guid>
			<author><![CDATA[comments@tidbits.com (Simon)]]></author>
			<description><![CDATA[You can script DU (or use asr on the CLI -&gt; shell scripts) for pre/post-flight tasks.<br><br>Incremental backups are indeed something DU doesn't do, but CCC and SD offer. But why would you want to do that? Think about it. A clone is an exact bit-by-bit copy. By its very definition you do not want to modify it through an incremental procedure. <br><br>Backups can be incremental (like Time Machine). But cloning should never be incremental. The extra 'functionality' offered by CCC and SD are the very cause of much of the trouble these tools have given people.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6943</link>
			<pubDate>Tue, 14 Dec 2010 06:19:50 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6943</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[A clone or a duplicate is a backup, but it is only a part of a real backup strategy (along with versioned backups and off-site backups). <br><br>The problem with a RAID 1 mirror, in comparison with a duplicate made on a schedule, is that any mistakes or logical corruption are immediately and automatically transferred to the mirror, rendering it useless as a backup. RAID is great for protecting against physical damage to the source drive, so it too can be part of a backup strategy, but isn't a backup on its own because it's so easily corrupted with bad information from the source.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6942</link>
			<pubDate>Tue, 14 Dec 2010 06:16:43 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6942</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Disk Utility certainly does have this capability, but I disagree strongly that CCC and SuperDuper are hacks or rip-offs in any way. Both offer significant features, such as scheduling, pre- and post-flight scripts, copying only of changed files, and so on, that go way beyond what Disk Utility does.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6941</link>
			<pubDate>Tue, 14 Dec 2010 06:13:53 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6941</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Yes, absolutely, which is why I mentioned that in the article too. What worries me more is that there may be other situations where a confusion with a clone disk could cause problems, potentially even more significant ones.]]></description>
		</item><item>
			<title><![CDATA[Comment from Steve Rickaby]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6940</link>
			<pubDate>Tue, 14 Dec 2010 05:17:11 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6940</guid>
			<author><![CDATA[comments@tidbits.com (Steve Rickaby)]]></author>
			<description><![CDATA[I worry when I hear people using the terms 'clone' and 'backup' synonymously. Each has their place, but they aren't the same thing. In my view, a far better approach to cloning is to use a SoftRAID RAID 1 mirror. This way your clone is always up to date without you having to do anything; if the clone is on an external drive, it can be instantly transferred to another Mac.]]></description>
		</item><item>
			<title><![CDATA[Comment from Simon]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6939</link>
			<pubDate>Tue, 14 Dec 2010 00:26:04 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6939</guid>
			<author><![CDATA[comments@tidbits.com (Simon)]]></author>
			<description><![CDATA[I never understood why people risked their data by using hacks like CCC or SuperDuper. Apart from the fact that the latter actually costs money, both have caused a lot of trouble for a lot of people.<br><br>Instead, people could opt to use Apple's built-in and rock stable cloning tool that comes with every OS X installation. It does the same (minus incremental, which you don't want on a clone anyway), but it does it reliably and for free. Thanks to block copies it's also much faster than rip-off hackware like CCC or SD.<br><br>/Applications/Utilities/DiskUtility &gt; Restore<br><br>(select 'erase destination' to make the clone bootable)]]></description>
		</item><item>
			<title><![CDATA[Comment from Michael Babcock]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6928</link>
			<pubDate>Mon, 13 Dec 2010 15:29:16 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6928</guid>
			<author><![CDATA[comments@tidbits.com (Michael Babcock)]]></author>
			<description><![CDATA[I prefer to use iPhoto Library Manager to open my various iPhoto libraries. Since you have to add each library to the list yourself there's no danger that you'll open the library on your clone.]]></description>
		</item><item>
			<title><![CDATA[Comment from P T Withington]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6573</link>
			<pubDate>Sat, 30 Oct 2010 03:48:37 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6573</guid>
			<author><![CDATA[comments@tidbits.com (P T Withington)]]></author>
			<description><![CDATA[Just a side note on something that burned me:  TimeMachine does _not_ back up your iPhoto library if iPhoto is open!  I tend to leave it open, because I use it so much.  Then my drive died, and I lost months of photos.  Luckily for me, like Adam, I had an off-site backup (backblaze) which does back up everything, so I was able to recover from a drive crash (with a bunch of fiddling to get iPhoto to recognize the restored images).  It is totally amazing to me that Apple doesn't at least pop up a warning to tell you that TimeMachine did not back up your photos when it last ran...]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6566</link>
			<pubDate>Thu, 28 Oct 2010 13:52:57 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6566</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[I had thought of that, but my initial testing was inconclusive. I know more now, and here's the deal. If I had put DoppleZeus in Spotlight's Privacy list initially, or if Spotlight hadn't lost it (I can't say for sure I did this, but I don't trust Spotlight not to forget settings), then I'd never have been presented with the DoppleZeus version of the iPhoto Library.<br><br>However, I was presented with it at some point, and I selected it, and once I did that, iPhoto remembered it in the com.apple.iPhoto.plist file, so regardless of whether DoppleZeus was in the Privacy list or not (and even after I deleted the Spotlight index on the volume manually just to be sure), iPhoto remembered that I had once selected it and made it available thereafter.<br><br>All of these capabilities make sense, but they can combine to undesirable behavior.]]></description>
		</item><item>
			<title><![CDATA[Comment from smitty]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6565</link>
			<pubDate>Thu, 28 Oct 2010 13:17:35 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6565</guid>
			<author><![CDATA[comments@tidbits.com (smitty)]]></author>
			<description><![CDATA[Why not exclude DoppleZeus from Spotlight? Wouldn't you be constantly plagued by duplicate found items if you didn't? (Just a thought, haven't tested)]]></description>
		</item><item>
			<title><![CDATA[Comment from Michael Wenyon]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6555</link>
			<pubDate>Thu, 28 Oct 2010 05:31:26 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6555</guid>
			<author><![CDATA[comments@tidbits.com (Michael Wenyon)]]></author>
			<description><![CDATA[Sorry to hear about your loss. After a very similar experience years ago, my Mac Pro has four 1TB drives: the start-up disk (always mounted) and three complete clones (unmounted unless SuperDuper! mounts them). The three other disks are Daily, Weekly and Monthly clones made by SD! This in addition to Time Machine and AASync that runs a nightly SFTP backup to Dreamhost of documents only.]]></description>
		</item><item>
			<title><![CDATA[Comment from Michael Elliott]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6554</link>
			<pubDate>Thu, 28 Oct 2010 05:23:11 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6554</guid>
			<author><![CDATA[comments@tidbits.com (Michael Elliott)]]></author>
			<description><![CDATA[Adam...what about iPhone backups?<br><br>You might want to try to go into iTunes, and restore your iPhone from a previous backup (I think located somewhere in ~/library/iTunes or something).  You might be surprised to find that your photos are still there in THOSE serial backups, even though you erased the pics from the iPhone every time you imported into iPhoto.<br><br>This should work unless 1) you cancel or prevent backups of your iPhone whenever it is connected or 2) you also have THAT library somehow on your "backup" drive.]]></description>
		</item><item>
			<title><![CDATA[Comment from Eric Seale]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6551</link>
			<pubDate>Wed, 27 Oct 2010 16:42:11 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6551</guid>
			<author><![CDATA[comments@tidbits.com (Eric Seale)]]></author>
			<description><![CDATA[Another approach: protection via *hand-carried* offsite backup.<br><br>To protect against easy mistakes (deletion of a file I should have kept, etc.), I have TimeMachine automatically backing up to a Drobo box -- but my absolute last-ditch defense is a pair of 2 TByte external drives.  One's always in a desk drawer at work, the other one's in transit.  <br><br>When one's at home, I connect it at bedtime and start up "Super Duper" to clone my iMac's drive.  When I get up in the morning, I disconnect it and stuff it in my briefcase.  This way, I can't get confused about what photo library I'm using, and I've got protection against home catastrophes.<br><br>Worth considering...]]></description>
		</item><item>
			<title><![CDATA[Comment from Lee Wilkirson]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6548</link>
			<pubDate>Wed, 27 Oct 2010 14:39:19 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6548</guid>
			<author><![CDATA[comments@tidbits.com (Lee Wilkirson)]]></author>
			<description><![CDATA[I had the same experience with iTunes, requiring me to re-rip a multiple-CD album. Thanks for the unmount at login script; it was the missing piece.]]></description>
		</item><item>
			<title><![CDATA[Comment from Adam Engst]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6547</link>
			<pubDate>Wed, 27 Oct 2010 14:24:57 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6547</guid>
			<author><![CDATA[comments@tidbits.com (Adam Engst)]]></author>
			<description><![CDATA[Yes, this is a slight issue, but it's easy to stop CCC when it kicks in on disk mount. (I've been doing a lot of that while testing.) If it were a real issue, I could schedule Keyboard Maestro to mount the disk at 11:16 PM and schedule CCC to back up at 11:18 PM, or something like that.]]></description>
		</item><item>
			<title><![CDATA[Comment from Charlie]]></title>
			<link>http://db.tidbits.com/article/11699?rss#comments_6546</link>
			<pubDate>Wed, 27 Oct 2010 14:23:51 PST</pubDate>
			<guid>http://db.tidbits.com/article/11699#comments_6546</guid>
			<author><![CDATA[comments@tidbits.com (Charlie)]]></author>
			<description><![CDATA[Since I've been spending part of my day today restoring my iPhoto library which iPhoto '11 so rudely destroyed, I've been thinking about backups.<br>I'm wondering if you might experience a problem if you needed to mount your DoppleZeus disk to recover a file which would then trigger CCC to start a backup - one that you may not want to occur at that precise moment. I ask because something similar, but not identical, happened to me today. I was in the middle of restoring some files from my cloned backup when I stepped away from the computer for a moment.  SuperDuper started (it's set to start at a specified time) and copied my corrupted drive onto my backup. Fortunately for me I had a separate Time Machine backup so no harm.<br><br>Just wondering<br><br>Charlie]]></description>
		</item>	
		
	</channel>
</rss>