@JB @gregbinsd @olivierlambert Yes restarting the tool stack works for me. I currently do not have any host offline at least not intentionally. If there is a network glitch that i am not aware of that might cause the issue if that is the actual cause. As @olivierlambert stated maybe we were having issues all along and they just changed something that is making the issue visible now. The support tunnel should still be open on my environment if you or the team want to look at logs.

I have also opened a support ticket with Veeam. Well trying to... Issue with my account preventing me to and working to fix that issue. Veeam forum did make this statment about CBT and snapshots - There is one known snapshot issue that I'm guessing could possibly have this side-effect (noted in the release notes BTW). We take standard Xen snapshots for CBT but then immediately rename them with our own naming convention. We've noticed that sometimes this rename operation returns success status even if it fails. In this case I can see how this might throw this sort of error but again best to confirm w/support Veeam support ticket - 08188639

Ping @Team-OS-Platform-Release

@irtaza9 Hi ! My instinct says it can be due to XAPI timeout: https://docs.xcp-ng.org/management/manage-locally/api/#24h-task-timeout

@andriy.sultanov said: I'll try to see why other devices are omitted and how this can be fixed. Any news on this? I have been fighting with getting an Intel Arc Pro B50 to work on Linux for months and i suspect that, the fact that the audio device isn't present, is what makes Linux fail to load the driver correctly. Going the xen-cmdline way, seams to disable xe passthrough both in command line and in XO gui, causing all kinds of issues. Windows seems to be able to initialise the GPU driver without the audio device, but it is in some kind of borked state. You can send workload to the GPU but the drivers are complaining about "no-pci compatibility". XCP-ng 8.3 (latest patches) Fedora server 44 - Kernel 7.1.5-201 on latest Arc firmware as well.

Hello all, Version 9.2.350 Release of the Windows guest tools has been released. Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases It will be integrated into the XCP-ng built-in tools ISO after a test period of 2 weeks. This major release brings a new Windows guest agent with many new features, plus multiple other improvements. To download XenClean, click here. The installer downloads also includes a copy of XenClean and XenBootFix. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Remember to carefully read XenClean docs before use. Note: Always download the latest XenClean/XenBootFix from https://github.com/xcp-ng/win-pv-drivers/releases Before installing Thank you for using our Windows PV tools. Please carefully read the instructions below. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing. Changes since 9.1.200 NEW: Overhauled Windows guest agent with many new features: Supports configuring guest IP addresses from within the host using xe vif-configure-ipv4 and xe vif-configure-ipv6. Session agent now gains a tray icon and About dialog. Improved clipboard sync stability and accuracy. Better reporting of OS versions. Time sync is now integrated with W32Time. NTP is now the only recommended setup for time sync on XCP-ng Windows guests. Improved: Update XSTDVGA to v0.1.211.1039; improve compatibility. Improved: Better reporting of IPv6 addresses. Fixed: Better network stability during high load. Fixed: Storage driver bug fixes. Fixed: Better installer resilience when the offboard task is pending. Help / Community support If you encounter installation/uninstallation errors, please try again with one of the following commands: For installing: msiexec.exe /i XenTools-x64.msi /log install.log For uninstalling: msiexec.exe /x XenTools-x64.msi /log uninstall.log Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues. Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated. Discussion: https://xcp-ng.org/forum (preferred) Issue Tracker: https://github.com/xcp-ng/xcp/issues IRC: #xcp-ng and #xcp-ng-dev on irc.freenode.net Full Changelog: https://github.com/xcp-ng/win-pv-drivers/compare/v9.1.200...v9.2.350 Original build: https://github.com/xcp-ng/win-pv-drivers/actions/runs/31088530595

So I ended up going with the Windows B&R as i could net setup the windows mount server when setting up the repo for the backups. It would setup the linux one but not the windows one. This was with using the veeam console from a windows client. So i ended up with the Windows one. Now after a few backups i am see this warning / error.... 8/5/2026 5:34:50 PM Warning : Failed to use CBT: [Task e75c4247-2ee1-7b51-088c-b970ace60f3d (Async.VDI.list_changed_blocks) failed: . SR_BACKEND_FAILURE_460. . Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated] First i thought it was because i maped the new job to older backups from Beta v1. So i purged all old backups and started fresh. The full backups were successful. Now on first delta 4 out of 7 vms have that warrning. This a Veeam issue or xcp-ng?