Yes, in this case it will be "live storage motion" (ie migrating with the storage, because you don't have a shared storage).

Note that you should add the server to the pool first, and then only add VMs on local storage. Because when you add a new host to a pool, all the existing storage/VMs will be removed (VMs on the new hosts)

Thanks. I guessed that I needed to put the full path on FreeNAS as there is not masking when expose as NSF by FreeNAS. So I put the full path as "/mnt/MybooksVolume/VM_ISOs" and that seems to have fixed the problem.

It's an admin privilege.

i don't use it cause i work only with mac. this is the reason why i get xoa.
... in the xencenter on windows it works normally.

but i try this on different browsers. the problem is the same

Migrate it to the host that will be the master (even local storage of the master). Then you can add any slave.

IIRC we have something in the pipes to solve this, but not yet. Please open a support ticket so we can continue discuss with more details related to your infrastructure 🙂

@olivierlambert issue created
https://github.com/vatesfr/xen-orchestra/issues/4515

abaughGHW created this issue in vatesfr/xen-orchestra open Support IPv6 in IP pool #4515

Please refer to https://github.com/vatesfr/xen-orchestra/issues/4455

olivierlambert created this issue in vatesfr/xen-orchestra closed Migrate VDI from SR view #4455

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 🙂