VAC for Veeam one?

[szwicker]

Will there but something coming along that functions for VeeamONE the way VAC does for Veeam B/R?
Rather than have to jump into each client's server, it would be nice to hit them all in a single pane of glass.

[Mike Resseler]

Seth,

Just to make sure I understand it correctly. You want some sort of VAC that can manage/ monitor your customers Veeam ONE installations? Is that correct?

[Vitaliy S.]

Hi Seth, what kind of data do you want to sync to the master Veeam ONE server from other installations?

[szwicker]

Well, just as I can hop into any client's network and see their Veeam ONE instrumentation, it would great if I could see all of them in one portal.

[nielsengelen]

Are you talking about the mini dashboard you see using the Veeam One Client (with the statistics and the open alarms) as a start?

[szwicker]

Well, ideally, I'd have the ability to jump into each client's Veeam One System from there to drill down further, but even, a mini-dashboard showing all would be a start.

[Shestakov]

Looks like a Veeam ONE client working with several VO Servers is what you are asking for. Currently it`s not available, but to get dashboards you may connect to customers` Veeam ONE Reporters via web interface.

[EugeneK]

The idea of having master/slave instances of VeeamOne is appealing: one of the greatest benefits of VeeamOne for Enterprise (Service Providers specifically) is an ability to monitor both, vSphere and Hyper-V environments from a single pane of glass.
However, the common challenge would arise from the fact those environments meant to be monitored, reside within the isolated/firewalled networks, which makes it a dillemma to punch DNAT holes through their perimiters to gather the required data, where to monitor every and each component behind the firewall would require that kind of rule to exist not only for vCenter (in vsphere environment), but also for every single node/component to be accessible over the network, making it rather complicated to implement.

If the concept of mast/slave was to be adopted, with an ability to collect data locally (Proxy-like VeeamOne appliance) to ship data later on upstream, to the Master collector, the design for monitoring purposes would be much easier, as not only it simplifies network communications, but also allows to scale-out (sorta) the VeeamOne instances.

[Shestakov]

Thanks for the clarification Eugene!
The request is taken into account.

[Vitaliy S.]

As a workaround, why not to install Veeam ONE in each site and then publish overview web-based dashboards in the central portal (for example, SharePoint)?

[szwicker]

Circling back on this....

Vitali,
Can you please elaborate?

[Vitaliy S.]

Sure! If you install Veeam ONE in each site and connect it to the client's infrastructure, then you can generate a direct linkto our web-based dashboards (Veeam ONE Reporter). Each site/client will have their own dashboard and unique URL which you can use in our own site (for example, if you have a web-based portal you can embed these direct links to a single view).

This is an old whitepaper, but it still gives you an idea on how to make it work > Integrating Veeam ONE Reporting into Microsoft SharePoint