Synchronize Files Across Servers with Azure File Sync

Lab Steps

lock
Logging in to the Microsoft Azure Portal
lock
Creating a Storage Sync Service
lock
Creating a File Share in Azure Files
lock
Creating a Sync Group
lock
Connecting to the Virtual Machine (RDP)
lock
Installing the File Sync Agent and Registering the Windows VM
lock
Creating a Server Endpoint in the Sync Group
lock
Testing the Sync Group with One Server Endpoint
lock
Testing the Sync Group with Two Server Endpoints

The hands-on lab is part of this learning path

AZ-104 Exam Preparation: Microsoft Azure Administrator
21
7
17
1

Ready for the real environment experience?

DifficultyIntermediate
Time Limit1h 50m
Students1999
Ratings
4.2/5
starstarstarstarstar-border

Description

Azure File Sync centralizes your company's file shares in Azure Files. Azure File Sync transforms Windows Servers running on-premises or in the cloud into a quick cache of your Azure file share. When you choose Azure File Sync, you do not need to sacrifice the flexibility, performance, or compatibility of an on-premises file server. Any protocol supported by Windows Server, including SMB, NFS, and FTPS, can be used to access the data locally.

In this Lab, you will create an Azure File Sync sync topology consisting of two Windows Server 2016 VMs running in Azure. You will then try out the synchronization and cloud tiering capabilities of Azure File Sync to better understand how the service works.

Lab Objectives

Upon completion of this Lab, you will be able to:

  • Explain when to use and when not to use Azure File Sync
  • Create and test a mutli-server sync group in Azure File Sync
  • Understand cloud tiering and how it can improve file sharing performance and save costs
  • Understand the fast disaster recovery feature of Azure File Sync

Lab Prerequisites

You should be familiar with:

  • Basic Azure compute and storage services, particularly VMs and storage accounts

The following Cloud Academy content can be used to meet the Lab's prerequisites:

Updates

May 14th, 2021 - Resolved an issue causing the lab provisioning to fail in some cases

March 8th, 2021 - Added to the prior warning about the storage account not being visible in the sync group wizard. Microsoft confirmed it can take up to 15 minutes to appear.

March 1st, 2021 - Added workaround instructions to sign out and sign back into the Azure Portal when the sync group fails to detect any storage accounts are available

February 25th, 2021 - Added a warning to let lab setup complete before creating the sync group to avoid issues where no storage accounts are listed, and extended the time limit

February 11th, 2021 - Added troubleshooting tips in case the Storage Sync Service deployment fails, and clarified some instructions.

July 8th, 2020 - Updated the screenshots to match the new Azure UI

May 5th, 2020 - Added a validation check function to check the work done in the lab

January 14th, 2020 - Updated lab startup resources to avoid unsupported regions

November 15th, 2019 - Changed lab region to South Central US to avoid an issue that prevented completion of the lab in West US

June 26th, 2019 - Updated instructions for creating the Storage Sync Service to match the latest Portal experience

May 7th, 2019 - Added instructions to workaround an Azure bug that causes the create cloud endpoint permission check to fail despite the student user having the required permissions

Environment before
PREVIEW
arrow_forward
Environment after
PREVIEW
About the Author
Students100716
Labs175
Courses9
Learning paths26

Logan has been involved in software development and research since 2007 and has been in the cloud since 2012. He is an AWS Certified DevOps Engineer - Professional, AWS Certified Solutions Architect - Professional, Microsoft Certified Azure Solutions Architect Expert, MCSE: Cloud Platform and Infrastructure, Google Cloud Certified Associate Cloud Engineer, Certified Kubernetes Security Specialist (CKS), Certified Kubernetes Administrator (CKA), Certified Kubernetes Application Developer (CKAD), and Certified OpenStack Administrator (COA). He earned his Ph.D. studying design automation and enjoys all things tech.