No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data which you upload to your new shared hosting account shall be ensured by the ZFS file system which we make use of on our cloud platform. Most internet hosting providers, including our firm, use multiple hard disks to keep content and because the drives work in a RAID, the same info is synchronized between the drives all the time. When a file on a drive becomes corrupted for some reason, yet, it's likely that it will be copied on the other drives as alternative file systems don't offer special checks for this. In contrast to them, ZFS applies a digital fingerprint, or a checksum, for each and every file. If a file gets corrupted, its checksum will not match what ZFS has as a record for it, which means that the damaged copy will be replaced with a good one from a different hard disk drive. Since this happens immediately, there's no possibility for any of your files to ever be damaged.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We have avoided any possibility of files getting damaged silently since the servers where your semi-dedicated hosting account will be created work with a powerful file system known as ZFS. Its main advantage over other file systems is that it uses a unique checksum for each and every 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 other drives and the one it has saved. In case there is a mismatch, the bad copy is replaced with a healthy one from one of the other drives and because this happens right away, there is no chance that a corrupted copy can remain on our website hosting servers or that it could be copied to the other drives in the RAID. None of the other file systems use this type of checks and furthermore, even during a file system check following an unexpected power loss, none of them will detect silently corrupted files. In contrast, ZFS doesn't crash after a power loss and the constant checksum monitoring makes a lenghty file system check unneeded.