kb2042

[PaulNSW]

According to kb2042, there is a bug in VDDK6 and its treatment of VMDKs with duplicate disk names
The workaround from Veeam, was to failback to NBD instead of hot-add

I contacted VMware to see if this was fixed in a newer version, otherwise I need to rename all disks, or move them to different SCSI IDs; changes that requires downtime

They said

We have checked internally, there are no such issues from VMware end.

Please find the link mentioned below.
https://www.vmware.com/support/develope ... nownissues
https://www.vmware.com/support/develope ... nownissues

Is this something Veeam needs to report?

[foggy]

I will ask support guys to update the article, if required. Anyway, as the KB says, if you're running at least Veeam B&R Update 2, there's nothing to worry about, since the issue was worked around there.

[foggy]

According to our information (VMware SDK support case 15684272306), the issue is still there and is planned to be fixed in VDDK 6.0 U2. I admit engineer you've talked to could confuse the issue with some other one.

[PaulNSW]

Thanks for looking into that, foggy

[ChuckS42]

Anything new on this one? Looks like VDDK 6.0 U2 was released on March 15th and includes the fix.

[Gostev]

Thanks for the heads up, we will test this new VDDK version and based on the results will consider including it in the next product update/release.