I’m evaluating v2.0.9 of the CLI version and I’ve been having a lot of trouble doing the initial backup to OneDrive. It keeps on failing due to the following error.
Failed to find the path for the chunk xxxxxxxxxxxxxxx: Maximum number of retries reached
I’ve tried using different number of threads (10, 5, 2 and 1) in case its an API limit but it keeps on failing.
I’m only trying to backup about 100GB worth of data.
Here are some logs from the last few tries:
(previous attempts above)
duplicacy_win_i386_2.0.9.exe backup -stats -threads 5
Storage set to one://foobar
No previous backup found
Indexing <path-to-backup>
Incomplete snapshot loaded from <path-to-backup>/.duplicacy/incomplete
Listing all chunks
Skipped 112 files from previous incomplete backup
...
Skipped chunk 2950 size 4924345, 10.59MB/s 02:52:01 6.7%
Skipped chunk 2951 size 1804920, 10.59MB/s 02:51:58 6.7%
Skipped chunk 2952 size 1108911, 10.59MB/s 02:51:57 6.7%
Failed to find the path for the chunk 9c2eeff7ff14eacec684fedc80047ac4f679a53277c135771226256d2e248add: Maximum number of retries reached
Incomplete snapshot saved to <path-to-backup>/.duplicacy/incomplete
duplicacy_win_i386_2.0.9.exe backup -stats -threads 5
...
Skipped chunk 9961 size 6582507, 10.32MB/s 02:10:44 30.9%
Failed to find the path for the chunk 44ba286b0eb1500ca59056c687437bdd3ef8ed642bfa166534c9aa1eb45f8e53: Maximum number of retries reached
Incomplete snapshot saved to <path-to-backup>/.duplicacy/incomplete
duplicacy_win_i386_2.0.9.exe backup -stats -threads 2
...
Skipped chunk 10124 size 1630727, 10.56MB/s 02:06:27 31.6%
Failed to find the path for the chunk 124bc126fe5e0af404fc5436203a119023c8f84bd71558fc5eb345b92db252d0: Maximum number o
f retries reached
Incomplete snapshot saved to <path-to-backup>/.duplicacy/incomplete
duplicacy_win_i386_2.0.9.exe backup -stats -threads 1
Storage set to one://foobar
No previous backup found
Indexing <path-to-backup>
Incomplete snapshot loaded from <path-to-backup>/.duplicacy/incomplete
Listing all chunks
Skipped 0 files from previous incomplete backup
Skipped chunk 1 size 9616800, 9.17MB/s 03:33:03 0.0%
Skipped chunk 2 size 1988760, 11.07MB/s 02:56:32 0.0%
Skipped chunk 3 size 2753776, 6.85MB/s 04:45:21 0.0%
Skipped chunk 4 size 13703758, 8.92MB/s 03:38:59 0.0%
Skipped chunk 5 size 6563636, 8.26MB/s 03:56:37 0.0%
Skipped chunk 6 size 4387581, 9.30MB/s 03:30:00 0.0%
Skipped chunk 7 size 16777216, 8.87MB/s 03:40:15 0.0%
Skipped chunk 8 size 4774157, 9.63MB/s 03:22:53 0.0%
...
Skipped chunk 9790 size 10634832, 10.13MB/s 02:14:29 30.3%
Skipped chunk 9791 size 6841295, 10.13MB/s 02:14:29 30.3%
Skipped chunk 9792 size 4037281, 10.13MB/s 02:14:27 30.3%
Skipped chunk 9795 size 8169823, 10.12MB/s 02:14:30 30.3%
Failed to find the path for the chunk e0817b53f86d96dab9bd89ca974415514f3b4c8018321ca7424e16bbddaab064: Maximum number of retries reached
Incomplete snapshot saved to <path-to-backup>/.duplicacy/incomplete
duplicacy_win_i386_2.0.9.exe backup -stats -threads 1
Storage set to one://foobar
No previous backup found
Indexing <path-to-backup>
Incomplete snapshot loaded from <path-to-backup>/.duplicacy/incomplete
Listing all chunks
Skipped 0 files from previous incomplete backup
...........
Skipped chunk 10107 size 2483644, 10.54MB/s 02:06:52 31.5%
Skipped chunk 10109 size 3869664, 10.53MB/s 02:06:55 31.5%
Skipped chunk 10110 size 2478120, 10.53MB/s 02:06:55 31.6%
Skipped chunk 10111 size 6858109, 10.53MB/s 02:06:55 31.6%
Failed to find the path for the chunk 3dc308b0d009d891e0215d84d098343eb94d57d4619640020e9e9b6f5be8c9af: Maximum number of retries reached
Incomplete snapshot saved to <path-to-backup>/.duplicacy/incomplete
You can see in one instance it was able to keep track of what files were left to upload (Skipped 112 files from previous incomplete backup) but most of the time it doesn’t and tries to determine if everything needs to be uploaded. Note that I only have around 170 files to upload, with an approx average of 1.5 GB/file.
This leads to thousands of skipped chunk uploads. It’s now erroring out before it can even upload a new chunk.
Any ideas?