No Data Corruption & Data Integrity in Shared Web Hosting
If you host your sites in a shared web hosting account with our firm, you don't have to worry about your data ever getting damaged. We can ensure that as our cloud hosting platform uses the outstanding ZFS file system. The latter is the only file system which uses checksums, or unique digital fingerprints, for each and every file. All of the data that you upload will be stored in a RAID i.e. simultaneously on numerous NVMes. A lot of file systems synchronize the files between the different drives using this kind of a setup, but there is no real guarantee that a file will not be corrupted. This could occur during the writing process on any drive and afterwards a bad copy can be copied on all other drives. What is different on our platform is that ZFS analyzes the checksums of all files on all drives in real time and in case a corrupted file is located, it is swapped with a good copy with the correct checksum from another drive. In this way, your info will stay undamaged no matter what, even if a whole drive fails.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any probability of files getting corrupted silently as the servers where your semi-dedicated hosting account will be created take advantage of a powerful file system named ZFS. Its key advantage over various other file systems is that it uses a unique checksum for every single file - a digital fingerprint that is checked in real time. Since we keep all content on multiple NVMe drives, ZFS checks if the fingerprint of a file on one drive corresponds to the one on the other drives and the one it has stored. If there's a mismatch, the corrupted copy is replaced with a healthy one from one of the other drives and considering that it happens instantly, there's no chance that a corrupted copy could remain on our website hosting servers or that it could be duplicated to the other hard drives in the RAID. None of the other file systems include this type of checks and what's more, even during a file system check right after an unexpected blackout, none of them will find silently corrupted files. In contrast, ZFS does not crash after a blackout and the constant checksum monitoring makes a lenghty file system check obsolete.