No Data Corruption & Data Integrity in Shared Hosting
We warrant the integrity of the information uploaded in each shared hosting account which is made on our cloud platform since we work with the advanced ZFS file system. The aforementioned is the only one that was designed to avert silent data corruption thanks to a unique checksum for each and every file. We will store your data on a large number of SSD drives which operate in a RAID, so identical 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 the event that the checksum of any file differs from what it has to be, the file system swaps that file with a healthy version from some other drive inside the RAID. No other file system uses checksums, so it is easy for data to get silently corrupted and the bad file to be duplicated on all drives over time, but since that can never happen on a server using ZFS, you don't have to worry about the integrity of your info.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We have avoided any risk of files getting corrupted 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 and every file - a digital fingerprint that's checked in real time. As 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 rest of the drives and the one it has saved. If there's a mismatch, the damaged copy is replaced with a good one from one of the other drives and considering that it happens right away, there is no chance that a corrupted copy can remain on our web servers or that it can be copied to the other hard disks in the RAID. None of the other file systems work with this kind of checks and in addition, even during a file system check right after a sudden power loss, none of them can discover silently corrupted files. In contrast, ZFS does not crash after a blackout and the constant checksum monitoring makes a lenghty file system check unneeded.