Inexplicably, now it's decided to start working right. I didn't do anything to the existing backup job. [image: 1717691279000-f8c9acb1-b4ca-4486-8dfe-b957b94055f3-image.png] I'm glad it seems to be working now but I wish I understood why it wasn't working previously. That makes me nervous that it could stop working in the future without notice. The only real difference is that I set up a brand new set of VMs to be backed up in the same way to the same remotes using two new backup plans. I guess this is kinda solved...

@Danp That's the same image I referenced but with everything at a single site. I'm looking for details regarding the hosts and SRs. In the documentation that's all hidden inside that green XenServer XCP-ng box. My concurrency is only 1 right now because I'm trying to find my bottleneck. Regardless of what it's set to, I'm stuck at ~150MBps for the whole backup job. But that's just what the UI reports. Looking at the network stats I see different things moving anywhere from ~50MBps to over 500MBps.

@Andrew Awesome, thanks

@sshughes When you go to 'Home > Hosts > YourRestoreHost > Tab:Network' in XO, is eth1 shown there? If not, it might need introduction.

@olivierlambert yes those 10 in the previous picture are the hosts from this pool

Can you write exactly what you would expect to be written as a "pre written" text?

@wtdrisco we are testing with alike A3 from Quadric software, it is a good solution as well, they have a lot of experience with xenserver and xcp as well, they also have builtin deduplication.

A good specification is always better to do things correctly (and to estimate the work needed)

Usually this error is caused by the merge process still running in the background from a previous backup job.

@Danp Hi! Yes, this is working, but there seems to be no alert or "delete-schedule" for those backups

@lawrencesystems Excellent, that's what I was hoping to confirm.

If a schedule parameter to ignore NOBAK is fine since you can create an extra schedule in the same job, that should be doable. What do you think @florent ?

Hi, You can't tell XCP-ng to push a VM disk to a backup repository, it doesn't work that way.

Since 2020, we added pool metadata restore for exactly this It should be really straightforward. The best way to validate it, is to use an experimental host, backup metadata, then reinstall a fresh XCP-ng from scratch on top of it, and then restore the metadata. That should work out of the box

@archw Scratch that one.....I should have googled first. I saw that someone suggested deleting the cache.json.gz file. I did and ran it again and it worked.

@olivierlambert that does look interesting. I really need to find a way to make it work over scp/sftp unless you have an in with rsync.net and can get them to add an S3-compatible service It's not really practical to make a move to an S3 provider at this time; we are 230 TB into rsync.net for a damn good price with no extra charges for data ingress or egress. If I add VM backup, the additional 10+ terabytes are a drop in the bucket of the overall usage.