• When backing up to a CIFS share, network connectivity issue during backup may cause backup storage to re-initialize, causing the following runs to fail with the “There is no FIB [summary.xml] in the specified restore point” error.
• Scheduled jobs fail to start when configuration database contains at least one record of unlicensed hypervisor host. For example, this may start happening once the licensed socket count has been exceeded.
• Transform fails with "Full point was not found" error for backup jobs that had their backup mode changed more than once.
• 1-Click FLR to the original location fails for files with ACL containing explicit ACEs and located on non-system drive.
• Failover Re-IP process fails for VMs with file level restore sessions active.
• Low space warning notification is not disabled when the corresponding check box is cleared.
• A number of bug fixes and performance improvements around the new GUI.VMware
• In some cases, backup in Virtual Appliance (hot add) processing mode may be failing with the "File name is too long" error. Usually happens when VMware vCenter server has a long name.
• Processing two VMware VMs with the same IDs (from different host) simultaneously results jobs skipping the VM with the "VM is locked by another task" event logged.
• Depending on the network infrastructure, automatic network mode backup proxy selection algorithm may sometimes pick a proxy from a different subnet.
• Unused thick disks blocks on replica VM may contain random data instead of zeroed blocks.Hyper-V
• On localized Hyper-V servers, restore does not work properly for VMs with SCSI disks.
• Backup of a Linux VM with Hyper-V integration tools version 3.2 or earlier fails.
• Hyper-V offhost backup may fail when both VM configuration files and disks are located on the same volume.
• Hyper-V replication resets vNIC settings of the source VM, whenever replication is performed to the same host or cluster.
• Under certain environment conditions, Veeam Hyper-V Integration service may fail to start.
• Under rare circumstances, backup for Hyper-V VMs with pass-through disks may fail.SureBackup
• SureBackup job may fail when processing domain controller VMs with the “Value was either too large or too small for an Int32” error.
• SureBackup job never stops if some VMs are present in both the application group and one of the linked jobs at the same time.
• SureBackup jobs may fail for DC VMs with file level restore sessions active.
• Virtual lab prevents usage of network interfaces with APIPA addresses, if VM has at least non-APIPA network interfaces.
• Virtual lab network mapping cannot be set for virtual networks with special symbols in names. New Features and Enhancements
Patch 1 brings the following additional changes and enhancement:
•Increased synthetic full transformation, and reverse incremental backup performance (up to a few times depending on backup storage).
• Improved Direct SAN Access mode performance by disabling excessive VDDK logging.
• Processing engine should now be much more tolerant to network packet loss.
• Added PowerShell cmdlet for VeeamZIP operation.
• Added new registry value that reverses the sequence of application-aware processing, making jobs try network-less processing mode before network one.
HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication
Value = 1
To disable (default behavior), value is 0 (false)
• Increased certain network-less application aware processing timeouts to make it work more reliably with applications requiring longer time to perform VSS quiescence.
• Added internet access from virtual lab environment for VMs using port groups other than first.
• Reduced the amount of logs application-aware processing produces on guest VMs.
• Added support for application-aware processing for VM's that use EFI boot