+ Reply to Thread
Results 1 to 3 of 3

Thread: Challenge

  1. Senior Member aaronchristenson's Avatar
    Join Date
    Nov 2003
    Posts
    253

    Certifications
    MCSE Cloud Platform and Infrastructure, MCSA Windows Server 2012, MCSA SQL Server 2012/2014, MCSA Windows 10, MCITP Server Admin, Security+
    #1

    Default Challenge

    I have a challenge for anyone that wants to take it up.

    I have a physical 2 node Windows 2008 R2 cluster running SQL Server 2012. I want to upgrade the Windows to 2012 R2 and everything I have read thus far says that you cannot migrate a SQL cluster to Windows 2012 R2. I do not have the resources to build a new physical server cluster and move databases individually to the new SQL Server. This plan must some how use the same hardware and cluster node name.
    Aaron
    MCSE Cloud Platform and Infrastructure, MCSA Windows Server 2012, MCSA SQL Server 2012/2014, MCSA Windows 10, MCITP Server Admin, Security+, Virtualization with Windows Server Hyper-V and System Center Specialist
    Reply With Quote Quote  

  2. SS -->
  3. Senior Member nachodba's Avatar
    Join Date
    Sep 2014
    Location
    Fairfax, VA
    Posts
    188

    Certifications
    MCSE: Servers, Sec +, MCITP:DBA 2008, MCSA SQL Server 2012/2014
    #2
    I haven't done this yet, but I think the following would be feasible.

    1) Is breaking the cluster and installing Windows 2012 on the non active node, then setting up a cluster (single-node, new virtual network name), then detach/attach or backup & restore databases an option? Granted, there would be a lot of work with SQL configuration, users, etc., but that can be scripted out ahead of time.

    2) Is breaking the cluster and installing Windows 2012 on the non active node, then setting up a cluster (single-node, new virtual network name), then configuring an SSIS job to copy the databases an option?

    Either way, once the db's are move you could wipe the other server and install Windows 2012, then add the freshly installed server to the cluster. Once everything is tested and you can logon via SSMS, modify the DNS entry for the virtual network name to point to the new cluster. All your old applications should work as expected.
    2017 Goals - MCSA SQL 2016 Database Administration, MCSA Windows Server 2016
    Reply With Quote Quote  

  4. Senior Member aaronchristenson's Avatar
    Join Date
    Nov 2003
    Posts
    253

    Certifications
    MCSE Cloud Platform and Infrastructure, MCSA Windows Server 2012, MCSA SQL Server 2012/2014, MCSA Windows 10, MCITP Server Admin, Security+
    #3
    Either of those options might be viable. I am hoping to reduce down time as you can guess. Option 1 you gave would be the quickest. I am scheming to virtually setup a copy of my production environment to experiment. Then I can try a few options and see what works best.
    Aaron
    MCSE Cloud Platform and Infrastructure, MCSA Windows Server 2012, MCSA SQL Server 2012/2014, MCSA Windows 10, MCITP Server Admin, Security+, Virtualization with Windows Server Hyper-V and System Center Specialist
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks