Restore to original location. If the original VM cannot be found by moRef identifier (as is the case if it was deleted and then restored from backup), the Multi-OS File Level Recovery wizard will prompt the user to specify target VM manually instead of failing.

Replication

Failback performance improvements. Failback can now optionally use changed block tracking data to determine the changes between the original VM and replica VM state. This dramatically accelerates the failback performance due removing the need to read the entire original VM disks (“Calculating original signature” operation). For VMware hypervisor, we recommend that this option is not used if the failover event was triggered by a disaster that involved host or storage crash or dirty shutdown, as CBT data may be inconsistent in this Case.

Storage integration

Optional NFS exports creation. You can now prevent Veeam from automatically creating the required NFS export rules on the NetApp storage by clearing the “Create required NFS export rules automatically” in the New NetApp Storage wizard.

Performance improvements. The performance of Backup from Storage Snapshot with application-aware processing enabled has been noticeably improved.

VeeamZIP usability improvements. VeeamZIP menu item with the default location will not be shown until a user performs VeeamZIP for the first time, selecting the required destination during this process. After that, said menu item will appear, reflecting the previously selected location. This should prevent users from accidentally overfilling the default C:\Backup VeeamZIP location.

ExaGrid preset. Changed the default concurrent tasks number from 1 to 10 per vendor request.

Update performance. The number of concurrently updated remote components have been increased to 10 to reduce the large backup environments update time, especially with high latency networks. This value can be further increased by creating MaxConcurrentComponentUpgrades (DWORD) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server.

Streamlined updates. Installing the update no longer requires to disabling all jobs and stopping Veeam services manually. However, you still have to ensure there’s no running backup or restore jobs before installing the update.

Veeam Cloud & Service Provider Partners

Update 2 introduces Veeam Backup Remote Access functionality, scalability and reporting enhancements for Veeam Cloud Connect platform, and improved offline usage reporting. For the full list of service provider specific enhancements and bug fixes, please refer to the issue tracking topic in the private VCSP forum. If you are VCSP but don't have access, please apply to Cloud & Service Providers group using Veeam forum's User Control Panel.

This update also resolves the following common support issues:

Networkless restores for files above 10MB should no longer result in corrupted file restored.

Backup infrastructure resource scheduling algorithms have been improved to reduce job initialization delays in large infrastructures.

Shutting down or rebooting the backup server should now correctly stop all jobs.

Instant VM Recovery should now be possible for VMs for which the original host is no longer registered with Veeam.

Fixed backup metadata resync issues caused by using storage-based replication or similar means of transferring backup files between Veeam backup repositories registered in the same backup server.

Improved SureBackup performance and domain controller (DC) recoverability testing logic. As a side effect, the recoverability testing for DCs backed up without application-aware processing will always fail (which however represents typical real-life recovery result from such a backup).