Demoting a 2003 Domain Controller Hosting SQL Server

Discussion in 'Clustering' started by Charles, Apr 8, 2010.

  1. Charles

    Charles Guest

    We have a 2-node Windows Server 2003 cluster, with both nodes as domain
    controllers and running clustered SQL Server 2003. I realise this goes
    against all good practice, and that is partly why I am trying to do the
    following.

    We additionally have two Windows Server 2008 R2 domain member servers, which
    we wish to make domain controllers. We then wish to demote the two existing
    WS2003 DCs.

    Is there any reason why I wouldn't be able to demote the 2003 DCs whilst
    they are hosting SQL Server 2003? I can stop the instance service, but I
    wouldn't want to uninstall SQL Server unless I really had to.

    TIA

    Charles
     
    Charles, Apr 8, 2010
    #1
    1. Advertisements

  2. Charles

    John Bell Guest

    Hi Charles

    Looking at
    http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/ReadmeSQL2005.htm
    section 2.5.12 it is not recommended to either promote or demote a
    domain controller after SQL 2005 is installed.

    Alhough it is bad practice you may want to leave it as it is unless
    there is some other reason to change it. I assume there are no
    problems with these servers. If you want to upgrade the OS or SQL
    Server versions then that may be the time to do it.

    John
     
    John Bell, Apr 8, 2010
    #2
    1. Advertisements

  3. Charles

    Charles Guest

    Hi John

    Thanks for the link. It seems pretty clear that I shouldn't do what I was
    going to do. Just in the nick of time. I am going to upgrade these servers
    shortly, so that's exactly when I'll do it.

    Cheers

    Charles
     
    Charles, Apr 9, 2010
    #3
  4. Charles

    RCan Guest

    Hi Charles,

    hmm - as there will definitly some major chances in the local security /
    authentification area unsure if this will work at all but the answer would
    be here .... it depends :)
    You should create a backup before you do this and if you need to do that I
    personally would drive here like this :

    #########THIS IS NOT TESTED AND JUST MY PERSONAL OPINION :)###############
    You should make 1 of the member server's to a 3rd DC before you proceed with
    the next steps.
    1. Failover all ressources from cluster and evict node1 + reboot (+ your
    should amend temporary the zoning for all LUN's in W2K3 it is best practice
    when the cluster service is not running on the evicted node !)
    2. dcpromo (un- promote) + reboot
    3. re-join to SQL cluster + reboot
    4. failover all ressources to new node1 and evict node2 + reboot (+ again
    youl should amend temporary the zoning for all LUN's in W2K3 it is best
    practice when the cluster service is not running on the evicted node !)
    5. dcpromo (un- promote) + reboot
    6. re-join to SQL cluster + reboot
    7. test SQL instances and check your eventlogs + replication
    #####################################################################
    How to evict a node (W2K3)
    http://technet.microsoft.com/en-us/library/bb123503(EXCHG.80).aspx

    As I said never have done this before and unsure if this will work,
    therefore do your BACKUP and if possible test the sceario before !

    BUT AS JOHN STATED SQL WILL BE VERY ANGRY WHEN YOU DO THAT .... :-(

    Hope that helps

    Regards
    Ramazan
     
    RCan, Apr 9, 2010
    #4
  5. Charles

    Charles Guest

    Hi Ramazan

    An interesting suggestion, but I think I have enough fear that I won't try
    it. Thank you anyway. If someone else is more brave then I'd be interested
    in their experience.

    Charles
     
    Charles, Apr 10, 2010
    #5
  6. Charles

    nithra

    Joined:
    Oct 13, 2010
    Messages:
    6
    Likes Received:
    0
    exchange server maintenance

    Hi

    Managed Network Services-Managed Services Provider-Network Management Services-Utiliware can manage your system at your data center or in our fully redundant data center. Our 24 X 7 Network Monitoring detects network, system, and application level failures.

    exchange server maintenance
     
    nithra, Dec 8, 2010
    #6
    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.