Learn Veeam - Adding Hypervisors & Hosts
This episode guides you through adding workload sources to VBR v13: vCenter/ESXi via the API with credentials and a VM rescan, Proxmox VE 8/9 with the native data mover on the node, Hyper-V/SCVMM hosts, and the Nutanix AHV plugin. You will understand how each platform connects differently and when to choose which.
#Introduction
Now that VBR is installed in episode 3, we connect its workload sources: the hypervisors where your VMs live. In episode 4 we add vCenter/ESXi, Proxmox VE, Hyper-V/SCVMM, and Nutanix AHV — complete with credentials, API connections, and rescans.
Each platform has a different way of connecting, and understanding the differences matters: Veeam does not read VMs as ordinary files, but communicates through the hypervisor API to take snapshots, read data, and restore VMs — consistent with the proxy architecture we covered in episode 2.
#Adding vCenter / ESXi (VMware)
#Add Server via the Console
From the VBR console: Backup Infrastructure → Managed Servers → Add Server → VMware vSphere. Fill in:
- DNS name/IP: vCenter Server (recommended) or a standalone ESXi host.
- Credentials: an account with vCenter rights (usually an administrator account or a user with a backup role).
The console will show a certificate summary (accept the fingerprint) then wait to finish when the server is successfully connected.
#Rescan VMs
After the server is added, Veeam runs a rescan — synchronizing the inventory (VMs, hosts, datastores) into the catalog. Rerun it whenever needed from the console (right-click the server → Rescan) or via PowerShell:
$server = Add-VBRServer -Name "vc01.example.com" -Credentials $creds -Type vCenter
Start-VBRRescan -Server $serverNote
Always add vCenter, not individual ESXi hosts, unless your environment is a single standalone host. vCenter provides a single API point for all hosts, and Veeam uses the vSphere API for snapshot consistency. Adding each ESXi separately means jobs must be split per host — not a recommended design.
#Adding Proxmox VE
#Native Support Since v13
Veeam v13 brings native Proxmox VE 8/9 support — no additional agents, directly from the console. From Backup Infrastructure → Managed Servers → Add Server → Proxmox VE, enter the node address and credentials (a user account with PVEVMAdmin rights or root@pam).
What sets it apart from other platforms: Veeam deploys a data mover on the Proxmox node — a lightweight component that handles data transfer directly from the node's storage (similar to a proxy's role), so backups do not pull data over the management network:
Node Proxmox ── data mover ──▶ VBR Server / Proxy ──▶ Repository#Verification & Rescan
After adding it, perform a rescan and make sure the status is green. Proxmox VMs will appear in the console and are ready to be added to a backup job (episode 5).
#Adding Hyper-V and SCVMM
#Hyper-V Hosts and Failover Clusters
For a standalone Hyper-V host or cluster: Add Server → Microsoft Hyper-V, fill in the host/SCVMM server and credentials. Veeam connects via WMI (Hyper-V) or the SCVMM API if you use System Center Virtual Machine Manager — SCVMM is recommended for large cluster environments because it provides a single management point.
#Hyper-V Proxy and On-Host Backup
Hyper-V uses the on-host backup model: the proxy runs on the Hyper-V host itself, so snapshotting and data transfer happen directly on the host — saving network bandwidth. For large environments, add separate Hyper-V proxies so the hosts are not overloaded.
#Adding Nutanix AHV
#The Nutanix AHV Plugin
Veeam integrates Nutanix AHV through an official plugin: Backup Infrastructure → Managed Servers → Add Server → Nutanix AHV, with Prism Central as the connection point (not per-cluster). Credentials use a Prism account with backup rights.
Once the plugin is active and the server is added, Veeam rescans AHV VMs through the Prism API, and snapshot consistency is handled natively by AHV. This completes the four main virtualization platforms Veeam supports equally.
#Comparing Connection Methods
| Platform | Connection point | Data mechanism | Notes |
|---|---|---|---|
| VMware vSphere | vCenter / ESXi | Proxy (SAN/NBD/HotAdd) | Transport modes from episode 2 |
| Proxmox VE 8/9 | PVE node | Data mover on the node | Native since v13 |
| Hyper-V / SCVMM | Host or SCVMM | On-host proxy (WMI) | Use SCVMM for large clusters |
| Nutanix AHV | Prism Central | AHV plugin | Single API point for all clusters |
Tip
Connection rule of thumb: one API point, not per-node. vCenter (not ESXi), SCVMM (not per-host), Prism Central (not per-cluster), and for Proxmox add the relevant nodes. The fewer connection points, the simpler the operations and the easier the inventory rescan.
#Verification
After this episode, make sure:
- vCenter/ESXi, Proxmox, Hyper-V/SCVMM, or AHV appear in Managed Servers with a green status.
- The rescan succeeded and VMs are visible in the inventory.
- Credentials are validated (Veeam shows an ok indicator on the credentials).
#Closing
Key takeaways:
- vCenter is the correct VMware connection point; a rescan syncs the inventory.
- Proxmox VE 8/9 is natively supported in v13 with a data mover on the node.
- Hyper-V uses on-host proxies; SCVMM for large clusters.
- Nutanix AHV connects via Prism Central with the official plugin.
- Always use one API point per platform for simple operations.
In the next episode, episode 5, we will create the first backup jobs: VM & Physical — selecting VMs/containers, setting the storage repository, schedule, retention (GFS), and guest processing with application-aware processing (VSS) for MS SQL, Exchange, and AD, plus Veeam Agent for physical servers. Your first job will run!