@florent It looks like the restore test failed because the connection stream failed (and did not retry). It's hard to test this particular one because it is rather large.
A good reminder to have more than one backup method (I do). I'll look for a XO update and see what changes. It is scheduled to do a full backup soon (as normal) to make sure issues like this are not a long term problem.
@florent@olivierlambert Looking at failed S3 backup problems the retry should be easy. Currently on the job report there is a button to restart all failed VM backups in that job. Can you just add an option for automatic restart failed VM backups after job completion. It can even be a separate job (just as clicking the button is). It would just "click" the restart failed VMs button once (or a setting) after a few minutes (or a setting). Or it could start the new job as pending or delayed and start after a few minutes allowing for time to cancel it.
It means the kernel tried to deference a null pointer. This generates a page fault which can't be handled in the kernel- if it's running a user task (but in kernel space), it generally makes an "Oops" which (uncleanly) kills the current task and may leak kernel resources. If it's in some other context, e.g. an interrupt, it generally causes a kernel panic.