1-800-691-1991 | 9am - 8pm ET
EN

Veeam Backup and Replication support for Microsoft Azure Files

KB ID: 4011
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10
Published: 2020-09-08
Last Modified: 2021-05-11

This article provides information around Veeam® Backup and Replication™ support for Microsoft Azure Files.

To learn more about implementing Azure Files, see the Microsoft Azure Files documentation. You can protect these using Veeam's NAS Backup support.

Implementation Steps

  1. Deploy an Azure file share, using either SMB or NFS.
  2. Deploy Veeam Backup and Replication in Azure.

Ensure you size your setup to allow enough throughput and storage capacity for primary retention.

For on-premises environments you can back up shares configured with Azure File Sync instead. If you must use Veeam Backup & Replication on-premises to protect an Azure File share, place the proxy and primary repository in Azure, and ensure the appropriate connectivity exists in and out of Azure.

Learn more about the components involved in Veeam NAS Backup. Standard requirements around connections and port usage apply.

  1. Determine if you wish to define a secondary target or store data for archival purposes.
    • secondary target can be set on jobs to make duplicate copy on a different repository in a different location.
    • An archive repository on Azure Blob can be used to store data no longer covered by the primary retention policy.
  2. Add the Azure file share under Veeam Backup and Replication Inventory.
    • For the SMB share option, you will be asked to provide the UNC path of your file share and specify access credentials. Under advanced options, select ‘backup directly from the file share’. Unlike Azure File Sync, Azure Files does not support VSS integration. Learn more about accessing an Azure Files SMB share.
    • For the NFS share option, you will need to provide the path in server:/folder format. In Azure, NFS file shares can only be accessed from trusted networks, so a virtual network rule must be configured. As NFS is considered less secure you may have to change the storage account configuration to not require secure transfer. Learn more about accessing an Azure Files NFS share.

It is recommended to use an Azure Private Endpoint for off-site backup stored in another region.

Use cases

  • Backup Azure SMB and NFS file shares.
  • Store off-site backups for Azure file shares in different regions, and or on different media, such as Azure Blob. Currently Azure Files premium tier only supports locally redundant (LRS) or zone-redundant storage (ZRS), making backup a key requirement for these types of file shares.
  • Migrate from on-premises environments to Azure, and or form a hybrid cloud solution with protected workloads residing both in Azure and on-premises.

Solution components

kb4011_1_new Figure 1: Deployment within Azure
kb4011_2_new Figure 2: Azure SMB file share connected to Veeam Backup & Replication
kb4011_3_new Figure 3: Azure NFS file share connected to Veeam Backup & Replication

More Information

KB ID: 4011
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10
Published: 2020-09-08
Last Modified: 2021-05-11

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.