Windows failover cluster migration to Azure files

Question

Hi all,
What do you think will be the easiest in terms of planning and effort way to migrate dozens of file shares from WSFC to Azure. Ideally we want to keep the servername\sharename.
I can think of Storage Migration Service, but how do I keep the share paths in this case?

Edit: The goal is to migrate out of datacenter to the cloud completely.

Answer 1

@Vadym Rybitskyy Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.

• What about file sync?

You can use the same share names on-prem. File sync will just extend their Fileshare to cloud sort of hybrid, although this will depend on your environment.

Note: servername\sharename on cloud - you can have same sharename but servername cannot be guaranteed because that's the storage account name

Windows Server Failover Clustering is supported by Azure File Sync for the "File Server for general use" deployment option. Failover Clustering is not supported on "Scale-Out File Server for application data" (SOFS) or on Clustered Shared Volumes (CSVs).

The Azure File Sync agent must be installed on every node in a Failover Cluster for sync to work correctly.

Additional information: Creating a traditional Windows Server Failover Cluster in Azure

Please let us know if you have any further queries. I’m happy to assist you further.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.