No Data Corruption & Data Integrity in Hosting
We guarantee the integrity of the data uploaded in any hosting account that is made on our cloud platform since we work with the advanced ZFS file system. The latter is the only one that was designed to avert silent data corruption thanks to a unique checksum for each file. We will store your data on a large number of SSD drives which function in a RAID, so the very same files will exist on several places at once. ZFS checks the digital fingerprint of all the files on all the drives in real time and in case the checksum of any file differs from what it has to be, the file system swaps that file with a healthy copy from another drive within the RAID. There's no other file system which uses checksums, so it's easy for data to be silently damaged and the bad file to be reproduced on all drives over time, but since that can never happen on a server running ZFS, you don't have to concern yourself with the integrity of your info.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We have avoided any probability of files getting damaged silently since the servers where your semi-dedicated hosting account will be created use a powerful file system known as ZFS. Its main advantage over alternative file systems is that it uses a unique checksum for each file - a digital fingerprint which is checked in real time. Since we store all content on a number of SSD drives, ZFS checks whether the fingerprint of a file on one drive corresponds to the one on the remaining drives and the one it has saved. When there's a mismatch, the damaged copy is replaced with a good one from one of the other drives and because this happens in real time, there's 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 include such checks and what is more, even during a file system check following an unexpected power failure, none of them can detect silently corrupted files. In comparison, ZFS won't crash after a power loss and the continual checksum monitoring makes a lenghty file system check unnecessary.