No Data Corruption & Data Integrity in Website Hosting
The integrity of the data which you upload to your new website hosting account shall be ensured by the ZFS file system that we use on our cloud platform. Most hosting service providers, like our firm, use multiple hard drives to keep content and since the drives work in a RAID, the exact same info is synchronized between the drives all of the time. When a file on a drive gets corrupted for some reason, yet, it is more than likely that it will be duplicated on the other drives as other file systems do not feature special checks for this. Unlike them, ZFS employs a digital fingerprint, or a checksum, for each file. In the event that a file gets damaged, its checksum won't match what ZFS has as a record for it, which means that the damaged copy will be replaced with a good one from another hard disk drive. Due to the fact that this happens in real time, there is no possibility for any of your files to ever be corrupted.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We have avoided any probability of files getting damaged silently because the servers where your semi-dedicated hosting account will be created employ a powerful file system named ZFS. Its key advantage over other file systems is that it uses a unique checksum for each file - a digital fingerprint that is checked in real time. Since we store all content on numerous SSD 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 saved. If there is a mismatch, the bad copy is replaced with a good one from one of the other drives and considering that this happens in real time, there's no chance that a damaged copy can remain on our web hosting servers or that it can be duplicated to the other hard disks in the RAID. None of the other file systems employ this type of checks and what is more, even during a file system check after a sudden power failure, none of them can detect silently corrupted files. In comparison, ZFS won't crash after an electrical power failure and the constant checksum monitoring makes a time-consuming file system check unneeded.