Associate
Hello people,
Once again I am trying to get best practice for some work based fun.
We have 6 NLB Clustered servers in a web farm. The first 3 of these servers are of one spec and model, the second 3 of a lower spec and model.
I now want to replace the first 3 with 3 of the lower spec and model.
My concerns, apart from not having a build document (I've just cloned one of the server, removed from domain, change to generic name, run NewSID, and change network card to DHCP), are:-
- Does any one server(the one with priority 1) hold the master NLB DB (if there is one?)
- Can I do without a priority 1, 2 or 3 server?
My plan was to basically:
- Ghost clone onto a new HDD, run NewSID again. Do I need to run sysprep? I would not have thought so.
- Unplug from network and set IP address and hostname the same as the replacement server.
- Taken server to be replaced out of the farm, and remove from domain. Turn it off.
- Boot up replacement server, and add back into the domain, and reboot.
- Add back into NLB Cluster with same priority as replcaed server (This should sync the IIS MetaDB aswell).
Any comments on this, or is this best practice?
Pax
edit: just found, searching, "Synchronize IIS on all nodes by using the IIScnfg.vbs /copy command to copy the IIS configuration to other nodes." which I should probably do just before adding server into NLB cluser.
Once again I am trying to get best practice for some work based fun.
We have 6 NLB Clustered servers in a web farm. The first 3 of these servers are of one spec and model, the second 3 of a lower spec and model.
I now want to replace the first 3 with 3 of the lower spec and model.
My concerns, apart from not having a build document (I've just cloned one of the server, removed from domain, change to generic name, run NewSID, and change network card to DHCP), are:-
- Does any one server(the one with priority 1) hold the master NLB DB (if there is one?)
- Can I do without a priority 1, 2 or 3 server?
My plan was to basically:
- Ghost clone onto a new HDD, run NewSID again. Do I need to run sysprep? I would not have thought so.
- Unplug from network and set IP address and hostname the same as the replacement server.
- Taken server to be replaced out of the farm, and remove from domain. Turn it off.
- Boot up replacement server, and add back into the domain, and reboot.
- Add back into NLB Cluster with same priority as replcaed server (This should sync the IIS MetaDB aswell).
Any comments on this, or is this best practice?
Pax
edit: just found, searching, "Synchronize IIS on all nodes by using the IIScnfg.vbs /copy command to copy the IIS configuration to other nodes." which I should probably do just before adding server into NLB cluser.
Last edited: