This happens to me sometimes, is there anything to do to allow a command to finish?
Otherwise I give up. I have a backup on a disk (synchronization)
In this case, I will delete all the data from the target (in the cloud) and create a new backup!
and Recreate is a variation of The REPAIR command done after a database is deleted. How you got into this situation is a good question, but sometimes recreation can take awhile. You can look for progress at About → Show log → Live → Verbose to see if anything is happening. In unusual error situations, it might download and process all destination files, attempting to locate some block of information that’s missing.
I can’t tell you if this is the case. You’d have to look. Alternatively, it’s possible that no activity is happening.
This is often easier for those who don’t mind losing old history. I’d still like to know errors you were getting. Backup errors often put no log in the usual log area, but you can also look in About → Show log → Stored.
From your screenshot and a ruler (centimeters is easier), it looks like it was doing the complete search for some missing information. This occurs from 90% to 100% on the progress bar. You’re at 95, so maybe it’s about half done 7 hours ago. Maybe it even made further progress and either finished or gave up with error.
Once information is missing from the destination, it stays missing. list-broken-files and purge-broken-files would be how to get limited deletion of only the affected source file backups, but a fresh backup is simpler.
In fact, I don’t know why this backup is not doing well (others don’t have problems with the same provider). Maybe a problem with the remote server.
About → Show log → Live → Verbose:
29 avr. 2021 21:40: The Repair operation failed with the error : The database was attempted repaired, but the repair did not complete. This database may be incomplete and the repair process is not allowed to alter remote files as that could result in data loss.