No Data Corruption & Data Integrity
See what No Data Corruption & Data Integrity is and how it can be beneficial for the files inside your website hosting account.
Data corruption is the accidental change of a file or the losing of info which often occurs during reading or writing. The reason could be hardware or software failure, and due to this fact, a file may become partially or fully corrupted, so it'll no longer work as it should since its bits shall be scrambled or lacking. An image file, for example, will no longer display an actual image, but a random mix of colors, an archive will be impossible to unpack because its content will be unreadable, etc. If this kind of a problem occurs and it's not identified by the system or by an admin, the data will be corrupted silently and in case this happens on a disk drive that is part of a RAID array where the data is synchronized between various drives, the corrupted file will be duplicated on all of the other drives and the harm will become long term. A large number of widely used file systems either do not offer real-time checks or don't have high quality ones that can detect a problem before the damage is done, so silent data corruption is a common matter on hosting servers where substantial volumes of data are kept.
No Data Corruption & Data Integrity in Shared Hosting
We warrant the integrity of the info uploaded in each and every shared hosting account which is made on our cloud platform as we work with the advanced ZFS file system. The latter is the only one which was designed to avert silent data corruption using a unique checksum for each and every file. We will store your data on multiple NVMe drives that work in a RAID, so exactly the same files will be available on several places at the same time. ZFS checks the digital fingerprint of all files on all drives in real time and if the checksum of any file differs from what it needs to be, the file system swaps that file with an undamaged copy from some other drive within the RAID. There's no other file system that uses checksums, so it is possible for data to become silently corrupted and the bad file to be reproduced on all drives with time, but since this can never happen on a server using ZFS, you won't have to worry about the integrity of your info.