2GiB is enough. Please create a support ticket (yes you can with XOA Free) so our dedicated support team assist 🙂

Yes, setting concurrency to 1 helps me. Will try to run concurrency >1 on th pool and see how it works.
When concurrency > 1 it would be nice to split backups per-host (in case of pool) or per-SR (in case of multiple SRs)

@LEB-ID It's called Add new Server in XCP-ng Center too... old habits die hard. But Pools is not the right word either. It's hard coming up with something short and precise.

@julien-f

Done: https://github.com/vatesfr/xen-orchestra/issues/4490

ghost created this issue in vatesfr/xen-orchestra closed Allow max concurrency per VDI/disk in backup jobs #4490

@olivierlambert said in Backup-NG Error "invalid header checksum" after VM-Disk-Resize and reaching retention Limit.:

So the issue appeared just when the oldest extended delta had to be merged in the full I suppose.

This is exact, but we need to have a proper process to reproduce it.

This might be related to:

increasing the size of the disk above a certain threshold increasing the content of the disk above a certain threshold

After:
mount 192.168.10.6:/mnt/raid/nfs /mnt/jan

and i look with mount i get this:
192.168.10.6:/mnt/raid/nfs on /mnt/jan type nfs4 (rw,relatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.211.55.19,local_lock=none,addr=192.168.10.6)
So its working.

After manual typing what XO tried:
mount -t nfs 192.168.10.6:/mnt/raid/nfs/backup /mnt/jan -o vers=3

I get the same error:
mount.nfs: access denied by server while mounting 192.168.10.6:/mnt/raid/nfs/backup

So the “-o vers=3" option is the problem.
Can i edit a file in XO to get rid of the “-o vers=3” option?

SOLVED 🙂
In XO i used the option -o vers=4 and this works.

@badrAZ

Gentleman, thank you very much.. I updated and recompiled and now I get all the storages on display.

Thanks again,
Peg

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 😉

@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.