Data corruption is the unintentional transformation of a file or the losing of info which often occurs during reading or writing. The reason may be hardware or software fail, and because of this, a file can become partially or completely corrupted, so it will no longer work correctly because its bits will be scrambled or missing. An image file, for example, will no longer show a real image, but a random mix of colors, an archive will be impossible to unpack since its content will be unreadable, and so on. In the event that this kind of a problem appears and it is not noticed by the system or by an admin, the data will get corrupted silently and if this happens on a disk drive that's a part of a RAID array where the data is synced between different drives, the corrupted file will be copied on all of the other drives and the harm will become permanent. A number of popular file systems either don't feature real-time checks or don't have high quality ones which can detect a problem before the damage is done, so silent data corruption is a rather common problem on internet hosting servers where huge volumes of info are kept.
No Data Corruption & Data Integrity in Shared Web Hosting
We warrant the integrity of the information uploaded in every single shared 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 avert silent data corruption using a unique checksum for each file. We shall store your information on multiple SSD drives that operate in a RAID, so identical files will exist on several places at the same time. ZFS checks the digital fingerprint of all the 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 replaces that file with an undamaged copy from a different drive inside the RAID. There's no other file system that uses checksums, so it is easy for data to get silently damaged and the bad file to be replicated on all drives with time, but since this can never happen on a server running ZFS, you don't have to worry about the integrity of your data.