No Data Corruption & Data Integrity
What does the 'No Data Corruption & Data Integrity' motto mean to every web hosting account owner?
The process of files getting corrupted caused by some hardware or software failure is known as data corruption and this is among the main problems that web hosting companies face since the larger a hard disk drive is and the more info is kept on it, the more likely it is for data to be corrupted. There are different fail-safes, yet often the info becomes corrupted silently, so neither the particular file system, nor the administrators notice anything. Because of this, a damaged file will be treated as a good one and if the HDD is a part of a RAID, the file will be copied on all other drives. In principle, this is done for redundancy, but in practice the damage will be worse. When a given file gets corrupted, it will be partially or fully unreadable, therefore a text file will not 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, so you risk sacrificing your website content. Although the most commonly used server file systems include various checks, they frequently fail to find a problem early enough or require an extensive period of time to be able to check all the files and the server will not be functional for the time being.
No Data Corruption & Data Integrity in Cloud Hosting
We warrant the integrity of the data uploaded in any cloud hosting account that is generated on our cloud platform due to the fact that we employ the advanced ZFS file system. The aforementioned is the only one that was designed to avoid silent data corruption through a unique checksum for every single file. We will store your information on a large number of NVMe drives which function in a RAID, so the same files will be present on several places at once. ZFS checks the digital fingerprint of all files on all of the drives in real time and in the event that the checksum of any file is different from what it needs to be, the file system swaps that file with an undamaged copy from some other drive in the RAID. No other file system uses checksums, so it's easy for data to be silently damaged and the bad file to be replicated on all drives with time, but since this can never happen on a server using ZFS, you will not have to concern yourself with the integrity of your data.