However, I just ran into a little "gotcha" when I was upgrading to a slightly newer machine. Mac's also have this wonderful feature of being able to easily clone your hard drive. With a utility like SuperDuper!, you can also clone your machine onto another machine (on the same network). What's even better is that there is a free version of SuperDuper! which makes a complete clone of your machine onto the new machine (the paid versions offer you lots of options such which files/folders to exclude from the clone, thereby making things run faster).. very nice!
Of course, before I cloned the machine, I did a current backup onto my Time Machine drive, setup the cloning operation, and away we went. Took over 2 hours (I've heard that if you have large files on the machine being cloned, things take waaaay longer than if you don't: I had a pair of 2Gig compressed files so what was expected to take 20-30 minutes took much longer. But this is a minor whine, as everything else worked flawlessly on the clone).
However, Time Machine believes that this cloned machine is actually a new machine, and that's not good at all. It means that the new (cloned) machine no longer recognizes my Time Machine HDrive as the current backup drive and wants to start all over with a full backup. What that also means is t hat I can no longer go back to the files that are saved on my old Time Machine backup drive -- they are essentially gone.
I wonder if anyone else has had this experience; if so, do you know how to:
- avoid the problem in the future or
- access the old Time Machine backup "just in case"