Data corruption is the unintentional change of a file or the loss of information that usually occurs during reading or writing. The reason may be hardware or software failure, and as a result, a file could become partially or fully corrupted, so it'll no longer function correctly as its bits will be scrambled or lacking. An image file, for example, will no longer display an actual image, but a random combination of colors, an archive will be impossible to unpack since its content will be unreadable, and so on. When such a problem appears and it's not found by the system or by an admin, the data will be corrupted silently and when this happens on a disk drive which is part of a RAID array where the data is synchronized between various drives, the corrupted file will be reproduced on all of the other drives and the harm will be long term. A large number of widespread file systems either do not offer real-time checks or do not have high quality ones which will detect an issue before the damage is done, so silent data corruption is a common matter on internet hosting servers where substantial volumes of data are kept.

No Data Corruption & Data Integrity in Hosting

We warrant the integrity of the data uploaded in any hosting account which is created on our cloud platform as we work with the advanced ZFS file system. The aforementioned is the only one that was designed to avoid silent data corruption thanks to a unique checksum for every single file. We will store your info on a large number of SSD drives which operate in a RAID, so identical files will exist on several places simultaneously. ZFS checks the digital fingerprint of all the files on all of the drives in real time and in the event that the checksum of any file is different from what it has to be, the file system replaces that file with an undamaged version from a different drive from the RAID. There's no other file system that uses checksums, so it's possible for data to be silently corrupted and the bad file to be duplicated on all drives over time, but since this can never happen on a server running ZFS, you do not have to concern yourself with the integrity of your information.