No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data that you upload to your new shared hosting account shall be guaranteed by the ZFS file system that we take advantage of on our cloud platform. The majority of internet hosting suppliers, including our company, use multiple HDDs to keep content and since the drives work in a RAID, the exact same info is synchronized between the drives at all times. When a file on a drive becomes damaged for reasons unknown, however, it is likely that it will be reproduced on the other drives since other file systems do not offer special checks for that. In contrast to them, ZFS works with a digital fingerprint, or a checksum, for every single file. If a file gets damaged, its checksum won't match what ZFS has as a record for it, which means that the damaged copy shall be substituted with a good one from another hard disk. As this happens instantly, there's 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 damaged silently because the servers where your semi-dedicated hosting account will be created employ a powerful file system known as ZFS. Its main advantage over other file systems is that it uses a unique checksum for every single file - a digital fingerprint which is checked in real time. Since we store all content on numerous SSD drives, ZFS checks whether the fingerprint of a file on one drive matches the one on the remaining drives and the one it has saved. In case there's a mismatch, the corrupted copy is replaced with a good one from one of the other drives and because this happens in real time, there's no chance that a damaged copy can remain on our web servers or that it can be duplicated to the other hard drives in the RAID. None of the other file systems use this kind of checks and what is more, even during a file system check right after an unexpected power failure, none of them will detect silently corrupted files. In contrast, ZFS will not crash after a power loss and the regular checksum monitoring makes a lenghty file system check unneeded.