No Data Corruption & Data Integrity
What exactly does the 'No Data Corruption & Data Integrity' motto mean to every web hosting account user?
The process of files being corrupted caused by some hardware or software failure is known as data corruption and this is among the main problems that Internet hosting companies face as the larger a hard drive is and the more info is placed on it, the more likely it is for data to get corrupted. There're different fail-safes, but often the information gets corrupted silently, so neither the file system, nor the admins notice a thing. Because of this, a corrupted file will be handled as a good one and if the hard disk is part of a RAID, that particular file will be duplicated on all other disk drives. Theoretically, this is for redundancy, but in reality the damage will be worse. The moment a given file gets damaged, it will be partly or entirely unreadable, so a text file will not be readable, an image file will display a random combination 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 commonly used server file systems feature various checks, they frequently fail to detect some problem early enough or require an extensive time period to be able to check all files and the server will not be functional for the time being.
No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data that you upload to your new shared hosting account will be guaranteed by the ZFS file system which we take advantage of on our cloud platform. The vast majority of internet hosting suppliers, including our company, use multiple hard drives to keep content and since the drives work in a RAID, the same info is synchronized between the drives all of the time. In case a file on a drive becomes damaged for some reason, yet, it is likely that it will be copied on the other drives because alternative file systems do not include special checks for that. Unlike them, ZFS employs a digital fingerprint, or a checksum, for each file. In case a file gets corrupted, its checksum won't match what ZFS has as a record for it, which means that the bad copy shall be swapped with a good one from another hard disk. Since this happens immediately, there is no possibility for any of your files to ever get damaged.