No Data Corruption & Data Integrity
Discover what No Data Corruption & Data Integrity is and how it can be beneficial for the files inside your web hosting account.
Data corruption is the accidental change of a file or the losing of information which often occurs during reading or writing. The reason may be hardware or software malfunction, and due to this fact, a file can become partially or completely corrupted, so it will no longer function correctly since its bits will be scrambled or missing. An image file, for instance, will no longer display an authentic image, but a random combination of colors, an archive will be impossible to unpack because its content will be unreadable, etcetera. When such an issue occurs and it's not recognized by the system or by an administrator, the data will be corrupted silently and if this happens on a disk drive that's a part of a RAID array where the data is synced between various different drives, the corrupted file shall be replicated on all other drives and the damage will be long term. A number of widely used file systems either do not 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 rather common issue on internet hosting servers where large volumes of info are stored.
No Data Corruption & Data Integrity in Shared Hosting
The integrity of the data that you upload to your new shared hosting account shall be ensured by the ZFS file system that we use on our cloud platform. Most of the hosting suppliers, like our company, use multiple hard disks to keep content and because the drives work in a RAID, the same data is synchronized between the drives all the time. In case a file on a drive is damaged for reasons unknown, however, it's more than likely that it will be reproduced on the other drives because other file systems do not feature special checks for this. In contrast to them, ZFS employs a digital fingerprint, or a checksum, for each and every file. In the event that a file gets damaged, its checksum will not match what ZFS has as a record for it, so the bad copy will be substituted with a good one from another hard disk drive. Because this happens in real time, there is no possibility for any of your files to ever be damaged.