I/O error on a sector is usually due to something between your XOA and the BR. It could be many things though.
I did further testing and found that I can reproduce the issue. While the file-restore dialogue is open, it is possible to access the files via XOA console in /tmp/<xxxx mountpoint>/, but as soon as you press "OK" the access to the disk disappears and all processes trying the mount point freeze. I reported the exact details in the ticket.
a case for this: have a lot old, disabled vms with some archive data\projects. Probably they will never be used again, but who knows. So i create 1 full backup, but when yet one vm go to archive, i need to run that task for all vms.
@Hightmar Excellent to see, yeah this worked well for me on the 2060 and have been using it on Jellyfin for a while now without any crashes or other odd behavior.
No sure this will be compatible with the level of memory isolation provided in Xen (vs the more "open bar" model in KVM). Worth taking a look though, thanks for the link.
@mersper Thank you. I will re-think the setup. Having 256 threads in one VM isn't perhaps possible. I have scheduled a meeting with the software manufacturer to talk about network rendering etc. It might be better to have serveral VMs with pinned CPUs and run render jobs. I'll update on the progress 😃
@olivierlambert Yea, I have bonded networks. I do rename them so that I know what they are for. It seems that the bond number (bond 1 and bond 0) changes on different servers, as I asked about before, so the name and description is needed here to make it easier.
That's correct. It's the new "reference" for the following delta, so we need to be able to read the full when we restore the backup (or a file) or when we coalesce (when reaching the retention).
@s-pam Yes indeed, this link is currently broken because of the new support platform. Thanks for the feedback, our team will fix it as soon as possible. 🙂
@s-pam Essentially the same feature, they force the export of a full backup.
Full backup interval forces a full after a number of delta exports.
Force full backup forces a full when this specific schedule is ran, which allows for instance to do delta during the week and a full on Sunday.
Ah, of course. So I can add a second schedule to the backup job, and in that I choose force full. 🙂 nice. I did try to search in the https://xen-orchestra.com/docs/backups.html docs for it before asking.