No Data Corruption & Data Integrity
See what No Data Corruption & Data Integrity is and how it could be beneficial for the files within your website hosting account.
Data corruption is the unintended modification of a file or the loss of information that usually occurs during reading or writing. The reason can be hardware or software fail, and consequently, a file may become partially or entirely corrupted, so it will no longer function correctly as its bits shall be scrambled or lost. An image file, for instance, will no longer show an authentic image, but a random combination of colors, an archive will be impossible to unpack since its content will be unreadable, and so on. If this kind of an issue appears and it is not noticed by the system or by an administrator, the data will get corrupted silently and if this happens on a disk drive that's a part of a RAID array where the info is synchronized between various drives, the corrupted file shall be duplicated on all the other drives and the damage will be permanent. A large number of commonly used file systems either don't feature real-time checks or don't have good ones which can detect an issue before the damage is done, so silent data corruption is a very common issue on hosting servers where huge volumes of data are stored.
No Data Corruption & Data Integrity in Shared Web Hosting
The integrity of the data that you upload to your new shared web hosting account shall be ensured by the ZFS file system that we work with on our cloud platform. Most of the hosting service providers, like our firm, use multiple hard drives to keep content and since the drives work in a RAID, the exact same data is synchronized between the drives all of the time. In case a file on a drive becomes corrupted for whatever reason, however, it's likely that it will be duplicated on the other drives since alternative file systems don't feature special checks for that. Unlike them, ZFS applies a digital fingerprint, or a checksum, for each file. In the event that a file gets damaged, its checksum won't match what ZFS has as a record for it, so the bad copy shall be substituted with a good one from another disk drive. As this happens in real time, there is no possibility for any of your files to ever get damaged.