Vcenter (VDDK) 6.7 San transport mode - works or need patch?

[userv]

Hi,

Using san transport mode.
Just migrated via VMware migration tool from windows-based Vcenter 6.0 to Appliance 6.7.
Host are 6.0 currently.
After migration B&R 9.5 Update 3a started throwing on each job
"VDDK error: 13 (You do not have access rights to this file). Value: 0x000000000000000d"
"Failed to open disk for read. Failed to upload disk. Agent failed to process method"

Ethernet NBD mode works fine, no errors.

Just looking for people with the same config or approximately.
Your san transport mode works with Vcenter Appliance 6.7 ?

At the moment it looks for me like B&R 9.5 update 3a san transport and VCSA 6.7 not working together as they should...

[userv]

Little update:
Just tested - san backup from ESXi directly works fine. Job uses VDDK 6.0 and everything is good.
But ESXis are connected to vCenter 6.7... In this case B&R uses VDDK 6.7 and thing go bad - VDDK error: 13

[userv]

Update 2:
While poking around Google and forums I discovered for myself lots of VDDK 6.5/6.7 bugs and pain.
For my problem with san mode vCenter 6.7 and 6.0 hosts i think about two possible workarounds:
a) Apply hotfix with VDDK 6.7 EP1 from Veeam KB 2711 (https://www.veeam.com/kb2711)
Not sure if EP1 touches my problem somehow, but who knows
b) Without hotfix apply registry hack HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\VMwareOverrideApiVersion
and put it say to "6.7 = 6.5" or "6.7 = 6.5.2" (not sure)
I was told that VDDK 6.5.2 should work with vCenter 6.7
May be VDDK 6.5.2 can run san mode fine?

Going to try soon.

[userv]

I solved this problem.

Root cause is old VDDK bug with non-English UTF letters in temporary folder path. Veeam article for old (same) bug: https://www.veeam.com/kb1506
I can confirm than in VDDK 6.7 and VDDK 6.7 EP1 this bug is back again!
When VixDiskLib_Open() is given a pathname containing UTF-16 characters, the virtual disk library fails to find the file.
It happens in SAN mode, NBD is unaffected.

I have changed all veeam services account from non-English system account to domain local admin account containing only English UTF-8 letters. Also granted dbo rights for configuration database for that account. That's all - Direct SAN backups immediately started to flow.

Hope this thread will help someone too.
Also, Veeam should publish updated KB for this bug and contact VMware for fixing their buggy VDDK 6.7

[Gostev]

Thanks, we should be able to work around this bug on our side in Update 4.