I had asked a similar question a few years ago without a clear response. Basically, I created my repository several years ago connecting to Backblaze and using the B2 connector. In diagnosing startup issues with the latest Kopia upgrade, I saw the warning “The B2 storage provider is deprecated and will be removed in the future, use the S3-compatible storage provider instead”. In doing a general search, I saw an open issue on github about potentially migrating users automatically but I’m wondering whether this is something I can/should do now, and if so, is it just changing the existing config file, something through cli or web UI?
Answering my own question sort of. I just saw a post made yesterday on Reddit with a similar question and took the advice of one of the commenters and (after backing up my existing config first), ran the following and it seems to be working
kopia repository connect s3 --bucket= --endpoint= --access-key=… --secret-access-key=…
tweaked the resulting config to match what I had previously for the repo description and cache directory
After having created the S3 repo, you’ll probably want to make use of kopie repo sync-to… which is able to sync between different on-device formats like local disk and S3. Probably the fastest as well.
well that’s the thing, it’s not a new repo in that sense, the data was in Backblaze using the B2 protocol but because Backblaze supports S3 as well, I just wanted to change how Kopia was connecting to it so the sync-to, unless I misunderstood (i.e., the data format isn’t changing, just how it’s accessed) isn’t necessary
Well, that may or may not be the case. I do know, that the on-disk format for a Kopia repo differs from local disk to S3 - if only in the naming of a couple of files, which are suffixed by an ‘.f’ on a file system based repo, whereas these files are not suffixed on a S3 based repo. If such a thing is the same for R2 vs. S3 you wouldn’t be able to simply change the transport channel…
If you can take a look at the repo’s data, you could can check that beforehand, though.