I'm running into the same issue; all my backups since friday have failed

my deployment relies on the docker container and I was going nuts trying to troubleshoot this until I ran into this thread.

@olivierlambert

Hello, sorry to bug but I was curious on the status of this. Was there any bug fixes made to alleviate this issue?

Thanks

So should I simply be patient and wait for an update?

Or does this warrant a bug report on git?

Thanks

@olivierlambert Ah duh.

With that being said, the xcp-ng version is 8.2.0.

Sorry, I should have specified my version:

xo-server 5.84.2

xo-web 5.90.0

Hello,

I'm running into an issue and would like to understand the proper procedure for how to mitigate this going forward.

As the title suggests, increasing a VM disk size breaks a Continuous Replication backup. My backup routine consists of a rolling snapshot, which then copies to two remote SRs using the continuous replication option.

Before modifying the disk size, the backups were running perfectly and they began failing with the errors:

VDI_IO_ERROR(Device I/O errors)

and

all targets have failed, step: writer.transfer()

I know this has to do with either a VDI chain protection or a lack of SR coalesce. I did "Rescan All Disks" and it did not alleviate the issue; was I not being patient enough?

It is working since then, but my main question is am I supposed to rescan all disks after making that VM disk modification so future backup routines don't fail?

Thank you!