No Data Corruption & Data Integrity in Web Hosting
The integrity of the data which you upload to your new web hosting account will be guaranteed by the ZFS file system which we make use of on our cloud platform. The majority of web hosting providers, including our company, use multiple hard disk drives to store content and considering that the drives work in a RAID, identical information is synchronized between the drives at all times. When a file on a drive is damaged for reasons unknown, however, it's very likely that it will be copied on the other drives as other file systems do not feature special checks for that. In contrast to them, ZFS uses a digital fingerprint, or a checksum, for every file. In case a file gets corrupted, its checksum won't match what ZFS has as a record for it, and the damaged copy will be replaced with a good one from a different hard 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've avoided any chance of files getting damaged silently as the servers where your semi-dedicated hosting account will be created use a powerful file system named ZFS. Its advantage over various other file systems is that it uses a unique checksum for each file - a digital fingerprint that is checked in real time. Since we keep all content on numerous 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 case there's a mismatch, the damaged copy is replaced with a healthy one from one of the other drives and considering that this happens right away, there is no chance that a damaged copy can remain on our web servers or that it could be copied to the other drives in the RAID. None of the other file systems work with this type of checks and in addition, even during a file system check following an unexpected blackout, none of them will identify silently corrupted files. In comparison, ZFS does not crash after a blackout and the constant checksum monitoring makes a time-consuming file system check unnecessary.