Skip to main content
Solved

Port 2521


Dear All
When two backups of different locations are executed to the same repository, it gives us a problem with Port 2521, there is a way to do it by changing the port

Best answer by MicoolPaul

Only thing I’d add to Mildur’s comment is, are these backups being orchestrated by the same repository? Whilst it’s possible to have jobs from multiple VBR instances going to one repository, a repository can only accept jobs from one VBR instance at a time.

 

https://helpcenter.veeam.com/docs/backup/vsphere/system_requirements.html?ver=110

View original
Did this topic help you find an answer to your question?

4 comments

Mildur
Forum|alt.badge.img+12
  • Influencer
  • 1035 comments
  • August 5, 2022

Default ports for the Data Transmission from a Agent/Proxy to the backup repository can be anything between 2500 to 3300. You should check your firewall, if the ports are allowed to go trough.


This port range can be configured in the managed server properties of the windows or Linux server from your backup repository:

https://helpcenter.veeam.com/docs/backup/hyperv/windows_server_credentials.html?ver=110

https://helpcenter.veeam.com/docs/backup/hyperv/linux_server_ssh.html?ver=110

 

 

 


MicoolPaul
Forum|alt.badge.img+23
  • 2361 comments
  • Answer
  • August 6, 2022

Only thing I’d add to Mildur’s comment is, are these backups being orchestrated by the same repository? Whilst it’s possible to have jobs from multiple VBR instances going to one repository, a repository can only accept jobs from one VBR instance at a time.

 

https://helpcenter.veeam.com/docs/backup/vsphere/system_requirements.html?ver=110


  • Author
  • Comes here often
  • 4 comments
  • August 7, 2022

Thank you very much for the help, they are very good comments

 

CesarTac


MicoolPaul
Forum|alt.badge.img+23
  • 2361 comments
  • August 8, 2022

Let us know if this resolved your issue or if you require further help. If one of the responses was an answer, please mark it as so to help those that find this topic in the future.


Comment