What size are the files on the destination, and what sort of storage is the destination?
File sizes are usually quite varied, but these two are now truncated to even boundary.
327155712 is 13800000 in hex, which makes me suspect remote filesystem problem.
0 is of course truncation to binary-even, and an impossible valid size for a dindex file.
If you have your old DB (i.e. didn’t destroy/recreate), an empty dindex is easily rebuilt.
Repair will do that if if finds dindex missing, e.g. change folder, or add hidden- prefix.
If your dblock got damaged, that’s an actual loss of data, but it only affects some files.
The AFFECTED command can show the files. Easiest way to run is by Commandline.
You need to change the Command from backup to affected and put the filenames in the
Commandline arguments box, and go to screen bottom to run the affected command.
Recovering by purging files is the plan, but note that first the damaged dblock must go
missing, e.g. move it to a parallel or higher folder, or rename with a prefix e.g. hidden-
Before doing any of this, look at sizes of those two files. Do they seem too even/short?
If your remote has timestamps, you might also be able to see when the file was written.
What Duplicati version is this, and what is the operating system?