Hi @KPS , The difference between these two settings is that sessionCookieValidity determines the time before a user gets disconnected if they did not check the "Remember me" option, and permanentCookieValidity determines this when this option was checked. If you want to force users to be disconnected after 12 hours regardless of how they connected, I think you need to set both sessionCookieValidity = '12 hours' and permanentCookieValidity = '12 hours'. However, this memory increase you're experiencing is intriguing, it is not an intended behaviour.

As Mathieu answered in this topic, the bug has been reproduced on our side but isn't trivial to fix. We'll discuss with the team to schedule this task, and we'll keep you informed when it's fixed.

@DavidMrLane said in Where to find the health-check results: The tasks log doesn't tell you which VM was health checked. If you click the Open raw log button, it will give you the details on the request, including the UUID of the VM being tested -- { "id": "0m2dmjnnh", "properties": { "name": "VM Backup Health Check", "objectId": "remote-2//xo-vm-backups/92832a7e-e72d-2d02-6a25-9802f1c24072/20241017T050741Z.json", "userId": "3b480e98-af4e-4dbf-9f1e-29ac59d6364f", "type": "backup.vm.healthCheck" }, "start": 1729189103741, "status": "success", "updatedAt": 1729189318550, "end": 1729189318550 } In this case, the VM's UUID is 92832a7e-e72d-2d02-6a25-9802f1c24072, and you can paste this value into the filter when viewing the VM list in XO to find the exact VM involved.

I don't think it's a good approach, BR weren't meant for that. If you want to send them offsite, mirror backup is the best option. About immutability, we have an external program doing it if you want.

@olivierlambert I will try to... Perhaps, it is related to the untrusted certificate of my installation.

@olivierlambert There is only "Dashboard/Alarms" and that is empty for me

Yes, you can ignore static min, 99% of the time it's not relevant.

@KPS it should be "yes" of course. Typo!

@KPS I don't know why my brain has decided to index all the xcp-ng forum, so when I read your post, I immediately remember the post with the clonezilla issue

Not a problem, something to be done correctly, and not implemented at all in the current XCP-ng API. In other words, it's not trivial You can create an issue in XO repo with all the details (and the screenshot), this at least needs some serious work to find what would be the best approach (and then sorted from our backlog)

Hi, I think that's a XAPI behavior, I'm not sure it's propagated when the VM is migrated. You might ask upstream XAPI project about this

There's no stupid questions, only bad UX/UI

I don't see the reason, the UUID is completely internal to XAPI. You might want to compare the 2 objects (like doing a diff between 2x xe vdi param list)

Ping @florent

Hi, See https://github.com/vatesfr/xen-orchestra/issues/7569 ep1p created this issue in vatesfr/xen-orchestra closed Backup of metadata is missing settings options for reporting failures. #7569

@KPS Because you changed the virtual hardware when disabling the option.Windows now see xcp-ng pci devices instead of Citrix pci devices, and you dont have the xcp-ng drivers installed - i.e. blue screen during boot because Windows cannot access the virtual harddisk.