SUN Microsystems Data Recovery Services

Established 1989
Emergency Service Available 24/7

We Recover Data Where Others Have Failed

Talk to a Technician not a Sales Person

Confidentiality is Assured. Non-Disclosures signed and any other Documents required by your Company.

 

Sun Solaris Data Recovery (SCO Recovery )

Mission critical data stored on multi-arrays require data recovery engineers with the experience ONLY DRC can provide.

Data Recovery Clinic has successfully recovered data from up to 12 Fibre Channel ports in dual RAID controller configurations where one or more drives have failed.

The most common problems are hardware failures that lead to configuration corruption. At this time DRC can still recover data even after an initialization.

In several instances data corruption is due to SATA, SAS or SCSI drive failures that are intermittent. The failure is not significant enough to red light, but still causes sectors and data to be overwritten causing corruption that is often misdiagnosed by phone support personnel.

 

When Lucent Technologies after 3 days working with engineers at Sun where told that they had lost all the data on there 4 TeraByte Raid and there was nothing that could be done. Someone said call Data Recovery Clinic. We flew out to Colorado that day. After 1 day we had figured it out and were recovering data by the 3rd day.
DRC has repaired and recovered data from many types of SAN/NAS devices as well as enterprise level Sun StorageTek.

If you are running Sun Sparc, Sun AMD Opteron, Sun Fire X series using the Sun Storage Tek Array in the TeraBytes or there Sun Blade Server, it doesn't matter we can recover your data. We have the knowledge and the experience.
NO OTHER COMPANY HAS THE EXPERIENCE WE DO TO RECOVER YOUR DATA!

The Sun StorEdge 9900 series includes the Sun StorEdge 9970, and 9980 systems. These devices require specialized equipment and software for data recovery. DRC has recovered 50TB SAN devices from SUN running their Solaris operating systems.

If you have any of these OS on your Sun:

* Solaris Operating System 8, 9, 10, and x64
* Microsoft Windows 2000 Server and Advanced Server (SP4)
* Microsoft Windows 2003 Server Standard, Enterprise, and Web editions
* HP-UX 11.11 and 11.23
* IBM AIX 5.2, 5.3
* Red Hat Linux AS/ES/WS Enterprise Edition 3.0/4.0
* SUSE LINUX LES 8 and 9
* Netware 6 SP5, Netware 6.5 SP3
* SGI IRIX 6.5.28
* VMWare ESX 3.0

We can help.

Mission critical data stored on multi-arrays require data recovery engineers with the experience ONLY DRC can provide.

Data Recovery Clinic has successfully recovered data from up to 12 Fibre Channel ports in dual RAID controller configurations where one or more drives have failed.

The most common problems are hardware failures that lead to configuration corruption. At this time DRC can still recover data even after an initialization.

In several instances data corruption is due to SATA or SCSI drive failures that are intermittent. The failure is not significant enough to red light, but still causes sectors and data to be overwritten causing corruption that is often misdiagnosed by phone support personnel.

Call 347-893-3354 before initializing or rebuilding anything on a Sun StorEdge

Sun StorEdge 6920 System Release Notes 11
System Usage Limitations
TABLE 7 lists maximum values for elements of the Sun StorEdge 6920 system.
Network Connection Limitations
The Sun StorEdge 6920 system firewall that connects to the site (customer) local area
network (LAN) supports a half-duplex 10-Mbps network connection. Configure the
port settings on your network switch or hub to an “auto-negotiate” setting. If for
some reason you cannot use an auto-negotiate setting, set the network switch or hub
to half duplex 10 Mbps.
TABLE 7 Sun StorEdge 6920 System Limitations
System Attribute Maximum
Volumes per system 1024 volumes
Virtual disks per tray 2 virtual disks
Volumes per virtual disk 32 striped volumes
Snapshots per volume 8 snapshots
Initiators* that can communicate with
the system
* The term initiator means the “initiator instance” as seen by the Sun StorEdge 6920 system. If a data
host-side HBA port sees ‘N’ ports, the system sees ‘N’ initiators. The 256-initiator limit translates to a maximum
of 128 dual-path data hosts, where each data host HBA port can see one port of the system.
256 initiators
Data Host HBA ports that can
communicate with one system port
128 data host HBA ports
Volumes that can be mapped to a
single data host HBA port worldwide
name (WWN)
256 volumes
Storage domains 14 storage domains (1 system defined; 13
available for user definition)
Storage pools 64 storage pools
Storage profiles 14 system-defined storage profiles; no limit for
user defined profiles
Fibre Channel Port Limitations
The Sun StorEdge 6920 system is configured with either two or four storage resource
card (SRC) sets; each SRC set consists of one SRC and one storage I/O card. Each
SRC set has four processors and eight Fibre Channel (FC) ports. One processor
serves adjacent FC ports (for example, ports 1 and 2 share a processor, ports 3 and 4
share a processor, and so forth). The FC ports are shared between SAN/data host
and storage array connections. These arrays are connected to the DSP and physically
installed in the Sun StorEdge 6920 system.
As described in the Sun StorEdge 6920 System Getting Started Guide and the online
help, you should evenly distribute FC ports between SAN/data host and storage
array connections. For example, in a system with two SRC sets and a total of 16 FC
ports, you would allocate 8 ports for SAN/data host connections and 8 ports for
storage connections. In a system with four SRC sets and a total of 32 FC ports, you
would allocate 16 ports for SAN/data host connections and 16 ports for storage
connections.
If you cannot evenly distribute the total number of FC ports between SAN/data host
and storage array connections, you must adhere to the following port allocation
rules:
¦ Adjacent FC ports that share a processor must be used exclusively for SAN/data
host connections or exclusively for storage array connections. For example, if port
1 is used for a SAN/data host connection, port 2 can be used only for a SAN/data
host connection.
¦ If only one of the FC ports that share a processor is used for a storage array
connection and the other port is unused, the unused port can be used only for a
future storage connection. Similarly, if only one of the FC ports sharing a
processor is used for a SAN/data host connection and the other port is unused,
the unused port can be used only for a future SAN/data host connection.
These rules apply to the following system configurations:
¦ 16 FC ports and more than 4 arrays
¦ 16 FC ports and more than 8 SAN/data host connections
¦ 32 FC ports and more than 8 arrays
¦ 32 FC ports and more than 16 SAN/data host connections