No Data Corruption & Data Integrity
What exactly does the 'No Data Corruption & Data Integrity' slogan mean to every hosting account user?
The process of files being corrupted as a consequence of some hardware or software failure is called data corruption and this is among the main problems which hosting companies face as the larger a hard drive is and the more info is stored on it, the more likely it is for data to get corrupted. There are a couple of fail-safes, but often the info gets damaged silently, so neither the particular file system, nor the admins see anything. Because of this, a damaged file will be treated as a regular one and if the HDD is a part of a RAID, that file will be duplicated on all other disk drives. In theory, this is for redundancy, but in practice the damage will get worse. The moment a file gets damaged, it will be partly or completely unreadable, which means that a text file will no longer be readable, an image file will present a random blend of colors in case it opens at all and an archive will be impossible to unpack, so you risk losing your site content. Although the most commonly used server file systems have various checks, they quite often fail to find a problem early enough or require a long period of time to check all the files and the web server will not be operational for the time being.
No Data Corruption & Data Integrity in Semi-dedicated Servers
We have avoided any risk of files getting corrupted silently as the servers where your semi-dedicated server
account will be created take advantage of a powerful file system called ZFS. Its main advantage over other file systems is that it uses a unique checksum for every single file - a digital fingerprint that is checked in real time. As we keep all content on multiple SSD drives, ZFS checks whether the fingerprint of a file on one drive matches the one on the other drives and the one it has stored. In case there's a mismatch, the damaged copy is replaced with a healthy one from one of the other drives and considering that it happens in real time, there's no chance that a corrupted copy could remain on our website hosting servers or that it could be duplicated to the other drives in the RAID. None of the other file systems work with this kind of checks and what's more, even during a file system check following a sudden power loss, none of them can discover silently corrupted files. In comparison, ZFS will not crash after a blackout and the continual checksum monitoring makes a time-consuming file system check unnecessary.