The process of files getting damaged as a consequence of some hardware or software failure is referred to as data corruption and this is among the main problems which hosting companies face since the larger a hard disk is and the more information is stored on it, the more likely it is for data to be corrupted. There're a couple of fail-safes, but often the info becomes damaged silently, so neither the particular file system, nor the admins see anything. As a result, a bad file will be treated as a standard one and if the HDD is part of a RAID, that file will be copied on all other disk drives. In principle, this is for redundancy, but in reality the damage will get worse. The moment some file gets damaged, it will be partially or fully unreadable, so a text file will not be readable, an image file will present a random blend of colors in case it opens at all and an archive shall be impossible to unpack, so you risk sacrificing your content. Although the most widespread server file systems include various checks, they often fail to identify a problem early enough or require a vast time period in order to check all of the files and the web server will not be functional for the time being.
No Data Corruption & Data Integrity in Web Hosting
We warrant the integrity of the data uploaded in every single web hosting account which is created on our cloud platform due to the fact that we use the advanced ZFS file system. The latter is the only one which was designed to avoid silent data corruption thanks to a unique checksum for each and every file. We will store your information on a number of SSD drives that function in a RAID, so exactly the same files will exist on several places concurrently. ZFS checks the digital fingerprint of all files on all of the drives in real time and in case the checksum of any file is different from what it has to be, the file system swaps that file with a healthy copy from another drive inside the RAID. No other file system uses checksums, so it is possible for data to get silently corrupted and the bad file to be duplicated on all drives with time, but since this can never happen on a server running ZFS, you won't have to concern yourself with the integrity of your data.