This may sound silly at first glance, but if you allow more than 100% redundancy, you do not need to distribute the data files at all. That does not make sense for the usenet, but it serves a purpose...
The limit on 100% is pure UI - if I remove the limit from the commandline version (commandline.cpp), it will happily create a set of files with 1000% redundancy. Which means that if I lose 90% of the created par2 files, I can still recover all data.
This is a very good thing to have for a distributed backup system: Store par2 files with 200% redundancy on 4 systems, and you can recover ALL data as long as any 2 of the 4 survive.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This may sound silly at first glance, but if you allow more than 100% redundancy, you do not need to distribute the data files at all. That does not make sense for the usenet, but it serves a purpose...
The limit on 100% is pure UI - if I remove the limit from the commandline version (commandline.cpp), it will happily create a set of files with 1000% redundancy. Which means that if I lose 90% of the created par2 files, I can still recover all data.
This is a very good thing to have for a distributed backup system: Store par2 files with 200% redundancy on 4 systems, and you can recover ALL data as long as any 2 of the 4 survive.
This is a seriously good idea.
Yes! Immediately useful!