Azure File Sync

 

Azure File Sync:

                                Azure File Sync enables centralizing your organization's file shares in Azure Files. We can use File sync to migrate the on-premises data to Azure File shares. It's a 2 way synchronization.

There are 4 main benefits of using Azure File Sync.

1.Cloud Tiering

                Least accessed data can be moved to cloud.

2. Multi-site access and synchronization

                Azure File Sync is ideal for distributed access scenarios. For each of your offices, you can provision a local Windows Server as part of your Azure File Sync deployment. Changes made to a server in one office automatically sync to the servers in all other offices.

                        1 Cloud Endpoint to Many Server Endpoint

3. Business Continuity and Disaster recovery

                In the event of DR, instead of restoring from backup, a new file sync agent server can be deployed and sync with the File share in Azure.

4. Cloud -Side Backup

                Cloud backup can be taken for the Azure file shares.

 

Implementation:

1. Create a File Share

2. Create a File/Storage Sync Service

3. Deploy an agent in the On-premise

4.  Create a Sync group with Cloud endpoint and Server endpoints

1.       Create a file share on the storage account

 



 

2.       Create Storage Sync Service in Azure



 

3.       Deploy an Azure File Sync Agent on the On-premise server



 

 

4.       Create a Sync group with Cloud endpoint and Server endpoints

5.       Server endpoint must be containing the drive path from on-premise sever


Once Server endpoint is created, server will be registered. You can see this under 'Registered Server'

On-premise Server:



File Shares after SYNC:



Cloud Tiering:

                                Cloud tiering transforms your server endpoint into a cache for your files in Azure file share, decreasing the amount of local storage required while keeping the performance of an on-premises file server. It creates Heat Map to monitor the status of the file.



Tiering will happen based on 2 policies.

1.       Based on free space on the local volume the server endpoint is located. This policy always ensure that the server endpoint is having 20% free space anytime.

2.       Based on date policy. Any files that weren’t accessed for more than 60 days will get tiered down to cloud.


Building a modern file share using Azure Storage to replace an on-premises file share solution (jussiroine.com)

Comments

Popular posts from this blog

Entra Connect/Azure AD Connect V2

On-premise Database to Azure Database using DMA (Data Migration Assistant)

Azure Active Directory Domain Services (AADDS)