No Data Corruption & Data Integrity in Shared Hosting
We've resolved the issue of silent data corruption on our shared hosting servers by using the leading-edge Z file system, or ZFS. The latter is superior to other file systems as it is the only one out there which checks all the files in real time by employing a checksum - a digital identifier that's unique for each file. When you upload content to your account, it'll be stored on several SSD drives and continually synchronized between them for redundancy. ZFS constantly analyzes the checksum of all files and in the event that any file is detected as corrupted, it is replaced right away with a good copy from another disk. As this happens in real time, there is no risk that a bad file may remain or may be copied on the rest of the SSDs. ZFS needs lots of physical memory to execute the real-time checks and the advantage of our cloud web hosting platform is that we employ multiple powerful servers working together. In case you host your sites with us, your data will be undamaged no matter what.
No Data Corruption & Data Integrity in Semi-dedicated Servers
We have avoided any risk of files getting corrupted silently as the servers where your semi-dedicated server account will be created employ a powerful file system named ZFS. Its key advantage over alternative file systems is that it uses a unique checksum for every single file - a digital fingerprint that is checked in real time. Since we store all content on multiple SSD drives, ZFS checks whether the fingerprint of a file on one drive matches the one on the rest of the drives and the one it has stored. In the event that there's a mismatch, the corrupted copy is replaced with a good one from one of the other drives and because it happens instantly, there's no chance that a corrupted copy can remain on our servers or that it can be duplicated to the other drives in the RAID. None of the other file systems work with this type of checks and furthermore, even during a file system check after an unexpected blackout, none of them can identify silently corrupted files. In contrast, ZFS doesn't crash after a blackout and the continual checksum monitoring makes a time-consuming file system check unneeded.