No Data Corruption & Data Integrity in Cloud Hosting
The integrity of the data which you upload to your new cloud hosting account will be ensured by the ZFS file system that we make use of on our cloud platform. Most of the hosting suppliers, including our firm, use multiple hard disks to store content and since the drives work in a RAID, the same information is synchronized between the drives all of the time. In case a file on a drive becomes damaged for reasons unknown, however, it's likely that it will be copied on the other drives as alternative file systems do not include special checks for this. In contrast to them, ZFS works with a digital fingerprint, or a checksum, for every file. In the event that a file gets corrupted, its checksum will not match what ZFS has as a record for it, and the damaged copy shall be swapped with a good one from a different hard disk drive. Due to the fact that this happens in real time, there's no risk for any of your files to ever get damaged.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any chance of files getting corrupted silently since the servers where your semi-dedicated hosting account will be created employ a powerful file system called ZFS. Its basic advantage over various other file systems is that it uses a unique checksum for each and every file - a digital fingerprint that's checked in real time. As we save all content on a number of SSD drives, ZFS checks whether the fingerprint of a file on one drive matches the one on the other drives and the one it has saved. When there's a mismatch, the bad copy is replaced with a good one from one of the other drives and since this happens instantly, there is no chance that a damaged copy could remain on our servers or that it could be copied to the other hard drives in the RAID. None of the other file systems use such checks and what is more, even during a file system check after an unexpected blackout, none of them will detect silently corrupted files. In contrast, ZFS will not crash after an electrical power failure and the constant checksum monitoring makes a lenghty file system check unneeded.