Thanks for the suggestion. Using hashing is indeed good for checking data integrity. As you said, if a file is corrupt, one may hope to find a good copy elsewhere.

I want to achieve more than that. Using ECC, one can hope to be able to handle corruptions and so, a backup may still be good even if several bytes/blocks/sectors did go bad.

Storage is very cheap today. This means that increasing the size with redundant ECC information does not cost much. Another way to look at is that since storage _is_ cheap, one shouldn't count on it too much and devise a way to still maintain its reliability.

In reply to Re^2: (OT) Redundant Backup by fundflow
in thread (OT) Redundant Backup by fundflow

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.