No Data Corruption & Data Integrity in Cloud Web Hosting
The integrity of the data that you upload to your new cloud web hosting account shall be ensured by the ZFS file system that we employ on our cloud platform. Most hosting suppliers, like our firm, use multiple hard disks to store content and considering that the drives work in a RAID, the same info is synchronized between the drives at all times. When a file on a drive gets damaged for reasons unknown, however, it's likely that it will be reproduced on the other drives as alternative file systems do not offer special checks for that. Unlike them, ZFS employs a digital fingerprint, or a checksum, for every file. In case a file gets damaged, its checksum won't match what ZFS has as a record for it, so the damaged copy shall be substituted with a good one from a different hard drive. Because this happens instantly, there's no risk 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 corrupted silently because the servers where your semi-dedicated hosting account will be created work with a powerful file system named ZFS. Its advantage over other file systems is that it uses a unique checksum for every single file - a digital fingerprint that is checked in real time. As we store all content on numerous NVMe drives, ZFS checks if the fingerprint of a file on one drive corresponds to the one on the rest of the drives and the one it has stored. If there's a mismatch, the corrupted copy is replaced with a healthy one from one of the other drives and considering that it happens in real time, there is no chance that a corrupted copy could 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 such checks and in addition, even during a file system check right after an unexpected power failure, none of them can detect silently corrupted files. In contrast, ZFS does not crash after a power failure and the constant checksum monitoring makes a lenghty file system check unnecessary.