Azure Files and Azure File Sync

Azure Files is a fully managed file share service in the cloud that uses the Server Message Block (SMB) protocol and Network File System (NFS) protocol. It allows you to lift and shift legacy file server applications to Azure without rewriting them. Azure file shares can be accessed from Windows, Linux, and macOS clients, either directly over the internet (using SMB 3.0 with encryption) or over Azure ExpressRoute or VPN. The service is built on Azure Blob Storage but provides a file system interface.

Azure Files supports two protocols: - SMB: Version 3.0 and later. Requires encryption for internet access. Supports Windows, macOS, and Linux (with cifs-utils). - NFS: Version 4.1. Only accessible from Linux clients. Does not support Active Directory integration or ACLs. Must be used with premium (FileStorage) accounts.

Azure File Sync is a service that syncs an Azure file share with on-premises Windows Servers. It provides cloud tiering, which keeps frequently accessed files locally and less frequently accessed files in the cloud. This enables: - Centralized backup: Azure file share snapshots protect all endpoints. - Disaster recovery: On-premises servers can be replaced by mounting the cloud share directly. - Multi-site sync: Multiple servers can sync the same share.

Azure File Sync uses a change journal (USN Journal on Windows) to track changes. It syncs changes in a hierarchical manner: 1. Initial Sync: Full upload of all files from the server endpoint to the cloud endpoint. 2. Incremental Sync: Only changed files are synced. Changes are detected via USN journal entries. 3. Conflict Resolution: If a file is changed on two endpoints simultaneously, the last writer wins. A conflicting file is saved with the server name appended.

Cloud tiering is a key feature that reduces local storage usage. It works as follows: - Policy: You set a free space policy on the volume (e.g., keep 20% free). When the volume reaches that threshold, the sync agent moves less frequently accessed files to the cloud, leaving a stub (reparse point) locally. - Recall: When a user accesses a tiered file, it is recalled from the cloud automatically. This can be immediate (if the file is in the cloud endpoint cache) or take some time. - Date Policy: Alternatively, you can set a date policy to tier files not accessed within X days.

- Azure Monitor: Metrics like FileShareQuota, FileShareSize, SyncSessionResult. - Storage Sync Service Monitoring: View sync health, per-item errors, and tiering recall rate. - Common Issues: - Sync not working: Check firewall rules (port 443), agent version, and server registration. - Tiering not happening: Verify cloud tiering policy and free space on the volume. - Recall failures: Ensure the cloud endpoint is accessible and the file is not locked.

Creating an Azure file share using Azure CLI:

az storage share create --name myshare --account-name mystorageaccount --quota 100

Mounting an SMB share on Windows:

net use Z: \\mystorageaccount.file.core.windows.net\myshare /u:Azure\mystorageaccount <storage-account-key>

On Linux:

sudo mount -t cifs //mystorageaccount.file.core.windows.net/myshare /mnt/myshare -o vers=3.0,username=mystorageaccount,password=<storage-account-key>,dir_mode=0777,file_mode=0777,sec=ntlmssp

Installing Azure File Sync agent (PowerShell):

Install-Module -Name Az -Force
Install-Module -Name Az.StorageSync -Force
Register-AzStorageSyncServer -ResourceGroupName myRG -StorageSyncServiceName mySyncService

Creating a sync group:

New-AzStorageSyncGroup -ResourceGroupName myRG -StorageSyncServiceName mySyncService -Name mySyncGroup

Adding a server endpoint:

New-AzStorageSyncServerEndpoint -ResourceGroupName myRG -StorageSyncServiceName mySyncService -SyncGroupName mySyncGroup -ServerId <serverId> -ServerLocalPath D:\MyShare -CloudTiering $true -VolumeFreeSpacePercent 20

A multinational corporation has 50 branch offices worldwide, each with its own file server. Managing backups and ensuring data consistency is a nightmare. They deploy Azure File Sync to centralize file storage in Azure Files. Each branch office gets a Windows Server with the File Sync agent. They create a single sync group per department (e.g., Finance, HR). Cloud tiering is enabled with a 20% free space policy. Frequently accessed files remain local for fast access; stale files are tiered to Azure. Backups are now handled by Azure file share snapshots taken daily. If a branch server fails, they can mount the Azure file share directly via SMB over VPN. Performance: Each server can handle up to 30 sync endpoints. The total data volume is 10 TB across all branches. Sync latency is typically under 5 minutes for most changes. The challenge is ensuring sufficient bandwidth; they use ExpressRoute for reliable connectivity.

A company runs a legacy line-of-business application that requires a Windows file share (SMB) for storing documents. They want to migrate to Azure without modifying the application. They create an Azure file share and mount it on the application server using SMB 3.0 encryption. The application sees it as a normal mapped drive. To improve performance, they use a Premium file share (FileStorage) with provisioned IOPS. They also enable soft delete to protect against accidental deletions. The migration is seamless: they copy data using AzCopy or Storage Explorer. The application continues to run without changes. The challenge is network latency; they use Azure ExpressRoute to reduce latency to under 10 ms. They also set up a private endpoint for the storage account to avoid public internet exposure.