Recently, I found out that my local database was corrupted, and I needed to recreate it from remote storage. It had been running the repair for like a week when it appeared to stop making progress. Given that I wasn’t seeing any new log messages, I restarted the duplicati service.
Performance problems are documented in some of these issues:
- Recreating broken DB takes forever [$25] · Issue #2889 · duplicati/duplicati · GitHub
- Database recreate desperately needs improvement · Issue #4041 · duplicati/duplicati · GitHub
According to the documentation for the repair command:
If no local database is found or the database is empty, the database is re-created with data from the storage. If the database is in place but the remote storage is corrupt, the remote storage gets repaired with local data (if available).
Obviously, I want to avoid restarting the repair from scratch. Is there any way to resume the database repair? Is any way to do the repair manually, or download the relevent dblocks to attempt a manual repair?