2 node 2008R2 cluster with SQL 2008R2 instance migration to multi-site Server 2016 cluster

YaroC 311 Reputation points

Due to both OS and hardware being out of support I'm looking for a way of creating a new multi site cluster based on Windows server 2016 and migrating the MSSQL database to that new cluster. The data is to stay as is on a FC SAN but would also need to be replicated to an additional SAN for the second site. Idea is to fail over to the second site in case the first one becomes unavailable which occurred in the past. LUNs are attached via Veritas Storage Foundations. Has anyone gone through such process and can share some steps and possible issues?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,608 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
953 questions
{count} votes

Accepted answer
  1. Xiaowei He 9,866 Reputation points


    Based on my understanding, you would like to migrate Server 2008R2 SQL cluster to Server 2016 Cluster, then configure Server 2016 SQL cluster to be multi-site Cluster for DR.

    If so, I would suggest you first follow the steps below to migrate Server 2008R2 SQL cluster to Server 2016 Cluster:

    You may check scenario 2 in the below link:


    And if you would like to use the same SAN storage for the new Cluster, we can just point the Storage to the Server 2016 cluster after migration.

    After migrating to the Server 2016 Cluster, we may follow the steps below to deploy multi-site SQL cluster:


    Thanks for your time!
    Best Regards,


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. YaroC 311 Reputation points

    At the moments this is in planning phase. Looking for a best way to be able to have an option to fail over to DR if main site is down without impacting performance of the main site which is connected to a very fast SAN while operational and the DR site would be in different city. This is with assumption that there may be some inconsistency if DR has to be brought up as don't expect real time replication between the two sites. It's also acceptable to have performance degradation but it's better to have something than nothing. I'll still have to discuss with DBAs what maximum time frame would be acceptable to be missed in case of disaster.

  2. YaroC 311 Reputation points

    There is no SAN replication set currently. Both the existing cluster and the SAN storage are at the same location pretty much next to each other. Some form of replication is being considered assuming whatever comes won't impact the performance of existing setup where the server hardware will be replaced and and database migrated to it.

    0 comments No comments

  3. Xiaowei He 9,866 Reputation points


    What's more, I'd like to check if you just want to migrate SQL cluster from Windows 2008r2 to Windows 2016 server, if yes, follow the above steps.

    If you also want to upgrade SQL 2008R2 to SQL 2016, then as far as I know, we need to use new storage, and we are unable to restore SQL 2008R2 system database to SQL 2016.

    Best Regards,

    0 comments No comments

  4. YaroC 311 Reputation points

    Oh that's a bummer. Thank's for the links. I'll be reviewing as soon as I can but you got me worried in your last comment. What do you mean a "new storage" will have to by used? Why? Any like specific type? What if it wasn't SQL 2016 but some earlier version?