Hi @jshiells, After some tests, I don't think it can be caused by the load balancer. If the load balancer tries to migrate a VM that is being backed up, the migration instantly fails and nothing happens. Reversely, if a backup job starts when a VM is being migrated by the load balancer, the backup will fail for that VM with error "cannot backup a VM currently being migrated".

https://forums.veeam.com/kvm-rhv-olvm-pve-schc-f62/xcp-ng-not-showing-as-virtualization-source-after-restore-t101040.html Et voilà suffit de demander

@Pilow You might be right, this may be simpler to implement than we imagined. We'll keep you informed when we progress on this.

Thanks @Pilow for the test

For completeness sake. Confirming that the fix also works in my second lab as well.

@Bastien-Nollet nice !

@florent turning off CBT removed the "fall back" message but my Delta backup is still doing full backups.

\o/

@planedrop yes

I had to disable Purge snapshot data when using CBT. Backups are not longer defaulting to full backups.

Just connect your XOA to your dedicated network and it will flow to it.

@olivierlambert Host started and issue resolved.

@olivierlambert Thanks that worked. Kind of obvious approach, still didn't try that

Are you sure the job isn't already running, as per the error message?

Backup job still failing. I have open a support ticket - Ticket#7746281

@stevewest15 I believe this issue was resolved when the health check system was changed to detect network connectivity at startup so it did not need to wait for then entire VM to boot. Needs the Xen tools to be installed. I have not had an issue since this change.

This look great! Something I was missing. But unfortunately I get an authentication error as well. I do not get it running. I am using PowerShell 7.5 and I am using a cert that is singed by my own CA. This CA is included in the Windows cert store for trusted root certificates. With all browser this works fine. Hopefully someone has an idea?

@olivierlambert minor update... its now been 48+ hours and task is still in the same state, not timed out yet.