none
Rebuild hardware running 2012 R2 File Share Cluster to run 2016 RRS feed

  • Question

  • Hello, I would like to rebuild current hardware running a Windows Server 2012 R2 Failover Cluster (2-node) to run same feature in Windows Server 2016.  Would this be an acceptable approach:

    1. Shut down one cluster node.
    2. Evict node from cluster
    3. Rebuild evicted node to 2016 Server.
    4. Install required roles for File Services and Failover Cluster
    5. Promote node into a new cluster
    6. On second cluster node, destroy cluster
    7. Create a new cluster on 2016 node 1.  Possibly use same name*
    8. Mount storage and set shares back up.
    9. Rebuild node 2 and join to cluster.

    So, I will be using the same back-end storage for this and rebuild the same hosts, so the storage part is easy (i think).

    Please fill in any gaps that I'm missing.  If attempting to use the same name is a big deal, I can deal with that (i think)


    Syst3m32 https://www.sysadminsoup.com

    Monday, April 8, 2019 5:06 PM

All replies

  • What roles are you running inside your Failover Cluster? If you are running Hyper-V or Scale-out File Server you can use Cluster OS Rolling Upgrade feature. 

    https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Monday, April 8, 2019 5:43 PM
  • Hi,

    Thanks for posting in our forum!

    Looking at your description, can I understand that you want to upgrade your 2012 cluster to 2016? If I misunderstand it, please let me know.

    Your step is to exit the node from the node, then destroy the cluster, then upgrade the node and rebuild the cluster. So why don't you upgrade the cluster from 12R2 to 16 directly? Instead of exiting the node, we can upgrade it directly.

    For more information, please visit:

    Step by Step Guide: Rolling Cluster Upgrade from 2012 r2 to 2016:

    https://pixelrobots.co.uk/2017/06/step-by-step-guide-rolling-cluster-upgrade-from-2012-r2-to-2016/

    Cluster operating system rolling upgrade:

    https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade

    Upgrade 2012 R2 Cluster to 2016 using Cluster OS Rolling Upgrade:

    https://www.altaro.com/hyper-v/upgrade-2012-r2-cluster-2016-using-cluster-os-rolling-upgrade/

    Hope this information can help you, if you have any question, please feel free to let me know.

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, April 9, 2019 6:28 AM
    Moderator
  • I agree with Daniel that you should perform a rolling upgrade of the cluster.

    Your first step is to ensure that all components of your cluster are supported by Windows Server 2016 (windowsservercatalog.com).  Though the hardware you are using may run Windows Server 2016, if the vendor has not certified it for 2016, you would have an unsupported configuration.  

    Then at what you list as step 5. Promote node into a new cluster, you would instead join the newly created 2016 node into the existing cluster.  Once the 2016 node is joined to the existing cluster, you would repeat the exact same steps on the other node of the cluster.


    tim

    Tuesday, April 9, 2019 1:20 PM
  • Hi,
    If this question has any update or is this issue solved? Also, for the question, is there any other assistance we could provide?

    Best Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 11, 2019 1:31 AM
    Moderator
  • Hi,
    This is Daniel and wish you all the best!
    Since you have not responded for a long time, we will temporarily archive this post.
    If the reply helped you, please remember to mark it as an answer.
    If you have any questions, please do not hesitate to contact us.
    Best Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 15, 2019 2:49 AM
    Moderator