Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

setting up Clustering - SQL Server 2008 R2 Expand / Collapse
Author
Message
Posted Friday, September 7, 2012 8:54 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:20 PM
Points: 764, Visits: 1,579

I have a couple of questions about installing SQL Server 2008 R2 Standard in a 2 node active\passive cluster

First, a little background. The Admin guys have not Clustered Windows yet. The hardware is due in next week so I'm just trying to get my notes together for the SQL install once the Cluster is available.

From what I'm reading, Failover clustering setup has a whole new work flow in SQL Server 2008.

These are the (very high level) steps as a see them to be:

- Run setup on the Active Node of the Cluster using the New Server Server Failover Cluster option

- Failover the resources and run set on the second (now active) Node using the Add Node to a SQL server Failover Cluster option

Is that correct?



Also, I'm not clear about how you would patch the installation and add Instances.

Would you run Service Packs and Cummulative Updates against both nodes? if so, in what order?

In order to add an Instance (I'll be adding 2 Named Instances), What setup option would you use? Would you run set up on the Active Node then failover and run it again to add an Instance?
Also about Named Instances... If I have a simple Active\Passive Cluster with one set of cluster resources and multiple instances, do I need seperate IP addresses for each Instance?

I apologize if the questions seem elementary but this is our first time with SQL Server 2008 and Clustering!

Any help or guidance would be greatly appreciated.




Post #1356032
Posted Saturday, September 8, 2012 5:53 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:01 AM
Points: 416, Visits: 1,345
To patch (MS-SQL)

You failover or move the resources to other node, let's call it B. You run the service pack or whatever on Node A. At that point, A is fully patched.

Now, you fail over to Node "A" which becomes active. And now you patch Node B.

Now both nodes are fully patched.

This was a major change from MS-SQL 2005 and MS-SQL2000, where you patch the virtual instance and the patch is being replicated over the network to other node. This caused some issues, because if network fails or something breaks, one of the nodes won't end fully patched ending in a non consistent state or different dll versions. Trust me, it was a pain when failed.
Post #1356424
Posted Saturday, September 8, 2012 5:57 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:01 AM
Points: 416, Visits: 1,345
More on the same,

Remember, Google is your friend!

SQL Server 2008 failover cluster rolling patch and service pack process
Post #1356426
Posted Saturday, September 8, 2012 7:21 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:20 PM
Points: 764, Visits: 1,579
Thanks for your help. Believe me.. I've googled this and read and googled and read.. : )

Until I can actually 'do it' it's hard to get my brain around the fact that you patch the passive node first.. or go to the passive node to add an instance. the cluster rsources are are not active on the passive node which means services are not started and the system databases not accessible.. I'm so used to having drilled into my head to backup system databases before you patch!! I guess that is not the case with 2008 in a cluster?



Post #1356432
Posted Monday, September 10, 2012 4:33 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 6,752, Visits: 14,400
Jpotucek (9/7/2012)

I have a couple of questions about installing SQL Server 2008 R2 Standard in a 2 node active\passive cluster

First, a little background. The Admin guys have not Clustered Windows yet. The hardware is due in next week so I'm just trying to get my notes together for the SQL install once the Cluster is available.

From what I'm reading, Failover clustering setup has a whole new work flow in SQL Server 2008.

These are the (very high level) steps as a see them to be:

- Run setup on the Active Node of the Cluster using the New Server Server Failover Cluster option

- Failover the resources and run set on the second (now active) Node using the Add Node to a SQL server Failover Cluster option

Is that correct?



Also, I'm not clear about how you would patch the installation and add Instances.

Would you run Service Packs and Cummulative Updates against both nodes? if so, in what order?

In order to add an Instance (I'll be adding 2 Named Instances), What setup option would you use? Would you run set up on the Active Node then failover and run it again to add an Instance?
Also about Named Instances... If I have a simple Active\Passive Cluster with one set of cluster resources and multiple instances, do I need seperate IP addresses for each Instance?

I apologize if the questions seem elementary but this is our first time with SQL Server 2008 and Clustering!

Any help or guidance would be greatly appreciated.


See my 3 part guide starting at this link to deploy and configure the Windows cluster and the clustered SQL server instance. It covers virtual but applies to physical too

See my guide at this link for details how to slipstream service packs and\or cumulative updates


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1356635
Posted Monday, September 10, 2012 6:16 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:20 PM
Points: 764, Visits: 1,579
Thank you very much for the Helpful links! I will share with the Server guys as well !!!

You wrote:
See my 3 part guide starting at this link to deploy and configure the Windows cluster and the clustered SQL server instance.

Do you have a link to Part 3? all I can find are parts 1 and 2.



Post #1356683
Posted Monday, September 10, 2012 6:34 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 6,752, Visits: 14,400
part 3

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

"Ya can't make an omelette without breaking just a few eggs"
Post #1356690
Posted Monday, September 10, 2012 8:14 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:20 PM
Points: 764, Visits: 1,579
awesome! Thank you Perry!

IS it true that you you cannot share resources, including disk resources, between instances.
You get one instance per "Service or Application"?

For a second instance, I would need a new set of Disks, a new network name, and a
new IP address?

So basically to add Named Instances after the default Instance is up and runnning in the Cluster, I would have to run BOTH the New SQL Server Failover Cluster Installation setup AND then switch over to the passive node and run the Add Node to a SQL Server Failover Cluster

Once again, I appoligize for the elementary questions, this will be alot easier once we have the DEV cluster built and can dig in. I am just trying to do some research and planning so I know how many IP addresses we need, how the SAN should be carved out, etc...



Post #1356765
Posted Monday, September 10, 2012 8:22 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 6,752, Visits: 14,400
Jpotucek (9/10/2012)
awesome! Thank you Perry!

You're welcome


Jpotucek (9/10/2012)
IS it true that you you cannot share resources, including disk resources, between instances.
You get one instance per "Service or Application"?

That's correct


Jpotucek (9/10/2012)
For a second instance, I would need a new set of Disks, a new network name, and a
new IP address?

Correct


Jpotucek (9/10/2012)
So basically to add Named Instances after the default Instance is up and runnning in the Cluster, I would have to run BOTH the New SQL Server Failover Cluster Installation setup AND then switch over to the passive node and run the Add Node to a SQL Server Failover Cluster

Yes you would


Jpotucek (9/10/2012)
Once again, I appoligize for the elementary questions, this will be alot easier once we have the DEV cluster built and can dig in. I am just trying to do some research and planning so I know how many IP addresses we need, how the SAN should be carved out, etc...

You'll need a virtual IP and networkname for the Windows cluster too

So, if you have a 2 node cluster with 2 instances of SQL Server clustered you need

3 IPs and 3 networknames


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

"Ya can't make an omelette without breaking just a few eggs"
Post #1356772
Posted Monday, September 10, 2012 8:45 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 2:20 PM
Points: 764, Visits: 1,579
Awesome stuff.. can anyone same MS Professional Services : )

So speaking specifically how the drives would need to get carved out, I already have a 2 node active passive cluster on sql server 2005 and the drive configuration looks like this:

C: Local to each node (for Biniaries) (50GB)
D: Local to each node (for misc files) (85GB)
Q: Quorum (1GB)
M: MSTSC (1GB)
F: Shared on the San (datafiles) (300GB)
G: Shared On the San (Logfiles) (300GB)
H: Shared on the San (TempDB) (50GB)
____________________________________________________________
My 2008R2 Cluster with 3 Instances, will would look like this:
Default Instance
C: Local to each node (for Biniaries) (50GB)
D: Local to each node (for misc files) (85GB)
Q: Quorum (1GB)
M: MSTSC (1GB)
F: Shared on the San (datafiles) (100GB)
G: Shared On the San (Logfiles) (100GB)
H: Shared on the San (TempDB) (50GB)

Named Instance 1
I: Shared on the San (datafiles) (100GB)
J: Shared On the San (Logfiles) (100GB)
K: Shared on the San (TempDB) (50GB)

Named Instance 2
L: Shared on the San (datafiles) (100GB)
M: Shared On the San (Logfiles) (100GB)
N: Shared on the San (TempDB) (50GB)

Named Instance 3
R: Shared on the San (datafiles) (100GB)
S: Shared On the San (Logfiles) (100GB)
T: Shared on the San (TempDB) (50GB)

Or does each install create a new Quorum Drive as well because you are actually adding a Node?



Post #1356790
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse