The process of files being damaged resulting from some hardware or software failure is referred to as data corruption and this is one of the main problems that web hosting companies face because the larger a hard drive is and the more data is placed on it, the more likely it is for data to get corrupted. You'll find a couple of fail-safes, still often the data becomes damaged silently, so neither the particular file system, nor the administrators notice anything. Consequently, a bad file will be treated as a regular one and if the hard drive is part of a RAID, that particular file will be duplicated on all other disk drives. In principle, this is for redundancy, but in reality the damage will be worse. When a given file gets damaged, it will be partially or entirely unreadable, so a text file will not be readable, an image file will present a random mix of colors in case it opens at all and an archive will be impossible to unpack, and you risk sacrificing your site content. Although the most commonly used server file systems feature various checks, they often fail to identify some problem early enough or require a vast period of time to check all the files and the web server will not be operational for the time being.
No Data Corruption & Data Integrity in Shared Web Hosting
We warrant the integrity of the data uploaded in each shared web hosting account that is created on our cloud platform since we employ the advanced ZFS file system. The aforementioned is the only one that was designed to prevent silent data corruption via a unique checksum for every single file. We shall store your information on a number of SSD drives which operate in a RAID, so exactly the same files will be accessible on several places concurrently. ZFS checks the digital fingerprint of all of the files on all the drives in real time and in the event that the checksum of any file is different from what it should be, the file system replaces that file with an undamaged copy from another drive within the RAID. There's no other file system which uses checksums, so it's possible for data to become silently damaged and the bad file to be reproduced on all drives over time, but since that can never happen on a server running ZFS, you won't have to worry about the integrity of your information.