As I experiment with different
b2.connections values to get optimal throughput when using restic 0.12.0 to backup to Backblaze B2, I wonder whether there is any risk whatsoever in aborting a backup with Ctrl+C? Subsequently, I used
restic rebuild-index to correct errors found by
restic check – is this correct/advised procedure, or could something go wrong when rebuilding the indices?
I am aware that when aborting backups there will be some unreferenced pack files, and that those are no problem for
restic. But I wonder: Could such abortion of
restic leave behind any incomplete or partial files on the remote repo, which
restic could see as corrupted – say, eg, a partial pack file without header? And, could this be worsened by
check or others?