SOAP connection limit in vCenter - still a thing with infrastructure cache?

[mdiver]

There used to be the SOAP connection limit adjustment recommended for large environments.
With 9.5 infrastructure cache was introduced. Best practices guide states that the setting should not be necessary and longer because the cache remove the stress on the connection to vCenter.
https://bp.veeam.com/vbr/VBP/3_Build_st ... phere.html

Though in a larger environment (1000+ VMs) on V10 I've seen some VMs failing in the first run of the jobs with SOAP related errors. The retry fetched those VMs correctly later.
vCenter as well as VBR are rationally sized according to sizing guidelines of course.

Does anyone still increase SOAP limits nowadays?

Thanks,
Mike

[PetrM]

Hello Mike,

As you correctly noticed, the Broker service dramatically reduced the load on vCenter, therefore I'm not sure that the SOAP errors you're talking about are related to some connection limits. I'd recommend to investigate the issue with our support team to understand the root cause. The best practice is to keep default settings unless there is a clear need to adjust them.

Thanks!

[Andreas Neufert]

Ran into some customers that still had issues with the SOAP connections, but those customers used 3 monitoring tools including Veeam ONE that pulled data from VMware. Even some of the storage systems have now plug-ins that pull statistical data from the vcenter.
Overall we still open at backup connections to the vcenter to get information and the VMware VDDK kit that all backup vendors integrate do this as well.

If you run into SOAP connection limitation issues, check where this is coming from and increase the value as outlined in the best practices guide.