Unsolved
This post is more than 5 years old
1 Message
0
281
May 14th, 2008 10:00
2 node active/active SQL Server 2005 / MSDTC error
We are implementing a two node active/active SQL Server 2005 failover cluster using EMC Autostart. There are two resource groups (i.e. SQL Server Failover Virutal Names) in our design with one resource group runs on node1 and another resource group runs on node2. We first ran into a problem with SQL Server replication because our SQL Server failover instances do not recognize the virtual server names. Our solution was to rename the physical server name to the virtual server name thru a PERL script. This PERL script runs as a utility service before we start SQL Server 2005 in Autostart. Once the resource group in Autostart is online, we reset the server name to its original physical server name. This workaround does solve our SQL Server replication problem.
We also have a requirement to use MSDTC in our cluster. As long as each resource group runs on separate nodes, MSDTC works OK. However, since MSDTC is not instance specific, we can¿t run both resource groups on the same node. Doing so, MSDTC will raise unrecognized server error messages because of the renaming of the server name thru the PERL scripts. There will be times where we need to run both resource groups on the same node for server maintenances. Is there a way to configure Autostart so that MSDTC can be managed by two resource groups?
We also have a requirement to use MSDTC in our cluster. As long as each resource group runs on separate nodes, MSDTC works OK. However, since MSDTC is not instance specific, we can¿t run both resource groups on the same node. Doing so, MSDTC will raise unrecognized server error messages because of the renaming of the server name thru the PERL scripts. There will be times where we need to run both resource groups on the same node for server maintenances. Is there a way to configure Autostart so that MSDTC can be managed by two resource groups?
No Events found!