On 10/17/2007 12:46 PM, "Ed Pastore" <email@hidden> wrote:
On Oct 17, 2007, at 1:31 PM, Craig Kabis wrote:
You're brave. Let us know what gets screwed up after you migrate.
The last one I did from 10.3.9 > 10.4.x was in January 2006. I'll
never do another. Working 20 hours straight and then having to boot
back up from the 10.3.9 Server blows. DNS was screwed up. The
service would stop by itself after a few minutes even after not
the GUI and editing the files by hand. I couldn't get Apple Mail
Server to work either.
Well, I gotta do something... I'd prefer not to leave all my servers
stuck on 10.4 forever. Was your bad experience with a migration or an
In any event, I'm hoping that the vast amount of migration-related
feedback generated on this list may have had some influence on
Apple's construction of the 10.5 migration guide; and perhaps it
won't be so bad. However, I'll be interested to see how it works with
NetInfo being killed off entirely in 10.5
I did mine as an in-place upgrade, and it was painless. However, it
until after 10.4.3, and with a lot of prep work before hand.
Amen to those last four words!
As they say, "prior proper planning prevents piss poor performance."
Overall I find that few Mac OS would-be sysadmins properly plan
updates yet alone upgrades.
At a minimum one needs to do a full standalone backup prior to any
upgrade or update. You need a roll back plan.
You also need an acceptance test plan. Who has one of those? Do I see
And many sites don't have good and stable systems from which they
upgrade. How many are sure they have no permissions issues before an
update? That the filesystem's integrity is solid? Or that DNS is true
and proper? I could imagine that those who are silently ignoring
those log messages from telling you to run changeip are going to
choke come an update.
And everyone's mileage is different. There are no two systems that
are the same. There is no "I have a basic OS X installation." So
while one might think they're not doing anything funky, unless you've
just installed the system you have a unique configuration and I'll
further bet that the hands raised would be slim to non-existant
The reasons OS X admins have so much trouble with updates and
upgrades is that as a group they have such little understanding of
how they have their systems configured. Other OSen force better
practices and systems hygiene. Larger shops document their systems
and configurations better.
Heck, do you know how few Mac shops I walk into that don't even have
a basic network diagram??
I have a client currently bifurcating a server and they were
haphazardly approaching it. I made them create a roadmap, before and
after diagrams, service assessment and configuration reports, and a
full checklist for pre-flight, launch and acceptance testing -- and
have a roll back plan. Was it a waste of time? Not if it leads to
success. Of course if it all goes smoothly will it be viewed that way?
So yes, upgrades and updates can be painful. As painful as you make
them. Plan well and prepare for potential pitfalls and the transition
can be smoother.
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden