dbTalk Databases Forums  

Upgrading NT4 Cluster to Win2K3

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Upgrading NT4 Cluster to Win2K3 in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Freddy
 
Posts: n/a

Default Upgrading NT4 Cluster to Win2K3 - 05-23-2004 , 06:27 AM






OK, here is the scenario.

We have bought some nice new servers to replace our 3 year old ones. Also,
we are migrating to Win2K3. Managed to upgrade the current active/active
cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how
to upgrade, it tells us that we need to evict a node by running SQL Server
setup and entering the name of the virtual server.

This is where we get the problem.

We have two SQL servers in the cluster, they are named SQL_SERVER1 AND
SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a
named instance (to avoid cluster conflicts)

When entering the virtual server name in SQL server setup it tells me that
"The format of the virtual server name is invalid" After some hours of
research, the only possible reason I can come up with for this is that the
virtual server names have underscores on them.

We get the same message when running SP3a. This only occurs on Win2K3 and
not NT4.

Has anybody come across this problem or has a solution?


Thanks,
Freddy



Reply With Quote
  #2  
Old   
Freddy
 
Posts: n/a

Default Re: Upgrading NT4 Cluster to Win2K3 - 05-26-2004 , 04:33 AM






It's OK, turns out to be a bug and Microsoft is producing a nice hotfix for
me.


"Freddy" <fredfreddy1892 (AT) NOSPAMhotmailPLEASE (DOT) com> wrote

Quote:
OK, here is the scenario.

We have bought some nice new servers to replace our 3 year old ones. Also,
we are migrating to Win2K3. Managed to upgrade the current active/active
cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how
to upgrade, it tells us that we need to evict a node by running SQL Server
setup and entering the name of the virtual server.

This is where we get the problem.

We have two SQL servers in the cluster, they are named SQL_SERVER1 AND
SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a
named instance (to avoid cluster conflicts)

When entering the virtual server name in SQL server setup it tells me that
"The format of the virtual server name is invalid" After some hours of
research, the only possible reason I can come up with for this is that the
virtual server names have underscores on them.

We get the same message when running SP3a. This only occurs on Win2K3 and
not NT4.

Has anybody come across this problem or has a solution?


Thanks,
Freddy





Reply With Quote
  #3  
Old   
Freddy
 
Posts: n/a

Default Re: Upgrading NT4 Cluster to Win2K3 - 05-26-2004 , 04:33 AM



It's OK, turns out to be a bug and Microsoft is producing a nice hotfix for
me.


"Freddy" <fredfreddy1892 (AT) NOSPAMhotmailPLEASE (DOT) com> wrote

Quote:
OK, here is the scenario.

We have bought some nice new servers to replace our 3 year old ones. Also,
we are migrating to Win2K3. Managed to upgrade the current active/active
cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how
to upgrade, it tells us that we need to evict a node by running SQL Server
setup and entering the name of the virtual server.

This is where we get the problem.

We have two SQL servers in the cluster, they are named SQL_SERVER1 AND
SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a
named instance (to avoid cluster conflicts)

When entering the virtual server name in SQL server setup it tells me that
"The format of the virtual server name is invalid" After some hours of
research, the only possible reason I can come up with for this is that the
virtual server names have underscores on them.

We get the same message when running SP3a. This only occurs on Win2K3 and
not NT4.

Has anybody come across this problem or has a solution?


Thanks,
Freddy





Reply With Quote
  #4  
Old   
Freddy
 
Posts: n/a

Default Re: Upgrading NT4 Cluster to Win2K3 - 05-26-2004 , 04:35 AM



It's OK, turns out to be a bug and Microsoft is producing a nice hotfix for
me.


"Freddy" <fredfreddy1892 (AT) NOSPAMhotmailPLEASE (DOT) com> wrote

Quote:
OK, here is the scenario.

We have bought some nice new servers to replace our 3 year old ones. Also,
we are migrating to Win2K3. Managed to upgrade the current active/active
cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how
to upgrade, it tells us that we need to evict a node by running SQL Server
setup and entering the name of the virtual server.

This is where we get the problem.

We have two SQL servers in the cluster, they are named SQL_SERVER1 AND
SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a
named instance (to avoid cluster conflicts)

When entering the virtual server name in SQL server setup it tells me that
"The format of the virtual server name is invalid" After some hours of
research, the only possible reason I can come up with for this is that the
virtual server names have underscores on them.

We get the same message when running SP3a. This only occurs on Win2K3 and
not NT4.

Has anybody come across this problem or has a solution?


Thanks,
Freddy






Reply With Quote
  #5  
Old   
Freddy
 
Posts: n/a

Default Re: Upgrading NT4 Cluster to Win2K3 - 05-26-2004 , 04:35 AM



It's OK, turns out to be a bug and Microsoft is producing a nice hotfix for
me.


"Freddy" <fredfreddy1892 (AT) NOSPAMhotmailPLEASE (DOT) com> wrote

Quote:
OK, here is the scenario.

We have bought some nice new servers to replace our 3 year old ones. Also,
we are migrating to Win2K3. Managed to upgrade the current active/active
cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how
to upgrade, it tells us that we need to evict a node by running SQL Server
setup and entering the name of the virtual server.

This is where we get the problem.

We have two SQL servers in the cluster, they are named SQL_SERVER1 AND
SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a
named instance (to avoid cluster conflicts)

When entering the virtual server name in SQL server setup it tells me that
"The format of the virtual server name is invalid" After some hours of
research, the only possible reason I can come up with for this is that the
virtual server names have underscores on them.

We get the same message when running SP3a. This only occurs on Win2K3 and
not NT4.

Has anybody come across this problem or has a solution?


Thanks,
Freddy






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.