Active/Active sql cluster configuration. Virtual sql server IP addresses

  • Installing 2 sql server instances in a cluster do I need two IP of these servers in different subnets or in the same?

    Thanks in advance

  • I'm not sure I understand the question. Are you asking whether you need 2 ip addresses, one for each instance in the same or different subnets?

  • You need:

    2 IP addresses; each one for the network connection from the node to the network

    2 IP addresses; each one for the heartbeat connection between the machines

    1 IP address for the Cluster group

    1 IP address for the MSDTC group

    2 IP addresses; each one for a SQL Server instance (you have 2, so you need 2 IP's)

    So in total you need 8 IP addresses!

  • Thanks c70070540. Yes it's clear for me. It was interesting whether 2 IP addresses for SQL server instances must reside in the same subnet or not.

    After reading your suggested articles about how to configure  MS DTC on win2003 one point came into my mind. Is it enough to do the following steps for optimal MS DTC work:

    Separate resource group for MS DTC

    Configure unique IP address for MS DTC

    Configure unique network name for MS DTC

    Configure separate shared disk on shared disk array for MS DTC (Is it enough ex. 200MB?)

    On dependancies set cluster network name and disk resource?

    I'm asking because  after cluster installation I moved MS DTC to cluster group and on dependancies set quorum disk instead of separate

  • It is recommended by Microsoft to use a separate MSDTC resource. Please stick to that to avoid problems.

  • Yes I understood that therefore I think to make separate MS DTC group. The previously typed steps looks ok? And maybe you could tell me from your practice what size of shared disk do I need for MS DTC

  • Because of our SAN it had to be 1Gb. Smaller lun's are not possible. But from a Microsoft consultant I understood that 500Mb was recommended.

  • Ok thanks again. It looks like my work hours come to end. Tomorrow I'll try to reconfigure MS DTC. Friendly speaking I don't understand why MSDTC needs separate IP address, but if it want it, it will get one

    Thank you for your help. It looks like you are my personal adviser. I'm very grateful to you

  • MSDTC has to have its own IP address because it is a serverwide service not directly dependend on any SQL Server instance. Because multiple services must be able to use it, it has to have it's own networkname and ip-address.

    I had a very frustrating time myself during installing the cluster 1,5 year ago. Windows 2003 was not yet very good documented on clustering, so I had to use all there was on clustering on Windows 2000. So I ran into very much problems because there were much more differences then yet was known. So I committed myself to help anyone who needs help on this subject.

  • It looks like I have a problem with MSDTC. You said that there is a difference on setting up resources between win2000 and win2003, so I don't want to risk and follow win2000 guide.

    So, my old DTC recourse was created on the fly in the cluster group and it had dependencies of cluster network name and Q disk.

    After some readings and recommendations I decided to make MSDTC own group with it's own resources. I made MSDTC network name, MSDTC IP address, disk J, then deleted old MSDTC resource from cluster group and created the new one in MSDTC group. I set dependencies of MSDTC network name and disk J.

    When I tried to bring this group online MSDTC resource  failed. All others came online. I checked error logs and find out that MSDTC doesn't find it's log. I checked disk J and checked that it is empty and disk Q still has msdtc folder.

    So How can I fix this problem? Simple delete Q:\msdtc? What about registry and other things? I guess that simply move the log file won't solve the problem because of different dependencies between old and new DTC resource

    Have you had such problem?

  • Try the following: (of course on the node where the cluster group and msdtc group is active, all msdtc resources except for the msdtc service in the msdtc group, because that is not working )

    1. Start, run, cmd.exe
    2. msdtc -stop
    3. msdtc -resetlog
    4. msdtc -uninstall
    5. delete the msdtc log file
    6. msdtc -install
    7. msdtc -resetlog
    8. start the msdtc service via cluster administrator.

    And of course, the all famous article 301600

  • It looks like I've solved the problem but not sure that clean. I went through configure application (not create new resource) and it created msdtc folder in disk J. Now can I simply delete Q:\msdtc? What about any registries?

  • Thanks again! All went just fine

  • So what I mentioned above helped?

  • As I wrote previously I installed new msdtc resource through configure application and it helped me. But when I got your recommendations about reinstalling I followed them in order to completelly remove my  old resource.

    As our old proverb says: Without you I feel like armless.

    Thanks

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply