This is an archive version of the document. To get the most up-to-date information, see the current version.

Veeam ONE Architecture

Veeam ONE relies on client-server architecture to work effectively in environments of any size and complexity. Veeam ONE architecture includes the following structural components:

  • Veeam ONE Server

Veeam ONE Server is responsible for collecting data from virtual and Veeam Backup & Replication servers, and storing this data into the database. As part of Veeam ONE Server, the following components are installed: Veeam ONE Monitoring Service, Veeam ONE Reporting Service, Veeam ONE Error Reporting Service, and Veeam ONE Web API.

  • Veeam ONE Web Services

Veeam ONE Web Services enable access to Veeam ONE web server and handle rendering of reports.

  • Veeam ONE Client

Veeam ONE Client is a client part for Veeam ONE Server. Veeam ONE Client communicates with the Veeam ONE Server installed locally or remotely.

  • Veeam ONE Database

Veeam ONE database stores data used by product components. The database is hosted on a Microsoft SQL Server that can run remotely, or can be co-installed with other Veeam ONE components.

  • Veeam ONE Agent

Veeam ONE agent is a component that enables communication with Veeam Backup & Replication servers, performs collection of logs, and sends remediation commands.

Veeam ONE agent can work in the following modes:

  • Server

In this mode, Veeam ONE agent is responsible for analyzing log data and signature updates.

Veeam ONE agent server is included into Veeam ONE installation package and deployed on the machine running Veeam ONE server during product installation.

  • Client

In this mode, Veeam ONE agent is responsible for collecting logs and executing remediation actions on Veeam Backup & Replication servers.

By default, Veeam ONE agent client is deployed on Veeam Backup & Replication servers when you connect these servers to Veeam ONE.

Veeam ONE architectural components can be installed on a single machine, or run on dedicated machines. For details, see Deployment Scenarios.