No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data that you upload to your new shared hosting account will be ensured by the ZFS file system which we use on our cloud platform. The majority of web hosting suppliers, including our company, use multiple hard drives to keep content and considering that the drives work in a RAID, the same data is synchronized between the drives at all times. If a file on a drive is damaged for some reason, however, it's likely that it will be copied on the other drives as other file systems do not feature special checks for this. Unlike them, ZFS works with a digital fingerprint, or a checksum, for each and every file. In case a file gets corrupted, its checksum won't match what ZFS has as a record for it, which means that the bad copy shall be replaced with a good one from a different disk drive. Since this happens right away, there's no possibility for any of your files to ever get corrupted.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We have avoided any risk of files getting corrupted silently since the servers where your semi-dedicated hosting account will be created use a powerful file system called ZFS. Its key advantage over alternative file systems is that it uses a unique checksum for every single file - a digital fingerprint that is checked in real time. As we save all content on a number of SSD drives, ZFS checks if the fingerprint of a file on one drive matches the one on the remaining 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 because it happens in real time, there is no chance that a corrupted copy can remain on our website hosting servers or that it could be duplicated to the other hard drives in the RAID. None of the other file systems include such checks and what is more, even during a file system check following an unexpected power failure, none of them will detect silently corrupted files. In contrast, ZFS does not crash after a blackout and the regular checksum monitoring makes a lenghty file system check unneeded.