The easiest solution is to change the destination CR for the replication, so it will start from scratch. I'm not sure you'll be able to move the whole chain like this (or maybe somehow manually but it will be tedious). I would go personally for a new SR target and start clean there.
Remote backup to NFS
Remote backup to NFS target which is connected to another storage server using iSCSI
Move the VM from one SR to another (on a completely different pool)
Copy the VM to another pool
@momofhlp I suspect it is a UID/GID mapping or permissions problem.
Mount the share manually no-root-squash. run a backup on that share. see what UID/GID xo expects you to use. Then set up an nfsshare for only that matching UID/GID and all should be good.
it is easiest to set it up wrong security wise with NFSv3 but easiest to make it work. Once it works, go back and switch to nfs4.1. read and weep. https://www.truenas.com/community/threads/nfs-sys-security-option.86501/
old nfs (v3) has little or no security. nfs4,1 has SYS for slightly better security. NFS4.2 + kerb5 has best security but a learning curve like:
only much much steeper. a better nfs security solution is nfs via stunnel
@Anonabhar The NAUbackup script goes in order of a list of VMs, so I can imagine it'd be easy to implement this if not already present in XCP-ng. Worst case, separate those big VMs out into a separate backup instance and offset it adequately from when the other backups run.
@techjeff Unfortunately, I do not have direct experience with that tool. I would hope it would have some way of independently staggering the startup times when they kick off.
If there is no other option, requesting a way to deal with this as an added feature seems like the best recourse.
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
Also, the issue is not due to Xen Orchestra, but when XO is trying to ask for a snapshot or your VM (Async.VM.snapshot). This VM has a disk which is not usable because likely connected to another host which is shutdown or not there.