With is important to know how to connect NICs to vSwitch.I would almost always recommend to have at least 2 NICs connected to each vSwitch and let VMware handle all the "network load balance".
Veeam backup vcenter software#
I have never seen this need since.the only reason I can think of is that the backup would take up so much bandwidth that the OS or backup software heart-beat may get timed out.īut this can be true for modern day servers as one of my guys did on a lab where the ESXi had only 1 working NIC port (other failed).when backups ran, vCenter got disconnected from that host.when backup completes, the host came back to vCenter automatically. So I did a little more digging, this time on Veeam proxies and came across this YT video that explains the choices: But you used a word that an old network geezer like me understands. I was about to dismiss this reply because I thought you were missing the question entirely (the question was HOW not WHY no matter how much deduplication happens, we do NOT want backup traffic mixing with storage traffic).
Veeam backup vcenter install#
You do not need a separate network for Veeam or backups, the traffic will be deduped, compressed and optimized for LAN or WAN based on your settings, if you install Veeam proxies between the guests and the backup target, they do all of the work before the data is sent over the LAN
Yes, but that is not what I was asking because it doesn't apply to us. Veeam also has the ability to do backups direct from a supported SAN or NAS device, meaning backups are taken right at the disk level and not even done via a network but directly from the storage. 'backup networks' are an old way to do things when systems were physical, your way of thinking seems to be stuck with that I miss the old days of backups when all we had to do was ensure each server had 2 NICs and configure the backup agent running on them to use the backup NIC to ensure segregation. Won't Veeam (which is a VM) connect to the vCenter (also a VM) on the VM network just to look at what the existing VMs are but still back these up using the backup network (assuming I configure the preferred network to use the backup network)? The Veeam VM will have 2 NICs (1 in the VM network and the other in the backup network) but the vCenter (VCSA) only has 1 NIC which is on the VM network). Is that correct? Or maybe I am misunderstanding his statement? I am a network guy and our storage guy is saying something that I don't understand: that the "Veeam software will still affect the VM network because it backs up the VMs from the vCenter". Each vSwitch has 2 physical 1Gbps NICs tied to them.Īre we correct in our understanding that when we install Veeam as a VM, we need to give it 2 NICs, 1 for managing it (via the VM network), and another for backup traffic (in the backup network)? Will this ensure that when the backups are running, that they don't affect the VM network and the storage networks? We do it this way because we don't want the storage traffic to be affected when backups are running and we rarely will need to use vMotion (only when the physical host fails). Each physical host (ESXi) has separate vSwitches for VM traffic (vSwitch2), storage traffic and vMotion (vSwitch1) and management and backup/restore traffic (vSwitch0). We plan to deploy Veeam as a VM on a cluster of physical hosts that also has vCenter on it running as a VM.