No Data Corruption & Data Integrity
See what No Data Corruption & Data Integrity is and how it could be good for the files in your web hosting account.
Data corruption is the damage of info caused by various hardware or software fails. After a file gets corrupted, it will no longer function properly, so an application will not start or shall give errors, a text file shall be partially or completely unreadable, an archive file will be impossible to open then unpack, etc. Silent data corruption is the process of info getting harmed without any acknowledgement by the system or an admin, that makes it a significant problem for website hosting servers as problems are very likely to happen on larger hard drives where substantial volumes of information are stored. When a drive is a part of a RAID and the info on it is duplicated on other drives for redundancy, it is more than likely that the bad file will be treated as a good one and it'll be copied on all of the drives, making the damage permanent. A huge number of the file systems that operate on web servers nowadays often are not able to detect corrupted files right away or they need time-consuming system checks during which the server is not working.
No Data Corruption & Data Integrity in Shared Web Hosting
We warrant the integrity of the info uploaded in each shared web hosting account which is generated on our cloud platform since we use the advanced ZFS file system. The aforementioned is the only one which was designed to avoid silent data corruption using a unique checksum for each file. We shall store your info on a large number of SSD drives which function in a RAID, so identical files will exist on several places concurrently. ZFS checks the digital fingerprint of all of the files on all of the drives in real time and in case the checksum of any file is different from what it needs to be, the file system replaces that file with a healthy version from another drive in the RAID. No other file system uses checksums, so it is possible for data to be silently damaged and the bad file to be reproduced on all drives over time, but since that can never happen on a server using ZFS, you don't have to worry about the integrity of your data.