Specialists in RAID and virtualization data recovery
Our team of specialized engineers develops data recovery processes for any type of RAID.
In 2011 Serman recovered data from an Oracle ASM file system for the first time in Europe. There was a failure in an HP EVA 4000 fiber channel disk drives cabinet. Both the manufacturer and the software developer predicted that it would be irrecoverable. We got 100% of the data back.
Any type of RAID
- RAID 0
- RAID 1E
- RAID 1
- RAID 0+1
- RAID 10
- RAID 3
- RAID 4
- RAID 5
- RAID 5E
- RAID 5EE
- RAID 6
- RAID 50
- RAID 51
Any operative system
- WINDOWS (NTFS, FAT)
- MAC
- LINUX
- VMWARE
- HYPER-V
- UNIX
- Discontinued operative systems (Pick, Novell NetWare, etc...)
Any type of failure
- Logical failure (data are not accessible, but the hardware is not damaged -data deletion, formatting, corruption, virus…-)
- Physical failure (mechanical, electronic, controller or low-level control software failure)
- Encryption
- Water damage
- Fire damage
Any brand
- Dell
- D-Link
- Drobo
- EMC
- FalconStor
- Fujitsu
- Hitachi
- Iomega
- HP
- IBM
- Intel
- LaCie
- NetApp
- Oracle/Sun
- Seagate
- QNAP
- Synology
- Western Digital
RAID data recovery - Base price reference
*Taxes not included.
| From 475€ * | From 950€ * | From 1.475€ * | ASK FOR A QUOTE | |
|---|---|---|---|---|
| RAID 1 | RAID 0 or 0+1 | RAID 5 or 6 | Virtualization | Special services |
RAID: "Redundant Array of Independent Disks".
A RAID 1 is made up of two units. The RAID’s size will be the same as one of them. If the two hard drives have different size, the RAID’s size will be that of the smallest one (although usually the two hard drives are identical).
The RAID 1 (mirroring) writes the same information (duplicated) in both hard drives. Therefore, a data loss is caused by the failure of both units or the RAID manager (controller, hard drives cabinet, RAID control software, etc.)
A RAID 1 is made up of two units. The RAID’s size will be the same as one of them. If the two hard drives have different size, the RAID’s size will be that of the smallest one (although usually the two hard drives are identical).
The RAID 1 (mirroring) writes the same information (duplicated) in both hard drives. Therefore, a data loss is caused by the failure of both units or the RAID manager (controller, hard drives cabinet, RAID control software, etc.)
A RAID 0 is made up of two or more units. The RAID’s size will be the sum of both of them.
The RAID 0 (striped) is not a redundant system, it does not have parity. It was conceived to achieve logical volumes bigger than the size of one hard drive, as well as to increase the performance by adding up the transfer rate of all the units. Files are saved in small pieces distributed in the different units. Therefore, the failure of one of the units will make the whole RAID fail. There is no theoretical limit to the number of units, but in practice it is restricted by the hardware (controller, cabinet, etc.). Usually it has between two and four units.
A RAID 0+1 has two identical RAID 0 (one of them is mirroring the other one).
The RAID 0 (striped) is not a redundant system, it does not have parity. It was conceived to achieve logical volumes bigger than the size of one hard drive, as well as to increase the performance by adding up the transfer rate of all the units. Files are saved in small pieces distributed in the different units. Therefore, the failure of one of the units will make the whole RAID fail. There is no theoretical limit to the number of units, but in practice it is restricted by the hardware (controller, cabinet, etc.). Usually it has between two and four units.
A RAID 0+1 has two identical RAID 0 (one of them is mirroring the other one).
A RAID 5 is made up of three or more units (the RAID’s size will be that of the smallest hard drive multiplied by the number of units minus one). A RAID 6 is made up of four or more units (the RAID’s size will be that of the smallest hard drive multiplied by the number of units minus two).
In RAID 5 and 6 files are saved in small pieces distributed in the different units. There is a replication sequential pattern to those pieces that acts as parity, so we lose the capacity of one of the units but, thanks to that, the system will keep working even after the failure of one of the hard drives. RAID 6 is different from RAID 5 because it has two parities (the capacity of two units is lost, but the system will keep working even if two of the units have failed).
Any data loss is necessarily caused by the failure of two (RAID 5) or three (RAID 6) units or the RAID manager (controller, hard drives cabinet, RAID control software, etc.).
In RAID 5 and 6 files are saved in small pieces distributed in the different units. There is a replication sequential pattern to those pieces that acts as parity, so we lose the capacity of one of the units but, thanks to that, the system will keep working even after the failure of one of the hard drives. RAID 6 is different from RAID 5 because it has two parities (the capacity of two units is lost, but the system will keep working even if two of the units have failed).
Any data loss is necessarily caused by the failure of two (RAID 5) or three (RAID 6) units or the RAID manager (controller, hard drives cabinet, RAID control software, etc.).
Virtualization systems emulate physical servers in a set of software systems managing a set of files. We can come across virtual hard drives represented by one file, virtual machines represented by several files, and resources managers represented by a program.
The most widespread are VMWare and Hyper V. The failure of any part of the system will mean data loss. To recover the data, it will be necessary to know the details of the platform setup (version, snapshots yes or no, fixed or dynamic provisioning, etc.).
The most widespread are VMWare and Hyper V. The failure of any part of the system will mean data loss. To recover the data, it will be necessary to know the details of the platform setup (version, snapshots yes or no, fixed or dynamic provisioning, etc.).
Some situations, platforms or systems must be managed by our special services team (R&D).
There may be systems that could not be recovered before because of its little market penetration, because they are customized platforms, or because they have very specific requirements.
In order to give a quote for these services a project will have to be designed first.
(Obsolete operative systems, like Pick, Novell, HP-UX; proprietary platforms like ZFS (Sun), Oracle ASM, Btrfs (Synology); advanced hardware platforms like Fibre Channel, cabinets with LUN setup distributed in metaLUNs, etc.).
There may be systems that could not be recovered before because of its little market penetration, because they are customized platforms, or because they have very specific requirements.
In order to give a quote for these services a project will have to be designed first.
(Obsolete operative systems, like Pick, Novell, HP-UX; proprietary platforms like ZFS (Sun), Oracle ASM, Btrfs (Synology); advanced hardware platforms like Fibre Channel, cabinets with LUN setup distributed in metaLUNs, etc.).