I am very confused with Azure File sync - please help!

Question

I am very confused with Azure File sync - please help!

Kirsten Chinnock 25

Hi everyone,

I'm hoping someone can help my poor brain out here as I really cannot grasp the concept of AZ file shares properly and I'm going bonkers!

We have file servers on-premise at the moment and we are migrating to Azure. We are not doing a full bang lift and shift so we need to find a way for on-premise files and AZ files to work together - hey presto, Azure File Sync.... marvellous!

Here's where I'm confused.... we currently have 3 file servers and each of those have many file shares on them. We use mapped drives and currently have around 12 mapped drives per person all pointing to various locations spread across each server.

eg - G:\Server1\d$\data\scans
H:\Server1\d$\data\clients
J:\Server2\e$\templates
S:\Server3\f$\clients
U:\Server1\f$\userdata

To get the files into AZ, do I need to register ALL on-premise file servers with just 1 Storage Sync service and then create different sync groups to match all of the shares that we currently have? Is that even possible or can 1 server only be registered with 1 sync service at a time? If that's the case, do I need to create 3 different sync services and then create a cloud endpoint for each data location?

I am SOOOOO confused even though I'm reading and watching videos! Please help! Thank you! :)

Accepted answer

0 additional answers

Your answer

Answer 1

Luke Murray 11,436 MVP Volunteer Moderator

Let's approach this bit by bit.

"A registered server can support multiple server endpoints. However, a sync group can only have one server endpoint per registered server at any time. Other server endpoints within the sync group must be on different registered servers.

Multiple server endpoints can exist on the same volume if their namespaces are not overlapping (for example, F:\sync1 and F:\sync2) and each endpoint synced to a unique sync group."

They can all be registered to a single Sync service.

Diagram that shows an example of a mapping table. Download the following file to experience and use the content of this image.

Have a look at the mapping table template.

I can look at standing up a demo environment, it's been a few years since I setup AFS.

I would have a sync group, for each drive (ie Data etc).

Kirsten Chinnock 25 Reputation points

2023-08-14T10:46:11.3566667+00:00

Thank you SO much Luke, I think that makes a little more sense now. Basically, install the file sync agent on every on-premise file server, register each server into the same storage sync service. Thn register each server endpoint into different sync groups and have each sync group pointing towards each drive. Then the file shares are created under each group for the different folders.....

I wish I could set up a demo environment! I have a test 365 account but the only thing I can't test with is Azure because I need to pay! :(
Kirsten Chinnock 25 Reputation points

2023-08-14T11:59:06.4066667+00:00

So, another question, do I create 1 storage account for each server or just 1 storage account for everything? I'm slowly grasping it........
Luke Murray 11,436 Reputation points MVP Volunteer Moderator

2023-08-14T19:28:14.3233333+00:00

I would create one storage account for everything, but it can be dependant on who has access to that storage account etc, so more of a business decision - but go with one to keep it simple.

Don't forget you can use Azure Recovery Vaults to backup the Azure File shares directly, so you can use Azure to restore files back to your share directly as well.
Kirsten Chinnock 25 Reputation points

2023-08-15T07:09:49.4133333+00:00

thank you so much for replying Luke, you're really helped! That article and the image really have made me understand it all and I now have 2 servers registered and 4 sync groups set up :)

Share via

I am very confused with Azure File sync - please help!

0 additional answers

Your answer