No Data Corruption & Data Integrity
See what No Data Corruption & Data Integrity is and how it can be beneficial for the files within your web hosting account.
The process of files getting damaged owing to some hardware or software failure is known as data corruption and this is among the main problems that 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 be corrupted. You'll find a couple of fail-safes, yet often the information gets damaged silently, so neither the file system, nor the administrators notice anything. Consequently, a bad file will be treated as a regular one and if the hard disk is part of a RAID, that particular file will be copied on all other disk drives. In principle, this is for redundancy, but in reality the damage will be even worse. Once some file gets damaged, it will be partially or entirely unreadable, so a text file will no longer be readable, an image file will display a random mix of colors in case it opens at all and an archive will be impossible to unpack, so you risk losing your website content. Although the most well-known server file systems have various checks, they frequently fail to identify some problem early enough or require an extensive amount of time to be able to check all the files and the web server will not be functional for the time being.
No Data Corruption & Data Integrity in Shared Website Hosting
We guarantee the integrity of the info uploaded in each shared website hosting account which is created on our cloud platform because we work with the advanced ZFS file system. The aforementioned is the only one which was designed to avoid silent data corruption thanks to a unique checksum for each file. We will store your information on a large number of SSD drives which work in a RAID, so the very same files will be present on several places simultaneously. ZFS checks the digital fingerprint of all of the files on all the drives in real time and in case the checksum of any file differs from what it needs to be, the file system swaps that file with an undamaged copy from another drive in the RAID. No other file system uses checksums, so it's possible for data to become silently damaged and the bad file to be replicated on all drives with time, but since this can never happen on a server running ZFS, you don't have to worry about the integrity of your information.