Ports on remote repository

[ober72]

Hi Folks,

Just wanted to double check. We have a Veeam server and want to connect over a cross connect to a windows server with a large directly connected driver to be used as a repository.

According to the documentation I need from the backup proxy (on the Veeam server in this case) ports TCP 49152-65535 to be open to the server with the large drive being used as a repository.

If I wanted to use CIFS then I would need 135, 137 to 139, 445 to be open only.

My understanding is that it would be better to add the remote windows server drive as a normal repository.

My second question is for cloud connect, do I then need just TCP 6180 open from the Veeam server to Clould connect SP?

Thanks

[veremin]

According to the documentation I need from the backup proxy (on the Veeam server in this case) ports TCP 49152-65535 to be open to the server with the large drive being used as a repository. If I wanted to use CIFS then I would need 135, 137 to 139, 445 to be open only.

In case of CIFS share, you will still need to open 49152-65535 range to a gateway server hosting a target datamover. This server should be located within close proximity to the share. So, overall you'd get the very same requirements.

My second question is for cloud connect, do I then need just TCP 6180 open from the Veeam server to Clould connect SP?

Are you willing to leverage only backup capabilities of Cloud Connect? Or you're looking into replication ones, as well?

Thanks.

[dellock6]

Just to anticipate the following question, with cloud connect backups you only need tcp/6180, while for replication you also need udp/6180 (so you need to open both tcp and udp).

Luca

[mps5056]

Thank you - this was really helpful I was looking for the answer on this. Appreciated