No Data Corruption & Data Integrity in Cloud Web Hosting
The integrity of the data which you upload to your new cloud web hosting account will be guaranteed by the ZFS file system which we employ on our cloud platform. Most internet hosting service providers, like our company, use multiple hard disk drives to keep content and since the drives work in a RAID, the same info is synchronized between the drives all of the time. When a file on a drive gets corrupted for whatever reason, yet, it's more than likely that it will be copied on the other drives since alternative file systems do not have special checks for this. Unlike them, ZFS uses a digital fingerprint, or a checksum, for each file. If a file gets corrupted, its checksum won't match what ZFS has as a record for it, and the bad copy will be replaced with a good one from a different disk drive. Because this happens instantly, there's no possibility for any of your files to ever be damaged.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any possibility of files getting damaged silently since the servers where your semi-dedicated hosting account will be created take advantage of a powerful file system called ZFS. Its key 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. Since we keep all content on multiple SSD drives, ZFS checks if the fingerprint of a file on one drive matches the one on the remaining drives and the one it has stored. In the event that there is a mismatch, the corrupted 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 corrupted copy could remain on our web servers or that it can be copied to the other drives in the RAID. None of the other file systems use this type of checks and what's more, even during a file system check after a sudden power failure, none of them can find silently corrupted files. In contrast, ZFS won't crash after a blackout and the regular checksum monitoring makes a lenghty file system check unneeded.