No Data Corruption & Data Integrity
Uncover what ‘No Data Corruption & Data Integrity’ means for the info inside your web hosting account.
Data corruption is the unintentional transformation of a file or the loss of info that often occurs during reading or writing. The reason may be hardware or software failure, and consequently, a file could become partially or completely corrupted, so it'll no longer work as it should since its bits shall be scrambled or lost. An image file, for instance, will no longer present a true image, but a random combination of colors, an archive will be impossible to unpack because its content will be unreadable, etcetera. In case such a problem occurs and it is not noticed by the system or by an admin, the data will become corrupted silently and when this happens on a disk drive that's a part of a RAID array where the information is synchronized between different drives, the corrupted file will be duplicated on all the other drives and the damage will be permanent. Numerous popular file systems either don't feature real-time checks or don't have good ones that will detect an issue before the damage is done, so silent data corruption is a very common matter on hosting servers where huge volumes of information are kept.
No Data Corruption & Data Integrity in Cloud Website Hosting
We warrant the integrity of the data uploaded in any cloud website hosting account which is generated on our cloud platform since we use the advanced ZFS file system. The latter is the only one which was designed to avoid silent data corruption through a unique checksum for each and every file. We shall store your info on a large number of NVMe drives that operate in a RAID, so the very same files will be available on several places simultaneously. ZFS checks the digital fingerprint of all the files on all drives in real time and in the event that the checksum of any file differs from what it needs to be, the file system swaps that file with a healthy copy from another drive inside the RAID. No other file system uses checksums, so it's possible for data to get silently corrupted and the bad file to be duplicated on all drives with time, but since this can never happen on a server using ZFS, you won't have to concern yourself with the integrity of your information.