The Veeam back-end data collection system consists of:
•Veeam Virtualization Extensions Service and UI
Veeam Virtualization Extensions Service
The Veeam Virtualization Extensions Service (VE Service) centrally manages all Veeam Collectors and their connections to VMware systems. It maintains a central license pool for distribution to Veeam Collectors, and assigns monitoring jobs to all Collectors.
The VE Service incorporates the Veeam Virtualization Extensions Shell (VEShell) that extends Windows PowerShell to allow configuration and management of Virtualization Extensions Service through command line. VEShell provides a set of its own cmdlets allowing you to automate configuration and monitoring tasks.
User can manage and configure the VE Service either via the Veeam Virtualization Extensions User Interface, or using the Veeam Virtualization Extensions Shell.
High-availability and load-balancing
High-availability, load-balanced monitoring is an option, as the Extensions Service monitors the heartbeat of all registered Collector servers. Should any Collector fail, the monitoring jobs will failover and be automatically and optimally distributed to other available Collectors.
The Extensions Service also monitors the heartbeat of the VMware vCenter server, and will automatically reconfigure Collectors to gather data directly from vSphere hosts if vCenter becomes unavailable. For more details see the vCenter Connection Failover section.
Veeam Virtualization Extensions UI
The Veeam Virtualization Extensions UI (Veeam UI) is used to configure the Extensions Service and Collectors.
The Veeam VMware Collector (Collector) is an installed service, configured and managed remotely by the VE Service.
The Collector can be installed either on a single server, or automatically on Ops Mgr Management Servers in a given Resource Pool. For details on installing the Collector and using the Veeam VMware Collector Auto-Deployment feature, refer to the Installation Guide.
The Collector will communicate remotely with VMware systems, gather performance, event and topology data, and deliver it to the locally installed Ops Mgr Health Service (agent, or management server). The Health Service will analyze the data using the Veeam MP for VMware Health Model and so drive alerts, charts, reports and dashboards available in the Ops Mgr console.
In This Section