[BETA] [XCP-ng] XCP-ng pool master change requires manual reconfiguration in Veeam B&R

[lpolnik]

Hello,

Environment Overview
I am using a beta version of Veeam B&R downloaded via: rhv-olvm-sc-hypercore-xcp-ng-hpe-vme-f6 ... 00399.html
The lab environment consists of three XCP-ng 8.3.0 nodes configured in a High Availability (HA) pool, managed by Xen Orchestra version 5.113.2.
When adding an XCP-ng server to the Veeam Backup & Replication inventory, we specify the IP address of the host in the pool that is currently the master, and additionally configure the XCP-ng worker.

Issue Description
If the host acting as the pool master becomes unavailable, another host in the pool automatically assumes the master role. However, Veeam Backup & Replication remains configured to use the previously defined master host, which results in backup jobs failing.

Workaround
To restore backup functionality, the failed host must be removed from the Veeam inventory, and the new pool master must be added manually.

Impact
This behavior also affects planned maintenance activities. Manually transferring the pool master role to another node causes backups to stop until the Veeam configuration is updated accordingly.

[cody.ault]

Thank you for the feedback. We have seen this behavior reported before by another customer "jmannik" in "[XCP] XCP-ng support" thread on page 6: rhv-olvm-sc-hypercore-xcp-ng-hpe-vme-f6 ... 0-150.html
It is a known issue with the beta and we plan on fixing this behavior in the GA version.

[lpolnik]

Thank you for the quick response.
If any further XCP-ng–related issues come up on my side, I will continue them in the thread you mentioned.