Tiger’s Filevault vs. Leopard’s Time Machine
My Time Machine sessions are failing in Leopard due to old Tiger FileVault settings. Going to talk a bit and then spill the beans. (It comes down to turning OFF FileVault in Tiger BEFORE you perform an upgrade)
The Leopard upgrade went really well. A little quicker than expected even. Only have this one reservation so far: I ran with FileVault “on” in Tiger. When I did the Upgrade (as opposed to the clean install and manual migration of files/apps) Time Machine is now complaining when I turn Time Machine on. At first it was the “Your chosen Time Machine disk doesn’t have enough space.” So, throwing away a lot of crud solve that. Now the complaint is that Leopard doesn’t like the version of FileVault I had been using… The suggestion from the system is to turn FileVault off and then back on. OK. Trying that gets me the error… “There’s not enough space to turn FileVault ‘off’.” So, CRAP! I can’t get there from here without shuffling a LOT of music, movies and pictures off to a temporary drive and then turning off FileVault.
This isn’t something I could have anticipated on my real day to day production machine. My development machine has had various flavors of Leopard running for over a year now with no seriously bad flaws. It’s not until you get into a real world situation like this where the bugaboos rear their heads and force you to improvise.
Hopefully this saves someone some grief at a beneficial time (before you install Leopard and not after).