No Data Corruption & Data Integrity
Find out what No Data Corruption & Data Integrity is and how it could be good for the files within your web hosting account.
The process of files getting corrupted as a consequence of some hardware or software failure is called data corruption and this is one of the main problems that web hosting companies face since the larger a hard disk is and the more information is stored on it, the much more likely it is for data to become corrupted. You can find several fail-safes, but often the information becomes damaged silently, so neither the file system, nor the admins notice anything. Thus, a bad file will be treated as a standard 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 for redundancy, but in reality the damage will get even worse. When a file gets damaged, it will be partially or fully unreadable, which means that 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 site content. Although the most frequently used server file systems have various checks, they quite often fail to identify a problem early enough or require an extensive amount of time to check all files and the web hosting server will not be functional for the time being.
-
No Data Corruption & Data Integrity in Shared Website Hosting
The integrity of the data that you upload to your new
shared website hosting account shall be guaranteed by the ZFS file system that we use on our cloud platform. The majority of web hosting suppliers, like our company, use multiple hard drives to keep content and since the drives work in a RAID, the same info is synchronized between the drives at all times. In case a file on a drive is corrupted for some reason, yet, it is more than likely that it will be copied on the other drives since other file systems don't include special checks for that. In contrast to them, ZFS works with a digital fingerprint, or a checksum, for every file. In case a file gets corrupted, its checksum won't match what ZFS has as a record for it, and the damaged copy shall be replaced with a good one from a different hard disk drive. Due to the fact that this happens immediately, there's no possibility for any of your files to ever be corrupted.
-
No Data Corruption & Data Integrity in Semi-dedicated Servers
We have avoided any risk of files getting damaged silently due to the fact that the servers where your
semi-dedicated server account will be created take advantage of a powerful file system named ZFS. Its advantage over alternative file systems is that it uses a unique checksum for each and every file - a digital fingerprint that is checked in real time. Since we save all content on numerous NVMe drives, ZFS checks whether the fingerprint of a file on one drive corresponds to the one on the remaining drives and the one it has saved. In the event that there is a mismatch, the bad copy is replaced with a good one from one of the other drives and considering that this happens right away, there's no chance that a corrupted copy could remain on our web servers or that it can be duplicated to the other drives in the RAID. None of the other file systems include such checks and what's more, even during a file system check right after a sudden power failure, none of them can identify silently corrupted files. In comparison, ZFS doesn't crash after a blackout and the constant checksum monitoring makes a lenghty file system check unnecessary.