PDA

View Full Version : Questions about "exclude system cache/temporary files" Copy Scripts


Darkside
05-12-2005, 02:13 AM
I see that most of the entries in the Copy Scripts for excluding temp and cache files match up with those that CCC removes. SD has a lot more temporary files listed, which is good I guess. :)

1) As you say, there are specific files that Apple recommends against copying when cloning. Is there a centralized list of these files anywhere on the web (at Apple's site, perhaps)? Maybe one with an explaination of what the files are/do? I'd do some digging, but I'm not really sure what to search for; plus, you probably know of it off the top of your head. :)

2) CCC and SD differ on some items that are ignored/removed. DesktopDB and DesktopDF are one such case; CCC copies them, SD does not. For these sort of temporary or autogenerated files, I'm assuming there's no risk in leaving them; after all, if they're recreated by the system at launch, they won't last long anyway. Is this a correct assumption?

3) CCC removes a lot more cache files in it's simple "backup everything" routine than SD; the "Exclude system cache files" Copy Script only seems to be used by Safety Clone (aka "Sandbox"... I agree with you that that term resonates more than Safety Clone :) ). Is there any particular reason the cache files aren't coppied with the "Sandbox" option, but they are with Backup - all files?

As you might have guessed, I'm a switcher from CCC. SD is all-around phenomenal; the auto-generated "What's going to happen" narrative is inspired.

Thanks for your help!

dnanian
05-12-2005, 10:48 AM
Hi, Darkside. Let's see if I can shine a little light.

1) I'd have to go hunting for this again -- it's been a while since the initial research -- but in general we're excluding each item suggested by Apple. These are all either temporary files or system-regenerated items that aren't valid on a different volume (or, potentially, machine). There's nothing here that is "dangerous" to exclude -- we're very careful.

2) Desktop DB/DF is a bit of a special case. OS9 people were having problems when backing up to a drive that had a different name, and were often forced to rebuild their desktop. Removing these files causes an 'automatic' desktop rebuild, which ensures things are correct when booting from the clone (but it does extract a one-time time penalty).

3) Unless this is a bug, there's no doubt some arcane reason why we did this that I can't remember (or think of) at the moment. My brain has turned to mint jelly after the last week or two due to the increased level of support traffic generated by Tiger's release. I'll look into the reasons again and, if appropriate, make a correction in a future release. Thanks for the question.

Thanks for the kind words about the UI: I'll be writing more blog posts (http://www.shirt-pocket.com/blog) about the genesis of SuperDuper! and its UI (and v2.0) in the coming weeks, so stay tuned!