Since VM copy jobs use the same infrastructure components
as backup jobs, you'd need connection between the proxy and repository server (or gateway server, in case of CIFS target). Of course, backup server would also need access to the remote repository, otherwise the repository cannot be added. Make sure all components shared between Veeam B&R instances are at the same patch level. Connection to remote vSphere would'n be required.
My network team needs a list of servers and specific ports that need connectivity to one another. They don't care/need to know whether communication is inbound/outbound, however.
Also, one thing I didn't mention is the Env B backup repository is connected locally to the Env B Veeam server. So I believe the only connectivity between the two networks is Env A Veeam Server
needs to communicate with Env B vSphere
and Env B Veeam Server
(which is acting as the proxy and the connection to backup repository, right?)?
If that assumption is correct, this is my best guess so far as to what exactly needs to be setup :
- Code: Select all
Servers Protocol Port/s Need
Env A Veeam / Env B vCenter HTTPS+TCP 443 Connections to vCenter Server
Env A Veeam / Env B Veeam TCP 2500-5000 Transmission channels for replication jobs
Env A Veeam / Env B Veeam TCP 6061 Veeam vPower NFS Service
Env A Veeam / Env B Veeam TCP 6062 Veeam Data Mover Service
Anything else I'm missing here or that can be removed?
Also, regarding the "Transmission channels for replication jobs" ports - if we only have 5 VMs we ever plan to copy, can we get away with only opening ports 2500-2504 or does Veeam randomly pick ports in that range?