Considerations and Limitations
Important |
Veeam Data Cloud for Microsoft Azure does not support Microsoft Azure features that are currently in the preview state. For more information, see Microsoft Docs. |
Before you start using Veeam Data Cloud for Microsoft Azure, keep in mind the following limitations and considerations.
Backup
Consider the following about backing up Azure resources:
- Veeam Data Cloud for Microsoft Azure only supports storage accounts that use the locally redundant storage (LRS) redundancy option.
- Veeam Data Cloud for Microsoft Azure does not support backup of Azure VMs whose source disks have the data access authentication mode enabled. For more information on the data access authentication mode, see Microsoft Docs.
- Due to Microsoft Azure limitations, Veeam Data Cloud for Microsoft Azure does not support backup of Ephemeral OS disks.
- You can create SQL backup policies to protect only Azure SQL databases running on SQL Servers and databases located on SQL Managed Instances. If you want to protect a database hosted by a SQL Server on Azure VM, create an Azure VM backup policy. Note that in this case, you will not be able to restore a single database without restoring the entire VM.
- Veeam Data Cloud for Microsoft Azure does not support backup of databases hosted by Azure Arc-enabled SQL Managed Instances and SQL Servers on Azure Arc-enabled servers.
- Veeam Data Cloud for Microsoft Azure uses BACPAC files to back up SQL databases. BACPAC export of databases with external references is not supported. If a SQL database was migrated to an Azure SQL Database Server or Azure SQL Managed Instance, make sure to clear legacy references, orphaned database users and credentials set up with authentication types not supported by Azure SQL, to avoid BACPAC export errors. To learn more about BACPAC files, see Microsoft Docs.
- Veeam Data Cloud for Microsoft Azure does not support adding of Azure SQL Server accounts using Microsoft Entra ID authentication. To add an Azure SQL Server account, you must specify credentials of a SQL Server Admin account.
- If you delete a file share from Microsoft Azure, all the snapshots of this file share will be deleted as well. To protect your snapshots from accidental deletion, you can use the file share soft delete option. For more information on the soft delete option for Azure Files, see Microsoft Docs.
- Before you create an Azure files backup policy, make sure that the Allow storage account key access option for Shared Key authorization is enabled for the storage accounts where the file shares that you plan to protect reside — otherwise, backup operations will fail. For more information on Shared Key authorization, see Microsoft Docs.
- Due to Microsoft Azure limitations, Veeam Data Cloud for Microsoft Azure does not support backup of NFS Azure file shares.
- Due to Microsoft Azure limitations, Veeam Data Cloud for Microsoft Azure does not support retention of locked snapshots. This means that Veeam Data Cloud for Microsoft Azure will not be able to remove an outdated snapshot during a retention session if the snapshot is protected from deletions and modifications using the lock feature. For more information on the lock feature, see Microsoft Docs.
Restore
Consider the following about restoring Azure resources:
- Veeam Data Cloud for Microsoft Azure does not support restore of Azure confidential VMs. For more information on Azure confidential VMs, see Microsoft Docs.
- When performing restore operations, Veeam Data Cloud for Microsoft Azure assigns Azure tags to the processed resources. If you have any Azure policies that do not allow tag assignment, the restore operations will fail. To learn more about Azure policies, see Microsoft Docs.
- Veeam Data Cloud for Microsoft Azure does not support restore of locked Azure VMs and Azure virtual disks. For more information on the lock feature, see Microsoft Docs.
Azure Disk Encryption
Backup and restore operations are supported within one Azure region only. If you choose to back up or restore your data to another region, you must first migrate to the target region all Azure key vaults, cryptographic keys and secrets used to encrypt the source Azure resources, as described in Microsoft Docs.
For more information on Azure Disk Encryption, see Microsoft Docs.