Monitoring for Remote Hosts

[vertices]

Looking through the setup guide, I couldn't find recommendations, port lists, or anything to monitor a remote Hyper-V host or VMware. Am I just missing it in the guide? We would like to monitor many remote Hyper-V hosts and also some VMware hosts. Can someone point me in the right direction for what ports must be allowed from Veeam One to these remote hosts?

Thank you.

[Shestakov]

Hello Rob,
Have you observed this user guide section?
Thanks

[vertices]

Right in front of my face and I didn't see it. Thank you.

Follow-up question: For Hyper-V it seems to require 135 and 445 which are commonly blocked by ISPs. We don't wish to run tunnels to these different sites. Do any guides exist for recommendations on how to monitor remote Hyper-V hosts? Is it possible to put a collector agent on them and have that send information to Veeam One?

[Shestakov]

There is no such a thing as remote data collection agent.
We don't have a guide as well, but you can find related discussions on this forum.
Hope that helps.

[vertices]

That's unfortunate. With moving to VAC, and managed agents and B&R deployments, it seems a critical piece that is missing is the ability to deploy Veeam One at a client, and then have that centrally report back to VAC, same as Windows Agents and B&R can do. "Veeam Availability Console" would be better named "Veeam Backup Management Console". To truly be Availability Console, it should also integrate with Veeam One. Are there any plans for this functionality? Service Providers need more tools to monitor client infrastructure. Thanks.

[Shestakov]

We have some ideas for the remote Veeam ONE servers but can not promise or share anything for now.
Your feedback is also taken into account.
Thanks!