Veeam One is connected to the VBR and receives all backup information via this path, except for the direct performance values of the proxies. These are queried by ONE directly from the proxies.
This means that there is no other way than to create a new user on the proxies and assign the WMI authorizations to this user. The user must then be assigned to the proxy in the ONE.
In large infrastructures with, for example, more than 50 proxies (partly non-domain joined), this is difficult to implement.
It would be practical if the performance data could be read out directly via access through the VBR (e.g. via the Veeam components already installed on the proxies).
-
petesteven
- Veeam Vanguard
- Posts: 32
- Liked: 39 times
- Joined: May 08, 2018 7:34 am
- Full Name: Peter Steffan
- Contact:
Feature request - Veeam ONE Proxy backup performance data collection via VBR
Peter Steffan - My Blog: petersvirtualworld.de; VMCE2024, VMCA2024, Veeam Vanguard since 2025, Object First ACES since 2026
-
jorgedlcruz
- Veeam Software
- Posts: 1837
- Liked: 804 times
- Joined: Jul 17, 2015 6:54 pm
- Full Name: Jorge de la Cruz
- Contact:
Re: Feature request - Veeam ONE Proxy backup performance data collection via VBR
Hello Peter,
I think we will have something that you would like in V13.1. Node Exporter for VIAs. This means that as soon as v13.1 drops out, you can migrate your proxies to the Linux ones hardened, and upgrade Veeam ONE v13.1. Then VONE will still connect to these Proxies, but the auth is much simpler (or even disabled just port 443).
Would that help? I do not see anytime soon the VBR becoming a proxy or proxies, or a performance collector of the rest of the Infrastructure, we did that couple of years ago and we had Large Enterprises with bigger problems at the VBR, and at the relay level of Veeam ONE waiting for hours because the proxy or repo wasn't sending data properly to the VBR, Node Exporter is clean and standard.
Let me know your thoughts.
I think we will have something that you would like in V13.1. Node Exporter for VIAs. This means that as soon as v13.1 drops out, you can migrate your proxies to the Linux ones hardened, and upgrade Veeam ONE v13.1. Then VONE will still connect to these Proxies, but the auth is much simpler (or even disabled just port 443).
Would that help? I do not see anytime soon the VBR becoming a proxy or proxies, or a performance collector of the rest of the Infrastructure, we did that couple of years ago and we had Large Enterprises with bigger problems at the VBR, and at the relay level of Veeam ONE waiting for hours because the proxy or repo wasn't sending data properly to the VBR, Node Exporter is clean and standard.
Let me know your thoughts.
Jorge de la Cruz
Director Observability & AI Product Management | Veeam ONE @ Veeam Software
@jorgedlcruz
https://www.jorgedelacruz.es / https://jorgedelacruz.uk
vExpert 2014-2025 / InfluxAce / Grafana Champion
Director Observability & AI Product Management | Veeam ONE @ Veeam Software
@jorgedlcruz
https://www.jorgedelacruz.es / https://jorgedelacruz.uk
vExpert 2014-2025 / InfluxAce / Grafana Champion
Who is online
Users browsing this forum: No registered users and 1 guest