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.
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)
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?
In XO i used the option -o vers=4 and this works.