No Data Corruption & Data Integrity
Discover what No Data Corruption & Data Integrity is and how it can be beneficial for the files in your web hosting account.
Data corruption is the damage of info caused by various software or hardware failures. After a file is corrupted, it will no longer work correctly, so an app will not start or will give errors, a text file shall be partially or completely unreadable, an archive file will be impossible to open and unpack, etc. Silent data corruption is the process of info getting harmed without any acknowledgement by the system or an admin, which makes it a significant problem for web hosting servers as failures are very likely to occur on bigger hard disk drives where vast volumes of information are placed. In case a drive is a part of a RAID and the data on it is replicated on other drives for redundancy, it's likely that the damaged file will be treated as an undamaged one and it'll be duplicated on all of the drives, making the damage permanent. Lots of the file systems which run on web servers nowadays often cannot locate corrupted files instantly or they need time-consuming system checks through which the server isn't functioning.
No Data Corruption & Data Integrity in Website Hosting
We warrant the integrity of the information uploaded in each website hosting account which is created on our cloud platform due to the fact that we employ the advanced ZFS file system. The latter is the only one which was designed to avoid silent data corruption thanks to a unique checksum for each and every file. We'll store your info on multiple SSD drives which work in a RAID, so the same files will be accessible on several places at once. ZFS checks the digital fingerprint of all of the files on all 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 an undamaged copy from a different drive within the RAID. There's no other file system that uses checksums, so it is easy for data to become silently damaged and the bad file to be replicated on all drives over time, but since that can never happen on a server running ZFS, you won't have to concern yourself with the integrity of your information.