Deciding how to upgrade your aging ZCM hardware or the best method to move the server from Linux to Windows can be complicated. So let me try to make it easier for you, but first please do some pushups or jumping jacks. I want your mind to be sharp and full of oxygen.
Upgrading the original server and then adding the new hardware to the zone is the least preferred.
I don't like it because it has extra steps and it requires that the original server remain in operation for a period until all workstations have the updated zone configuration.
This option does allow you to migrate from a Linux Primary server to a Windows Primary server and the other way around too. Also option 2 will not work if the original server is too small or poorly designed.
The second option is nice because you have a backup if the upgrade fails and the old hardware can be retired immediately.
Choosing option 1
- Upgrade the original server to version 11 (performed with the iso)
- Apply post patches. At the time of this writing, Cumulative Update 2 is recommended, although SP1 is soon to be released. SP1 will be a better choice as you can upgrade directly from 10.x to 11 SP1.
- Install the second server (performed with the iso)
- Migrate the certificate services
- Backing Up the Certificate Authority
- Restoring the Certificate Authority
- Migrate the database
- Update the closest server rules
- Update any switches that are configured with helper addresses for imaging
- Monitor the original server for any machines that are still contacting it
- Retire the old server. Follow the steps to remove a server from a zone.
Choosing option 2
- This option is really easy. Create an image of your old server using any DISK cloning software. See List of disk cloning software for a list
- Clonezilla is usually a good choice if you are looking for free
- Shutdown the old server
- Restore the image
- Upgrade to version 11
- Have a beer
Editor's Note: With option 2, it's important to be sure that the Operating System you're moving from the first server will run on the second (there may be hardware driver issues for example).
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.