New ports in Veeam 13.1.0.411 & Proxmox Plugin 13.4.0.300?

[AntonJH]

Hello,

This is just a general question, and so that others may also see it if the issue occur for them aswell.

After updating to 13.1.0.411 we ran into issues where we were unable to take any backups of VMs in Proxmox. After some troubleshooting we found that traffic was being blocked in the firewall. It seems that in 13.1.0.411 port 6162 and 6160 are being used to communicate with the Worker VMs from the backup server - I could not find this in the user guide so it might not be documented?

It would be great to have a more detailed changelog with what has changed, not just the broad one that is available right now.

BR
Anton

[AntonJH]

Updating with some other findings.

We found that the granular sudo Permissions for Veeam Plug-in for Proxmox VE had also been updated for 13.1.x. Make sure to update these, otherwise jobs will fail.
https://www.veeam.com/kb4701

[vnikiforov]

Hello, Anton,

Thank you for reporting on ports. We are now working on updating the documentation.

[AntonJH]

Hopefully everything will be in the docs soon.

We are having a lot of problems with 13.1 and backups seems to be failing sporadically - but for this we have opened a case to hopefully get it resolved #08184145

BR
Anton

[vnikiforov]

Hello, Anton,

User's guide section for Proxmox ports was updated to reflect recent changes.

[arausch@lydig.com]

Have any work-arounds or hotfixes been released to address this?
We've been running into similar issues where Proxmox backup jobs that were rock solid on 13.0.2 are very inconsistent on 13.1.0.
Sometimes they complete without a problem, other times they throw an error, and the errors are always very cryptic and not even the same error each time.
eg. "Error: pier ps not found"

[vnikiforov]

Hello, Andrew,

Please open a support case - that issue could have multiple root causes. It happened sometimes with 13.0 as well...