Posts made by olivierlambert

It depends on what you need, only you is able to answer that.

It's using Amazon S3 JS library, IDK if it's compatible with S3.

@vmpr Please create an issue on Xen Orchestra GitHub repo, this way XO dev will see it

XO docs contains a good overview of all features: https://xen-orchestra.com/docs/

Please take time to read stuff before asking

You can do it manually yes When @fohdeesha is around it could give you a quick guide but most of what's require to do is available on Google (we have a blog post here: https://xen-orchestra.com/blog/debian-cloud-template-for-xenserver/ )

This is for @r1 I suppose

I said in XOA, not XO from the sources. XOA Free got it

This is a question for @julien-f

XO (in fact, its server part, not the browser client) is meant to run 24/7, as a service/daemon.

As long as XO is the same network of your pool, it's fine. If you access XO behind a NAT, it's not a problem. But xo-server MUST be in the host network.

That might be interesting info for @r1

I don't think intellicache is doing what you expect exactly. Try NFS in async mode to see if it's better.

From Citrix doc:

IntelliCache works by caching data from a VMs parent VDI in local storage on the VM host. This local cache is then populated as data is read from the parent VDI. When many VMs share a common parent VDI, a VM can use the data read into the cache from another VM. Further access to the master image on shared storage is not required.

I suppose this is not what you require.

Yep, if it was an XCP-ng issue, it would also fails with xe command.

Noted. Pinging @julien-f

Don't we have already some webhooks? Anyway, the VDI.snapshot method can be done in one or 2 releases, might worth to wait anyway

edit: we have indeed webhooks but for jobs, I wonder it might be trivial to get them for backup

Ping @nraynaud

[NOBAK] works, at the transfer level. It means, the disk will be snapshot, but the data won't be export to the backup.

It's due to the fact we use VM.snapshot method that doesn't allow to make a VM snapshot by excluding disks.

We have an alternative in the pipes, working directly on disk level snapshot (VDI.snapshot) that will solve this.

In XOA, Hub category.

I have the feeling there's a connection between those snapshots and the error.

Could you deploy an XOA, open a support tunnel so we can take a look?

Do you have snapshots for this VM?

Do you have any CD plug to this VM?