![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Ah, that's better.
Mar. 13th, 2009 03:49 pmSo the key takeaway is that backing up over the net works fine; restoring over the net, not so much. At least, not for me. Here's the thread on all of it on apple.com. But to sum up:
0: Go ahead and back up over the network. That's okay. Then, when you need to restore later:
1. Shut down the server with the external HD backup disc. Unplug that external HD.
2. On the machine to which you wish to restore the data, create a new admin account with a different name than previous user accounts represented in the archive. Then plug the HD containing the time machine archive into that machine with the new admin user logged in.
3. Mount the sparsebundle archive as a local drive. (A gui mount works fine, command line not necessary.)
4. Run Migration Assistant which, once steps 1, 2, and 3 are completed, should see the Time Machine backup. Tell it to migrate everything in that Time Machine backup to the new machine.
Then life is good and you have ponies. Or at least files. Note that files in weird places (e.g., /usr/local/bin) will NOT be recovered this way. I didn't have much there (tf, mostly) so this was good enough, but keep that in mind.
0: Go ahead and back up over the network. That's okay. Then, when you need to restore later:
1. Shut down the server with the external HD backup disc. Unplug that external HD.
2. On the machine to which you wish to restore the data, create a new admin account with a different name than previous user accounts represented in the archive. Then plug the HD containing the time machine archive into that machine with the new admin user logged in.
3. Mount the sparsebundle archive as a local drive. (A gui mount works fine, command line not necessary.)
4. Run Migration Assistant which, once steps 1, 2, and 3 are completed, should see the Time Machine backup. Tell it to migrate everything in that Time Machine backup to the new machine.
Then life is good and you have ponies. Or at least files. Note that files in weird places (e.g., /usr/local/bin) will NOT be recovered this way. I didn't have much there (tf, mostly) so this was good enough, but keep that in mind.
