The process of files getting damaged resulting from some hardware or software failure is known as data corruption and this is one of the main problems that Internet hosting companies face as the larger a hard disk drive is and the more information is placed on it, the more likely it is for data to be corrupted. You'll find a couple of fail-safes, still often the information is damaged silently, so neither the file system, nor the admins detect a thing. As a result, a damaged file will be handled as a standard one and if the HDD is a part of a RAID, that file will be copied on all other drives. In principle, this is done for redundancy, but in practice the damage will get even worse. The moment a file gets damaged, it will be partially or fully unreadable, therefore a text file will not be readable, an image file will show a random mix of colors if it opens at all and an archive will be impossible to unpack, so you risk losing your website content. Although the most frequently used server file systems have various checks, they quite often fail to discover some problem early enough or require a long amount of time in order to check all files and the hosting server will not be operational in the meantime.

No Data Corruption & Data Integrity in Shared Hosting

We guarantee the integrity of the info uploaded in every shared hosting account that is generated on our cloud platform because we use the advanced ZFS file system. The latter is the only one that was designed to avoid silent data corruption using a unique checksum for each file. We shall store your info on a large number of SSD drives which work in a RAID, so the exact same files will be present on several places concurrently. ZFS checks the digital fingerprint of all files on all the drives in real time and in case the checksum of any file is different from what it should be, the file system replaces that file with a healthy version from a different drive from the RAID. No other file system uses checksums, so it is possible for data to be silently damaged and the bad file to be replicated on all drives over time, but since that can never happen on a server running ZFS, you will not have to worry about the integrity of your data.