No Data Corruption & Data Integrity in Hosting
The integrity of the data that you upload to your new hosting account shall be guaranteed by the ZFS file system that we take advantage of on our cloud platform. The majority of web hosting suppliers, like our company, use multiple HDDs to keep content and considering that the drives work in a RAID, exactly the same info is synchronized between the drives all the time. If a file on a drive gets corrupted for reasons unknown, yet, it is likely that it will be copied on the other drives as other file systems do not offer special checks for this. In contrast to them, ZFS uses a digital fingerprint, or a checksum, for every single file. If a file gets damaged, its checksum will not match what ZFS has as a record for it, which means that the bad copy will be replaced with a good one from a different drive. Because this happens immediately, there is no risk for any of your files to ever be damaged.
No Data Corruption & Data Integrity in Semi-dedicated Servers
We've avoided any risk of files getting damaged silently due to the fact that the servers where your semi-dedicated server account will be created use a powerful file system called ZFS. Its key advantage over various other file systems is that it uses a unique checksum for each file - a digital fingerprint which is checked in real time. Since we store all content on numerous SSD drives, ZFS checks if the fingerprint of a file on one drive corresponds to the one on the remaining drives and the one it has stored. If there's a mismatch, the corrupted copy is replaced with a good one from one of the other drives and considering that it happens in real time, there's no chance that a damaged copy can remain on our web servers or that it can be copied to the other hard disks in the RAID. None of the other file systems work with this kind of checks and what is more, even during a file system check right after an unexpected power loss, none of them can discover silently corrupted files. In contrast, ZFS does not crash after a power loss and the continual checksum monitoring makes a lenghty file system check unneeded.