Do you get the three-dot icon to the right of Backup destination
as I showed? Click it for menu.
The icon is likened to a hamburger, which especially fits when it’s three lines instead of three dots.
Although screen “should” adjust with display, it’s also conceivable that yours is not directly to right.
If somehow that button is nowhere there (which would be interesting and would be a bug), there’s:
etc. and still needed, if you’re still saying that WebDAV files wind up as local files. What of below?
Note that Duplicati doesn’t know where the actual storage is, but refers to destination as “remote”.
If you’re still saying that WebDAV files wind up on local drive, it’s essential for you to check config.
Are you still seeing below in your new test? If so, please do the file date check as was requested.
and if it is still happening, then I need the destination (a.k.a. target) URL. You can post the whole thing with its sensitive parts redacted. Alternatively, you can paste part of Destination screenshot.
Where are your test backups going? Do you have direct visibility to WebDAV through some way?
Troubleshooting your latest findings may need looking at Destination, so where are the files now?
EDIT 1:
The file activity is in <job> → Show log → Remote, however if it was a small backup below 50 MB, then it would be 3 files with names containing dblock, dindex, and dlist. The question is whether it managed to upload them with put
, but can’t see them with list
(click line) or are really not there, confirmed through some independent means such as a WebDAV browser, a cloud UI, or Explorer.
EDIT 2:
and for tools, I would usually say it’s where you configured it to go, but that is still awaiting info too.
There is also About → Show log → Live → Retry to look at if you want to repeat some testing runs. This is also a good way to find out what file names are missing. Are they the ones it just uploaded?
You can also test the destination directly with a URL from Export As Command-line and then use Duplicati.CommandLine.BackendTool.exe or Duplicati.CommandLine.BackendTester.exe (which needs an empty folder to test in – just edit the URL away from the job URL if you want to protect existing backup – although with the latest test I’m not sure that there’s an existing one to protect).