Sync-to duplicating blobs to remote storage?

General Topics
1

I recently moved my filesystem repo from one drive to another, with the mount point changing.

I used sync-to to make a copy of the repository from the first location (/media/storage1/kopia) to the new location (/media/storage7/kopia). I then disconnected the old repo and connected to the new one across devices. This worked fine.

In the process I also moved some source data and used snapshot move-history to update snapshot paths. This also worked fine.

Where I am hitting a potential issue is that the old repository (/media/storage1/kopia) was sync-to a remote location (Wasabi). I had assumed that syncing the new location (/media/storage7/kopia) would reuse the already uploaded blobs since it was a sync-to of the original location (and so bit identical). However, the sync-to is reporting it will upload everything again.

# Running Kopia sync to remote
Synchronizing repositories:
  Source:      Filesystem: /media/storage7/kopia/
  Destination: S3: s3.eu-central-1.wasabisys.com XXXX
Looking for BLOBs to synchronize...
  Found 118967 BLOBs in the destination repository (2.3 TB) 
  Found 119148 BLOBs (2.3 TB) in the source repository, 119148 (2.3 TB) to copy  
  Found 0 BLOBs to delete (0 B), 0 in sync (0 B)

Is there any way to avoid this duplicate upload?

If not, how do I clear the old repository from the remote as well so I don’t pay for the duplicate storage?

2

You should always be able to perform the move-history on the repos on the Wasabi bucket, befor attempting another sync, but I concur, that this seems to be redundand, or at least it should be, because the blobs are already in the repo and haven’t changed, other than the actual changes on the source, of course.

Maybe try the move history on the Wasabi repo first and see what it does for you?

3

Thanks. I suspect if I had moved history first on the remote it might have helped. However, it seems when viewing the snapshots on the remote that they are already updated - so the move-history is a no-op.

I’ll wait it out - hopefully the time drops from 4 days to complete!