Discussions related to using object storage as a backup target.
Post Reply
Asahi
Expert
Posts: 160
Liked: 11 times
Joined: Jun 03, 2016 5:44 am
Full Name: Iio Asahi
Location: Japan
Contact:

Inbound communication to VBR component servers

Post by Asahi »

Hi,

This may seem like a silly question now, but I would like to confirm something. :roll:

I would like to confirm the port requirements for backup and restore to object storage.
https://helpcenter.veeam.com/docs/backu ... repository

The above user guide says that TCP/IP 2500-3300 communication is required from the Source Object storage repository to the Veeam component servers.

However, in my test environment, I registered Amazon S3 to an all-in-one configuration VBR server and blocked TCP/IP 2500-3300 inbound communication to the VBR server with Windows Firewall.

In this case, NAS backup and restore of VBR server local files to Amazon S3 was still successful.

So when is inbound communication on the TCP/IP 2500-3300 port to the Veeam component server used?
Is it used for backup copy operations from object storage?

Kind Regards,
Asahi,
Climb Inc.
Mildur
Product Manager
Posts: 10402
Liked: 2789 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Inbound communication to VBR component servers

Post by Mildur »

Hi Asahi,

This port description is missing some information.
It should mention that ports 2500-3300 are required between the gateway server of the source object storage and other Veeam components.
The gateway server will read the objects from the object storage and transfer it with the Veeam Transport Service (Port 2500-3500) to other Veeam components machines. Such as Mount Server, Target object storage gateway server or backup server.

I will request an update to the Help Center documentation to make this clearer. Thank you for bringing it to our attention.

Best,
Fabian
Product Management Analyst @ Veeam Software
Asahi
Expert
Posts: 160
Liked: 11 times
Joined: Jun 03, 2016 5:44 am
Full Name: Iio Asahi
Location: Japan
Contact:

Re: Inbound communication to VBR component servers

Post by Asahi »

Hi Fabian

Thank you for information.

I understand why blocking TCP/IP 2500-3300 inbound communication worked fine in my environment.:)
Hopefully the Help Center documentation will be updated.

Kind Regards,
Asahi,
Climb Inc.
Post Reply

Who is online

Users browsing this forum: No registered users and 15 guests