No Data Corruption & Data Integrity in Shared Hosting
In case you host your websites in a shared hosting account with our company, you will not have to worry about your data ever getting corrupted. We can ensure that as our cloud hosting platform uses the state-of-the-art ZFS file system. The latter is the only file system that works with checksums, or unique digital fingerprints, for every single file. All info that you upload will be stored in a RAID i.e. simultaneously on a number of SSDs. Many file systems synchronize the files between the separate drives with this kind of a setup, but there is no real warranty that a file will not get corrupted. This could happen at the time of the writing process on any drive and then a damaged copy may be copied on the rest of the drives. What makes the difference on our platform is that ZFS examines the checksums of all files on all drives live and if a corrupted file is found, it is replaced with a good copy with the correct checksum from another drive. In this way, your data will continue to be unharmed no matter what, even if a whole drive fails.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any possibility of files getting corrupted silently due to the fact that the servers where your semi-dedicated hosting account will be created work with a powerful file system named ZFS. Its basic advantage over various other file systems is that it uses a unique checksum for each and every file - a digital fingerprint which is checked in real time. As we keep all content on numerous SSD drives, ZFS checks if the fingerprint of a file on one drive matches the one on the other drives and the one it has saved. If there is a mismatch, the bad copy is replaced with a good one from one of the other drives and since this happens in real time, there's no chance that a damaged copy can remain on our web hosting servers or that it could be duplicated to the other drives in the RAID. None of the other file systems employ this kind of checks and furthermore, even during a file system check after an unexpected blackout, none of them will find silently corrupted files. In contrast, ZFS doesn't crash after a blackout and the continual checksum monitoring makes a time-consuming file system check obsolete.