migration to leopard

This is something I am working on as well, and I would strongly suggest you test before you make the jump, and make sure you have a good image of your system first.

One of the best ways I have heard for doing this is to promote a replica, wipe and install your current master, make it a replica of the promoted box, then promote that new Leopard server. Make sense?

I would highly suggest getting a second drive for the server, imaging your current system to that using SuperDuper, and then doing your upgrade on that second drive. That way you can roll back easily. And definitely test in a sandbox if you can.

Steve Wood
Director, Information Technology
swood at integerdallas.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6907 | C 940.312.2475

Well all the users are gone, so I do have the ability to take the ODM
offline for a while. One advantage of working for a school system is
that all your users are gone for 2.5 months over the summer.

Thomas Larkin
TIS Department
KCKPS USD500
tlarki at kckps.org
cell: 913-449-7589
office: 913-627-0351

In that case, assuming you have replica(s), I'd take the ODM offline. Then choose a replica, wipe it, and build your new Leopard ODM from scratch. Once you have it working and configured the way you want it, you could boot your Tiger ODM (off the network), export your users, then import them into your Leopard ODM.

Wow, no clients. I miss academia.

-----
Miles Leacy
ACTC|ACSA|ACT|CCA
Senior Mac Technologist
Polo Ralph Lauren
212.318.7603
miles.leacy at poloralphlauren.com

Well, I tested it on a Mac mini today and it all worked. I got summer
school the next two weeks actually, and I forgot about that earlier,
hehe, glad I remembered. During July there are practically zero mac
users at all so I will take it down first week of july. That gives me a
few weeks to test it out on my Mini as well then create an image as
well.

Thomas Larkin
TIS Department
KCKPS USD500
tlarki at kckps.org
cell: 913-449-7589
office: 913-627-0351

"Leacy, Miles (US)" <Miles.Leacy at PoloRalphLauren.com> 05/29/08 3:40

PM >>>
In that case, assuming you have replica(s), I'd take the ODM offline. Then choose a replica, wipe it, and build your new Leopard ODM from
scratch. Once you have it working and configured the way you want it,
you could boot your Tiger ODM (off the network), export your users, then
import them into your Leopard ODM.

Wow, no clients. I miss academia.

-----
Miles Leacy
ACTC|ACSA|ACT|CCA
Senior Mac Technologist
Polo Ralph Lauren
212.318.7603
miles.leacy at poloralphlauren.com

Per Apple IT & Education, I've always been told to:

1) Backup everything important on the test system or related production services (archive the OD master)
2) Force a replication event immediately before upgrading
3) Upgrade the MASTER and test - if it fails you can then promote a replica

This way, hopefully you're testing OD-based services....but then again, I usually do this AFTER a full backup and AFTER testing with a separate "skeleton" environment.
It saved me from losing a LOT of information when we upgraded some 10.4.11 server to 10.5.0 (patched to 10.5.2) - most of our LDAP records simply dropped out.
Would've been a nightmare...

-j
ACHDS/ACTC/ACSA 10.3/10.4
ACSP/ACTC 10.5