Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!not-for-mail From: Bread Newsgroups: comp.sys.mac.system Subject: Re: External HD Recommendation Date: Mon, 30 Dec 2013 14:49:04 -0800 Organization: lined up neatly Lines: 26 Message-ID: References: <281220130921464151%otto@bogus.address.com> <291220132136524546%otto@bogus.address.com> NNTP-Posting-Host: localhost Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Trace: reader1.panix.com 1388443745 21997 127.0.0.1 (30 Dec 2013 22:49:05 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Mon, 30 Dec 2013 22:49:05 +0000 (UTC) User-Agent: Unison/2.1.10 Xref: csiph.com comp.sys.mac.system:54092 On 2013-12-30 19:54:17 +0000, TaliesinSoft said: > On 2013-12-30 17:37:19 +0000, Bread said: > >> The thing is that the SuperDuper clones require more intervention on my >> part and >> the least reliable part of my backup system/workflow is *me*. Crashplan and >> Time Machine just happen. > > I'm puzzled by the statement that SuperDuper! clones require more > intervention. I have two SuperDuper! clones produced automatically in > the middle of the night and no intervention on my part is required. Inasmuch as I specifically want my clones *not* plugged in all the time, it requires me to pull out drives and swap them and such. And in the case of the laptop, as opposed to the desktop, such plugging and unplugging would not even be optional - it's the only way, whereas Time Machine and Crashplan both work all across the network entirely in the background. (And, yes, I'm aware that SD! can go to a network-mounted drive and/or disk image, but in practice, I've never found that to be successful or time-efficient).