RAID in Cloud Website Hosting
The NVMe drives which our cutting-edge cloud web hosting platform employs for storage function in RAID-Z. This type of RAID is created to work with the ZFS file system that runs on the platform and it uses the so-called parity disk - a special drive where information stored on the other drives is copied with an extra bit added to it. In case one of the disks fails, your sites will continue working from the other ones and as soon as we replace the problematic one, the info that will be duplicated on it will be recovered from what is stored on the rest of the drives together with the information from the parity disk. This is done so as to be able to recalculate the elements of every file properly and to authenticate the integrity of the info duplicated on the new drive. This is an additional level of security for the info which you upload to your cloud website hosting account together with the ZFS file system that analyzes a unique digital fingerprint for each file on all the hard drives in real time.
RAID in Semi-dedicated Servers
The NVMe drives which are used for holding any site content uploaded to the semi-dedicated server accounts that we offer function in RAID-Z. This is a special setup where one or more hard drives are used for parity i.e. the system will include an extra bit to any data copied on this type of a hard drive. In case that a disk fails and is substituted with a new one, what information will be cloned on the latter will be a combination calculated between the data on the remaining disks and that on the parity one. This is done to guarantee that the data on the new drive shall be accurate. Throughout the process, the RAID will continue functioning adequately and the malfunctioning drive won't affect the adequate operation of your Internet sites in any way. Working with NVMes in RAID-Z is an excellent addition to the ZFS file system which runs on our state-of-the-art cloud platform with respect to preserving the integrity of your files because ZFS uses unique digital identifiers named checksums so as to prevent silent data corruption.