Previous Setup MSDTC Network Access Manual Configuration Install .Net 2.0 Next

Setup MSDTC Cluster

FineBuild can configure a MSDTC Cluster. This processing is only relevant if SQL Server is being installed as a cluster.

If MSDTC is setup as a cluster, then it can coordinate transactions that span multiple resource managers (such SQL database services, SSAS, and SSIS) with clustered instances of those managers.

If SQL Server is being installed as a cluster, it is not mandatory to also setup a MSDTC cluster. However, when Windows is clustered then MSDTC will not work unless it is also clustered, and SSIS packages will be unable to connect to SQL Server if MSDTC is not working. It is therefore recommended to always setup a MSDTC cluster if Windows is clustered. When a MSDTC cluster is setup, then MSDTC on all nodes in the Windows cluster will automatically join the MSDTC cluster.

FineBuild MSDTC Cluster configuration

The MSDTC Cluster configuration relates to Process Id 2AD and is controlled by the parameters below:

Parameter Build SQL 2005 SQL 2008 SQL 2008 R2 SQL 2012
SetupDTCCluster FULL Yes Yes Yes Yes
DTCMultiInstance Yes Yes Yes Yes
SetupDTCCluster WORKSTATION Yes Yes Yes Yes
DTCMultiInstance Yes Yes Yes Yes
SetupDTCCluster CLIENT N/A N/A N/A N/A
DTCMultiInstance N/A N/A N/A N/A

For a Windows 2003 server, only one MSDTC cluster can be created. On a Windows 2008 server and above, it is considered best practice to create one MSDTC cluster for each node of the windows cluster. This allows clustered services in Windows 2008 to access a local MSDTC cluster, which is more efficient than using the cluster network to access MSDTC.

FineBuild will create one MSDTC cluster for every SQL Server instance you install on Windows 2008 or above. If you do not want FineBuild to create a MSDTC cluster for each SQL instance, then add the following parameter:
/DTCMultiInstance:No

Manual MSDTC Cluster configuration

The following steps show what you would have to do for manual MSDTC Cluster configuration. FineBuild does all of this work for you automatically.

The example below uses the disk, server and IP addresses used in Install First SQL Server Cluster Node in the Reference Manual.

The MSDTC cluster name is formed by adding the value of the /ClusDTCSuffix parameter (default value DTC) to the Windows cluster name PDGB01SQLC01.
The IP address is formed by adding the value of the /ClusDTCIdx parameter (default value 1) to the Windows cluster IP address 192.168.0.150. The subnet mask and network name are taken from the Windows cluster network details.
The disk name for the MSDTC files is taken from the value of the /LabDTC parameter (default value MSDTC).
1) Create the MSDTC cluster using the following commands:
CLUSTER "PDGB01SQLC01DTC" GROUP "PDGB01SQLC01DTC" /CREATE
CLUSTER "PDGB01SQLC01DTC" RESOURCE "PDGB01SQLC01DTC" ^
  /CREATE /GROUP:"PDGB01SQLC01DTC" /TYPE:""Distributed Transaction Coordinator"
CLUSTER "PDGB01SQLC01DTC" RESOURCE "PDGB01SQLC01DTC Network Name" ^
  /CREATE /GROUP:"PDGB01SQLC01DTC" /TYPE:"Network Name" ^
  /PRIV NAME="PDGB01SQLC01DTC" DNSNAME="PDGB01SQLC01DTC"
CLUSTER "PDGB01SQLC01DTC" RESOURCE "PDGB01SQLC01DTC IP Address" ^
  /CREATE /GROUP: "PDGB01SQLC01DTC" /TYPE:"IP Address" ^
  /PRIV ADDRESS="192.168.0.151" SUBNETMASK="255.255.255.0" NETWORK="Cluster"
CLUSTER "PDGB01SQLC01DTC" RESOURCE "PDGB01SQLC01DTC Network Name" ^
  /ADDDEP:"PDGB01SQLC01DTC IP Address"
CLUSTER "PDGB01SQLC01DTC" RESOURCE "PDGB01SQLC01DTC" ^
  /ADDDEP:"PDGB01SQLC01DTC Network Name"
CLUSTER "PDGB01SQLC01DTC" RESOURCE "MSDTC" /MOVE:"PDGB01SQLC01DTC"
CLUSTER "PDGB01SQLC01DTC" RESOURCE "PDGB01SQLC01DTC" /ADDDEP:"MSDTC" 

2) Put the MSDTC cluster online with the following comand:
 CLUSTER "PDGB01SQLC01DTC" GROUP "PDGB01SQLC01DTC" /ON 

3) Setup network access for the MSDTC cluster using the process given in Setup MSDTC Network Access, but using the MSDTC cluster name in place of the local MSDTC.

Copyright © 2012 Edward Vassie. License and Acknowledgements
Previous Setup MSDTC Network Access Top Install .Net 2.0 Next

Last edited Nov 22, 2012 at 4:07 PM by EdVassie, version 1

Comments

No comments yet.