No Data Corruption & Data Integrity in Shared Hosting
If you host your sites in a shared hosting account with our firm, you do not need to worry about any of your data ever getting damaged. We can ensure that due to the fact that our cloud hosting platform uses the advanced ZFS file system. The latter is the only file system which works with checksums, or unique digital fingerprints, for each and every file. All of the information that you upload will be kept in a RAID i.e. simultaneously on many NVMes. A lot of file systems synchronize the files between the separate drives with this type of a setup, but there is no real warranty that a file won't be corrupted. This could occur during the writing process on any drive and after that a corrupted copy can be copied on the other drives. What is different on our platform is the fact that ZFS examines the checksums of all files on all of the drives instantly and if a corrupted file is found, it's swapped with a good copy with the correct checksum from some other drive. This way, your info will continue to be intact no matter what, even if a whole drive fails.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any chance of files getting damaged silently as the servers where your semi-dedicated hosting account will be created use a powerful file system called ZFS. Its basic advantage over other file systems is that it uses a unique checksum for every single file - a digital fingerprint that's checked in real time. Since we save all content on numerous NVMe drives, ZFS checks whether the fingerprint of a file on one drive matches the one on the other drives and the one it has saved. In the event that there is a mismatch, the bad copy is replaced with a good one from one of the other drives and considering that it happens right away, there is no chance that a damaged copy can remain on our website hosting servers or that it could be duplicated to the other hard disks in the RAID. None of the other file systems employ such checks and what's more, even during a file system check following an unexpected power failure, none of them can identify silently corrupted files. In contrast, ZFS doesn't crash after a blackout and the regular checksum monitoring makes a lenghty file system check unneeded.