How to effortless migrating a 2-node, 3TB file server cluster from Windows Server 2012 R2 to Windows Server 2019.

Migrating a 2-node, 3TB file server cluster from Windows Server 2012 R2 to Windows Server 2019 can be achieved using Storage Migration Service (SMS) or by breaking the cluster and migrating each node individually.

Migrating using Storage Migration Service (SMS)

Storage Migration Service (SMS) is a Microsoft tool that simplifies the migration of data, applications, and operating systems between Windows Server and Windows client operating systems. It provides a user-friendly interface and automates many of the tasks involved in migration.

High-level guide for migrating using SMS:

1. Prepare the source and destination environments: Ensure that both the source and destination environments meet the SMS requirements. This includes installing the SMS proxy on the source and destination servers, configuring network connectivity, and preparing the destination storage.
2. Create a migration project: Launch the SMS console and create a new migration project. Specify the source and destination servers, select the migration type (clustered file server), and choose the migration options.
3. Scan the source data: SMS will scan the source cluster to identify the data to be migrated. This includes identifying the shared folders, file permissions, and other relevant metadata.
4. Start the migration: Once the scan is complete, you can initiate the migration process. SMS will copy the data from the source cluster to the destination cluster, maintaining file permissions and other metadata.
5. Verify the migration: After the migration is complete, verify that the data has been successfully copied and that all file permissions and configurations are intact.

Migrating by breaking the cluster

Breaking the cluster and migrating each node individually is a more complex approach but can be necessary in certain situations, such as when SMS is not an option.

High-level guide for migrating by breaking the cluster:

Evacuate the node: Disconnect the node from the cluster and transfer its workload to the remaining node. This may involve temporarily increasing the storage capacity of the remaining node.

Decommission the node: Remove the node from the cluster and prepare it for migration. This includes updating the node's operating system to Windows Server 2019 and configuring it as a standalone file server.

Migrate the node: Use a suitable migration method, such as Hyper-V migration or SAN replication, to move the decommissioned node to the new datacenter.

Join the new cluster: Once the node is in the new datacenter, join it to the new Windows Server 2019 file server cluster. This may involve reconfiguring the cluster and replicating the data.

Verify the migration: After the migration is complete, verify that the node has been successfully added to the cluster and that all data and configurations are intact.

Recommendations:

• Consult with a Microsoft-certified engineer: For a complex migration, it is advisable to consult with a Microsoft-certified engineer who has expertise in file server clustering and migration. They can provide guidance and ensure that the migration is performed smoothly and efficiently.
• Test the migration plan: Before executing the migration, thoroughly test the migration plan in a staging environment. This will help identify and address any potential issues and ensure a successful migration.
• Minimize downtime: Plan the migration during a time when downtime is minimal to minimize disruption to users. Consider scheduling the migration during off-peak hours or weekends.
• Maintain backups: Throughout the migration process, maintain regular backups of the data to safeguard against data loss or corruption.

Also you can take a look at some available migration tools that can handle this case easily and quickly such as Goodsync and Gs Richcopy360 , both are GUI and If you are familiar with CLI , you can use Rclone , it is the best

Hi,

Hope you're doing well.

Here are 2 plans for you reference:

1. Use Storage Migration Service: You can use the "Storage Migration Service"the process of migrating servers, files, and shares from one Windows Server version to another.
2. Manually migrate the file server cluster: If you prefer to manually migrate your file server cluster, you can do so by following these high-level steps:

(1) Create a new Windows Server 2019 file server cluster**: You will need to create a new file server cluster in your new datacenter running Windows Server 2019.

(2) Configure the new file server cluster: You will need to configure the new file server cluster with the same configuration and permissions as your old file server cluster.

(3) Migrate the data: You can use a variety of tools to migrate the data from your old file server cluster to your new file server cluster, such as "Robocopy".

(4) Redirect clients to the new file server cluster: Once you have migrated the data, you will need to redirect your clients to the new file server cluster.

Breaking the 2012 R2 cluster and moving the nodes to another cluster is not recommended, as it can result in data loss or configuration issues. It's best to use one of the migration options outlined above.

Here is the relevant document for you reference:

Migrate a file server by using Storage Migration Service | Microsoft Learn

I hope this helps!

Best Regards,

Ian Xue

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.