Help Center
Choose product document...
Veeam ONE 9.5
Deployment Guide

Typical Deployment

The following diagram illustrates the typical Veeam ONE deployment scenario.

Veeam ONE Typical Deployment

In the typical deployment scenario:

  • All Veeam ONE architectural components (Veeam ONE Server, Veeam ONE Web UI, and Veeam ONE Monitor Client) are installed altogether on a single machine (either physical or virtual).
  • To store data retrieved from connected servers, a local or remote Microsoft SQL Server instance is required. If you have a Microsoft SQL Server instance that meets Veeam ONE system requirements, you can adopt it for Veeam ONE deployment. Otherwise, you can install a new Microsoft SQL Server instance during the product installation — Veeam ONE setup package includes Microsoft SQL Server 2012 Express Edition.

Typical Deployment Note:

For large-scale deployments (1000+ VMs), is it recommended to use a remote Microsoft SQL Server installation as a backend. It is also recommended to run Veeam ONE services on a dedicated server. Such distributed installation will improve performance of Veeam ONE services.

  • To enable multi-user access to real-time performance statistics and configurable alarms, you can additionally install several instances of Veeam ONE Monitor Client on separate machines. Thus, you will be able to access Veeam ONE functionality either from a local machine or from remote computers.

For instructions on the typical deployment procedure, see Typical Installation.

Veeam Large Logo

Deployment Guide

Deployment for Large-Scale Environments

Monitor User Guide

Reporter User Guide

Business View User Guide

Multi-Tenant Monitoring and Reporting

Working with Alarms

Veeam Backup & Replication Documentation

Veeam Agent for Windows Documentation

Veeam Agent for Linux Documentation

Veeam Management Pack Documentation