No Data Corruption & Data Integrity
Find out what ‘No Data Corruption & Data Integrity’ indicates for the data within your hosting account.
The process of files getting corrupted because of some hardware or software failure is referred to as data corruption and this is one of the main problems which web hosting companies face because the larger a hard disk is and the more information is filed on it, the more likely it is for data to get corrupted. There're several fail-safes, yet often the information is corrupted silently, so neither the particular file system, nor the admins notice a thing. As a result, a damaged file will be handled as a regular one and if the hard disk drive is part of a RAID, that particular file will be duplicated on all other drives. Theoretically, this is done for redundancy, but in practice the damage will get worse. Once a given file gets corrupted, it will be partially or fully unreadable, therefore a text file will no longer be readable, an image file will present a random blend of colors if it opens at all and an archive shall be impossible to unpack, and you risk sacrificing your content. Although the most commonly used server file systems include various checks, they quite often fail to detect a problem early enough or require a vast period of time to be able to check all the files and the web server will not be functional in the meantime.
No Data Corruption & Data Integrity in Website Hosting
We guarantee the integrity of the info uploaded in every single website hosting account which is generated on our cloud platform as we work with the advanced ZFS file system. The aforementioned is the only one which was designed to avoid silent data corruption via a unique checksum for every single file. We shall store your information on multiple SSD drives which work in a RAID, so the same files will be accessible on several places concurrently. ZFS checks the digital fingerprint of all files on all of the drives in real time and if the checksum of any file is different from what it has to be, the file system replaces that file with a healthy copy from a different drive from the RAID. No other file system uses checksums, so it's easy for data to get 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 won't have to concern yourself with the integrity of your info.