@s-master I was exporting some VMS from esxi via XO a few months ago and exporting machines with one or two drives seems to work okay. Failing that, can your esxi system export to OVA?if not, that, your clonezilla approach will probably work. Sometimes you just have to bite the bullet and start over again from scratch. It sucks, it's horrible but it is better than a half-assed copy that flakes out at you at random times.

🦆

For my usage, core count matters less than decent clock speed. But it's only my use case and indeed you might need many cores. It's just a reminder -however- that sometimes it's faster to use less cores but at faster speed.

@olivierlambert I see, seems like the GPG key for NodeJS apt repo was out, I will get this sorted and then post back this evening / tomo as to if it corrected any issues.

Adding @stormi

I think it would be more reasonable to start patching on 8.3, because it seems to be a lot of modification for a LTS. Anyway, we'll take a look and come back to you, please do the same in terms of Ceph stability in your own tests! Thanks 🙂

If it's XO from sources, check the git commit number to be sure you are latest.

Hi @brodiecyber, glad to hear that Terraform has become an important part of your workflow with XO 🙂

To @olivierlambert's point, the projects needed to implement a terraform provider (terraform-plugin sdk and the terraform-plugin-framework) have not been relicensed. Unless that occurs, which I think is extremely unlikely, there will be no impact for the Xen Orchestra terraform provider. The OpenTofu team also believes that the terraform provider interface will not be changed in their FAQ:

Does OpenTofu work with all the providers Terraform works with?
OpenTofu will not have its own providers. Terraform providers have not altered their licenses, and the potential for such a change is virtually zero. OpenTofu will work with the current Terraform providers, but it will use a separate registry.

I would like to have testing coverage across OpenTofu and terraform to catch any discrepancies. There isn't a timeline for accomplishing that, but that is my current thinking.

hi @ricky222

the structure of the backup repository is documented here https://github.com/vatesfr/xen-orchestra/tree/master/%40xen-orchestra/backups/docs/VM backups .

Checking if a backup is done/running can be done with the XO rest api from https://xen-orchestra.com/docs/restapi.html

You can go confidently with rsync/rclone for the full backups ( the xva files ). For restoration you can even use the import VM function of XO or xo-cli to directly import the xva. If you rsync data back from rsync to a local backup repository, you must delete the local cache.json.gsz to ensure XO see the downloaded backup (xva + hash + json)

The caveat is for the incremental backup and the merging. In XO we are merging older incremental backups, that means modifying older files. This process is offloaded to another node process which does not appear for now in the api. Making a transfer during a merge may lead to an invalid backup on target.

Do you have enough informations ? Also, it could be great if you share your setup when you have a working/tested setup with rsync

Regards

Haha yeah, it's an usual mistake I'm often doing myself 😆

Yes, if you removed the master without tell it to transition the master role to another machine, you have to promote manually your current slave if your "old master" isn't there anymore 🙂

Hi,

That's weird. do you have the same view in Xen Orchestra? Can you screeshot htop in the Dom0?