Veeam Service Providers Best Practice Site
Site-to-Site sizing
This page describes the minimum required components for the site-to-site DR scenario.
Source Site
The minimum components deployed at the Source site are:
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
Proxmox Worker
This role is deployed on the Proxmox VE node as an appliance when using the Add Workers (Console - Web UI) wizard and is sized by default with 6 vCPU and 6 GB RAM.
Target (DR) Site
Backup Server
| VBR Server (+ PostgreSQL) | ||
|---|---|---|
| CPU | 8 vCPUs | |
| Memory | 32 GB RAM | |
| Disk 1 | 120 GB | OS/Install |
| Disk 2 | 120 GB | Logs/Database |
| OS | Supported OS |
Orchestrator Server (for clean room)
| VRO Server (+Databases) | ||
|---|---|---|
| CPU | 8 vCPUs | |
| Memory | 32 GB RAM | |
| Disk 1 | 240 GB | OS/Installation/Database |
| Disk 2 | 240 GB | Temp/Logs |
| OS | Supported OS |
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
Proxmox Worker
This role is deployed on the Proxmox VE node as an appliance when using the Add Workers (Console - Web UI) wizard and is sized by default with 6 vCPU and 6 GB RAM.