There are no free DVS ports on portgroup - 00528498

[ThinkGrid]

Hi

I upgraded to Veeam v7 Patch 3

On doing a Veeam test restore I got the below error. Now there is a workaround which is restore VM with different settings and chose a vSwitch with empty ports but still needs solution

Code: Select all

10/03/2014 10:35:43          Starting restore job
10/03/2014 10:35:45          Locking required backup files
10/03/2014 10:36:11          Queued for processing at 10/03/2014 10:36:11
10/03/2014 10:36:11          Required backup infrastructure resources have been assigned
10/03/2014 10:36:13          Preparing next VM for processing
10/03/2014 10:36:13          Using source proxy Veeam-Proxy1-883 [hotadd]
10/03/2014 10:36:15          Starting restore agents on server "v140202.mgmt.hvdi.net"
10/03/2014 10:36:15          5 files to restore (20.0 GB)
10/03/2014 10:36:26          Reconfiguring VM
10/03/2014 10:36:32          Restoring '[v1402-v02] 2236/2236.vmx'
10/03/2014 10:36:33          Restoring file '2236.vmxf' (0.3 KB)
10/03/2014 10:36:34          Restoring file '2236.nvram' (8.5 KB)
[color=#FF0000][b]10/03/2014 10:36:39 Error    Restore job failed Error: There are no free DVS ports on portgroup [46 22 17 50 b5 97 31 c0-86 e0 64 8e fd 7a 86 73]/[dvportgroup-5194]

Regards
Petrit

[Vitaliy S.]

Hi Petrit,

I don't think there is anything to do with Veeam here, as VMware has these KB articles that describe your issue > http://kb.vmware.com/selfservice/micros ... Id=1037531 and http://kb.vmware.com/selfservice/micros ... Id=1035819

Thanks!

[ThinkGrid]

Reason why I say this is a Veeam issue is because it works on v6.5

Also, there is no limit on the Ports. It grows as needed. I'll check the ESXi logs but it wasn't an issue with 6.5

[Vitaliy S.]

Then I would suggest waiting what our engineer can say you after reviewing restore log files, but the restore engine didn't change between these versions. Thanks!

[ThinkGrid]

Your restore engine has changed, well something has. I got the below from Support

"Hello Petrit
It has now been confirmed that if you're using the ephemeral port binding for the distributed port group, the restore will fail.
Is is configured that way? Please see http://kb.vmware.com/selfservice/micros ... #ephemeral for more details.

This issue is going to be fixed in the next Veeam B&R release.
For now the workaround is to use standard port binding.

--
Kind regards,
Vsevolod Zubarev
Veeam Software Support"

[Vitaliy S.]

Thanks for the update, I will follow up this question with the dev team then.

[masonit]

Hi

Is this issue fixed? Can't see it in patch 4: http://www.veeam.com/kb1891

\Masonit

[veremin]

As mentioned, the said issue was supposed to be fixed in the next release, not update. Thanks.