Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.7: Use local Time Machine as an instant safety net' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.7: Use local Time Machine as an instant safety net
Authored by: polarbreeze on Nov 10, '11 07:22:31PM

Cautionary tale:
I was moving some files around to clean things up on my MBA. Once of the things I did was bring in a Parallels virtual machine file that I had saved on an external hard drive, and then, later on, move it to a different location. Unbeknownst to me, Lion's new TM caching feature was saving copies of this very large file. I ended up with 32GB of data in my .MobileBackup folder in one afernoon! When I reconnected with my TM drive, it went into frantic backup mode, presumably moving those (completely useless and redundant) 32GB of data onto my TM drive. It would have then stayed there for ever, taking up unnecessary TM space. I didn't wait long enough to see if it would then give me back the space on my MacBook drive but I assume it would have in the end. Anyway, I did the disablelocal thing and that definitely did recover my disk space.

I had another thought too. I'm in the habit of running two TM backups: one at work and one at home. I've been doing this for a long time, manually flipping the save location when I'm at home vs at work (BTW, it would be nice if OS X would take care of that for me automatically). Anyway, I'm wondering whether the .MobileBackup caching feature would confuse things in that scenario and mess up my backups. So just in case I'm leaving the feature disabled. It does seem to be a lot more trouble than it's worth.



[ Reply to This | # ]