Share

Tweet

Share

Share

Email

Comments

Patch 3 Release Notes for Veeam Backup & Replication 6.0.0.153

A patch is avai­lable for Veeam Backup & Replication v6. If you plan to use Direct SAN access mode, are run­ning a loca­li­zed ver­sion of Micro­soft Win­dows, or are upgra­ding from a pre­vious ver­sion of Veeam Backup & Repli­ca­tion, consi­der ins­tal­ling the patch.

http://www.veeam.com/kb_articles.html/KB1442

 

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.