Restoring Files with Azure File Sync
In this post, I will show you how to restore files that were synchronized to the cloud, using Azure File Sync, and backups up using Azure Backup.
Note that this post is based on the preview release of Azure Backup support for Azure Files.
In my lab, a file server is synchronizing three shares (Accounting, Marketing and Sales) to the cloud using Azure File Sync. Each share is in its own sync group and is synchronizing to an Azure Files share in a general purpose storage account. Each Azure Files share is named after the synchronized folder on the file server (accounting, marketing and sales).
I have already deployed Azure Backup to protect the files and the backups are stored as snapshots with the Azure Files share in the storage account.
Restoring a Share
I have created a scenario where all of the files in the Accounting share were deleted on the file server, and this damage was synchronized to the share in Azure Files. This could also have been a ransom-ware attack. Now I will show how to restore the entire share in the storage account.
You will start the restore process in the Manage Backups blade which you can reach by:
- Navigating to the share in the storage account > Files and clicking Manage Backups.
- Browsing to Backup Items in the recovery services vault that is managing the backups, and opening the share in question under Azure Storage (Azure Files).
- Restore to the original location or a new location
- Choose how to handle conflicts: Overwrite Existing or Skip
In my case, I restored to the original location and chose to overwrite any existing files (as if I was hit by ransom-ware). I clicked OK and then confirmed the task by clicking Restore. A restore job began and the files were restored from the snapshot to the original location in the share. You can monitor the restore progress in Backup Jobs in the recovery services vault.
Restoring a File
You can also restore one or a subset of files from a backup. In this example, I am going to restore a file from the Accounting share to a different share in the same storage account – it could be any existing storage account in the same region.
Once again, I opened Manage Backups for the share, but this time I click File Recovery. I chose a restore point to recover from, and then the Select Restore Location Blade appeared, which allows you to specify the Recovery Location, which can be either the original share or another share in the same or another storage account. I chose Alternative Location, and then entered:
- Storage Account: I selected the same storage account, but I could have selected another one.
- Select File Share: Choose a share that already exists in the storage account.
- Folder Name: You can leave this empty to restore the file to root (/) or enter a folder to restore the file into.
- In Case Of Conflicts: Overwrite the existing copy or create a new copy of the file.
The file, which was 6.83 MiB in size, was restored to the new share in 83 seconds, and appeared on the file server soon after.
More in Microsoft Azure
Microsoft Now Lets IT Admins Review & Remove Inactive Azure AD Users
May 27, 2022 | Rabia Noureen
Build 2022: Microsoft's Intelligent Data Platform Combines Data and Analytics
May 25, 2022 | Rabia Noureen
Microsoft Revises Restrictive Cloud Licensing Policies to Avoid EU Antitrust Probe
May 19, 2022 | Rabia Noureen
Microsoft's Azure AD Conditional Access Service Can Now Require Reauthentication
May 13, 2022 | Rabia Noureen
Microsoft Addresses Cross-Tenant Database Vulnerability in Azure PostgreSQL
Apr 29, 2022 | Rabia Noureen
Microsoft Simplifies IT Monitoring with New Azure Managed Grafana Service
Apr 19, 2022 | Rabia Noureen
Most popular on petri