Is this Docker? GUI says “No version yet”, but was there a prior attempt at one?
If you did one, interrupted it, and are trying again, it will try to record what it had
managed to get on the interrupted backup attempt, plus prior backup if it’s there.
This case is described here, with a deep description here and current work here,
showing analysis of its slowness, a disable-synthetic-filelist workaround,
and a speedup for any willing testers of Release: 2.3.0.102 (Canary) 2026-05-09.
Synthetic Filelist Optimization
Optimized the creation of synthetic filelists, improving performance for large datasets.
If this sounds like your case and you don’t want to try to wait it out, you can try
stopping backup (which might not work), or harder stop of service or container.
EDIT 1:
If you have any performance tools, the symptom of being stuck in slow SQL is
sometimes one CPU core being fully used, however disk use might limit usage.
If your system seems idle, then something else is going on and will need study.