I have found that making a new remote to the same bucket with a different directory gave the same error. I also tried restarting Xen Orchestra in case there was an old task that was stuck etc.

I have managed to get this backup to work via the same newer remote but targeting a new bucket with one directory inside.

Odd because the other older bucket jobs are working. Worth noting other potential factors on the older bucket; there is a lifecycle policy in place on the older wasabi bucket. This reduced Wasabi's versioning files within a time period where no available restores were listed in Xen Orchestra. We have object lock and versioning turned on for immutable backups in Wasabi. The backups in that bucket were not being reduced automatically by Xen Orchestra and the size had gone over 100TB when retention was 15 backups total & should've started dropping the older files. The bucket size has since reduced down to about 40TB now and we're looking to further optimise the backups across our whole infra.

If there are other suggestions I can go test them later but just noting what we're doing and how I've worked around the issue to keep the backup running when getting this error.

@olivierlambert Hey Olivier, thanks for replying! We are using Wasabi buckets.

Hi all,

I've had a VM with a backup job to S3 storage get this error (the same error also appears on retry):

"Invalid RFC7231 date-time value 2026-09-15T16:44:47Z. Deserialization error: to see the raw response, inspect the hidden field {error}.$response on this object."

Host and VM time are correct. S3 remote test works.
Other backups to the same bucket, different folder and different remote do work.
The snapshot gets created but is deleted after around 5-10seconds on the retry.
I can make a new remote to a new folder in the bucket and attempt other troubleshooting steps, just thought I'd mention this one in case it helps others because I did not find much of a record for it in the documentation or searches.

Has anyone seen the error before? Let me know if you need more info on this.

Thanks,

J

@olivierlambert said in Netbox 4.3 not supported:

Ping @pdonias

Looks like this keeps happening because of Netbox! - Have you experienced a lot of issues if we force it to work with newer versions, I understand there's potential data loss but just wondered if it had been observed to cause major issues with data loss recently? I am considering doing this on ours. Just working out where I need to put the change!

@Greg_E Thanks for the update Greg! OK will keep going on mine. I had found some issues with one of the file servers which the testing was using so that could have caused my speed issues. I reckon I'll do domain/forest later on too but bring in user facing 2025 desktops first. I'm getting rid of folder redirection with One Drive known folders in its place then will be able to investigate Intune after that for round 2 of desktop updates! Good luck on your end.

@Greg_E Interesting to read through when having performance issues on my end too albeit not running ADDS on windows server 2025. Did you decide to upgrade your production system?
I'm building a new Citrix multi session image but have found many things "not responding" e.g. file explorer slowness and just opening task manager. I could be having different issues to you all and would need to provide more detailed info but working through the forums here and on Microsoft end to see what I can find against this OS and how the rollout is going. Any feedback on Windows Server 2025 would be great here unless we have another more suitable thread to follow.
Thanks.