Highlighted
Absent Member.
Absent Member.
1400 views

rolling cluster upgrade wt hardware upgrade

We are planning a rolling cluster upgrade with simultaneously change the hardware.
Is there anybody who has experiances with that?

Presens:
2-node-cluster NW 6.0 SP5, only Volume-Resources (SAN)

Plan:
- migrate all resources to one node
- remove that node from cluster and remove ds (kill that server)
- install a new (and newly named) server wt NW 6.5 SP7 into the same tree (has another server what is eDirectory master wt v8.8 on NW 6.5SP7)
- install NWCS 1.8 on that server and put it to the running (one-node-) cluster
- migrate all resources to the new node und remove the second old node (and server from tree)
(is now running the resouce state 'upgrade' because of only NWCS1.8-servers running?)
- install the second new node as a new server (with new name) in the same tree and install NWCS 1.8 on it and bring it into the cluster

Will this plan work?

Regards

Holger
Labels (1)
0 Likes
4 Replies
Highlighted
Frequent Contributor.
Frequent Contributor.

Re: rolling cluster upgrade wt hardware upgrade


no, don't do that. too much work (changing the server actually
invalidates NICI and certs and such).

migrate resources to one node.
do an across the wire hardware migration.
fail all resources back and do the other server.

migration help is available on the novell wiki:

http://wiki.novell.com/index.php/Migration_Wizard


--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS



-- Cheers! Richard Beels ~ Network Consultant ~ MCNE, CNE*, CNA*, CNS*, N*LS
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: rolling cluster upgrade wt hardware upgrade

Hi Richard,

thanks. It sounds good, but:
My first migration from nw6.0sp5 to nw6.5sp7 with NSCU was working. But then I noticed the LDAP 636 was not working and other such things.
All manually repaired. That server is now the eDirectory master.
I think, I take some old stuff into the new servers using NSCU. There are no significant certificates and so on. They are only clustered file servers.
It doesn't matter, when there names are changing.

The cause of my question was: I've got doubts about the technical feasibility.
And what will happen when the second node is leaving the cluster permanently.

Regards,

Holger
0 Likes
Highlighted
Frequent Contributor.
Frequent Contributor.

Re: rolling cluster upgrade wt hardware upgrade


it's much better to across the wire migrate a server than uninstall and
replace - if you want to keep the same name and such.

if you're going to install a new server and change the names and don't
mind reconfiguring everything, then your plan will work, albeit
sub-optimally.



--
Cheers!
Richard Beels
~ Network Consultant
~ Sysop, Novell Support Connection
~ MCNE, CNE*, CNA*, CNS*, N*LS



-- Cheers! Richard Beels ~ Network Consultant ~ MCNE, CNE*, CNA*, CNS*, N*LS
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: rolling cluster upgrade wt hardware upgrade

hello...I am in the same situation and have a few questions:

I am migrating from one NW6.5 two node cluster to another NW6.5 2 node cluster (all new hardware) and I'm not sure the correct way to do it. I have plenty of experience with the migration wizzard but that only deals with single servers and no shared volumes.

Should I set up the new hardware in a temp tree and set up a temp cluster or should I just set up one new server at a time and migrate the old fashioned way...my primary concern is getting the cluster resources and the Split Brain Partition migrated to the new SAN.

Any suggestions?

Jason Lepper
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.