No Data Corruption & Data Integrity
Uncover what ‘No Data Corruption & Data Integrity’ means for the data inside your hosting account.
Data corruption is the unintended change of a file or the losing of info that usually occurs during reading or writing. The reason could be hardware or software fail, and due to this fact, a file may become partially or fully corrupted, so it will no longer function correctly because its bits will be scrambled or lost. An image file, for example, will no longer display an actual image, but a random combination of colors, an archive will be impossible to unpack as its content will be unreadable, etc. In the event that such an issue appears and it isn't found by the system or by an administrator, the data will become corrupted silently and in case this happens on a drive which is a part of a RAID array where the info is synchronized between various different drives, the corrupted file will be replicated on all of the other drives and the damage will be permanent. A number of popular file systems either do not feature real-time checks or don't have high quality ones that will detect a problem before the damage is done, so silent data corruption is a rather common issue on internet hosting servers where large amounts of information are stored.
No Data Corruption & Data Integrity in Cloud Hosting
The integrity of the data which you upload to your new cloud hosting account will be ensured by the ZFS file system which we take advantage of on our cloud platform. The vast majority of hosting providers, like our firm, use multiple hard drives to keep content and considering that the drives work in a RAID, the same information is synchronized between the drives all of the time. When a file on a drive gets damaged for reasons unknown, yet, it's likely that it will be reproduced on the other drives as alternative file systems don't have special checks for this. Unlike them, ZFS employs a digital fingerprint, or a checksum, for each and every file. In the event that a file gets damaged, its checksum won't match what ZFS has as a record for it, therefore the bad copy shall be swapped with a good one from a different hard drive. As this happens in real time, there's no possibility for any of your files to ever get damaged.