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 take advantage of on our cloud platform. The majority of hosting suppliers, like our firm, use multiple hard drives to store content and considering that the drives work in a RAID, the same information is synchronized between the drives all the time. If a file on a drive gets damaged for some reason, however, it's more than likely that it will be copied on the other drives since other file systems do not have special checks for this. Unlike them, ZFS applies a digital fingerprint, or a checksum, for every single file. In case a file gets corrupted, its checksum will not match what ZFS has as a record for it, which means that the damaged copy shall be replaced with a good one from another hard disk. As this happens instantly, there is no risk for any of your files to ever get corrupted.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any chance of files getting corrupted silently due to the fact that the servers where your semi-dedicated hosting account will be created work with a powerful file system called ZFS. Its advantage over alternative file systems is that it uses a unique checksum for each file - a digital fingerprint that's checked in real time. As we store all content on multiple 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. When there's a mismatch, the damaged copy is replaced with a good one from one of the other drives and since this happens right away, there is no chance that a damaged copy can remain on our hosting servers or that it could be duplicated to the other drives in the RAID. None of the other file systems include this type of checks and what's more, even during a file system check right after a sudden power failure, none of them can discover silently corrupted files. In comparison, ZFS does not crash after a blackout and the constant checksum monitoring makes a time-consuming file system check unneeded.