@Danp Hi, I just updated the commit via a git pull and a yarn build. Here is the commit version: 'Xen Orchestra, commit da84a'. I tried to restore the VMs again, but I still encounter the same error. Expected values to be strictly equal: + actual - expected + '8d1c3759-e958-465f-a018-87afc098642f' - 'fed97090-e59f-43e4-adad-3bb8ba8716f2' Knowing that I have the VHDs in my possession, is it possible to restore the full .VHD with the Deltas? I tried importing the full VHD via the web browser import, but after 20 minutes, the loading gets canceled. Is it possible to do this via the CLI? If you have any documentation on this, I'd appreciate it Thank you very much. Itayal

Hello all! It should be fixed https://github.com/vatesfr/xen-orchestra/commit/72592a54d2225d5368a3410e4b3c19039f8e5df1 0 b-Nollet committed to vatesfr/xen-orchestra fix(backups): correctly update allowed_operations - temporary fix (#7924) Fixes https://xcp-ng.org/forum/post/81327 `allowed_operations` are currently not updated correctly when `blocked_operations` are modified, which causes backup jobs to remove `migrate_send` and `pool_migrate` from VM's `allowed_operations`. This commit fixes that, until `allowed_operations` updates correctly again.

@olivierlambert Yes, once CBT with Snapshot purge is production ready that will totally solve our problem! Perhaps its better to just wait for that. I wondered if they were doing something like a partial restore of the metadata as well.

@olivierlambert Thank your for poiting this out! Very much apreciated!

Exactly what @nick-lloyd said, it is important to backup XO configuration AND the pool metadata as well to be able to recovery completely.

@ph7 thanks guys!

As an update here, rebooting did resolve the issue, I thought I did so shortly after I did the restore but maybe I forgot to do so. Anyway, rebooted yesterday and the backups ran last night just as they should.

Perfect, thank you

@norrisson I don't believe so. I think I just built a new VM to replace it.

@olivierlambert Thanks. I will do that. I did bump the memory up to 12GiB and the backup ran successfully but I will pursue a ticket with the 3rd party script maker as well. Thank you for your time!

@codenin Is the NAS something local or are you hosting a NAS in Azure? I guess I just got a bit confused by the mention of Azure here. Usually, with cloud providers, you want to use their services more than just directly hosting something there. So for file storage, either S3 compatible blob storage, or using one of their file share services that exposes SMB or NFS.

Your backup is a stream, doing backupressure (or not). As explained in the linked topic, it depends on dozens of different parameters. You might try to use NBD with 4 concurrent download, that might be better though, because I'm betting your bottleneck is likely XAPI export speed.

They are able, but not at a great speed. It doesn't matter how many cores, it's likely heavily single threaded and relying on how fast you can do many efficient instructions per cycle. That's why you should switch to CR.

Ping @florent

Depending on the size of your backup repo you can copy the whole disk repo to tape with tar. So you have a desaster-backup. You can also span mutiple tapes with tar. https://www.gnu.org/software/tar/manual/html_section/Using-Multiple-Tapes.html

You shouldn't run anything other than the last commit as possible (which is de934ec609b1bfb48cd598de8b096a6b4cf1f963 now).

At a certain point, I don't know when because we are talking about a home lab here. I could attach the USB HDD same as a virtual HDD and I could put exclusions on it