No Data Corruption & Data Integrity in Cloud Web Hosting
The integrity of the data which you upload to your new cloud web hosting account shall be guaranteed by the ZFS file system that we work with on our cloud platform. Most internet hosting providers, including our firm, use multiple hard drives to keep content and since the drives work in a RAID, exactly the same info is synchronized between the drives all of the time. In case a file on a drive gets damaged for reasons unknown, however, it is very likely that it will be copied on the other drives as other file systems don't feature special checks for that. Unlike them, ZFS works with a digital fingerprint, or a checksum, for every single file. If a file gets damaged, its checksum will not match what ZFS has as a record for it, and the bad copy shall be replaced with a good one from another drive. Because this happens immediately, there is no possibility for any of your files to ever get damaged.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We have avoided any possibility of files getting damaged silently since the servers where your semi-dedicated hosting account will be created use a powerful file system named ZFS. Its key advantage over alternative 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 corresponds to the one on the remaining drives and the one it has saved. In the event that there is a mismatch, the corrupted copy is replaced with a healthy one from one of the other drives and because it happens in real time, there is no chance that a damaged copy could remain on our servers or that it could be duplicated to the other hard disks in the RAID. None of the other file systems employ this type of checks and in addition, even during a file system check following an unexpected power loss, none of them will find silently corrupted files. In comparison, ZFS won't crash after a blackout and the constant checksum monitoring makes a lenghty file system check unneeded.