No Data Corruption & Data Integrity in Hosting
We warrant the integrity of the information uploaded in any hosting account that is created on our cloud platform since we employ the advanced ZFS file system. The latter is the only one that was designed to avert silent data corruption using a unique checksum for each and every file. We will store your data on multiple NVMe drives that work in a RAID, so exactly the same files will be present on several places at the same time. ZFS checks the digital fingerprint of all files on all drives in real time and if the checksum of any file differs from what it should be, the file system replaces that file with an undamaged copy from a different drive in the RAID. There's no other file system which uses checksums, so it is possible for data to be silently corrupted and the bad file to be reproduced on all drives with time, but since that can never happen on a server running ZFS, you won't have to worry about the integrity of your information.
No Data Corruption & Data Integrity in Semi-dedicated Hosting
We've avoided any probability of files getting damaged silently since the servers where your semi-dedicated hosting account will be created use a powerful file system called ZFS. Its key advantage over alternative file systems is that it uses a unique checksum for each file - a digital fingerprint that's checked in real time. As we keep all content on a number of NVMe drives, ZFS checks if the fingerprint of a file on one drive matches the one on the rest of the 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 because this happens instantly, there's no chance that a damaged copy could remain on our servers or that it could be duplicated to the other hard drives in the RAID. None of the other file systems work with this type of checks and what is more, even during a file system check following a sudden power failure, none of them can find silently corrupted files. In comparison, ZFS will not crash after a power failure and the constant checksum monitoring makes a lenghty file system check unnecessary.