Changing Template and Helper Appliance Size

While creating a helper appliance template, Veeam Backup & Replication sends a command to create two VMs: one Linux-based and one Microsoft Windows-based. By default, both VMs use the Standard_D4lds_v5 size. This size requires 4 CPUs for each VM, totaling 8 CPUs in the target Microsoft Azure subscription. If your Azure subscription does not have enough available CPUs of this family, you can change the VM size.

While recovering and migrating VMs to Microsoft Azure, Veeam Backup & Replication deploys a helper appliance for each recovered VM. The helper appliance also uses the Standard_D4lds_v5 size by default. If your subscription lacks available CPUs of this family, you can change the helper appliance size.

Considerations and Limitations

Consider the following:

• You must apply the VM size change before you start Instant Restore to Microsoft Azure.
• Use VM sizes with at least 4 CPUs and 8 GB RAM.
• It is recommended to select Azure VM sizes that provide temporary disks. For more information, see the Temporary disk and Azure VM sizes with no local temporary disk sections in Microsoft Docs.
• B-family (burstable) VM sizes are not recommended.
• Azure VM sizes that support only NVMe storage controllers are not supported yet. For more information on such VM sizes, see Microsoft Docs.
• No reboot or service restart is required.

Changing VM Size Used for Helper Appliance Template Creation

To change the VM size

1. Open the /etc/veeam/veeam_backup_and_replication.conf configuration file as a root user.
2. Set the AzureApplianceTemplate_DefaultVmSize variable to the required VM size. For example:
   AzureApplianceTemplate_DefaultVmSize = Standard_F4s_v2

Changing Helper Appliance Size

To change the VM size:

1. Open the /etc/veeam/veeam_backup_and_replication.conf configuration file as a root user.
2. Set the AzureIr_Start_Appliance_DefaultVmSize variable to the required VM size. For example:
   AzureIr_Start_Appliance_DefaultVmSize = Standard_F4s_v2