No Data Corruption & Data Integrity
Find out what No Data Corruption & Data Integrity is and how it can be good for the files inside your website hosting account.
The process of files being damaged owing to some hardware or software failure is called data corruption and this is among the main problems that web hosting companies face because the larger a hard disk is and the more information is kept on it, the much more likely it is for data to become corrupted. You'll find several fail-safes, yet often the information becomes damaged silently, so neither the file system, nor the admins detect anything. As a result, a damaged file will be treated as a good one and if the hard disk drive is part of a RAID, the file will be copied on all other disk drives. In principle, this is for redundancy, but in reality the damage will get even worse. Once a given file gets damaged, it will be partly or completely unreadable, so a text file will not be readable, an image file will display a random blend of colors if it opens at all and an archive shall be impossible to unpack, and you risk losing your content. Although the most widely used server file systems include various checks, they often fail to find some problem early enough or require an extensive period of time to be able to check all the files and the web hosting server will not be functional for the time being.
No Data Corruption & Data Integrity in Cloud Hosting
The integrity of the data which you upload to your new cloud hosting account shall be ensured by the ZFS file system which we take advantage of on our cloud platform. The vast majority of web hosting providers, like our company, use multiple hard disk drives to keep content and because the drives work in a RAID, the same data is synchronized between the drives at all times. When a file on a drive is corrupted for whatever reason, however, it is very likely that it will be copied on the other drives as other file systems don't feature special checks for that. In contrast to them, ZFS employs a digital fingerprint, or a checksum, for each file. If a file gets corrupted, its checksum will not match what ZFS has as a record for it, so the bad copy will be replaced with a good one from another hard disk. As this happens right away, there's no risk for any of your files to ever get corrupted.
