# Duplicati stalls and requires manual recovery
**URL:** https://forum.duplicati.com/t/duplicati-stalls-and-requires-manual-recovery/483
**Category:** Support
**Created:** [September 7, 2017, 4:35pm UTC](https://forum.duplicati.com/t/duplicati-stalls-and-requires-manual-recovery/483 "2017-09-07T16:35:30Z")
**Posts on this page:** 1
**Showing post:** 3
### Author:  [@bernarddt](https://forum.duplicati.com/u/bernarddt)
#### Post date: [March 2, 2022, 6:55am UTC](https://forum.duplicati.com/t/duplicati-stalls-and-requires-manual-recovery/483/3 "2022-03-02T06:55:00Z")
I’m experiencing the same situation on Duplicati 2. Since not a lot has changed since then I’m continuing this conversation. I have many cases that my backup end point is going offline during backups and this causes the backup to stall (not fail as would be preferred). I’ve captured a screenshot of the “Live” logs to give you an idea. I took this screenshot at 9 AM on the next day. This backup stalled on the 6 PM the previous day already.
If a feature have been added to put a timeout on a backup job, please let me know.
I see this topic is also being discussed for years now in this post:
> [@Verifying Backend Data](https://forum.duplicati.com/t/verifying-backend-data/348/65):
>
> Dear Duplicati authors, analysis of user RGupta is correct and issue of “Verifying Backend Data” is not resolved in 2.0.4.17 build. What is recommended to be changed is: a) create index i1 on BlocklistHash(Hash); b) LocalDatabase(1301) issue commands: PRAGMA optimize; ANALYZE sqlite\_master; ANALYZE Block; ANALYZE BlocklistHash; ANALYZE BlocksetEntry; c) in LocalDatabase.cs(1304): var sql = string.Format(@“SELECT ““A””.”“Hash”", ““C””."“Hash”" FROM " + @"(SELECT bb1."“BlocksetID”", b…
and
> [@Stuck on Verifying Backend Data \[2.0.3.6\]](https://forum.duplicati.com/t/stuck-on-verifying-backend-data-2-0-3-6/1916/8):
>
> The first thing I’d suggest is the same - try running the backup with --no-backend-verification enabled. If the job runs without error, then we’ve verified where the problem is. (Note that this is NOT a fix as disabling backend-verification means if something goes wrong with a backend file you won’t know about it until you try to restore from it.) The next thing you might want to do is use --log-file=\ and --log-level=profiling to create an actual text file log of what Duplicati is doing…
---
_[View the full topic](https://forum.duplicati.com/t/duplicati-stalls-and-requires-manual-recovery/483)._