No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data that you upload to your new shared hosting account shall be ensured by the ZFS file system which we employ on our cloud platform. Most of the web hosting service providers, including our firm, use multiple hard disks to keep content and because the drives work in a RAID, identical data is synchronized between the drives all of the time. When a file on a drive becomes damaged for some reason, yet, it's likely that it will be copied on the other drives because other file systems don't offer special checks for that. In contrast to them, ZFS works with a digital fingerprint, or a checksum, for every file. In the event that a file gets corrupted, its checksum won't match what ZFS has as a record for it, so the bad copy shall be swapped with a good one from another hard disk. Since this happens right away, there is no possibility for any of your files to ever get damaged.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any possibility of files getting damaged silently because the servers where your semi-dedicated hosting account will be created take advantage of a powerful file system named ZFS. Its advantage over various other file systems is that it uses a unique checksum for every single file - a digital fingerprint that's checked in real time. As we keep all content on numerous NVMe drives, ZFS checks whether the fingerprint of a file on one drive corresponds to the one on the remaining drives and the one it has saved. If there's a mismatch, the bad 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 can remain on our hosting servers or that it could be copied to the other hard disks in the RAID. None of the other file systems use such checks and what's more, even during a file system check after a sudden electrical power failure, none of them can discover silently corrupted files. In contrast, ZFS will not crash after a power loss and the continual checksum monitoring makes a time-consuming file system check unnecessary.