No Data Corruption & Data Integrity
Discover what No Data Corruption & Data Integrity is and how it could be good for the files in your hosting account.
The process of files getting damaged because of some hardware or software failure is referred to as data corruption and this is one of the main problems which web hosting companies face since the larger a hard disk is and the more info is filed on it, the more likely it is for data to get corrupted. You will find different fail-safes, still often the data gets corrupted silently, so neither the file system, nor the administrators detect anything. Because of this, a damaged file will be handled as a standard one and if the HDD is a part of a RAID, that file will be duplicated on all other disk drives. In theory, this is for redundancy, but in reality the damage will be even worse. When a file gets corrupted, it will be partially or fully unreadable, so a text file will no longer be readable, an image file will show a random blend of colors in case it opens at all and an archive shall be impossible to unpack, and you risk sacrificing your site content. Although the most widespread server file systems include various checks, they frequently fail to find a problem early enough or require an extensive amount of time to check all the files and the web server will not be operational for the time being.
No Data Corruption & Data Integrity in Web Hosting
The integrity of the data that you upload to your new web hosting account will be ensured by the ZFS file system that we make use of on our cloud platform. Most internet hosting providers, including our company, use multiple hard disk drives to keep content and since the drives work in a RAID, exactly the same data is synchronized between the drives at all times. If a file on a drive gets corrupted for some reason, however, it's more than likely that it will be copied on the other drives as alternative file systems do not feature special checks for that. Unlike them, ZFS employs a digital fingerprint, or a checksum, for every file. If a file gets corrupted, its checksum will not match what ZFS has as a record for it, which means that the bad copy will be substituted with a good one from a different hard disk. As this happens in real time, there's no possibility for any of your files to ever be corrupted.