Extremely resilient archive

There are two main options in the context of blkar, one uses blkar exclusively, and one uses blkar + par2.

blkar only

You can ask blkar to use a fairly high burst error resistance level (e.g. 100) to lower probability of burst errors damaging the archive irrecoverably.

Blkar does not limit the burst error resistance level during encoding, but in operations where it needs to determine the burst error resistance level, it only guesses up to (and including) level 1000 automatically.

decode, repair, and sort modes support --burst flag which overrides the burst error resistance level and blkar skips guessing if level is provided manually. Use this if blkar fails to guess the level correctly.

For very important data, a simple strategy is just to pump the numbers up, for instance you can do the following

blkar encode --sbx-version 17 --rs-data 100 --rs-parity 100 --burst 100 important_data

This will be very slow if the data is large, so lower the numbers as you see fit with your time budget.

blkar + par2

TODO