This post is also available in: Italian

Reading Time: 2 minutes

Compatibility remain one of major reason for wait before a major upgrade, but now several backup products are compatible with vSphere 6.0 (see Backup products and vSphere 6.0 compatibility – Updated). Same for several other 3rd part software.

But in the backup space there are still some issues that may limiting the choice of running (yet) vSphere 6.0 in production environments. As written in VMware vSphere 6.0 – Upgrade or not upgrade post one was related in CBT in ESXi 6.0 that can impact your environment also if your backup program will already support vSphere 6.0: for more information see KB 2114076 (Backing up a virtual machine with Change Block Tracking (CBT) enabled fails after upgrading to or installing VMware ESXi 6.0).

I said was because this morning I’ve read in the last Veeam Community Forums Digest that this issue has been fixed.

UpgradeLate last week, VMware has released the patch for the major CBT issue. First customers who have already had a chance to install the patch are reporting that it fully resolved the issue. This becomes a must-install patch for all vSphere 6 deployments until VMware releases Update 1.

But there is another bug related to backup using the native API (VDAP); fortunately, this one is environmental-specific and has a workaround that should work for majority of users. The issue causes jobs using Direct SAN access mode to crash on backup proxies with a large amount of NIC adapters having IPv6 enabled. The actual fault sits in one of the VDDK 6.0 libraries, in the function that collects DNS addresses from all proxy NICs, and puts them into a string. When string’s length becomes larger than certain amount of characters, VDDK crashes. As you can probably guess by now, the main issue here is IPv6 address length.

The easiest workaround is to simply go into each NIC’s properties, and disable IPv6, but Veeam is working to an hot fix for customers who cannot disable IPv6.

Share

Related Posts

  • VMware vSphere 5.1 upgrade path - Conclusions

    Finally there are several other aspects to consider: backup software, storage plugins, vSphere client, ... Backup The backup software must be compatible with vSphere 5.1, so check it before the upgrade procedure. Actually most of the backup software vendors have version for vSphere 5.1, but…

  • Upgrade path to vSphere 5 - The backup part

    Aggiornata l'infrastruttura ovviamente bisogna aggiornare anche la parte dei backup. In realtà il consiglio è di pensare prima a questa parte per evitare spiacevoli sorprese di software non funzionante e/o non supportato. Il consiglio è anche i approfittare di questo momento per rivedere, anche in…

  • Upgrade path to vSphere 5 - The backup part

    When the vSphere infrastructure is upgraded, than also the backup part needs a check (and maybe a refresh). But, in order to avoid big issue, is better check it also before the entire upgrade, just to be sure that all remain supported. I also suggest…

Virtualization, Cloud and Storage Architect. Tech Field delegate. VMUG IT Co-Founder and board member. VMware VMTN Moderator and vExpert 2010-24. Dell TechCenter Rockstar 2014-15. Microsoft MVP 2014-16. Veeam Vanguard 2015-23. Nutanix NTC 2014-20. Several certifications including: VCDX-DCV, VCP-DCV/DT/Cloud, VCAP-DCA/DCD/CIA/CID/DTA/DTD, MCSA, MCSE, MCITP, CCA, NPP.