Release Information for Veeam Backup for Microsoft Azure 7 Cumulative Patches

What's New

Security and Performance

• Overall stability and product security have been improved.
• Server-Side Request Forgery (SSRF) vulnerability has been resolved, preventing network enumeration and reducing the risk of related attacks.
   

Resolved Issues

Restore

• File-Level Recovery to the original location for VMs with unmanaged disks fails with the error:

  Object reference not set to an instance of an object.
  

• Cross-region restore fails if the restored VM has two static network interfaces assigned.

Upgrade

• The first backup policy run after upgrading creates new disk access resources instead of using the existing ones.

What's New

Security and Performance

• Overall stability and product security has been improved.
• The FLR process is enhanced to address and prevent potential local privilege escalation, ensuring greater security during operations.

Cost Optimization

• Enhancements in the usage of Azure Storage Queue service for better cost efficiency.
   

Resolved Issues

General

• Unexpected errors occur if Azure VMs have no primary network interface attached.

Backup

• Under certain circumstances, backup policies fail with the error:

  Crypto key {ID} was not found.
  

• Application-aware processing for Azure VMs that belong to a subnet with NAT gateway enabled may fail due to the missing ‘Microsoft.Network/natGateways/join/action’ permission.
• When the private deployment mode is enabled, Veeam Backup for Microsoft Azure disables the ‘Network Policy for Private Endpoints’ setting in the subnet associated with the backup appliance.
• Under certain circumstances, backup policies fail to perform weekly and monthly backups to immutable repositories.
• Backup policies fail when processing VMs with ephemeral OS disks.
  

Restore

• File-Level Recovery fails with the error:

  Requested operation requires an element of type 'String', but the target element has type 'Object'.
  

• When the resource group of the virtual network associated with the backed-up Azure VM is changed, the restore operation fails with a 500 error.

Retention

• The retention policy session fails when the repository is used to store configuration backups.

Upgrade

• If the appliance VM has certain customized settings, the upgrade process fails with the error:

  Failed to create snapshot of virtual machine.
  

• If a decimal comma is used instead of a dot for system account settings on the Veeam Backup & Replication server, the backup appliance upgrade fails with the error:

  The input string was not in the correct format.