Storage Migration Service for Clustered FileServer

Wesley Baeyens 21 Reputation points

Hey guys,

i am running atm 2 node fileserver cluster. i created my orchestration server with failover installed. I have 2 new vms ready, domain joined. i succesfully started a inventory for the old fileserver, coming to the new part of selecting the destination servers. I am just wondering, do i need to build the new cluster first on the 2 new vms, or will the migration service handle this when adjusting settings? i just need to know a step-by-step guide to completed our migration. (will the migration service, also name the clusterroles with the same name?)

and tx already

Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
411 questions
0 comments No comments
{count} votes

Accepted answer
  1. Mico Mi 1,921 Reputation points

    Please follow the steps in:
    Windows Server File Migration Service Guide
    Use Storage Migration Service to migrate a server

    In Storage Migration Service frequently asked questions (FAQ)

    Are clusters supported as sources or destinations?
    The Storage Migration Service supports migrating from and to clusters after installation of cumulative update KB4513534 or subsequent updates. This includes migrating from a source cluster to a destination cluster as well as migrating from a standalone source server to a destination cluster for device consolidation purposes. You cannot, however, migrate a cluster to a standalone server.

    Storage Migration Service August Update

    With support for Windows Server failover clusters, you can migrate existing clusters to new clusters. The new cluster must exist with a File Server resource installed in either File Server for General Use or Scale-out File Server mode, and migration from a legacy clustered file server to SOFS is supported.

    Once the data has been copied to your destination server you have the option to migrate the file server itself. This allows users to continue to access their files on the new hardware with minimal disruption. After completing the migration, select the Cut Over to the New Servers option and enter your Active Directory credentials. You can rename the server, but most likely you will keep the same file server name. If you do not copy the identity, the users will keep access files on the source server.

    Thanks for your time!
    Best Regards,
    Mico Mi

    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

1 additional answer

Sort by: Most helpful
  1. Wesley Baeyens 21 Reputation points

    Tx for your answer, I did now a test, and was able to start copying over.
    I have another question if possible :

    • we have dedup enabled on our old fileserver, the new fileserver is located on brand new storage with dedup on itself. so should I enable on the new fileserver the dedup, or just let it of and let the storage handle it? any ideas on this?

    -when i did the inventory last week, i see the job now in my admin center list, and i can start the copy whenever i want, but if in this inventory isnt the latest files, do i need to start a new inventory again or how will this handle newly added not inventoried files?


    0 comments No comments