SCCM 2012 SP1 - Can CAS and primary share same SQL cluster with different instance

[Ajay]

Hi,

 

We are designing a SCCM infrastructure, as part of that want to know if CAS and Primary servers database can be on same SQL cluster server(separate instance for each site). While researching I found couple of post:

 

http://technet.microsoft.com/en-us/library/gg712282.aspx

• You cannot use a clustered SQL Server for the site database server when the site database is co-located with the site server

http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLSrvReq

 

Configuration Manager with no service pack does not support the site database on any version of a SQL Server 2008 R2 cluster. This includes any service pack version or cumulative update version of SQL Server 2008 R2. With Configuration Manager SP1, the site database is supported on a SQL Server 2008 R2 cluster

 

Have some one used single cluster for multiple sites before? and if so what are the limitation and precautionary to be taken care of?

 

Thank you..

[krisjturn]

Yes but I wouldn't recomend it. Nothing against it but having all your eggs in one basket comes to mine. Yes I know it is a cluster etc.. Nothing wrong with it and it should work.

 

 

As for this:

"You cannot use a clustered SQL Server for the site database server when the site database is co-located with the site server"

 

This is true if you will have the SQL server and the site server on the same physical/virtual machine. The SMS provider can't be load balanced. Don't take my direct word but from past research I believe that is the case.

 

"Configuration Manager with no service pack does not support the site database on any version of a SQL Server 2008 R2 cluster. This includes any service pack version or cumulative update version of SQL Server 2008 R2. With Configuration Manager SP1, the site database is supported on a SQL Server 2008 R2 cluster"

 

Please install SP1 even though there are bugs "known features" that microsoft will fix in R2 coming up soon SP1 has a lot more benifits over RTM.

 

I have been in different environments where we have our databases on clustered dedicated sql servers to the location I am at now where everything is on a single box. Sorry that I can't answer your question directly. I have never used the same SQL cluster for both the CAS and a Primary server. However, like I mentioned above if the cluster is powerful enough you shouldn't have a problem with it if it. Just take note, you will want that CAS and that Primary server to be within that same network and not across the a wire at another physical location.

[Ajay]

Thanks Kris..

 

"You cannot use a clustered SQL Server for the site database server when the site database is co-located with the site server"

This is true if you will have the SQL server and the site server on the same physical/virtual machine. The SMS provider can't be load balanced. Don't take my direct word but from past research I believe that is the case.

Even I was confused with this microsoft saying.. not sure who can go and think to that extent of having site server in clustered node.. thanks for your clarification and confirmation on this..

Regarding the second one.. we have no confusion in implementing SP1 but want to know if clustering in SP1 really works.. Already burnt hands by testing pull DP which is not actually working for us and saw many facing same issue with it. Also I'm not specialized in clustering.. hence want to get expert opinion on this...

Thanks you very much for your response..

[Kevin Dai]

 

 

Have some one used single cluster for multiple sites before? and if so what are the limitation and precautionary to be taken care of?

 

 

 

The following words will have you totally make clear your question.

Although, 2 years passed.

 

 

Each System Center 2012 Configuration Manager site database can be installed on either the default instance or a named instance of a SQL Serverinstallation. The SQL Server instance can be co-located with the site system server, or on a remote computer. In a hierarchy with multiple sites, each site can use a different version of SQL Server to host the site database so long as that version of SQL Server is supported by the version of Configuration Manager that you use. For example, if your hierarchy runs Configuration Manager SP1, it is supported to use SQL Server 2008 R2 with SP1 and cumulative update 6 at the central administration site, and to use SQL Server 2012 with no service pack and cumulative update 2 at a child primary site, or vice versa.

When you use a remote SQL Server, the instance of SQL Server used to host the site database can also be configured as a SQL Server failover cluster in a single instance cluster, or a multiple instance configuration. SQL Server cluster configurations that have multiple active nodes are supported for hosting the site database. The site database site system role is the only System Center 2012 Configuration Manager site system role supported on an instance of a Windows Server cluster. If you use a SQL Server cluster for the site database, you must add the computer account of the site server to the Local Administrators group of each Windows Server cluster node computer.

Note

A SQL Server cluster in a Network Load Balancing (NLB) cluster configuration is not supported. Additionally, SQL Server database mirroring technology and peer-to-peer replication are not supported.

 

 

 

For communication to the SQL Server database engine, and for intersite replication, you can use the default SQL Server port configurations or specify custom ports:

• Intersite communications use the SQL Server Service Broker, which by default uses port TCP 4022.

• Intrasite communication between the SQL Server database engine and various Configuration Manager site system roles by default use port TCP 1433. The following site system roles communicate directly with the SQL Server database:

  • Management point

  • SMS Provider computer

  • Reporting Services point

  • Site server

When a SQL Server hosts a database from more than one site, each database must use a separate instance of SQL Server, and each instance must be configured to use a unique set of ports.

Warning

Configuration Manager does not support dynamic ports. Because SQL Server named instances by default use dynamic ports for connections to the database engine, when you use a named instance, you must manually configure the static port that you want to use for intrasite communication

 

 

 

With the introduction of the Central Administration site (CAS) option, customers will likely implement the CAS and first local Primary site in the same datacenter. The typical thought is the CAS will be used for central administration, while the Primary site will service clients at each location. Since the CAS and local primary site likely are in the same data center, it might additionally be a desire to combine both site server databases on the same SQL server.

 

This may yield undesirable performance depending on many factors; but is a supported configuration. Below are some pointers to assist you through setting up this model:

o Make sure you’re using a supported version of SQL server.

o Use a domain account to run as the SQL service.

o Ensure the SQL service account has been configured with the appropriate SPN(s).

o While installing each of the two instances, ensure they use completely different database directory locations. (this is key because of the MS_AgentSigningCertificate file)

o Ensure the “SQL Server Browser” service is installed, set to “Automatic” startup and is running. This will be a requirement for the site servers to find their respective SQL instance.

o After each instance is installed, disable dynamic ports and define a specific port for each instance using the SQL Server Configuration Manager.

 

 

1. Expand “SQL Server Network Configuration”

2. Select the “Protocols for x” (x=instance name)

3. Double-click “TCP/IP”

4. Select the “IP Addresses” tab

5. For every “TCP Dynamic Ports” field, clear all data (field should be completely empty)

6. For every “TCP Port” field, enter “5033”

7. Repeat steps 1-6 for your second SQL instance, this time using port 5034

You should now be ready to install your CAS and first primary ConfigMgr 2012 sites using their respective and dedicated SQL instances on the same SQL server/cluster.