Just installed duplicati and connected it to Backblaze B2, but immediately get this error. I presume it’s from Backblaze:
"Operation Put with file duplicati-20180511T110002Z.dlist.zip.aes attempt 2 of 5 failed with message: 400 - bad_request: File names must not contain '\'
System.Exception: 400 - bad_request: File names must not contain '\'
at Duplicati.Library.Backend.Backblaze.B2AuthHelper.AttemptParseAndThrowException(Exception ex)
at Duplicati.Library.JSONWebHelper.GetResponse(AsyncHttpRequest req, Object requestdata)
at Duplicati.Library.JSONWebHelper.ReadJSONResponse[T](AsyncHttpRequest req, Object requestdata)
at Duplicati.Library.Backend.Backblaze.B2.Put(String remotename, Stream stream)
at Duplicati.Library.Main.BackendManager.DoPut(FileEntryItem item)
at Duplicati.Library.Main.BackendManager.ThreadRun()"
Should I just go hunting for a file with \ in the name or is this something more complicated?
Duplicati doesn’t create any file names using a slash (forward or backward) though I suppose it MIGHT be possible to “force” it to by using the --prefix=xxxxxx parameter with a “\” somewhere in xxxxxx. (Note that using --prefix is not recommended as it can cause unnecessary confusion later on.)
--prefix
A string used to prefix the filenames of the remote volumes, can be used to store multiple backups in the same remote folder. The prefix cannot contain a hyphen (-), but can contain all other characters allowed by the remote storage.
Default value: “duplicati”
I see it’s on attempt 2 of 5, did the backup job quit there or continue on? If it continued, then most likely the next attempt succeeded and there was just something odd about attempt 2.
(By the way, I edited your post by adding “~~~” before and after the error message to make it more readable.)
Can you (and @dunnry) let us know what version of Duplicati you’re running and on what OS (Linux, MacOS, Windows)?
Oh, and are you able to use the job menu to Export your job “As commandline” and paste it here (with personal stuff like passwords & email address removed)?
This is your problem… You put F:\Boot\bg-BG in the “Folder Path” field on the Destination config. It should just be a simple folder name without any slashes. In my case I put the name of the PC there so that I can store multiple PC’s backups int he same B2 bucket. (This keeps the backup data separated.)
You were right. I think I actually didn’t put anything and somehow it populated itself, because I certainly don’t know where “F:\Boot\bg-BG” comes from.
It’s chugging along nicely now, thanks for very quick help! Awesome forum! Looking forward to messing about with duplicati some more!
I see the problem now based on the previous replies. I also don’t know how that got there as I didn’t set it. Fixing it now and will see if it work tonight.
I notice you have your dblock size set to 50GB… why is that? I think it will kill deduplication efficiency, but maybe there is a good reason to use that sometimes.
In the UI wizard, the dblock size is called ‘Upload volume size’. I had not understood what that meant. I set it to a high value thinking it was the max size for the total backup. What’s the recommended setting? 5 MB?
Something like “Upload block size”. I would have understood that ‘block’ was not the total volume. The label ‘Upload volume size’ makes me think it’s the total value.
I am sure you could also put a tool tip or otherwise to explain the de-duplication trade-offs as well as max block limits at cloud providers.
I see now that block size and remote volume block size are two different things. I would call it something like ‘remote volume block size’ and include a link to the article you have.
Hopefully that will cut down on the confusion there, but if not I’d suggest not using the word “volume” since that means something very different to many tech people.
Personally, I’d go with something like “Upload file size” or “Upload archive size”. But that’s just me - and I have no idea how well any of those would translate.
.