June 8, 2012 at 8:07 am
Hi All
Setup: Windows 2008 Ent/SQL Server 2008 Ent
The server is a Single Node cluster and SQL is installed as a Clustered instance
We need to change the name of the server,
Is this possible without having to rebuild the Cluster
Any ideas?
Thanks
Derek
June 10, 2012 at 8:59 am
to change the actual node name uninstall any clustered instances from that node then remove the node from the cluster.
Rename and reboot and then re join to the cluster, then re join any clustered instances.
Are you able to temporarily introduce another machine to the cluster whilst re configuring your original node?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 10, 2012 at 11:24 am
Perry Whittle (6/10/2012)
to change the actual node name uninstall any clustered instances from that node then remove the node from the cluster.Rename and reboot and then re join to the cluster, then re join any clustered instances.
Are you able to temporarily introduce another machine to the cluster whilst re configuring your original node?
What we did was:
>> Renamed the Node
>> When the Node came back up with the new name, I couldn't connect to the VFS and I couldn't start the Cluster Service on the Server
I noted the following errors in Event Viewer:
The Cluster Service service terminated with service-specific error 5043 (0x13B3).
The Cluster service cannot identify node 'Node_Name' as a member of failover cluster ''. If the computer name for this node was recently changed, consider reverting to the previous name. Alternatively, add the node to the failover cluster and if necessary, reinstall clustered applications.
The Cluster service cannot be started on this node because a registry operation failed with error '5043'.
Getting another server introduced into the cluster should't be a problem
What would I need to do?
Thanks
Derek
June 10, 2012 at 2:52 pm
Doing it the way you did has produced errors as you can see.
You now need to reinstall all clustered apps.
Best thing is to revert back to the original name and carry out my steps above.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 11, 2012 at 12:43 am
Perry Whittle (6/10/2012)
Doing it the way you did has produced errors as you can see.You now need to reinstall all clustered apps.
Best thing is to revert back to the original name and carry out my steps above.
Thanks
The server name has been changed back to the original name and all is fine.
This is the scenario:
We have 3 Clustered servers namely: Server1, Server2 & Server3
Server1 & Server 2 participate in a 2 Node Cluster
Server 3 is a Single Node cluster in a different geographic location running from Completely seperate storage
We need to Shutdown Server1 and rename Server2 to Server1
Any ideas how this can be done effciently, easily and cleanly at the same time?
Thanks
Derek
June 11, 2012 at 12:55 am
Forget renaming them and instead create 3 new dns aliases (cname records)
June 11, 2012 at 12:58 am
Each computername must be unique within the domain. Why is changing the node name so important?
What you're asking involves destroying the current server1 and removing server2 from the cluster. Bit difficult if you only have 2 nodes in the cluster.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 11, 2012 at 1:01 am
Perry Whittle (6/11/2012)
Each computername must be unique within the domain. Why is changing the node name so important?What you're asking involves destroying the current server1 and removing server2 from the cluster. Bit difficult if you only have 2 nodes in the cluster.
My apologies for this - I had my initial scenario incorrect
We need to Shutdown Server1 and rename Server3 to Server1
Thanks
Derek
June 11, 2012 at 3:44 am
Perry Whittle (6/11/2012)
Each computername must be unique within the domain. Why is changing the node name so important?What you're asking involves destroying the current server1 and removing server2 from the cluster. Bit difficult if you only have 2 nodes in the cluster.
Hi Perry
This is what we're dealing with
Thanks
The server name has been changed back to the original name and all is fine.
This is the scenario:
We have 3 Clustered servers namely: Server1, Server2 & Server3
Server1 & Server 2 participate in a 2 Node Cluster
Server 3 is a Single Node cluster in a different geographic location running from Completely seperate storage
We need to Shutdown Server1 and rename Server3 to Server1
Any ideas how this can be done effciently, easily and cleanly at the same time?
Thanks
Derek
June 11, 2012 at 1:03 pm
SQLSACT (6/11/2012)
We have 3 Clustered servers namely: Server1, Server2 & Server3
Are all servers in the same domain?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 12, 2012 at 12:38 am
Perry Whittle (6/11/2012)
SQLSACT (6/11/2012)
We have 3 Clustered servers namely: Server1, Server2 & Server3Are all servers in the same domain?
Yep
All Servers are in the same domain
However, Server3 has its' own storage
Basically, what I want to achieve is:
Currently Server1 & Server2 are together in a 2 node cluster and Server3 is a single Node cluster on seperate storage
What I want to accomplish is a 2 Node cluster running on the storage currently being provided to Server3 - The issues is that the names have to be identical to the current 2 node cluster (Server1 & Server 2)
Thanks
June 12, 2012 at 2:42 am
hi,
When you setup a cluster then the node added to the cluster gets recorded somewhere on the registries, so you need to first remove node from cluster and all the services running on that node, reboot the node, rename the node, add the node to cluster again with its new node. Make sure the node name pre-exists on AD.
June 12, 2012 at 3:58 am
SQLSACT (6/12/2012)[hrYep
All Servers are in the same domain
However, Server3 has its' own storage
Basically, what I want to achieve is:
Currently Server1 & Server2 are together in a 2 node cluster and Server3 is a single Node cluster on seperate storage
What I want to accomplish is a 2 Node cluster running on the storage currently being provided to Server3 - The issues is that the names have to be identical to the current 2 node cluster (Server1 & Server 2)
Thanks
You'll need to uninstall any clustered instances from server1 so that they are only available on server2. Once this is done you then evict server1 from the cluster, leaving just server2 in a single node cluster.
As for replacing server1 with server3 i would perform the following high level steps;
➡ Backup and make a note of all objects in the clustered instance(s) on server3
➡ Agree a maintenance window with the business.
➡ export any last minute config and ensure backup integrity
➡ destroy the cluster on server3
➡ attach all storage that was on server3 to server2
➡ install the destroyed instance(s) from server3 onto server2
➡ rebuild server3 NOS as server1 and join to the cluster (don't forget to attach the storage)
➡ join the new server1 to any installed instances on server2 using the "Add Node" wizard
This shouldn't take too long to accomplish
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 12, 2012 at 4:03 am
Perry Whittle (6/12/2012)
SQLSACT (6/12/2012)[hrYep
All Servers are in the same domain
However, Server3 has its' own storage
Basically, what I want to achieve is:
Currently Server1 & Server2 are together in a 2 node cluster and Server3 is a single Node cluster on seperate storage
What I want to accomplish is a 2 Node cluster running on the storage currently being provided to Server3 - The issues is that the names have to be identical to the current 2 node cluster (Server1 & Server 2)
Thanks
You'll need to uninstall any clustered instances from server1 so that they are only available on server2. Once this is done you then evict server1 from the cluster, leaving just server2 in a single node cluster.
As for replacing server1 with server3 i would perform the following high level steps;
➡ Backup and make a note of all objects in the clustered instance(s) on server3
➡ Agree a maintenance window with the business.
➡ export any last minute config and ensure backup integrity
➡ destroy the cluster on server3
➡ attach all storage that was on server3 to server2
➡ install the destroyed instance(s) from server3 onto server2
➡ rebuild server3 NOS as server1 and join to the cluster (don't forget to attach the storage)
➡ join the new server1 to any installed instances on server2 using the "Add Node" wizard
This shouldn't take too long to accomplish
Thanks Perry
A question regarding this part:
You'll need to uninstall any clustered instances from server1 so that they are only available on server2. Once this is done you then evict server1 from the cluster, leaving just server2 in a single node cluster
Can I swap Server1 with Server2 in the above directions - I don't see any issue with that?
Thanks
Derek
June 12, 2012 at 4:44 am
Perry Whittle (6/12/2012)
SQLSACT (6/12/2012)[hrYep
All Servers are in the same domain
However, Server3 has its' own storage
Basically, what I want to achieve is:
Currently Server1 & Server2 are together in a 2 node cluster and Server3 is a single Node cluster on seperate storage
What I want to accomplish is a 2 Node cluster running on the storage currently being provided to Server3 - The issues is that the names have to be identical to the current 2 node cluster (Server1 & Server 2)
Thanks
You'll need to uninstall any clustered instances from server1 so that they are only available on server2. Once this is done you then evict server1 from the cluster, leaving just server2 in a single node cluster.
As for replacing server1 with server3 i would perform the following high level steps;
➡ Backup and make a note of all objects in the clustered instance(s) on server3
➡ Agree a maintenance window with the business.
➡ export any last minute config and ensure backup integrity
➡ destroy the cluster on server3
➡ attach all storage that was on server3 to server2
➡ install the destroyed instance(s) from server3 onto server2
➡ rebuild server3 NOS as server1 and join to the cluster (don't forget to attach the storage)
➡ join the new server1 to any installed instances on server2 using the "Add Node" wizard
This shouldn't take too long to accomplish
Hi Perry
I forgot to mention that not only do I have to keep the Server names the same, the VFS, VDB and DTC names need to stay the same as well
Does this change the process above?
Thanks
Derek
Viewing 15 posts - 1 through 15 (of 23 total)
You must be logged in to reply to this topic. Login to reply