by ToddBooth3 on Mon Jul 21, 2014 4:05 pm
Hello,
Wow, Syncovery is awesome!!! However, I ran into a problem when backing up to OneDrive. I'm running Syncovery 6.67 build 237
My folder structure and file naming are not compatible with OneDrive. So Syncovery is receiving and displaying error messages like the following:
Short version:
"WAIT 89 SECONDS AND TRY AGAIN"
Long version:
\Vacation, Cruise, Michelle, 2012-07\Michelle's Pictures\IMG_1678.JPG (HTTP ERROR 420 ONEDRIVE UPLOAD: {
"ERROR": {
"CODE": "REQUEST_THROTTLED",
"MESSAGE": "THE REQUEST WASN'T MADE BECAUSE THE SAME TYPE OF REQUEST WAS REPEATED TOO MANY TIMES. WAIT 56 SECONDS AND TRY AGAIN."
}
} (6 ATTEMPTS UPLOADING STREAM) AT 00FD5247.CHECKPOINTS: GFC5B/TGGETORPUTEX:HTTP ERROR 420 ONEDRIVE UPLOAD: {
"ERROR": {
"CODE": "REQUEST_THROTTLED",
"MESSAGE": "THE REQUEST WASN'T MADE BECAUSE THE SAME TYPE OF REQUEST WAS REPEATED TOO MANY TIMES. WAIT 56 SECONDS AND TRY AGAIN."
}
} (6 ATTEMPTS UPL)
Is there a way to configure Syncovery to rename all my files as they are backed up to OneDrive such as:
OneDrive_Folder\Backup\... followed by perhaps the hash.date.time
Either way, I suggest the following enhancements:
. I would like Syncovery to
1) skip the files that are not compatible with the OneDrive naming convention and
2) put the list of files in the log
Also, it would be nice to get a list of all files and folders which are incompatible PRIOR to Syncovery trying to send. Then I can fix the problems.
If you won't implement the above, here is a hack that you can easily implement:
Since OneDrive will delay the transfer by 89 seconds, every time that Syncovery retries 6 times, I suggest the following:
When a transfer to OneDrive fails, put it in an end_of_transfer queue. Then after all files are transfered, only then do a retry and NEVER retry more than 5 times.
Thanks for listening!!!
Regards, Todd Booth