One of my biggest interests in the tech and computer world is the field of storage management and storage systems; you would know this had you read my detailing of a new age data management architecture that I proposed earlier in this post. The one advancement in recent years that has seriously blown me away was the Sun Microsystems’ (now Oracle‘s) introduction of this revolutionary filesystem called ZFS. What was so revolutionary about it was its ability to be a filesystem and a volume manager all wrapped into one big suite of data storage bliss that is self-healing, expandable, and so easily manageable, not to mention that it has one of the simplest command line interfaces I have ever seen on such a high-end performance system.
But the one feature of ZFS that was a mind-blasting feature and was in fact a big hit in the media, was the idea of the fact that you could absolutely ruin/destroy/explode/[insert term of mass destruction here] any one of your disks that are running in a ZFS pool (of course assuming that you set it up with redundancy features enabled) and despite this, your data will remain intact and will always be available on-demand, while you (or the IT guy comes to) replace the ruined hard disk with a fresh new one. I couldn’t believe it myself until I watched this video below; the guy literally places one of the hard disks on an anvil and bashes it with a sledge hammer, and then guess what? The data remains intact, available and deliverable.
If this doesn’t scream out reliability and continuity of your data then I don’t know what does.