Topics created by Forza

No, it's useless on Linux.

Thanks!

I tried the ESC option but could never get it to work. I thing the UEFI is set to 0s waiting time for boot options, which makes it tricky to time it.

@Forza No, it's not possible to add multiple hosts of the same pool to XO.

Indeed, that makes sense now 🙂

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

You can only if you select Cloud init.

@Danp the first backup after the fix will show the warning ( since it controls the data of the previous backup)
the following backups should be ok

Great. Thanks for checking this. 🙂

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

Feel free to ask for a feature request, as long it's well described in terms of the "what I need" functionally 🙂

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

That's why compressing the full isn't trivial.

@olivierlambert said in Alerts in XO/XOA?:

it's in your dashboard view.

Do you mean the Alarms section? It is not showing anything for me. There is no log showing past events.

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

@julien-f said in Force full backup vs Full backup interval:

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

@julien-f any opinion on this?

@olivierlambert said in Backup does not work if one host in the pool is offline:

When you connect to a working, machine, yes it does 🙂

But XAPI connection isn't persistent: it means, when the pool is disconnected, XO has no recollection whatsoever on who was the "real" master the last time it was connected. The only info we store is the IP address you entered in Settings/server.

I agree, functionally speaking, it can be limiting in your case. A viable option would be to save all existing hosts IPs in the XO database, as fallback if we can't connect to the IP you entered. This is not a very common case, that's why it wasn't done before 🙂

Looks like a good suggestion. Thanks.

In my case I migrated everything from the poolmaster to the second host, then changed the second host to pool master, waited an hour and then shut down the old pool master (now just a pool member). XOA was online during the entire process and I had forgotten to check the server list. 🙂

I created an issue on https://gitlab.alpinelinux.org/alpine/aports/-/issues/13506 to track this.

Ok, let me know 🙂

@marcungeschikts Yes, it's the third point of the GitHub issue 🙂