No Data Corruption & Data Integrity
Uncover what ‘No Data Corruption & Data Integrity’ signifies for the info as part of your website hosting account.
The process of files getting corrupted because of some hardware or software failure is known as data corruption and this is one of the main problems that web hosting companies face as the larger a hard disk drive is and the more information is kept on it, the more likely it is for data to get corrupted. You will find several fail-safes, but often the information gets corrupted silently, so neither the particular file system, nor the administrators detect a thing. Thus, a bad file will be treated as a regular one and if the hard disk drive is part of a RAID, that file will be copied on all other disk drives. In theory, this is done for redundancy, but in reality the damage will be worse. Once some file gets corrupted, it will be partly or completely unreadable, therefore a text file will no longer be readable, an image file will present a random combination of colors in case 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 frequently fail to find some problem early enough or require an extensive time period in order to check all files and the web server will not be operational in the meantime.
No Data Corruption & Data Integrity in Shared Website Hosting
We warrant the integrity of the information uploaded in each shared website hosting account which is made on our cloud platform as we use the advanced ZFS file system. The latter is the only one that was designed to prevent silent data corruption via a unique checksum for each and every file. We will store your data on a number of SSD drives that operate in a RAID, so the very same files will be accessible on several places at the same time. ZFS checks the digital fingerprint of all the files on all the drives in real time and if the checksum of any file differs from what it should be, the file system swaps that file with a healthy copy from another drive inside the RAID. There's no other file system which uses checksums, so it's easy for data to be 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 do not have to concern yourself with the integrity of your data.