@florent They are set to 30GB, but thinned provisioned, so they might be a less than that.

@florent OK gotcha, I figured this was the case. So best option would be to create a new backup job, encrypt that to a new remote, then go back and delete all the old stuff when ready?

@florent what if we use XO Proxies ?

I worked around this issue by changing my full backup job to "delta backup" and enabling "force full backup" in the schedule options. Delta backup seems more reliable as of now. Looking forward to a fix as Zstd compression is an appealing feature of the full backup method.

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

as @MBNext stated disabling Purge snapshot data when using CBT worked for me.

@Forza We plan to make it configurable during the upcoming months.

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

@olivierlambert Host started and issue resolved.

Question for @pierrebrunet I assume

@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

@olivierlambert Here's the new model. We've tried a few combinations and I think with TrueNAS shared storage this will now work well. [image: 1759787234216-f78178c0-3330-4233-8f9b-debc3c61a3e9-image.png]