foggy wrote: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.
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
skrause wrote:Typically the Veeam process starts at the bottom and works up from my experience but you want to make sure you give it at least some overhead.
Are you wanting to do Backup Copy jobs or replication? The processes work very differently and require different network connections
skrause wrote:For Backup Copy jobs, you will need to make sure that the ports listed in "Microsoft Windows Server" on the used port lists are open between the B&R server managing the jobs and the repository server:
https://helpcenter.veeam.com/docs/backu ... =95#backup
skrause wrote:You only need 2500-5000 to be open between two repository servers for Backup Copy jobs as long as the B&R server managing the job can access both servers as listed above.
skrause wrote:In the document it describes which services are used by each port. For example, if you don't plan on using vPower NFS to do Instant VM Recovery from the backup copy location, those ports would be unnecessary.
Users browsing this forum: Bing [Bot], Google Feedfetcher, michael-itnow and 1 guest