Veeam Backup and Replication support for Microsoft Azure Files

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 Unstructured Data Backup (formerly called NAS Backup). Standard requirements around connections and port usage apply.
3. Determine if you wish to define a secondary target or store data for archival purposes.
   • A 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.
4. 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.