On Fri, 2004-11-12 at 09:32, David Madsen wrote: > This utility creates parity archives of any data you give it. Think of it > as RAID5 for data files. A quick example. Say you have a 3 100MB files > that you want to burn to CD. You then generate a number of parity > archives for this data set (you can make as many or as few as you like). > Creating parity archives that use about %10 of the total dataset's space > has worked well for me.
This would probably work best if you burned several CDs. It's been my experience (due to the linear track of a CD) that when the CD goes bad, the entire thing becomes unreadable. This program would save you from bad spots (ie scratches or holes) in the data layer, though. If you are concerned about data longevity, you should expect (in addition to using a program like this) to copy your CDs onto new CDs every two years or so. The average lifespan of current CDRs is about 2 years. Pressed CDs should last 10-20 years, depending on climate. Michael > > 4 years later you come back to retrieve some of this data and find one of > the 100MB files corrupt. QuickPAR will then scan the datafile,determine > which section of the file is bad, and use data from the generated parity > archives to regenerate the original data. Tne amount of parity archives > you will need depends on the original block size you used and how > localized the file's damage is but this gives you a general idea. It has > worked quite well. > > --Dave Madsen > > ____________________ > BYU Unix Users Group > http://uug.byu.edu/ > ___________________________________________________________________ > List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list -- Michael Torrie <[EMAIL PROTECTED]> ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
