tag:blogger.com,1999:blog-2224358098357507182.post1921965193829359168..comments2023-06-29T05:28:55.037-03:00Comments on Progeny Genealogy: The perils of cycling your backupsPierre Clouthierhttp://www.blogger.com/profile/14656043477858844404noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2224358098357507182.post-78896615126314488742015-11-14T12:12:45.215-04:002015-11-14T12:12:45.215-04:00Your point is valid, and your solution excellent. ...Your point is valid, and your solution excellent. <br /><br />I was referring to corruption introduced by the application itself, due to bugs.Pierre Clouthierhttps://www.blogger.com/profile/14656043477858844404noreply@blogger.comtag:blogger.com,1999:blog-2224358098357507182.post-43154880973595119832012-11-30T13:33:16.420-04:002012-11-30T13:33:16.420-04:00This could have been caused by bit loss, also know...This could have been caused by bit loss, also known as "bit rot": http://en.wikipedia.org/wiki/Bit_rot<br /><br />USB flash memory drives are extremely prone to this as they are not designed for long-term use. Any type of internal or external hard drive is as well. Unfortunately, the random, often undetectable loss of data is very difficult to combat.<br /><br />I wrote about how I approached this in my latest post: http://www.thehineks.com/preserving-family-history-records-digitally/<br /><br />Unfortunately, the technique I use at home to protect against the loss of data integrity is too technically complex for most people, but the CrashPlan service is something anyone can take advantage of. The benefit of that service is that it keeps unlimited versions of your files so that you can always go back to a copy that was working. That being said, a very frequent (at least weekly), hopefully automated integrity check should be run so that you know as soon as possible when corruption has occurred.Anonymoushttps://www.blogger.com/profile/18273577258545909496noreply@blogger.com