No Data Corruption & Data Integrity
What exactly does the 'No Data Corruption & Data Integrity' slogan mean to every hosting account owner?
Data corruption is the unintentional change of a file or the loss of info that often occurs during reading or writing. The reason could be hardware or software fail, and because of this, a file can become partially or completely corrupted, so it will no longer function properly because its bits will be scrambled or missing. An image file, for instance, will no longer show a real image, but a random mix of colors, an archive will be impossible to unpack since its content will be unreadable, etcetera. If this kind of a problem appears and it's not recognized by the system or by an administrator, the data will get corrupted silently and in case this happens on a disk drive that's a part of a RAID array where the info is synchronized between various different drives, the corrupted file shall be copied on all other drives and the damage will become long term. A large number of widely used file systems either don't have real-time checks or do not have high quality ones which will detect an issue before the damage is done, so silent data corruption is a common matter on internet hosting servers where large amounts of information are kept.
No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data which you upload to your new shared hosting
account shall be guaranteed by the ZFS file system that we take advantage of on our cloud platform. The vast majority of internet hosting providers, like our firm, use multiple hard drives to keep content and considering that the drives work in a RAID, the exact same information is synchronized between the drives all of the time. If a file on a drive becomes corrupted for whatever reason, however, it's more than likely that it will be duplicated on the other drives since other file systems do not include special checks for that. Unlike them, ZFS applies a digital fingerprint, or a checksum, for each and every file. If a file gets damaged, its checksum won't match what ZFS has as a record for it, so the bad copy will be substituted with a good one from a different drive. Due to the fact that this happens instantly, there is no risk for any of your files to ever be corrupted.