Cluster Server Rename

Is there an easy way to rename the Cluster Server Name ?
What about renaming the underlying physical nodes as well ?
Can this easily be done or does this call for an entire Cluster rebuild ?
Using SQL 2K and Windows 2003
you can rename your cluster :
http://technet2.microsoft.com/WindowsServer/en/library/3423f079-753c-4066-a998-26bf274298f41033.mspx?mfr=true
you can not rename the individual nodes, unless you evict them from the
cluster, rename the nodes, and add them to the cluster
"Hassan" <Hassan@.hotmail.com> wrote in message
news:%23MLZr5IBHHA.1220@.TK2MSFTNGP04.phx.gbl...
> Is there an easy way to rename the Cluster Server Name ?
> What about renaming the underlying physical nodes as well ?
> Can this easily be done or does this call for an entire Cluster rebuild ?
> Using SQL 2K and Windows 2003
>
|||SQL 2000 does not allow you to rename the SQL Virtual Instance name.
Everything else Edwin has correct.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Hassan" <Hassan@.hotmail.com> wrote in message
news:%23MLZr5IBHHA.1220@.TK2MSFTNGP04.phx.gbl...
> Is there an easy way to rename the Cluster Server Name ?
> What about renaming the underlying physical nodes as well ?
> Can this easily be done or does this call for an entire Cluster rebuild ?
> Using SQL 2K and Windows 2003
>
|||So how does one go about renaming the SQL Virtual ?
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:OH$Z4CQBHHA.1220@.TK2MSFTNGP04.phx.gbl...
> SQL 2000 does not allow you to rename the SQL Virtual Instance name.
> Everything else Edwin has correct.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:%23MLZr5IBHHA.1220@.TK2MSFTNGP04.phx.gbl...
>
|||With SQL 2000? Start all over
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Hassan" <Hassan@.hotmail.com> wrote in message
news:%23dn3NXhBHHA.3560@.TK2MSFTNGP04.phx.gbl...
> So how does one go about renaming the SQL Virtual ?
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:OH$Z4CQBHHA.1220@.TK2MSFTNGP04.phx.gbl...
>
|||the question was about rename cluster, not renaming named instance
;-)
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:OH$Z4CQBHHA.1220@.TK2MSFTNGP04.phx.gbl...[vbcol=seagreen]
> SQL 2000 does not allow you to rename the SQL Virtual Instance name.
> Everything else Edwin has correct.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Hassan" <Hassan@.hotmail.com> wrote in message
> news:%23MLZr5IBHHA.1220@.TK2MSFTNGP04.phx.gbl...
?
>
|||Trying to add value and guess the next question, in this case I was correct

Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Edwin vMierlo" <EdwinvMierlo@.discussions.microsoft.com> wrote in message
news:u2Vr0PwBHHA.5064@.TK2MSFTNGP02.phx.gbl...
> the question was about rename cluster, not renaming named instance
> ;-)
>
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:OH$Z4CQBHHA.1220@.TK2MSFTNGP04.phx.gbl...
> ?
>
|||See this article for renaming SQL 2005 virtual server name:
http://msdn2.microsoft.com/en-US/library/ms178083.aspx
However, you cannot rename SQL 2000 virtual server name.
"Rodney R. Fournier [MVP]" wrote:

> Trying to add value and guess the next question, in this case I was correct
>
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Edwin vMierlo" <EdwinvMierlo@.discussions.microsoft.com> wrote in message
> news:u2Vr0PwBHHA.5064@.TK2MSFTNGP02.phx.gbl...
>
>

Cluster Resource replacing physical server

We are replacing an existing SQL 2000 EE server with a clustered
resource by the same name. We have done this before, but are running
into an issue on this install. Here are the steps we have performed:
* Migrate databases as files
* Shut off original server
* Delete original computer account and replicate to all domain
controllers.
* Create cluster resource (third resource in this cluster)
We are having problems though with cluster recognizing the old server
account. We are getting Event ID 1210 on Clussvc on the install.
"Cluster resource 'SQL Network Name(ITSQLEE)' failed to go online
because its associated computer account (ITSQLEE) exists in Active
Directory and the Kerberos authentication is not enabled for the
resource. Client applications that are using Kerberos based
authentication (either directly or through the Negotiate security
package) will fail to authenticate when contacting a service by this
network name.
To bring the resource online, either enable Kerberos authentication or
delete the computer account."
In a prior event message, we get 1119 - Clussvc - Bad DNS Key. I have
tried this multiple times after waiting for Active directory to
synchronize and verifying with replmon. Any ideas? Thank you.
Hi Bowulf
The reason for this could be that the changes in Active Directory isn't
replicated around to all Domain Controllers. You could initiate Force
Replication but if you are in an enterprise environment this could cost in
terms of bandwith. Hence when you delete the computer account and it's not
replicated you would get this message.
Any help?
"Bowulf" wrote:

> We are replacing an existing SQL 2000 EE server with a clustered
> resource by the same name. We have done this before, but are running
> into an issue on this install. Here are the steps we have performed:
> * Migrate databases as files
> * Shut off original server
> * Delete original computer account and replicate to all domain
> controllers.
> * Create cluster resource (third resource in this cluster)
> We are having problems though with cluster recognizing the old server
> account. We are getting Event ID 1210 on Clussvc on the install.
> "Cluster resource 'SQL Network Name(ITSQLEE)' failed to go online
> because its associated computer account (ITSQLEE) exists in Active
> Directory and the Kerberos authentication is not enabled for the
> resource. Client applications that are using Kerberos based
> authentication (either directly or through the Negotiate security
> package) will fail to authenticate when contacting a service by this
> network name.
> To bring the resource online, either enable Kerberos authentication or
> delete the computer account."
> In a prior event message, we get 1119 - Clussvc - Bad DNS Key. I have
> tried this multiple times after waiting for Active directory to
> synchronize and verifying with replmon. Any ideas? Thank you.
>
|||Thanks for the reply. I had ensured with replmon that the 11 Domain
Controllers had all been synchronized with the each other, and that the
ADUC on each domain controller showed the computer as removed. The
entry was of course still present but tombstoned. I would hate to
think I would have to wait 90 days though.
ipconfig2 wrote:[vbcol=seagreen]
> Hi Bowulf
> The reason for this could be that the changes in Active Directory isn't
> replicated around to all Domain Controllers. You could initiate Force
> Replication but if you are in an enterprise environment this could cost in
> terms of bandwith. Hence when you delete the computer account and it's not
> replicated you would get this message.
> Any help?
>
> "Bowulf" wrote:
|||It is my understanding that this would be the behavior if DDNS did not
properly delete the entry, regardless of the status of the AD replication.
A simple ping of the name for the A record and reverse for the PTR would
indicate if it were still present.
Delete the DNS records manually.
Install the installation.
Create the virtual computer account manually if the Cluster service account
does not have sufficient rights.
Manually apply the SPN registrations for the SQL Server service account.
Then connect to cluster administrator to Enable Kerberos on the network name
resources.
Sincerely,
Anthony Thomas

"Bowulf" <bowulf@.gmail.com> wrote in message
news:1165709800.241227.11990@.79g2000cws.googlegrou ps.com...[vbcol=seagreen]
> Thanks for the reply. I had ensured with replmon that the 11 Domain
> Controllers had all been synchronized with the each other, and that the
> ADUC on each domain controller showed the computer as removed. The
> entry was of course still present but tombstoned. I would hate to
> think I would have to wait 90 days though.
> ipconfig2 wrote:
in[vbcol=seagreen]
not
>

Cluster IP address change and delay

Hi all,

I have recently changed IP addresses on my MS SQL cluster (the new IP
addresses belongs to a different network). Both physical node's IP
addresses and resource's IP addresses have been changed.

Everything seems to work fine. The cluster is up and responding
normally. The resources failover to another node when needed correctly.
However, I have noticed that the time it takes for the resource to
failover to another node is much longer than in the past (before IP
addresses change). I have noticed that "Network Name" is the resource
type that causes the delay. Could you please advise if there is
something that I overlooked and needs to be changed.updated as well, so
that groups fail over faster?

Thanks,
AleuHi

<aleu@.vp.plwrote in message news:f34s2m$b1q$2@.news.onet.pl...

Quote:

Originally Posted by

Hi all,
>
I have recently changed IP addresses on my MS SQL cluster (the new IP
addresses belongs to a different network). Both physical node's IP
addresses and resource's IP addresses have been changed.
>
Everything seems to work fine. The cluster is up and responding normally.
The resources failover to another node when needed correctly. However, I
have noticed that the time it takes for the resource to failover to
another node is much longer than in the past (before IP addresses change).
I have noticed that "Network Name" is the resource type that causes the
delay. Could you please advise if there is something that I overlooked and
needs to be changed.updated as well, so that groups fail over faster?
>
Thanks,
Aleu

I assume that you have followed http://support.microsoft.com/kb/244980 or
http://msdn2.microsoft.com/en-us/library/ms190460.aspx? Which version of SQL
Server is this?

When did you test the failover as it will take time to propogate the IP
address change. Have you tried to ping each of the servers or resolve the
names in the DNS?

John|||John Bell wrote:

Quote:

Originally Posted by

I assume that you have followed http://support.microsoft.com/kb/244980 or
http://msdn2.microsoft.com/en-us/library/ms190460.aspx? Which version of SQL
Server is this?

John, thanks for your response. Yes I did follow MS knowledge base
articles. I have MS SQL server 2005 x64.

Quote:

Originally Posted by

When did you test the failover as it will take time to propogate the IP
address change. Have you tried to ping each of the servers or resolve the
names in the DNS?

I did the ping commands. Well, I have tested the failover many hours
after that...

Any idea why this is so slow?

Thanks,
Aleu|||Hi

On May 28, 2:17 pm, "a...@.vp.pl" <a...@.vp.plwrote:

Quote:

Originally Posted by

John Bell wrote:

Quote:

Originally Posted by

I assume that you have followedhttp://support.microsoft.com/kb/244980or
http://msdn2.microsoft.com/en-us/li...0460.aspx?Which version of SQL
Server is this?

>
John, thanks for your response. Yes I did follow MS knowledge base
articles. I have MS SQL server 2005 x64.
>

Quote:

Originally Posted by

When did you test the failover as it will take time to propogate the IP
address change. Have you tried to ping each of the servers or resolve the
names in the DNS?

>
I did the ping commands. Well, I have tested the failover many hours
after that...
>
Any idea why this is so slow?
>
Thanks,
Aleu

I can't think of any other reasons why this should be an issue if your
DNS and routing are working fine. You may want to try changing it back
and seeing if the time improves.

John|||John Bell wrote:

Quote:

Originally Posted by

>
I can't think of any other reasons why this should be an issue if your
DNS and routing are working fine. You may want to try changing it back
and seeing if the time improves.

Unfortunately, I cannot change it back. Not only the IP addresses of
cluster resources have changed but also, cluster node's IP addresses
(moved to a different network). The "SQL IP address 1" becomes active
very fast (in around 6 seconds), however, "SQL Network Name" takes a few
good minutes (3-4) to change status from "online pending" to "online".

I have checked system logs and found few relevant things:

1. The configuration of the AdminConnection\TCP protocol in the SQL
instance VALIDATION is not valid.

2. Database mirroring connection error 4 'An error occurred while
receiving data: '10053(An established connection was aborted by the
software in your host machine.)'.' for 'TCP://hostname.x.x:2343'.

3. Database mirroring connection error 4 'An error occurred while
receiving data: '64(The specified network name is no longer available.)'.'

4. Configuration option 'Agent XPs' changed from 1 to 0. Run the
RECONFIGURE statement to install.

I do not know whether they are of any use, but (1) seems to be relevant.
What does it mean? Where can I check/change settings of
AdminConnection\TCP protocol?

What is the best place to look for the error logs? Does MS SQL server
store its error logs in some specific files? If so, what is the filename
and it's location?

Sorry for many questions but I am still newbie in this thing.

Thanks,
Aleu|||Hi Aleu

On May 28, 5:55 pm, "a...@.vp.pl" <a...@.vp.plwrote:

Quote:

Originally Posted by

John Bell wrote:
>

Quote:

Originally Posted by

I can't think of any other reasons why this should be an issue if your
DNS and routing are working fine. You may want to try changing it back
and seeing if the time improves.

>
Unfortunately, I cannot change it back. Not only the IP addresses of
cluster resources have changed but also, cluster node's IP addresses
(moved to a different network). The "SQL IP address 1" becomes active
very fast (in around 6 seconds), however, "SQL Network Name" takes a few
good minutes (3-4) to change status from "online pending" to "online".
>
I have checked system logs and found few relevant things:
>
1. The configuration of theAdminConnection\TCPprotocol in the SQL
instance VALIDATION is not valid.
>
2. Database mirroring connection error 4 'An error occurred while
receiving data: '10053(An established connection was aborted by the
software in your host machine.)'.' for 'TCP://hostname.x.x:2343'.
>
3. Database mirroring connection error 4 'An error occurred while
receiving data: '64(The specified network name is no longer available.)'.'
>
4. Configuration option 'Agent XPs' changed from 1 to 0. Run the
RECONFIGURE statement to install.
>
I do not know whether they are of any use, but (1) seems to be relevant.
What does it mean? Where can I check/change settings ofAdminConnection\TCPprotocol?
>
What is the best place to look for the error logs? Does MS SQL server
store its error logs in some specific files? If so, what is the filename
and it's location?
>
Sorry for many questions but I am still newbie in this thing.
>
Thanks,
Aleu

There are quite a few posts if you look for "AdminConnection\TCP"
http://groups.google.com/groups/sea...ection%5CTCP%22
they seems to suggest networking issues (incorrect aliases, firewall
issues etc) or possibly service account permissions.

I assume that the error messages regarding mirroring are related to
the period when you are switching, therefore may be expected.

John

Cluster help

I got a question/prob:
I changed the ip addy of my CLUSTER (physical) and now my
virtual servers won't pass the "online pending" stage.
They maintained the old ips.Is this possible? Can anyone
tell me what can i do to get the online pending to online?
any info?
Try doing this : http://support.microsoft.com/?id=244980
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"" <anonymous@.discussions.microsoft.com> wrote in message
news:2734601c46350$29675d70$a401280a@.phx.gbl...
> I got a question/prob:
> I changed the ip addy of my CLUSTER (physical) and now my
> virtual servers won't pass the "online pending" stage.
> They maintained the old ips.Is this possible? Can anyone
> tell me what can i do to get the online pending to online?
> any info?
>