Oracle / Sun Microsystems Server data recovery

Sun Microsystems server Recovery - We help you after data loss

We provide multiple diagnosis options depending on the urgency of your data rescue case
After the diagnosis is completed you receive a fixed price offer
No hidden costs - Expenses are only incurred if the server data rescue is successful
The recovery of your Sun Microsystems server will be done by experienced and specially trained engineers
Fast reaction times - in urgent cases, we offer a 24x7 service
In-house research and development for fast virtual simulations of your server Array
More than 14.500 spare parts in Vienna, Hamburg and Amsterdam

Contact us - order your diagnosis today.

Possible reasons for a Sun Microsystems server failure

The statistical most common reason are physical defects of the integrated SAS or SCSI hard drives. An aborted Rebuild in succession can cause the RAID to go offline. This error pattern is no rarity, especially with older Sun Microsystems server models where a single read error on one of the other SAS or SCSI hard drive can suffice in order to abort the rebuild. But also defective RAID-controller are a common cause.

Core competence: RAID Recovery

With profound know-how and continuous research and development, Attingo is a leading provider for data recovery of enterprise storage systems in virtualized environments.

No matter what RAID-level is applied - RAID 0, RAID 1, RAID 3, RAID4, RAID 5, RAID 6,RAID 1+0, RAID 50 or RAID 60 - we recover your data from Sun Microsystem servers and Oracle servers.

Attingo has developed procedures, in order to simulate the RAID-systems via software. Our specialists recover RAID-systems even after fatal rebuilds with wrong hard drives, reboot with the wrong hard drive order or deleted/newly applied RAID configurations.

Host systems / File systems:

Solaris (ZFS, UFS)
Red Hat Enterprise Linux (Ext2, Ext3, XFS, Ext4)
SUSE Linux Enterprise Server (ReiserFS, OCFS)
VMware ESX Server 3.x (VMFS)
Microsoft Windows Standard/Enterprise Server 2003 (NTFS)

Follow the following steps after a Oracle / Sun Microsystems server failure

Do not reboot the server in order to prevent automatic rebuilds.
Power off the server immediately and do not restart it.
Mark each and every hard drive of the server-array with the corresponding slot number.
Additionally mark the as defective flagged hard drives by the RAID-controller.
Tell us the exact model number of the server (e.g. Sun StorEdge 3510).
Tell us the exact RAID-controller model (e.g. Sun StorageTek 2540 FC).
Do not open any hard drive, as this will negatively influence the chances for a successful recovery.
Tell us the applied RAID level (RAID 0, RAID 1, RAID 1+0, RAID 3, RAID 4, RAID 5, RAID 6)
Do not install anything onto the system, if even possible.

Attingo has already successfully recovered data from following models

X

Sun StorEdge 3000

StorEdge 3510 FC
StorEdge 3511 SA
Sun StorEdge 3320 SCSI
Sun StorEdge 3310
Sun StorEdge D1000
Sun StorEdge 3120
Sun StorEdge 6120
Sun StorEdge 6130
Sun StorEdge 6140
Sun StorEdge 6540
Sun StorEdge
Sun StorEdge 9970
Sun StorEdge 9910
Sun StorEdge 9960
Sun StorEdge 9980
Sun StorEdge 9985V
Sun StorEdge 9990V