@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.

@olivierlambert Sure It was just a question I know WE don't have same infra or feature IS not vmware but thé stack IS really good and interesting And i Saw Comvault IS compatible with your stack and WE will replace networker with Comvault during next year

@planedrop I usually don't use SMB for remotes - prefer for stability reasons NFS. But in the past on customer systems we had, from time to time, the problem that the SMB Client/Server (both had the problem, so it might be the case that they stalled each other) processes stalled for a moment, which might cause that file locks are not set or ended correctly. Maybe it's something like this in your case too. Catching that is a bit of a pain in the *** , because you need to do process memory tracking on both sides to see if and when they stall for a short moment. Not sure if there is a way under TrueNAS to check if a file has a lock set or not. If possible it might be already enough to remove the lock of the file (if possible via cli) to make it visible to the XCP-NG host again.

Yeah it sounds that the merge on the backup side can't succeed since the chain seems corrupted.