January 12, 2012 at 1:56 pm
We have a single SQL server running 2008 R2 Standard Edition. The OS is 2008 R2 Enterprise Edition. We just got a second server, also running OS Server 2008 R2 Enterprise, but we still need to install SQL. We would like to implement failover clustering. Since we are actively using the existing server, I'm unsure of how to approach an implementation of failover clustering. Do I...
1. Just run the cluster setup on the existing server? Can I keep my existing server\instance name if I do this?
2. Run setup on the secondary node, create the cluster there. Then add the other node using "add a node to cluster"? Since the two will be available simultaneously, I assume I can't use my existing server name as the cluster SQL name, correct?
Basically, I would like to be able to leave the application servers that point to the existing SQL instance alone if possible. I have some thoughts on taking a short outage to do the secondary server which would allow this, but it's not clean. Any guidance would be appreciated. Thanks!
January 12, 2012 at 2:17 pm
garthwaimr27 (1/12/2012)
1. Just run the cluster setup on the existing server? Can I keep my existing server\instance name if I do this?
No, it doesn't work like that.
garthwaimr27 (1/12/2012)
2. Run setup on the secondary node, create the cluster there. Then add the other node using "add a node to cluster"?
In short;
Create a new single node cluster on the new server and install a new clustered instance of SQL server.
Migrate all objects (databases, logins, etc) from stand alone to new cluster.
Reinstall OS on old node and introduce it into the cluster.
Add the node to the new clustered instance of SQL server.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 12, 2012 at 2:27 pm
I was hoping you wouldn't say that : ).
What's the purpose of reinstalling the OS on the old node? Could I just reinstall SQL?
January 13, 2012 at 1:04 am
garthwaimr27 (1/12/2012)
I was hoping you wouldn't say that : ).What's the purpose of reinstalling the OS on the old node? Could I just reinstall SQL?
Reinstall to get a clean OS, install using same configuration\drivers.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 30, 2012 at 4:09 pm
Perry Whittle (1/12/2012)
garthwaimr27 (1/12/2012)
1. Just run the cluster setup on the existing server? Can I keep my existing server\instance name if I do this?No, it doesn't work like that.
garthwaimr27 (1/12/2012)
2. Run setup on the secondary node, create the cluster there. Then add the other node using "add a node to cluster"?In short;
Create a new single node cluster on the new server and install a new clustered instance of SQL server.
Migrate all objects (databases, logins, etc) from stand alone to new cluster.
Reinstall OS on old node and introduce it into the cluster.
Add the node to the new clustered instance of SQL server.
this also might work....
Create a new single node cluster on the new server and install a new clustered instance of SQL server.
Migrate all objects (logins, etc) from stand alone to new cluster.
Mirror db's to new cluster
Install failover cluster component on origional node
add new sql instance to cluster
Add the node to the new clustered instance of SQL server.
Prakash Heda
Lead DBA Team - www.sqlfeatures.com
Video sessions on Performance Tuning and SQL 2012 HA
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply