https://github.com/vatesfr/xen-orchestra/issues/4467

pdonias created this issue in vatesfr/xen-orchestra closed Hide legacy backup menu entry #4467

For example, xo-server crashed/interrupted/restarted during the export.

@olivierlambert said in Continuous Replication fails with VDI_IO_ERROR(Device I/O errors) on fresh XOA install after XenServer 7.2 -> XCP-ng 8.0 upgrade:

To your config file, yes. Where this config file is depends on where do you installed Xen Orchestra (I suppose from the sources, so I can't guess where do you installed, could be anyware 😉 )

edit: I think it's fixed now and integrated by default in the config

Great, this fix already is in the new version.
I was having this problem (Error: VDI_IO_ERROR(Device I/O errors)) and was not be able to do CR of my VMs but now CR works.
Thank you

PS: BTW that was my config file 😉

So copy/paste won't work in this case. We are adding soon a link in the console page to open with ssh (eg: ssh://VMURL)

I think that scrolling is passed to the VM, you can test with on a VM with a X server or Windows.

@akurzawa
OK then I know 🙂

@axiom00

Thank you for your answer, this worked great.
Was able to clean the entire list of old versions this way.

@olivierlambert

xcp-ng Center displays it properly, so yeah, it must be the way XO is pulling data.

cpu.jpg

Oh well. Not a big deal. Just was curious. Thanks Olivier!

When you click on the link of the error message it should send you to the official documentation, explaining what it means: https://xen-orchestra.com/docs/backup_troubleshooting.html#error-messages

I'm not sure to understand the UI question, can you post a screenshot?

@jedimarcus You were right

[root@XCP02 ~]# xe vm-list is-a-snapshot=false | grep 29_ name-label ( RW): 29_Hades

@Danp

[root@XCP02 ~]# xe vm-list params=name-label,uuid,other-config uuid=c2ae0376-b164-1d63-5c9a-e90a6be4cfbc uuid ( RO) : c2ae0376-b164-1d63-5c9a-e90a6be4cfbc name-label ( RW): 29_zeus-file-archive_2019-08-08T13:36:58.771Z other-config (MRW): base_template_name: Debian Stretch 9.0; import_task: OpaqueRef:c1020902-7587-47fd-9035-ad97d0f82c99; mac_seed: 06e28f1e-e6b0-3a82-1d50-33414ceea41e; install-methods: cdrom,nfs,http,ftp; linux_template: true

ok thank You guys.

Yeah I would say that's the more logical solution in the end 🙂

Do you mean to say when you edit the network config box, and fill it out with your own network info (adhering to this standard: https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v1.html) that cloudinit in the vm gives a yaml error? This indicates the way you filled out the entry box is not properly formatted. Keep in mind to pass networking info, your cloudinit install in your template VM needs to be set to use nocloud data sources, and keep in mind the network configuration passed via cloud-init is added to the template VM, not replaced, so you need to properly configure your template VM to not already have adapters configured with IP addresses etc

Yes, you are right infact the old instances are halted and are temporarily kept till I am not sure the imported ones are perfectly working on new node. Unfortunately in the meantime I need a way to manage boths and it means xencenter or cli. Thanks for having pointed my attention to the duplicated uiids problem.

See me previous post here -- https://xen-orchestra.com/forum/post/5072

I'm guessing that you were missing the symlinks for the plugins, otherwise they should have been present in XO.

Thank you, @olivierlambert, for all you do here.

Great! Your team proves just how legendary it is once again! Thank you!

I think the simplest way to just do this once is to go to Settings > Config, there you can export the backup. Once you create your new instance of XOCE, you can import the backup using the same page, then just logout of the default user, and you can login using your old credentials. Make sure to delete the admin@admin.net account after.

So you can't create a backup with XOA Free. This edition is meant for all usual administrative tasks, like XCP-ng Center if you like.

If you want backup features, 2 choices:

going for XOA Starter, Enterprise or Premium depending on your backup needs. See each edition features here: https://xen-orchestra.com/#!/featuresmatrix (each edition comes with pro support, updater and remote SSH access if needed) install XO from the sources on a system you like, following our guide: https://xen-orchestra.com/docs/from_the_sources.html

@axel I just ran the installation script on a Debian 10 VM and it worked as expected. 🤷

Even when using the "official" way, sometimes the installation can fail due to things like --

issues with recent commit to github repo issues with upstream dependency etc

This is why the pre-built XOA appliance exists. 😸

Feel free to open an issue over on the script's Github repo if you continue to encounter issues.

This is a 3rd party container not validated nor endorsed by XO devs. We don't know what's inside, if you have questions on it, ask on the Github repo of the maintainer Backup reports will answer your initial question/requirement (reports can be sent by email, Slack etc.) There's also a Nagios plugin, or you can use XO API to make request to be support in any software of your infrastructure Monitoring a Docker container is outside scope of XO, I would suggest to ask Docker community.

Regarding XO and how backup are done, any fresh XOA deployed (or from the sources) will be able to find all the previous backup done by an old XOA, because we store every info on the remote.