No Data Corruption & Data Integrity
See what No Data Corruption & Data Integrity is and how it can be beneficial for the files in your website hosting account.
The process of files being corrupted due to some hardware or software failure is known as data corruption and this is one of the main problems that Internet hosting companies face since the larger a hard disk drive is and the more data is stored on it, the much more likely it is for data to get corrupted. You will find a couple of fail-safes, yet often the information is damaged silently, so neither the file system, nor the admins notice a thing. Thus, a corrupted file will be handled 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 practice the damage will be worse. When some file gets corrupted, it will be partially or completely unreadable, which means that a text file will no longer be readable, an image file will display a random blend of colors in case it opens at all and an archive shall be impossible to unpack, and you risk losing your content. Although the most widespread server file systems feature various checks, they are likely to fail to find some problem early enough or require a long time period to be able to check all files and the web server will not be functional for the time being.
-
No Data Corruption & Data Integrity in Shared Hosting
We warrant the integrity of the information uploaded in any
shared hosting account that is generated on our cloud platform due to the fact that we work with the advanced ZFS file system. The aforementioned is the only one which was designed to avert silent data corruption thanks to a unique checksum for each and every file. We'll store your data on a number of NVMe drives that function in a RAID, so identical files will exist on several places at the same time. ZFS checks the digital fingerprint of all of the files on all drives in real time and in case the checksum of any file is different from what it should be, the file system replaces that file with a healthy version from a different drive inside the RAID. No other file system uses checksums, so it's possible for data to become silently corrupted and the bad file to be duplicated on all drives with time, but since this can never happen on a server running ZFS, you won't have to worry about the integrity of your information.
-
No Data Corruption & Data Integrity in Semi-dedicated Servers
We've avoided any risk of files getting damaged silently because the servers where your
semi-dedicated server account will be created work with a powerful file system known as ZFS. Its basic advantage over various other file systems is that it uses a unique checksum for each and every file - a digital fingerprint that's checked in real time. Since we store all content on numerous NVMe drives, ZFS checks if the fingerprint of a file on one drive matches the one on the remaining drives and the one it has stored. In case there's a mismatch, the damaged copy is replaced with a healthy one from one of the other drives and considering that it happens right away, there is no chance that a corrupted copy can remain on our web hosting servers or that it can be duplicated to the other hard drives in the RAID. None of the other file systems use this type of checks and what's more, even during a file system check right after an unexpected electrical power failure, none of them will identify silently corrupted files. In comparison, ZFS will not crash after a blackout and the regular checksum monitoring makes a lenghty file system check obsolete.