No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data which you upload to your new shared hosting account shall be guaranteed by the ZFS file system which we use on our cloud platform. Most of the web hosting service providers, like our company, use multiple hard disk drives to store content and since the drives work in a RAID, the same data is synchronized between the drives all of the time. If a file on a drive is damaged for reasons unknown, yet, it is very likely that it will be copied on the other drives as other file systems don't have special checks for this. Unlike them, ZFS applies a digital fingerprint, or a checksum, for every file. If a file gets damaged, its checksum will not match what ZFS has as a record for it, therefore the bad copy shall be swapped with a good one from a different hard disk drive. Because this happens immediately, there's no risk for any of your files to ever be corrupted.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We have avoided any possibility of files getting corrupted silently due to the fact that the servers where your semi-dedicated hosting account will be created use a powerful file system known as ZFS. Its basic advantage over alternative file systems is that it uses a unique checksum for each file - a digital fingerprint that is checked in real time. Since we keep all content on a number of SSD drives, ZFS checks if the fingerprint of a file on one drive corresponds to the one on the rest of the drives and the one it has stored. When there's a mismatch, the corrupted copy is replaced with a healthy one from one of the other drives and considering that this happens in real time, there is 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 include such checks and in addition, even during a file system check right after an unexpected power loss, none of them can detect silently corrupted files. In contrast, ZFS will not crash after a power failure and the regular checksum monitoring makes a time-consuming file system check obsolete.