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

Just a quick update. I tried changing the time to see if somehow doing it at midnight was causing the issue. I also tried changing the destination for the health check to restore to in case it was some issue with the HDD. Neither were successful.

@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.

Since I'm not used to using git, I was running a few tests on my "test" host. I had made a change in my "one line commando" My memory is not in best shape so I forgot the change and ran it in my update. Now It's sorted out and ran a new update and voila