The process of files being damaged as a consequence of some hardware or software failure is referred to as data corruption and this is one of the main problems which web hosting companies face as the larger a hard disk is and the more information is stored on it, the much more likely it is for data to be corrupted. You can find different fail-safes, yet often the data gets damaged silently, so neither the file system, nor the admins see a thing. Thus, a damaged file will be treated as a standard one and if the hard disk is part of a RAID, that file will be duplicated on all other drives. Theoretically, this is for redundancy, but in reality the damage will get even worse. When a file gets corrupted, it will be partly or completely unreadable, which means that a text file will not be readable, an image file will present a random mix of colors if it opens at all and an archive will be impossible to unpack, and you risk losing your website content. Although the most popular server file systems include various checks, they are likely to fail to detect a problem early enough or require an extensive amount of time to check all of the files and the hosting server will not be functional in the meantime.

No Data Corruption & Data Integrity in Web Hosting

We guarantee the integrity of the information uploaded in every single web hosting account that is created on our cloud platform due to the fact that we employ the advanced ZFS file system. The aforementioned is the only one which was designed to prevent silent data corruption thanks to a unique checksum for each file. We'll store your information on multiple NVMe drives that operate in a RAID, so identical files will be available on several places at the same time. ZFS checks the digital fingerprint of all the files on all drives in real time and in case the checksum of any file differs from what it should be, the file system replaces that file with a healthy version from a different drive from the RAID. There's no other file system that uses checksums, so it's easy for data to get silently damaged and the bad file to be replicated on all drives with time, but since that can never happen on a server using ZFS, you won't have to concern yourself with the integrity of your data.

No Data Corruption & Data Integrity in Semi-dedicated Servers

We've avoided any risk of files getting damaged silently since the servers where your semi-dedicated server account will be created employ a powerful file system known as ZFS. Its advantage over other file systems is that it uses a unique checksum for every single file - a digital fingerprint that's checked in real time. As we store all content on a number of NVMe drives, ZFS checks whether the fingerprint of a file on one drive corresponds to the one on the other drives and the one it has saved. In case there's a mismatch, the bad copy is replaced with a good one from one of the other drives and considering that this happens right away, there's no chance that a corrupted copy can remain on our servers or that it can be duplicated to the other drives in the RAID. None of the other file systems employ this kind of checks and furthermore, even during a file system check after an unexpected electrical power failure, none of them will identify silently corrupted files. In comparison, ZFS will not crash after a power failure and the constant checksum monitoring makes a lenghty file system check obsolete.