What are "cache files"? What do they contain?
I'm wondering because I've noticed that when I tell Retrospect to do an incremental backup, it decides that it needs to back up around 3GB worth
of files, even if I've only done only a little bit of Email since the
last backup. In fact, if I complete a backup and then immediately fire
off a new backup, it concludes that it needs to back up nearly 400Meg!
I'm telling it to back up "all but cache files," but I've noticed that
many of the files it backs up are named of the form "<digits>.<digits>.cache". I presume those must be "cache files,"
whatever they are...
This is Retrospect version 6.0.212 on my 17" G4 PowerBook. It doesn't
do this with a similar backup on my Dual-G5 machine.
see all those files ending with .cache or the files in the Metadata directories on Tiger? Those are cache files.
Michael Vilain wrote:
see all those files ending with .cache or the files in the Metadata directories on Tiger? Those are cache files.
OK, but what are they? What creates them (the OS, some application,
or...)?
What purpose do they serve?
Is there something I'm doing to
create, or modify, a lot of them?
Do any of you have any guesses as to
why Retrospect would back them up when I told it to back up all but
cache files?
Michael Vilain wrote:
see all those files ending with .cache or the files in the Metadata directories on Tiger? Those are cache files.
OK, but what are they? What creates them (the OS, some application,
or...)? What purpose do they serve? Is there something I'm doing to
create, or modify, a lot of them? Do any of you have any guesses as to
why Retrospect would back them up when I told it to back up all but
cache files?
Caches contain temporary storage, such as web pages you've visited.
OK, but what are they? What creates them (the OS, some application, >>or...)?The OS.
What purpose do they serve?
To make things happen faster.
The OS.
I too have seen that Retrospect still backs up cache files, even if you choose the option not to do so. I guess it's a bug.
Johan W. Elzenga wrote:
Caches contain temporary storage, such as web pages you've visited.
Are you sure they're browser cache files? It seems curious that they wouldn't be in a folder specific to Safari or whatever other browser.
Another reply suggested that the OS creates them to cache ... well, something else.
In article <1he540z.1y04syj1mgfhs0N%nomail@please.invalid>,
nomail@please.invalid (Johan W. Elzenga) wrote:
I too have seen that Retrospect still backs up cache files, even if you choose the option not to do so. I guess it's a bug.
Yes, an incomplete specification. The existing spec is pretty long,
but I added
Or File Name ends with "cache"
which seems to have fixed it.
That condition, plus Enclosing Folder matches "Caches", catches
essentially all cache-type files, including those in ~/Library/Icons.
The only caveat is that it also matches a few items that are part of application packages and such. Very few true cache files exist outside
users' home folders, so you don't really need to exclude them when
backing up system or application files.
The real problem, in my view, is that Retrospect's interface is so
crappy. There's no way to have Retrospect start a contemplated backup
and then say to it, "please highlight all the files on the computer that
are included in the "Cache" exclusionary rule, so that I may see what it
does in practice." m.
matt neuburg <matt@tidbits.com> wrote:
The real problem, in my view, is that Retrospect's interface is so
crappy. There's no way to have Retrospect start a contemplated backup
and then say to it, "please highlight all the files on the computer that are included in the "Cache" exclusionary rule, so that I may see what it does in practice." m.
Well, you can "Check Selector" to see a list of items that will be
selected from a target volume or subvolume; and you can view a backup
set's contents, snapshot by snapshot, after the fact. But yes,
Retrospect's interface is a convoluted, confusing, click-happy mess.
That condition, plus Enclosing Folder matches "Caches", catches
essentially all cache-type files, including those in ~/Library/Icons.
The only caveat is that it also matches a few items that are part of application packages and such.
I hope everybody caches my drift.
It will also exclude backing up some files which are actually not
caches, like these:
/Library/Caches/com.apple.user501pictureCache.tiff /Library/Caches/com.apple.user502pictureCache.tiff /Library/Caches/com.apple.user503pictureCache.tiff
Jerry Kindall wrote:
OK, but what are they? What creates them (the OS, some application, >>or...)?The OS.
What purpose do they serve?
To make things happen faster.
What things do they make faster? What sort of information do they
cache? For example, are they VM page files?
Jerry Kindall wrote:
OK, but what are they? What creates them (the OS, some application, >>or...)?The OS.
What purpose do they serve?
To make things happen faster.
What things do they make faster? What sort of information do they
cache? For example, are they VM page files?
/Library/Caches/com.apple.user501pictureCache.tiff /Library/Caches/com.apple.user502pictureCache.tiff /Library/Caches/com.apple.user503pictureCache.tiff
Nope. Those filenames don't end in "cache". They end in "tiff".
Various different things.
"Such as" means that browser cache is only one example of a cache.
Yes, an incomplete specification. The existing spec is pretty long, but
I added
Or File Name ends with "cache"
which seems to have fixed it.
Johan W. Elzenga wrote:
"Such as" means that browser cache is only one example of a cache.
OK, good point. The idea that it a wide variety of different kinds of things could be cached in that one place there hadn't occurred to me.
Sysop: | Gate Keeper |
---|---|
Location: | Shelby, NC |
Users: | 790 |
Nodes: | 20 (0 / 20) |
Uptime: | 41:14:41 |
Calls: | 12,115 |
Calls today: | 5 |
Files: | 5,294 |
D/L today: |
72 files (9,959K bytes) |
Messages: | 564,934 |