No Data Corruption & Data Integrity
What does the 'No Data Corruption & Data Integrity' motto mean to every web hosting account user?
The process of files getting damaged due to some hardware or software failure is called data corruption and this is one of the main problems which Internet hosting companies face since the larger a hard disk drive is and the more info is kept on it, the much more likely it is for data to get corrupted. There are various fail-safes, but often the info becomes damaged silently, so neither the particular file system, nor the admins see a thing. Thus, a corrupted file will be handled as a good one and if the hard disk is part of a RAID, the file will be duplicated on all other drives. Theoretically, this is done for redundancy, but in reality the damage will get even worse. Once a file gets corrupted, it will be partially or completely unreadable, so a text file will not be readable, an image file will show a random blend of colors if it opens at all and an archive shall be impossible to unpack, so you risk losing your content. Although the most commonly used server file systems feature various checks, they quite often fail to discover a problem early enough or require an extensive time period to be able to check all of the files and the hosting server will not be functional for the time being.
No Data Corruption & Data Integrity in Hosting
The integrity of the data which you upload to your new hosting account shall be ensured by the ZFS file system that we employ on our cloud platform. Most of the internet hosting service providers, including our company, use multiple HDDs to keep content and considering that the drives work in a RAID, identical information is synchronized between the drives all the time. In case a file on a drive becomes damaged for reasons unknown, however, it's more than likely that it will be copied on the other drives because alternative file systems do not feature special checks for this. In contrast to them, ZFS works with a digital fingerprint, or a checksum, for each and every file. In case a file gets corrupted, its checksum will not match what ZFS has as a record for it, which means that the damaged copy will be substituted with a good one from a different hard disk drive. Because this happens right away, there's no risk for any of your files to ever get corrupted.