-
Thoughts on Leopard Migration
There are two strategies that make sense to me right now if you want to do this safely.
1. Don’t be the first on your block.
Figure a new startup disk from the get go when you do too. ANY IT person will tell you to do this. Multiple installations should give one a go or something… Migrate that way at least folks… Might be week 2, ya never know. But read the forums about it first.
Or:
2. Start the moment they ship.
I think you keep your current startup disks however to be safe. Have a dual boot system for now. FW drives will work for this.
Partition them big drives guys… it’s time if you own big ones like 1TB drives. But a separate physical hard drive is best for startup disks in your Mac Pros. The fuller the drive the slower it gets…
But keep a startup that you KNOW works with ALL your gear if you’re a pro or just wanna be safe with your kid’s birthday video and pics.
When I migrate to a new OS with a newish Mac, I go thru the pain of partitioning or buying another disk drive to create the new OS startup volume. I do it one time for the life of that tower usually… It’s a given that OS X will be upgraded AGAIN someday, so that way I got a rock solid “last OS” system AND the lastest and greatest setup. Always have that real world backup on my Mac Pro.
I think I’d be wary of just hitting that “upgrade button” with a new leopard disk in my drive if you want to be “sure”.
When you upgrade to Leopard, it’s the time to start clean software/wise in any event.
Jerry
-
3 Replies
-
Jerry,
Agree with you completely.
We create a “model drive” on an external firewire drive which contains the new OS and a clean software install of ALL our other apps (FCS included). Then we use “Carbon Copy Cloner” to wipe and make a new “system drive” for all of our computers. Doing it this way achieves two goals: A clean install, and a “clean sweep” of all the crap that accumulates on the drives.
We warn everyone to “save it off-line” or it’s gone forever… and then we clone away.The only other advice I’d add is to wait until “low tide” to do this. Pick a day (or a week) where you’re going to have some time to troubleshoot before you have to use it. Don’t be an idiot and do this in the middle of a time-sensitive project. Of course the people reading this now already know this. It’s the people that come looking for help two weeks from now who should read this now. I guess they’d have to use “time machine” to do that…
mark
-
[Mark Raudonis] “It’s the people that come looking for help two weeks from now who should read this now. I guess they’d have to use “time machine” to do that…”
According to a post I think Walter wrote, Time Machine requires its own dedicated hard drive to write to, so its really just a more sophisticated and automated version of the clone for protection scheme that many of us already use.
David Roth Weiss
Director/Editor
David Weiss Productions, Inc.
Los AngelesPOST-PRODUCTION WITHOUT THE USUAL INSANITY™
A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.
-
uhhhh… I meant H. G. Wells version of a time machine, not Steve Jobs. 🙂
Mark
Reply to this Discussion! Login or Sign Up