Azure Files Backup provides cloud-based backup for data stored in Azure Files shares. The solution is designed to work natively with Azure Backup, which is the main backup service offered by Azure. To set this up, you need to integrate Azure File Sync with Azure Backup, and then you can securely centralize all your file share data and any backups you create. Once you set this up, you can configure backup and disaster recovery measures to ensure the protection of your data during disasters.
In this article, you will learn:
Azure Files lets you create point-in-time snapshots of file shares. You can use snapshots to recover data after accidental deletion, unwanted changes, or data corruption. Another use is for periodic backups of a file share, for disaster recovery purposes or to meet your auditing or compliance obligations.
Azure Files snapshots provide the following capabilities:
Take into account following snapshot limitations:
Here are some architecture processes that work behind the scenes once backup is enabled:
Here are a few steps to guide you through the initial configuration:
1. Go to the Azure portal—log into your account.
2. Create a Recovery Services vault—provides you with a storage entity you can use to view all of your backups across several workloads.
3. Choose a storage account—after creating the vault, Azure Backup looks for all storage repositories in your account. Choose the storage account containing your file shares. Once you choose an account, Azure Backup displays the sets of file shares in your account and stores their names in a management-layer catalog
4. Configure a backup policy—schedules and retains backups based on your requirements.
5. Select the file shares—you want to back up. Azure Backup service will then register the schedules you have set up into the control plane.
After you set up the policy and enable it, the Azure Backup scheduler starts triggering backups according to the pre-configured timeframes.
NetApp Cloud Volumes ONTAP, the leading enterprise-grade storage management solution, delivers secure, proven storage management services on AWS, Azure, and Google Cloud. Cloud Volumes ONTAP capacity can scale into the petabytes, and it supports various use cases such as file services, databases, DevOps, or any other enterprise workload, with a strong set of features including high availability, data protection, storage efficiencies, Kubernetes integration, and more.
In particular, Cloud Volumes ONTAP provides centralized file storage management, serving NAS, including NFS, SMB / CIFS as well as iSCSI and S3, and multiprotocol access.
Learn more about how Cloud Volumes ONTAP helps to address the challenges of file sharing in these Cloud Volumes ONTAP Customer Case Studies.
Azure NetApp Files is another file storage managed service alternative from Microsoft Azure built on NetApp technology, giving you enterprise file share capabilities that can support even your core business applications.
Azure Backup lets you create isolated and independent backups. You can use these backups to protect your data against accidental destruction. Azure stores your backups in Recovery Services vaults that come with a built-in management of recovery points. Azure Backup is relatively simple to configure and scale. The system optimizes backups, and lets you easily restore backups as needed.
Azure Backup is offered at fixed prices, calculated according to the number of protected instances. In addition to these costs, there are other factors that impact the overall cost. Storage and bandwidth costs for your backups are charged separately from the fixed instance pricing. When planning your backup strategy, remember to choose the storage space and bandwidth that suits your budget.
Azure File Storage lets you access and store data in file formats that work both in the cloud and on-premises. You can set up access to Azure Files shares using the SMB protocol or a REST API. You can also use the Azure File Sync service. Once you set up this integration, you can share files between the Azure cloud and on-premise Windows Server instances.