First time user here. I am backing up a ~5TB set of Data to B2 backend. Encryption is enabled. Upload volume size is set to 500MB. Initial backup is still in progress but due to connection interruption today (12hrs) backup stopped therefore I wanted to try restoring a file.
After 20 minutes it is still “verifying remote data” but I barely see any traffic from duplicati host + cpu is idling at 14%.
What is duplicati doing when doing “verifying remote data”? The file to be restored is 300MB, i.e. I would expect it to be spread to 2 archives max. Content has not changed.
The B2 URL varies and I don’t think you can directly get Duplicati to show it (short of using a debugger), but Calling the API expresses the idea. The 123 stands for a three digit number showing where B2 has sent you. This sort of go-there behavior is even more prevalent on uploads, where you might get redirected anytime… This is all supposed to be handled automatically, but seemingly you’re having some sort of connecting issue, which you could try to check in “netstat”, Wireshark, or something like that. Don’t expect IP name resolutions. Easy non-connect would be SYN_SENT, saying TCP-level connect didn’t occur. Beyond that, it gets complex.