Windows 2000 Server and Windows Server 2003 together with SQL 2000?

Discussion in 'Clustering' started by rschatz, Apr 12, 2007.

  1. rschatz

    rschatz Guest

    I have a one node Windows 2000 Server cluster. I want to add a Windows
    Server 2003 node to it. I have added it to the node, but can not install SQL
    server 2000 to the new node. I think I would need to manually add my new
    node as a possible owner of the cluster resource. I have SQL resources, and
    an FTP resource that do not list the new node as a possible owner. If I try
    to add it, it is not in the list of available nodes. I have installed FTP on
    the new node, but obviously can't install SQL Server.
    Why?
    How can I fix this?
    P.S. I managed to get the MSDTC resource (don't know if I even really need
    that) to work by putting it into the Cluster Group. That program is a bitch
    to make work and I still haven't quite gotten it to work fully in that I
    have not been able to fully configure it as per
    http://support.microsoft.com/kb/817064/. The component services gives me
    errors, won't start, and therefore does not have the MSDTC tab in the
    properties section of "my computer".
     
    rschatz, Apr 12, 2007
    #1
    1. Advertisements

  2. Why are you running a mixed cluster like this? Hopefully you are planning
    on turning that W2K node into a W2K3 node.

    For SQL, once you get the W2K3 node joined to the cluster, you have to
    re-run SQL Setup on the W2K node, select the instance (if more than one
    instance, you have to run setup for each instance), look for the 'Advanced'
    option to maintain the virtual server and then just add the new node in.
    SQL Setup should take care of the rest.

    Chuck Timon, Jr.
    Microsoft Corporation
    Longhorn Readiness Team
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Chuck Timon [MSFT], Apr 12, 2007
    #2
    1. Advertisements

  3. I have to echo Chuck's comments....do NOT run a mixed OS cluster like this
    for long...this is like stopping in the middle of a rolling upgrade. This
    can cause all sorts of issues and problems that are difficult (if not
    impossible) to troubleshoot.

    Additionally, I'm fuzzy on your MSDTC comments. a couple of things:

    1. Yes you do need MSDTC for a SQL Cluster.
    2. Yes, it must be a clustered resource for Microsoft to support it.
    3. Yes, it should be in its own resource group, with a separate disk, IP
    Address and Network Name resource.

    Hope this helps,
    --Ryan

    --
    Ryan Sokolowski
    MVP - Windows Server - Clustering
    MCSE, CCNA, CCDA, BCFP


    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Ryan Sokolowski [MVP], Apr 12, 2007
    #3
  4. Rodney R. Fournier [MVP], Apr 12, 2007
    #4
  5. rschatz

    rschatz Guest

    Thanks for the comments. I am trying to upgrade to both servers having
    Windows 2003 without hours of downtime and having to recreate all the
    configuration.
    I did more reading and
    http://technet2.microsoft.com/Windo...1fc9-45de-bd9a-b3e2af91fd7c1033.mspx?mfr=true
    seems to say that FTP and SQL are not listed as rolling upgradeable. So,
    maybe I can't keep any nodes up and untouched while upgrading?
    I found Chuck Timon's comment a little confusing:
    "For SQL, once you get the W2K3 node joined to the cluster, you have to
    re-run SQL Setup on the W2K node, select the instance (if more than one
    instance, you have to run setup for each instance), look for the 'Advanced'
    option to maintain the virtual server and then just add the new node in.
    SQL Setup should take care of the rest."
    You say that the W2K node must have SQL re-run once W2K3 is joined to
    cluster, but then you say to go to Advanced and add the NEW node in. Well,
    maybe I'll try re-running SQL from the W2K node to see what happens. When I
    run it from the W2k3 node, the new node is in the unavailable nodes list.
    As for my MSDTC, on another Win2000 only cluster it is in the same group as
    the SQL server resources. I have also setup a Win2003 only cluster with it
    there as well; so, I was trying to put it somewhere where Windows would
    accept it only temporarily. I'm certain that I will eventually be able to
    put it in the SQL server group as I have done that before.
    Thanks Rodney, I'll try looking up those two articles: 817064 then 301600.
     
    rschatz, Apr 12, 2007
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.