New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extremely slow when restoring files, Fetching path information ... #2224
Comments
can you please give some more information about the backup and your machine? How many files? What size? Blocksize? Volume Size? Used advanced options? |
Windows server 2012 R2 64 bit. Total size of files backed up: 275 GB. Approx 119 000 files in 16 000 folders. Upload volume size: 200 Mbyte No advanced options except: Encryption AES-256. |
I did some more tests: I tried to run a "restore backup" without the local database. That was working fine. No problems with browsing all dirs etc. Restored a file and a local temporary database was created. All working fine. So i decided to delete the database and rebuild. After approx 15 hours it failed with the following error: 9 jan 2017 21:26: Failed while executing "Repair" with id: 1
|
If you can try with the latest canary, it has some extra information that can help trace the cause of this issuse: https://github.com/duplicati/duplicati/releases/tag/v2.0.1.39-2.0.1.39_canary_2017-01-08 |
Duplicati - 2.0.1.39_canary_2017-01-08
|
@Athep Do you see any other messages in the log? |
The only entries in the log before the error is: 10 jan 2017 12:20: Message 10 jan 2017 15:02: Message |
This is still an issue for me. Very slow resolving each step as I browse down through directory structure in restore dialog |
Referring to issue #2198.
Both when the backup set was on google drive and now on local storage, it is extremely slow working with.
Example: When restoring files, "Fetching path information ..." takes about 11 minutes. And after that listing directory's is almost impossible. It takes forever.
Something must be wrong. What can I do to correct this ?
The text was updated successfully, but these errors were encountered: