Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Progress bar does not show meaningful information during restore #3646
When doing a restore from an existing backup, on a newly installed instance of Duplicati, the progress bar does not show actual progress. It does display messages chat indicate that the database is being reconstructed, and then that files are being downloaded, but the progress bar never advances. This caused me some concern during my restore, since I couldn't tell if anything was happening - during the phase of reconstructing the database, it ran for almost an hour, and I couldn't tell if it was actually doing anything at all (other than by looking at Task Manager and seeing that it was using CPU and I/O), and again when it indicated that it was downloading files, it behaved in a similar manner.
This is similar to feature request #2159, but I can't tell if it's the same thing - that feature request implies that there is no progress bar and asks that it be implemented. In this instance, there is a progress bar, but it just doesn't do anything.
Steps to reproduce
The lack of progress indication is particularly unnerving during a full restore, which takes a significant amount of time.
Ideally, a current file number/total number of files to be restored counter, along with the current file name, would be a great way of keeping the user informed as to what is going on. If this is not possible, at least a running total of how much data has been restored (possibly differentiated by local blocks vs. downloaded files) would allow the user to know that things are still happening.
In fact, both types of counters together (file progress and data progress) would be the perfect solution, since restoring a large file (e.g., a VM), would not show progress in terms of file count or file name for a long time, even though much data was being restored. Having total data restored as a secondary counter would reassure the user that things were still working as they should.
This issue has been mentioned on Duplicati. There might be relevant details there: