Best way to change pwd+keys for b2 repo without losing history?

Update: Copy succeeded.

$ restic stats --mode raw-data

repository xxxxxx opened (version 2, compression level auto)
….
Total Uncompressed Size: 7.751 GiB
Total Size: 7.454 GiB
Compression Progress: 100.00%
Compression Ratio: 1.04x
Compression Space Saving: 3.83%

On B2 web interface: old repo 8.8GB vs new repo: 8GB (don’t know if it’s good enough for compression max). Strange that compression level auto sneaked in (maybe this). restic copy was done with --compression max

Some notes (just in case it helps someone else):

  • --dry-run didn’t work either with init or copy (not sure I missed something or that’s how it is)

  • During first copy attempt the command was interrupted; succeeded in next try. But the new repo had ballooned to 17GB (vs 8GB of old repo). restic check said ……additional files were found in the repo, which likely contain duplicate data…restic prune fixed it.

  • restic check, restic check --read-data-subset=1/20, and restic restore (checked on couple of smaller file/folders) passed.

I will check with --read-data later, set up backrest, and then delete old repo.
Thank you @kapitainsky and restic community.

1 Like