Web developer Ukiah Smith wrote a blog post about which compression format to use when archiving. Obviously the algorithm must be lossless but beyond that he sets some criteria and then evaluates how some of the more common methods line up.
After some brainstorming I have arrived with a set of criteria that I believe will help ensure my data is safe while using compression.
- The compression tool must be opensource.
- The compression format must be open.
- The tool must be popular enough to be supported by the community.
- Ideally there would be multiple implementations.
- The format must be resilient to data loss.
Some formats I am looking at are zip, 7zip, rar, xz, bzip2, tar.
He closes by mentioning error correction. That has become more important than most acknowledge due to the large size of data files, the density of storage, and the propensity for bits to flip.
(Score: 0) by Anonymous Coward on Friday September 13 2019, @11:29AM (1 child)
Strangely I couldn't find a newer one. Thank you.
(Score: 0) by Anonymous Coward on Friday September 13 2019, @02:39PM
now to be found only through some distros' repos; not even the Github code mirror has it.
https://packages.debian.org/source/sid/dvdisaster [debian.org]
This is actually the version featuring the multithreaded implementation, so is much faster on todays' multicore hardware.
The mirror of original project page in its final state:
https://web.archive.org/web/20180428070843/http://dvdisaster.net/en/index.html [archive.org] (the source tarball itself isn't archived though)