Challenge

These are the issues resolved by the Patch 3 for Veeam Backup version 6.0.0.153. All patches are cumulative so each below fix is contained in this patch. Application-aware processing fails for SQL server where Veeam configuration database is located. Cannot specify "0" in re-IP rule. Hot add operation can sometimes cause a very long backup source/target proxy Virtual Machine stun. This stun can be so long that it can cause all jobs using this backup proxy to fail due to timeout with:"Error: Client error: A connection attempt failed because the connected party did not properly respond after a period of time". CBT may fail on  virtual disks other than Hard Disk 1 with the "Soap fault. A specified parameter was not correct" error when the hot add processing mode is used. Backup console UI freezes periodically (upon automatic refresh event) when there is a large number of managed objects exist. Any job processing the same Virtual Machine longer than 48 hours is forcibly terminated.The new timeout is set to 7 days. Very large jobs start failing with the "Failed to save file content" error after the VBM metadata file reaches 4 MB in size. Hyper-V CSV ownership change during backup or replication preparation process may take too long with certain storage devices, causing bug check (BSOD) on Hyper-V hosts. Hyper-V virtual disks with the disk file’s extension in capital letters (.VHD) are backed up like regular files, and not like virtual disks. Copying very large files to Linux or ESX host with service console credentials specified may fail. Enhancements For VMware virtual machines with multiple disks, hot add was changed to only happen once for each processed virtual machine instead of multiple times, before each processed disk. Improved VMware replication failback performance by enhancing the virtual disk digest calculation process. Improved vPower NFS performance by removing some excessive logging. Changed the warning about outdated VMware Tools on the processed virtual machine to an information event. Removed CBT warning from the initial run of backup and replication jobs which have backup and replica mapping configured. Added support for adding Hyper-V with Veeam Backup and Replicationg installed. Previously, adding the host would fail with the "User credentials cannot be used for local connections" error. Improved bottleneck analysis formulas for proxy and network processing stages. For example, heavy backup target load should no longer affect the Network stage percent busy value. Previously resolved by the Patch 2 for Veeam Backup version 6.0.0.153 (Build 6.0.0.164) Direct SAN Access processing mode does not work for certain SAN makes and models. Virtual Appliance (Hot Add) processing mode does not work when backup proxy is installed on localized version of Microsoft Windows. Upgrade related issues affecting jobs created in v5 - poor incremental backup performance, and large VIB file created on the first incremental run. Guest file system indexing fail on certain VMs with "Failed to index guest file system. Details: Error: Cannot read data from volume Win32 error: The handle is invalid. Code: 6" For v6 backup servers that were upgraded from v5, jobs fail to send email notifications if SMTP server requires authentication. Reversed incremental backup mode jobs scheduled to run on specific days only will also start on synthetic full backup day (as set under incremental backup mode options in the advanced job settings). Due to the same bug, Replication and VM Copy jobs will always start on Saturday (which is the default day for synthetic full backup). For jobs writing to CIFS-based backup repositories, backup results are not set in the selected VM attribute upon job completion. Added support for Cisco Nexus 1000V switch (port groups were not visible in UI). Added VM heartbeat check for Migration jobs. Original VM files will not be removed until the heartbeat is received. This was needed because it was reported that under certain circumstances (we were not able to reproduce this to date), the migration job fails to copy the virtual disk contents correctly, but nevertheless deletes the original. Under certain circumstances the job fails with the following error: "Client error: Cannot allocate memory for an array. Array size: [4198400]." For VMs configured to use VMware DVS (Distributed Virtual Switch), restore and replication into a different vCenter server will fail. Previously resolved by the Patch 1 for Veeam Backup version 6.0.0.153 (Build 6.0.0.158) Direct SAN Access processing mode does not work for certain SAN makes and models. Virtual Appliance (Hot Add) processing mode does not work when backup proxy is installed on localized version of Microsoft Windows. Upgrade related issues affecting jobs created in v5 - poor incremenal backup performance, and large VIB file created on the first incremental run.