Skip to content

F OpenNebula/engineering#924: Added Firewall configuration guidelines for Veeam - #930

Open
roamingengineer311 wants to merge 1 commit into
OpenNebula:one-7.4-maintenancefrom
roamingengineer311:f-eng-924
Open

F OpenNebula/engineering#924: Added Firewall configuration guidelines for Veeam#930
roamingengineer311 wants to merge 1 commit into
OpenNebula:one-7.4-maintenancefrom
roamingengineer311:f-eng-924

Conversation

@roamingengineer311

@roamingengineer311 roamingengineer311 commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Description

Resolves OpenNebula/engineering#924
Added firewall port requirements for Veeam backup integration.

Branches to which this PR applies

  • master
  • one-X.X

  • Check this if this PR should not be squashed

… for Veeam

Signed-off-by: Dmitrii Gilev <dgilev@opennebula.io>
| Veeam Workers | OpenNebula Hosts | TCP/13014 | OneBEX backup and restore transfers |
| Veeam Server | OpenNebula Hosts | TCP/13015 | OneBEX SSL image transfers (optional) |
| Veeam Workers | OpenNebula Hosts | TCP/13015 | OneBEX SSL backup and restore transfers (optional) |
| Veeam Workers | OpenNebula Hosts | TCP/3500–4500 | Interactive restore transfers |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MarioRobres I believe the interactive restore ports are only accessed from ovirtapi to the frontend, so no need for the workers to reach those ports directly right? Since they will be communicating with ovirtapi and then ovirtapi forwards the body.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants