Topics created by Andrew

@olivierlambert @julien-f 61691ac46b50659f05159594b8c672b6187a9f9c causes my S3 backup failures.

packages/vhd-lib/Vhd/VhdDirectory.js childBlockPath === undefined

@Andrew Hi Andrew,

Metadata backup use the report plugin settings to send mail so you can define the email address there.

@julien-f Much better! I can add servers/remotes/jobs again. Thanks!

@Andrew it seems that the merge fails but the watcher still report progress ( which doesn't move)

Can you see if there is an error before ?

Thank you, that fix worked.

@julien-f Restore showed that there were backups even when it said it failed.... I did not test one, sorry.

I deleted the snapshots and old backup data which forced a full backup to S3 and XO was happy. A delta backup after that was also successful.

@julien-f Thanks. I'll post an update if I hit the problem again.

Thank you!

Thanks for your feedback @Andrew !

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

It's hard to know exactly: is it something we can see on XO's side or not? I can't tell. Maybe SMlog got more info at the time the VM snapshot is removed.

Backup autorestore for basic tests is already planned and should be out this quarter 🙂 @florent is the one working on it (he started to do some basic tests).

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

That's a question for @julien-f

Congrats @Andrew : you are now noted as a top contributor 💪

Thank you and all your efforts on S3 testing and reporting issues a lot!

I don't think you can reset power state with XCP-ng Center 🤔

@andrew It's now fixed, thank you 🙂

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.