Unexpected difference in fileset version error

Yes

There’s a backup folder on Storj. This is a bucket that does not include the source (in another bucket), but both buckets are on storj.

Is Destination going to Storj through Mountain Duck, or Duplicati configured to use Storj?

image

using Mountain Duck as a fake local drive, or

image

Only in the latter case could the Duplicati Storj update help. It won’t help Mountain Duck.

Yes.

But I got the storj backup (the job we have been chatting about) to work. I deleted and then re added the storj network drive via Mountain Duck. The backup I manually ran about 30 minutes ago had no errors and no warnings.

Then you can forget I mentioned the Storj update in the Canary. Eventually it will be in a Beta.

I don’t know anything about fixing that setup, but I’m glad you were able to get it working again.

That sounds good to me. I still worry about the fragility of this setup, but I guess it’s running now.