So our backups, and I mean what appears in the Duplicati web interface, disappeared during an upgrade of Duplicati. Of course, I hadn’t exported them. These were backing up to AWS S3. I configured new backups with the information I could find and from memory, confirmed the connection, then set the database to repair. That was two days ago and its still going.
I was surprised to see that the Duplicati is retrieving the dblock files during the repair. Shouldn’t it just be grabbing the dlist and dindex files to rebuild the database? (Note: I was able to find a recent answer to this question here in the forum.)
If a database repair requires downloading the whole backup… I should expect a nice bill from AWS this month.
In case it matters, we’re running 2.0.3.3_beta_2018-04-02. lastPgEvent is showing:
{"BackupID":"3","TaskID":39,"BackendAction":"Get", "BackendPath":"duplicati-bd63d0c75be4a471589195ad7eef4ef2e.dblock.zip.aes", "BackendFileSize":52433277,"BackendFileProgress":52433277, "BackendSpeed":303462,"BackendIsBlocking":false, "CurrentFilename":null,"CurrentFilesize":0, "CurrentFileoffset":0,"Phase":"Recreate_Running", "OverallProgress":0.7838964,"ProcessedFileCount":0, "ProcessedFileSize":0,"TotalFileCount":0,"TotalFileSize":0, "StillCounting":false}
Does the OverallProgress being 0.7838964 mean that it is approximately 78% or 0.78% done?