Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Adding a second instance to a cluster


Adding a second instance to a cluster

Author
Message
matt.gyton
matt.gyton
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 295
Hi there,

I currently have a single instance cluster with 2 nodes and I have a requirement to add a second instance to it (both instances will be live on the same node, so one node will still be 'passive'). I just have the following questions:

1. Can I specify the same network name for the second instance during setup? So the instances would be as follows...cluster1\inst1, cluster1\inst2.
2. Does installing a second instance require any additional IP addresses?
3. Can the second instance share the same SAN disks as the first, so all the MDF and LDF files are in the same location?

Thanks,

Matt
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8845 Visits: 16579
matt.gyton (8/10/2012)
1. Can I specify the same network name for the second instance during setup? So the instances would be as follows...cluster1\inst1, cluster1\inst2.

No, networknames, like computernames, must be unique in the Windows domain.


matt.gyton (8/10/2012)
2. Does installing a second instance require any additional IP addresses?

Yes, IP address, network name, storage, etc


matt.gyton (8/10/2012)
3. Can the second instance share the same SAN disks as the first, so all the MDF and LDF files are in the same location?

No, you need separate storage resources for each new instance.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
matt.gyton
matt.gyton
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 295
That's great, thanks Perry.
matt.gyton
matt.gyton
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 295
Actually just one more question if I may....

Would we only need new disks for the Data and Logs for the new instance? (and just keep the single instances of Quorum and MSDTC for the whole cluster)

So we would go from this:

Q: - Quorum
M: - MSDTC
D: - Data
L: - Logs

...to this:

Q: - Quorum
M: - MSDTC
D: - Instance1 Data
L: - Instance1 Logs
K: - Instance2 Data
J: - Instance2 Logs

(...we won't worry where the tempdb is for now! ;-))
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8845 Visits: 16579
you only need 1 quorum disk resource, period. There are other quorum models available and depending on the number of nodes and geographical location, you could probably do away with quorum disk altogether

With regards to MSDTC, yes you could possibly get away with one resource for both instances especially as they're all going to be active on the same node ;-)

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
matt.gyton
matt.gyton
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 295
Excellent - Thanks again.
matt.gyton
matt.gyton
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 295
Sorry to revive this thread but I have encountered one final dilemma during the SQL Install...!

When installing the second instance to the existing cluster, in addition to giving the new instance it's own Network name, does it have to have a different instance name too or can I have 2 default instances with different network names?

So could I have the following both hosted on the same cluster:

cluster1/MSSQLSERVER
cluster2/MSSQLSERVER

Or would it have to be something like:

cluster1/MSSQLSERVER
cluster2/instance2

The first default instance is already on there.

Thanks
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8845 Visits: 16579
No, you may have only 1 default instance. The rest would be named

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
matt.gyton
matt.gyton
SSC Journeyman
SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)SSC Journeyman (88 reputation)

Group: General Forum Members
Points: 88 Visits: 295
Thanks again Perry....just wondered if I might be able to get away with it as they had different network names! ;-)

Cheers
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8845 Visits: 16579
No, the network names have nothing to do with it, it's the instance name that is the restriction. Each machine can only have 1 default instance clustered or not.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search