Data corruption is the damage of information due to various software or hardware problems. Once a file is damaged, it will no longer work correctly, so an application will not start or shall give errors, a text file will be partially or fully unreadable, an archive will be impossible to open and unpack, etc. Silent data corruption is the process of info getting damaged without any identification by the system or an admin, that makes it a significant problem for website hosting servers as fails are more likely to happen on bigger hard disks where vast volumes of info are stored. If a drive is part of a RAID and the data on it is copied on other drives for redundancy, it's likely that the damaged file will be treated as a good one and it will be duplicated on all of the drives, making the harm permanent. A huge number of the file systems which run on web servers nowadays often are unable to locate corrupted files right away or they need time-consuming system checks during which the server isn't functioning.

No Data Corruption & Data Integrity in Semi-dedicated Hosting

We've avoided any risk of files getting corrupted silently as the servers where your semi-dedicated hosting account will be created work with a powerful file system named ZFS. Its key advantage over alternative file systems is that it uses a unique checksum for each and every file - a digital fingerprint that is checked in real time. Since we keep all content on multiple SSD drives, ZFS checks whether the fingerprint of a file on one drive corresponds to the one on the rest of the drives and the one it has stored. If there is a mismatch, the damaged copy is replaced with a healthy one from one of the other drives and considering that this happens instantly, there is no chance that a corrupted copy can remain on our web hosting servers or that it can be copied to the other hard drives in the RAID. None of the other file systems use such checks and what is more, even during a file system check right after an unexpected blackout, none of them will find silently corrupted files. In comparison, ZFS won't crash after a blackout and the regular checksum monitoring makes a time-consuming file system check unneeded.