No Data Corruption & Data Integrity
What exactly does the 'No Data Corruption & Data Integrity' slogan mean to each hosting account owner?
The process of files getting corrupted resulting from some hardware or software failure is called data corruption and this is among the main problems which hosting companies face because the larger a hard disk drive is and the more information is placed on it, the more likely it is for data to get corrupted. You'll find various fail-safes, but often the info gets damaged silently, so neither the particular file system, nor the administrators notice a thing. Because of this, a corrupted file will be treated as a standard one and if the hard disk drive is a part of a RAID, that particular file will be copied on all other disk drives. In theory, this is for redundancy, but in reality the damage will be even worse. When a given file gets corrupted, it will be partly or fully unreadable, which means that 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 will be impossible to unpack, so you risk sacrificing your website content. Although the most frequently used server file systems feature various checks, they are likely to fail to identify some problem early enough or require a vast time period to be able to check all of the files and the server will not be functional in the meantime.
No Data Corruption & Data Integrity in Hosting
The integrity of the data that you upload to your new hosting account will be guaranteed by the ZFS file system which we work with on our cloud platform. The majority of web hosting suppliers, like our firm, use multiple hard drives to keep content and since the drives work in a RAID, the exact same information is synchronized between the drives all the time. If a file on a drive becomes damaged for whatever reason, yet, it's very likely that it will be reproduced on the other drives since other file systems don't include special checks for that. Unlike them, ZFS applies a digital fingerprint, or a checksum, for every single file. In case a file gets damaged, its checksum will not match what ZFS has as a record for it, therefore the bad copy will be swapped with a good one from another disk drive. Due to the fact that this happens right away, there's no possibility for any of your files to ever be damaged.