Hotadd (appliance proxy) failing after VCenter 6 upgrade

[bhodgins]

Veeam case #00889245

The day that I upgrade VCenter server to 6 Veeam stopped working for me in appliance mode. Currently running the latest patch of Veeam 8, the Veeam tech and I made it as far as manually trying to hotadd a VMDK. Only open ones though. Should I try this process on a powered off VM, the VMDK attaches normally. This rules out permissions.

This is the error I receive with the manual attach of a live VMDK after the snapshot:
Failed to lock the file
Cannot open the disk '/vmfs/volumes/528683bb-fea59a2e-8b92-a4badb441103/Windows7#2/Windows7 Pro X64 #2.vmdk' or one of the snapshot disks it depends on.
Failed to power on scsi0:3.
Failed to add disk scsi0:3.

Doesn't matter if this is done via VCenter or direct to the host.

My question is, what is with the first part of the error? The file would already be locked by the host, as one the snapshot delta file has been created, the .lck file attached to the main VMDK would lock the file to be read-only.

In KB1184 it states: "If this task completes this means the infrastructure is present to allow the Proxy to hotadd the VMs base disk." And if it doesn't then what?

Brad

[foggy]

Brad, have you already contacted VMware support? Since you can reproduce this behavior without Veeam B&R in picture, I believe this should be reported to VMware directly. Btw, are all the VMs affected by this issue or just some of them?

[Maledict]

Hi everyone.
We have been using backup using network mode for a long time. I tried to make it VA mode, but for some reason when tested manual hot add function found out that if VM was backuped with CBT enabled i can not hot add it, and i did not found a good way to reverse VM to normal state after CBT.

this what happens if i try to hot add a VM disk to proxy, btw there are no snapshots

Failed to lock the file
Cannot open the disk '/vmfs/volumes/56501689-1f13b10c-0e51-e41f13448e9c/XXXXXX/XXXXX13-01_3.vmdk' or one of the snapshot disks it depends on.
Failed to power on scsi0:1.
Failed to add disk scsi0:1.

[Shestakov]

Hi Artyom and welcome to the forums!
Please review, Hot Add mode requirements and limitations. CBT should not be the case. If everything is ok, but backup still fails, please open a support case.
Thanks!

[Maledict]

Hi!
I have VMware 5.5, vmfs 5 on all storages all drives are scsi lsi or paravirtual, requirements are ok.

[foggy]

Check whether any of these limitations apply to your setup.

[Maledict]

i do not have more than 5 drive per VM, i have 2 vcenter, 2 clusters ... proxy`s are in each of them, backup proxy is in the same claster vcenter and even host, vm version is 10. You there is no problem if i create VM from template and then manually hot add its drive to backup proxy, problem is only with VM`s processed by veeam with cbt..

[foggy]

Please contact support for a closer look at your environment.

[Maledict]

ok...
btw i have found out intresting thing. I can hot add if the source VM is power off, but if it is powered than i get this error.
Failed to lock the file
Cannot open the disk '/vmfs/volumes/56501689-1f13b10c-0e51-e41f13448e9c/cxxxxxx1/xxxxxxx1_4.vmdk' or one of the snapshot disks it depends on.
Failed to power on scsi0:1.
Failed to add disk scsi0:1.

[foggy]

Looks similar to the above, except the vSphere version. Anyway, more close investigation is required.

[Maledict]

ticked opened

[Shestakov]

Could you post the case number for us to follow the investigation? Thanks