Possible to compress a TM backup file?
in [Mac Systems]
|
From: Mark Conrad on 29 Mar 2010 19:20 In article <4bb0ed71$0$22143$742ec2ed(a)news.sonic.net>, Kevin McMurtrie <mcmurtrie(a)pixelmemory.us> wrote: > > Error message was something to the effect that > > I did not have the necessary "permissions" for > > some file named "spotlight_repair". > > > > I could not locate that file anywhere on disk. > > > > Mark- > > OS X has some access controls hacked in by filename. Interesting. I even tried putting _ALL_ my hard drives in the "Do Not Access" section of Spotlight. I _still_ got the error message from TM that TM was trying to access the supposed file "spotlight_repair" which of course I was not "authorized" to access. <g> > Restoring a bootable volume from a TM backup might > require the installation DVD. Yes it indeed does, in order to initially create the environment to render the internal hard drive "bootable", as per the instructions in TM itself. Mark-
From: Mark Conrad on 29 Mar 2010 19:20 In article <tfljdbszgq.fsf(a)ethel.the.log>, Doug Anderson <ethelthelogremovethis(a)gmail.com> wrote: > And then you would uncompress them before > giving them back to TM? Yep. > If that is what you are going to do, why don't you > just use gzip and tar? They won't give you any > confusing error messages. You'd want to > use options that preserve all the various bits of > information. [Of course like any backup scheme - > test to make sure that restore works.] That sounds good at least for gzip. tar frightens me. <g> Mark-
From: Tom Stiller on 29 Mar 2010 18:48 In article <michelle-479F6C.14155529032010(a)nothing.attdns.com>, Michelle Steiner <michelle(a)michelle.org> wrote: > In article <tom_stiller-5DE6D3.16571729032010(a)news.individual.net>, > Tom Stiller <tom_stiller(a)yahoo.com> wrote: > > > Where did you read that? The only compressed TM files on my machine are > > those that were compressed before TM made the backup. > > If you're backing up to a Time Capsule (or network storage device, I think, > as well), the backup is a sparse disk image; if you're backing up to a > directly attached (USB or Firewire) device, the backup is individual files. Actually, they're sparse disk image bundles and, as far as I can tell, they can be encrypted but I see no way to make them compressed, except after the fact. -- Tom Stiller PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF
From: Kevin McMurtrie on 29 Mar 2010 20:17 In article <290320101520132053%aeiou(a)mostly.invalid>, Mark Conrad <aeiou(a)mostly.invalid> wrote: > In article <4bb0ed71$0$22143$742ec2ed(a)news.sonic.net>, Kevin McMurtrie > <mcmurtrie(a)pixelmemory.us> wrote: > > > > Error message was something to the effect that > > > I did not have the necessary "permissions" for > > > some file named "spotlight_repair". > > > > > > I could not locate that file anywhere on disk. > > > > > > Mark- > > > > OS X has some access controls hacked in by filename. > > Interesting. > > > I even tried putting _ALL_ my hard drives in the > "Do Not Access" section of Spotlight. > > I _still_ got the error message from TM that TM was > trying to access the supposed file "spotlight_repair" > which of course I was not "authorized" to access. <g> > > > > Restoring a bootable volume from a TM backup might > > require the installation DVD. > > Yes it indeed does, in order to initially create the > environment to render the internal hard drive "bootable", > as per the instructions in TM itself. > > Mark- 'ls -al' can show invisible files on the command line. Don't mess the Info files or any bands. The Spotlight data is OK to erase but TM might spend hours or days rebuilding it. Interestingly, the 10.6.3 update copies the HFS metadata out of TM backups to a local directory then runs fsck on it. It looks like Apple is trying to recover from a bug. -- I won't see Google Groups replies because I must filter them as spam
From: J.J. O'Shea on 29 Mar 2010 22:17
On Mon, 29 Mar 2010 16:57:17 -0400, Tom Stiller wrote (in article <tom_stiller-5DE6D3.16571729032010(a)news.individual.net>): > In article <hor1d902ghk(a)news4.newsguy.com>, > J.J. O'Shea <try.not.to(a)but.see.sig> wrote: > >> On Mon, 29 Mar 2010 13:01:35 -0400, Mark Conrad wrote >> (in article <290320100901350163%aeiou(a)mostly.invalid>): >> > [[snip] > >>> My attempts to compress them were doomed to >>> failure because I do not have the smarts to handle >>> the various road blocks from the error messages >>> that pop up when I attempt to compress >>> the TM file, by using "Compress Archive". >>> (from the "File" menu) >> >> The TM files are already compressed. Attempting to compress already >> compressed files usually leads to Unexpected Results. > > Where did you read that? The only compressed TM files on my machine are > those that were compressed before TM made the backup. Isn't the sparse image compressed? -- email to oshea dot j dot j at gmail dot com. |