Posts made by probain

Looking a tiny bit further. The same discrepancy is present with Disaster recovery too. Being reference as Full Replication (formerly: Disaster recovery)

XO and the docs are conflicting with each other, with what the backup function should actually be called. See attached pic for example.

This is truly a niche sittuation. But I noticed that when I have VMs without any disks attached. The Rolling Snapshot schedule doesn't remove snapshots in accordance to the schedules Snapshot retention.

So I'm guessing that the schedule only looks at cleaning up snapshots of disks. But since the snapshots are acctually of the entire VM. Then maybe this should be takin into account as well?

If this is working as intended, then just ignore this post

I finally have some new hardware to play with. And I'm noticing that the Healtcheck fails, due to the vGPU being busy with the acctual host.

INTERNAL_ERROR(xenopsd internal error: Cannot_add(0000:81:00.0, Xenctrlext.Unix_error(4, "16: Device or resource busy")))

My suggestion is that for the sake of Healthchecks should unassign any attached PCIe devices. If it is crucial that they are attached, then maybe have an opt-in checkbox either in the VM or next to the Healthcheck portion of backups?

The address field doesn't trim trailing whitespace. Not a big deal breaker. But it did take me a couple of minutes until I found out why my copy/paste address was giving me errors

I'm unsure if Threadripper is affected. But the EPYCs have a problem with networking speeds. And I'm quite sure they haven't found the root cause yet,

Epyc VM to VM networking slow

@Houbsi
what NAS are you using?

I've acctually got a PR to help solve the documentation regarding the yarn forever part. Since I never could get that to work, I implemented a systemd variant instead.

#7848

Ping @olivierlambert for visibility

@zach
XCP-ng is unfortunately quite slow on individual streams for storage. It kind of disappears when using lots of VMs. But looking at any one individual one, it is surprising.

A good read is the write up on Understanding the storage stack in XCP-ng

@ludovic78
In the case of such a power outage, the backup would fail anyway.
And I'm also assuming that you have a separate share/dataset for those specific backups.
Coble it together with the Health Checks, and it is semi-production at least.
If it is for such a highly critical environment, that it wouldn't tolerate more than that. Then obviously you should open a support ticket

@ludovic78
Try and set the Sync-setting to Disabled, on the target dataset that you're sharing. See if that does any difference.

This makes a GIANT difference for me.

@jasonnix
Yeah that folder can fill up quite heavily.
See the following on how to clear the cache with yarn
https://yarnpkg.com/cli/cache/clean

@olivierlambert
PR #7846

@olivierlambert If I could get a pointer as to which source-document we're talking about. Then yes, I could whip something up.

I've managed to get this working to a 93% satisfactory state. Techincally I get SAML working. However, when the login is authorized, it just kicks the user (me) back to the login page. However, manually going to the bare URL (https://xo.company.net), takes the login further.

I'm sharing sanitized screenshots below for how to get this to work. XO<->Google Workspace SAML.
@olivierlambert Maybe this can be of use to further flesh out the minimalistic section for SAML within the docs?

Sorry for the screenshots being huge. But they're better than nothing.

@JamfoFL I'm still guessing cache.. Could try in incognito mode.
OR... you got a broken URL. I can replicate similar stuff if I do bad things with the address.
e.g.
Browse to https://<xo.example.net>/signin
Try https://<xo.example.net>/signin/callback
Continue to https://<xo.example.net>/signin again
The sign in page is now borked. And the page needs to be closed, and open in a new window/tab instead.

But it might not be the same as what you're experiencing.

@JamfoFL Cleared cache?

Scenario:
Backups are done to a (remote/networked/local) SR. The filesystem on the SR has features enabled e.g. ZFS Block Cloning. Having support for using reflink=always (or similar) would enable near instant replications of any copied data. I.e a Health Check is done. Another benefit would be that the data blocks being tested in said Health Check, would be the actual data blocks of the backup e.g. Disaster Recovery.

Now my guess is that the VDIs are being migrated/imported through XAPI. And therefore would probably need upstream implementation. But as the title mentions, this is only a idea/suggestion/wish.

ZFS has the block cloning. BTRFS and other filesystems have similar advanced features. This could greatly improve perceived speeds far beyond what is currently being seen.

Two cents deposited.
Thanks for this great software.