Sync failing with "in-progress backup"

[Cayuga]

Hi,

I have two Proxmox Backup Servers where there is a regular sync job between the two. I upgrade from 1.x to 2.2 last week. Starting 4 days ago, a handful of the VMs and CTs won't sync and always fail with "in-progress backup" even though I can't see any backups running. I've rebooted both machines and still see the same message.

Any thoughts on where I should look to see what's going on or what I can do to "reset" an in-progress flag?

Thanks!

 

[dcsapak]

hi,

are there any backups not finished in the content overview on the source pbs ?

 

[Cayuga]

A little more information that might help. I've noticed that I occasionally see

group lock failed: unable to acquire lock on backup group directory - another backup is already running​

even though none of the Proxmox nodes have any vzdump processes running.

Also, while some of the sync's fail as described above, many VMs/CTs sync just fine.

hi,

are there any backups not finished in the content overview on the source pbs ?

There are no backups "running" or "tasks" that correspond, but when I look at the GUI, I see backups that are "spinning" . If I remove them, then the problem goes away, but I don't understand why/when this occurs.

 

[dcsapak]

There are no backups "running" or "tasks" that correspond, but when I look at the GUI, I see backups that are "spinning" . If I remove them, then the problem goes away, but I don't understand why/when this occurs.

this 'normally' happens when there are backups that will be aborted by e.g. broken network connection or when the client/server crashes

 

[Cayuga]

A

this 'normally' happens when there are backups that will be aborted by e.g. broken network connection or when the client/server crashes

As far as I can tell that hasn't happened. Should I be able to see this in the logs?

 

[dcsapak]

yes, the task log of that backup should normally contain what happened