No Data Corruption & Data Integrity in Cloud Hosting
The integrity of the data that you upload to your new cloud hosting account will be ensured by the ZFS file system that we use on our cloud platform. The majority of internet hosting providers, like our firm, use multiple hard drives to store content and because the drives work in a RAID, the same information is synchronized between the drives all the time. If a file on a drive is damaged for reasons unknown, however, it is very likely that it will be reproduced on the other drives as alternative file systems don't feature special checks for this. Unlike them, ZFS uses a digital fingerprint, or a checksum, for each file. In case a file gets damaged, its checksum won't match what ZFS has as a record for it, therefore the damaged copy shall be replaced with a good one from another hard drive. Since this happens immediately, there is no possibility for any of your files to ever be corrupted.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've 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 known as ZFS. Its main advantage over various other file systems is that it uses a unique checksum for each file - a digital fingerprint that's checked in real time. As we keep all content on a number of SSD drives, ZFS checks if the fingerprint of a file on one drive matches 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 it happens in real time, there's no chance that a damaged copy can remain on our hosting servers or that it can be duplicated to the other hard disks in the RAID. None of the other file systems include this type of checks and furthermore, even during a file system check right after a sudden power loss, none of them will discover silently corrupted files. In contrast, ZFS won't crash after a power failure and the constant checksum monitoring makes a lenghty file system check obsolete.