Veeam Service Providers Best Practice Site
VCCR POD Sizing
This page describes a pod build for Veeam Cloud Connect Replication up to 500 concurrent tenant tasks.
POD design concept
A POD represents a self-contained, scalable unit of backup infrastructure that can operate independently. This modular approach enables horizontal scaling by deploying additional PODs as demand grows, while limiting failure domains and maintaining predictable performance characteristics.
POD specifications
Capacity: 500 concurrent backup tasks with each component (Cloud Gateway and Proxy) in a redundant N+2 setup.
Database: The following POD design is oriented towards a simplified architecture using VBR with the built-in PostgreSQL instance. A separate Microsoft SQL Server can be introduced to support Veeam Service Provider Console deployment when centralized management and billing capabilities are required (see the MSP build section).
System requirements
Cloud Connect core infrastructure
| VCC Server (+ PostgreSQL) | ||
|---|---|---|
| CPU | 36 vCPUs | |
| Memory | 42 GB RAM | |
| Disk 1 | 240 GB | OS/Install |
| Disk 2* | 120 GB | Logs/Database |
| OS | Supported OS |
* Note Disk 2 is only required when you first manually deploy PostgreSQL on its dedicated drive. The default will deploy it on Disk 1 (= C:\ drive).
| VCC Cloud Gateway (N+2) | |||
|---|---|---|---|
| OS | Windows/Linux | VIA | |
| CPU | 8 cores | 8 cores | |
| Memory | 16 GB RAM | 16 GB RAM | |
| Disk 1 | 120 GB | 120 GB | OS/Logs |
Proxy Servers
VMware VM Replication (N+2)
| Proxy | |||
|---|---|---|---|
| OS | Windows/Linux | VIA | |
| CPU | 4 cores | 8 cores | |
| Memory | 8 GB RAM | 16 GB RAM | |
| Disk 1 | 120 GB | 120 GB | OS/Logs |
VMware CDP Replication (N+2)
| CDP Proxy | |||
|---|---|---|---|
| OS | Windows/Linux | VIA | |
| CPU | 8 cores | 8 cores | |
| Memory | 16 GB RAM | 16 GB RAM | |
| Disk 1 | 120 GB | 120 GB | OS/Logs |
Hyper-V On-Host Proxy
This component is automatically deployed onto every Hyper-V node and is set with a task limit of 4 by default. Make sure to account for enough available resources on each Hyper-V host:
- 1 core for each 2 additional concurrent tasks
- 2 GB RAM plus 500 MB for each concurrent task
Changing the (default) number of concurrent tasks can be done here: Web UI - Console
Performance optimization
Additional registry values can help optimize performance. Please refer to Veeam KB4217 for further information.