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: 1000 concurrent backup tasks.
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).
Repository: This POD sizing does not include backup repository compute resources, which should be sized separately based on storage architecture and performance requirements.
System requirements
VCC Server (+ PostgreSQL)
| Server | ||
|---|---|---|
| CPU | 36 vCPUs | |
| Memory | 42 GB RAM | |
| Disk 1 | 100 GB | OS/Installation/Database |
| Disk 2 | 100 GB | Temp/Logs |
| OS | Supported OS |
VCC Cloud Gateway
| Server | |||
|---|---|---|---|
| CPU | 4 vCPUs | ||
| Memory | 8 GB RAM | ||
| Disk 1 | 100 GB | OS/Logs | |
| OS | Supported OS |
Performance optimization
Additional registry values can help optimize performance. Please refer to Veeam KB4217 for further information.