Moving virtual server and instance names to a new server

We currently have a (2) node active/active cluster with each node ideally
hosting (2) virtual servers and their instances. We want to split the
cluster into (2) active/passive clusters and move what normally resides on a
given node to it's own cluster. Here is the catch. We have cross
server/instances queries/procedures and Access database/queries with the
Virtual Server and instance name hard coded, and creating new names isn't
really an viable option.
Here is the current setup:
Current Cluster:
NODE01
VSQL1\sqlsrv01
VSQL1\sqlsrv02
NODE02
VSQL1\sqlsrv03
VSQL1\sqlsrv04
And here is the proposed setup::
New Cluster 1:
NODE01 - active
VSQL1\sqlsrv01
VSQL1\sqlsrv02
NODE02 - inactive
New Cluster 2:
NODE01 - active
VSQL1\sqlsrv03
VSQL1\sqlsrv04
NODE02 - inactive
Can we create the servers in a different domain, moving them to our
production domain when testing has been completed? And if so, how do we
handle the fact that the VSQLx and named instances already exists in Active
Directory? Can the old server just be turned off, the new one brought up and
added to the domain by resetting the current domain accounts and re-joining?
Of course. Does anyone have a good solution, I'm all ears. Thanks
> Here is the current setup:
> Current Cluster:
> NODE01
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
That can't be your current setup. Your current setup is probably more like:
NODE01
VSQL01\sqlsrv01
VSQL02\sqlsrv02
NODE02
VSQL03\sqlsrv03
VSQL04\sqlsrv04
I'd probably just do a switchover with the current cluster. First, get the
necessary database files to a staging server. Then, remove the cluster from
the network. But keep it as your rollback plan. Create two new clusters and
install SQL instances as follows:
New Cluster 1:
NODE01 - active
VSQL01\sqlsrv01
VSQL02\sqlsrv02
NODE02 - inactive
New Cluster 2:
NODE01 - active
VSQL03\sqlsrv03
VSQL04\sqlsrv04
And finally get the database files from the staging server to their
respective new servers.
Linchi
"randall_dh" wrote:

> We currently have a (2) node active/active cluster with each node ideally
> hosting (2) virtual servers and their instances. We want to split the
> cluster into (2) active/passive clusters and move what normally resides on a
> given node to it's own cluster. Here is the catch. We have cross
> server/instances queries/procedures and Access database/queries with the
> Virtual Server and instance name hard coded, and creating new names isn't
> really an viable option.
> Here is the current setup:
> Current Cluster:
> NODE01
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
>
> And here is the proposed setup::
> New Cluster 1:
> NODE01 - active
> VSQL1\sqlsrv01
> VSQL1\sqlsrv02
> NODE02 - inactive
> New Cluster 2:
> NODE01 - active
> VSQL1\sqlsrv03
> VSQL1\sqlsrv04
> NODE02 - inactive
> Can we create the servers in a different domain, moving them to our
> production domain when testing has been completed? And if so, how do we
> handle the fact that the VSQLx and named instances already exists in Active
> Directory? Can the old server just be turned off, the new one brought up and
> added to the domain by resetting the current domain accounts and re-joining?
> Of course. Does anyone have a good solution, I'm all ears. Thanks
|||Yes, you are correct regarding the Virtual Server naming (careless cutting
and pasting on my part). Ideally, we would like to test the new cluster for
several days prior to bringing it live. My main concern is that the reusing
of the names doesn't cause a problem. Am I correct in my assumtions that AD
isn't involved in the virtual server or instance naming and that the only
network ties are through the DNS entries?
ALso, would you expect that any issues with restoring the master and msdb to
the new cluster instances (any references to the old nodes etc...)?
Thank you.
"Linchi Shea" wrote:
[vbcol=seagreen]
> That can't be your current setup. Your current setup is probably more like:
> NODE01
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
> NODE02
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
> I'd probably just do a switchover with the current cluster. First, get the
> necessary database files to a staging server. Then, remove the cluster from
> the network. But keep it as your rollback plan. Create two new clusters and
> install SQL instances as follows:
> New Cluster 1:
> NODE01 - active
> VSQL01\sqlsrv01
> VSQL02\sqlsrv02
> NODE02 - inactive
> New Cluster 2:
> NODE01 - active
> VSQL03\sqlsrv03
> VSQL04\sqlsrv04
> And finally get the database files from the staging server to their
> respective new servers.
> Linchi
> "randall_dh" wrote:

Moving SQL Cluster to a new subnet

Hello All,
I need to move a SQL Server Cluster from one subnet to another subnet so I
need to update 5 cluster IP addresses (node a, node b, cluster, SQL Server
and MS DTC). Any help on how to do this would be appreciated.
I found article 230356 explaining how to change the IP address in the nodes
but it is still confusing because it says that "do not work ... if you change
the IP address from one subnet to abother subnet". Then Allan Hirts' book
'SQL High Availability' shows the same procedure (page 190) but says
'Warning: Do not do this unless your servers need to change subnets". Any
idea what the problem is here?
Looks like article 244980 describes how to change the IP address for SQL
Server.
I still need to know how to change the IP address for the cluster and for
MSDTC.
Any help on this?
Thanks,
Benjamin Nevarez
SQL Server Database Administrator
"=?Utf-8?B?QmVuamFtaW4gTmV2YXJleg==?="
<BenjaminNevarez@.discussions.microsoft.com> wrote in
news:782BC7F5-3D71-4543-860B-92F396F9115F@.microsoft.com:

> Looks like article 244980 describes how to change the IP address for
> SQL Server.
Yes, for a virtual server. Exactly what you need, as far as I can see. It
seems to be pretty detailed as well.
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging
|||The article can be very confusing. The key to remember is that your cluster
always needs a clear communications path for its private communications.
Everything else is optional. Of course, you may be offline for a while
during the transition. Here are a few absolutely key elements
Make sure you have the 'Public" interface enabled for private
communications. Then you can change the private network without losing the
cluster. Once the private side is stable, you can change the public side.
Don't forget the impact of changes on your SAN. It may not like having a
host change IP addresses.
Make sure to read this KB article as well.
How to change the network IP addresses of SQL Server virtual servers
http://support.microsoft.com/kb/244980/
Geoff N. Hiten
Microsoft SQL Server MVP.
"Benjamin Nevarez" <BenjaminNevarez@.discussions.microsoft.com> wrote in
message news:782BC7F5-3D71-4543-860B-92F396F9115F@.microsoft.com...
> Hello All,
> I need to move a SQL Server Cluster from one subnet to another subnet so I
> need to update 5 cluster IP addresses (node a, node b, cluster, SQL Server
> and MS DTC). Any help on how to do this would be appreciated.
> I found article 230356 explaining how to change the IP address in the
> nodes
> but it is still confusing because it says that "do not work ... if you
> change
> the IP address from one subnet to abother subnet". Then Allan Hirts' book
> 'SQL High Availability' shows the same procedure (page 190) but says
> 'Warning: Do not do this unless your servers need to change subnets". Any
> idea what the problem is here?
> Looks like article 244980 describes how to change the IP address for SQL
> Server.
> I still need to know how to change the IP address for the cluster and for
> MSDTC.
> Any help on this?
> Thanks,
> Benjamin Nevarez
> SQL Server Database Administrator
>

Moving Quorum Drive

Hi,
I have a two node failover cluster with two external disk arrays. I have
these two array for some special testing. I no longer need both of them and
need to do some specific testing with just one array. My problem is that the
array I need to test with has all my SQL data but the other array has the
quorum drive. What is the best method to moving the quorum drive to the
other array?
Also, is it possible to have active/active SQL cluster where both SQL
servers (cluster nodes) are sharing the same SQL data files?
Thank you in advance.
Rodney or one of the other Cluster MVPs will have to anwer the quorum disk
move question.
The Active/Active nomenclature is misleading and obsolete. There is no
sharing of data files between SQL instances within a cluster (or anywhere
else for that matter).
Geoff N. Hiten
Microsoft SQL Server MVP
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OAPXqwwgFHA.3312@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have a two node failover cluster with two external disk arrays. I have
> these two array for some special testing. I no longer need both of them
> and need to do some specific testing with just one array. My problem is
> that the array I need to test with has all my SQL data but the other array
> has the quorum drive. What is the best method to moving the quorum drive
> to the other array?
> Also, is it possible to have active/active SQL cluster where both SQL
> servers (cluster nodes) are sharing the same SQL data files?
> Thank you in advance.
>
|||can't help your sql question, but hopefully this will help you to move your
quorum drive
http://support.microsoft.com/default...b;en-us;280353
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OAPXqwwgFHA.3312@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have a two node failover cluster with two external disk arrays. I have
> these two array for some special testing. I no longer need both of them
> and need to do some specific testing with just one array. My problem is
> that the array I need to test with has all my SQL data but the other array
> has the quorum drive. What is the best method to moving the quorum drive
> to the other array?
> Also, is it possible to have active/active SQL cluster where both SQL
> servers (cluster nodes) are sharing the same SQL data files?
> Thank you in advance.
>
|||So does that mean if you need to manage extremely high availability with
900K+ users using SQL, the only option you have is to get beefier boxes? and
live with the 40 second downtime you will get from the cluster failover?
Please note that most of these users are not humans and they know how to
hammer a box :-)
Thanks.
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:eHOrQQxgFHA.3936@.TK2MSFTNGP10.phx.gbl...
> Rodney or one of the other Cluster MVPs will have to anwer the quorum disk
> move question.
> The Active/Active nomenclature is misleading and obsolete. There is no
> sharing of data files between SQL instances within a cluster (or anywhere
> else for that matter).
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Dragon" <baadil_nospam@.hotmail.com> wrote in message
> news:OAPXqwwgFHA.3312@.TK2MSFTNGP10.phx.gbl...
>
|||SQL is a scale up not a scale out technology. SQL 2005 has some new tricks
to give you more high availability options, but you are still looking at
buying larger boxes as you outgrow your existing ones. I wouldn't worry too
much, the new TCP-C benchmark released last month by Microsoft is several
times the average daily transaction volume of Visa and it was run on a
single system. Besides, after a certain scale, the disk subsystem and
license costs far outweigh the host computer costs on almost any system,
regardless of which DMBS you are using.
Geoff N. Hiten
Microsoft SQL Server MVP.
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OooBB4ygFHA.3692@.TK2MSFTNGP09.phx.gbl...
> So does that mean if you need to manage extremely high availability with
> 900K+ users using SQL, the only option you have is to get beefier boxes?
> and live with the 40 second downtime you will get from the cluster
> failover? Please note that most of these users are not humans and they
> know how to hammer a box :-)
> Thanks.
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
> news:eHOrQQxgFHA.3936@.TK2MSFTNGP10.phx.gbl...
>
|||"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OAPXqwwgFHA.3312@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have a two node failover cluster with two external disk arrays. I have
> these two array for some special testing. I no longer need both of them
> and need to do some specific testing with just one array. My problem is
> that the array I need to test with has all my SQL data but the other array
> has the quorum drive. What is the best method to moving the quorum drive
> to the other array?
The best method of moving the quorum, in my opinion, is to simply use the
GUI. Using the GUI requires that both arrays be visible to the nodes and
that the physical disk that you want to use be also visible to both nodes.
In cluster admin, right click the cluster name, select the Quorum tab and
use the drop down box to select what drive you want to host the quorum.

> Also, is it possible to have active/active SQL cluster where both SQL
> servers (cluster nodes) are sharing the same SQL data files?
Active/active? No. It isn't possible for two instances to share the same
databases and logs.
|||"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OooBB4ygFHA.3692@.TK2MSFTNGP09.phx.gbl...
> So does that mean if you need to manage extremely high availability with
> 900K+ users using SQL, the only option you have is to get beefier boxes?
> and live with the 40 second downtime you will get from the cluster
> failover? Please note that most of these users are not humans and they
> know how to hammer a box :-)
You can do both. You can scale up, and you can scale out by using multiple
instances of SQL. However, to scale out, you must be able to break up
databases between the instances. If everyone requires access to the same
database, then you don't have the ability to scale out.
900K+ users? I am only guessing that there are not that many simultaneous
users. How many queries a second are we talking about, just out of
curiosity?
|||Thank you Russ.
I will defo give it a try as soon as I create some space on my DB array. :-)
It sound way to simple. hehe
"Russ Kaufmann" <russ@.nospam.exchangemct.com> wrote in message
news:uyGCMO3gFHA.3448@.TK2MSFTNGP12.phx.gbl...
> "Dragon" <baadil_nospam@.hotmail.com> wrote in message
> news:OAPXqwwgFHA.3312@.TK2MSFTNGP10.phx.gbl...
> The best method of moving the quorum, in my opinion, is to simply use the
> GUI. Using the GUI requires that both arrays be visible to the nodes and
> that the physical disk that you want to use be also visible to both nodes.
> In cluster admin, right click the cluster name, select the Quorum tab and
> use the drop down box to select what drive you want to host the quorum.
>
> Active/active? No. It isn't possible for two instances to share the same
> databases and logs.
>
|||Thank you Seth.
"seth" <seth@.work.net> wrote in message
news:e58ddYxgFHA.4000@.TK2MSFTNGP12.phx.gbl...
> can't help your sql question, but hopefully this will help you to move
> your quorum drive
> http://support.microsoft.com/default...b;en-us;280353
>
> "Dragon" <baadil_nospam@.hotmail.com> wrote in message
> news:OAPXqwwgFHA.3312@.TK2MSFTNGP10.phx.gbl...
>
|||http://www.tpc.org/tpcc/results/tpcc...p?id=105060604
GNH
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:ODmlkZ8gFHA.2560@.TK2MSFTNGP10.phx.gbl...
> Thank you Geof. Would you happen to have a link to the benchmark study?
> "Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
> news:eMbN%239ygFHA.3936@.TK2MSFTNGP10.phx.gbl...
>