No Data Corruption & Data Integrity in Shared Hosting
We have dealt with the matter of silent data corruption on all our shared hosting servers by using the cutting-edge Z file system, or ZFS. The latter is better than other file systems as it is the only one in existence which checks all of the files in real time by using a checksum - a digital identifier which is unique for each and every file. When you upload content to your account, it'll be stored on several SSD drives and constantly synchronized between them for redundancy. ZFS constantly analyzes the checksum of all files and in case any file is detected as damaged, it's replaced quickly 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 remaining SSDs. ZFS requires lots of physical memory in order to carry out the real-time checks and the benefit of our cloud website hosting platform is that we take advantage of multiple very powerful servers working together. If you host your sites with us, your information will be intact no matter what.
No Data Corruption & Data Integrity in Semi-dedicated Servers
We have avoided any possibility of files getting damaged silently since the servers where your semi-dedicated server account will be created use a powerful file system known as ZFS. Its basic advantage over various other file systems is that it uses a unique checksum for each and every file - a digital fingerprint that's checked in real time. As we store all content on multiple SSD drives, ZFS checks whether the fingerprint of a file on one drive matches the one on the other drives and the one it has stored. In case there is a mismatch, the bad copy is replaced with a healthy one from one of the other drives and considering that this happens right away, there is no chance that a damaged copy can remain on our website hosting servers or that it can be copied to the other hard drives in the RAID. None of the other file systems include this type of checks and what is more, even during a file system check after a sudden blackout, none of them will identify silently corrupted files. In contrast, ZFS doesn't crash after a blackout and the regular checksum monitoring makes a lenghty file system check unnecessary.