<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Data Recovery Zone Hard Drive Repair Services &#187; Sun SAN data recovery</title>
	<atom:link href="http://www.datarecoveryzone.com/tag/sun-san-data-recovery/feed" rel="self" type="application/rss+xml" />
	<link>http://www.datarecoveryzone.com</link>
	<description>Data Recovery Zone Provides hard drive recovery services</description>
	<lastBuildDate>Fri, 17 Apr 2009 19:54:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Sun Data Recovery</title>
		<link>http://www.datarecoveryzone.com/sun_data_recovery.htm</link>
		<comments>http://www.datarecoveryzone.com/sun_data_recovery.htm#comments</comments>
		<pubDate>Wed, 28 May 2008 18:38:55 +0000</pubDate>
		<dc:creator>Victoria Stankard</dc:creator>
				<category><![CDATA[Data Recovery Services]]></category>
		<category><![CDATA[data recovery]]></category>
		<category><![CDATA[data recovery service]]></category>
		<category><![CDATA[Sun data recovery]]></category>
		<category><![CDATA[Sun SAN data recovery]]></category>

		<guid isPermaLink="false">http://www.datarecoveryzone.com/?p=24</guid>
		<description><![CDATA[While Sun puts out a great product, there are still issues that can happen during field usage.
Data Recovery Zone has repaired and recovered data from amny types of SAN/NAS devices as well as enterprise level Sun storage devices.
NO OTHER COMPANY HAS THE EXPERIENCE TO RECOVER YOUR DATA!
The Sun StorEdge 9900 series includes the Sun StorEdge 9970, [...]]]></description>
			<content:encoded><![CDATA[<p>While Sun puts out a great product, there are still issues that can happen during field usage.<br />
<strong>Data Recovery Zone</strong> has repaired and recovered data from amny types of <em>SAN/NAS devices</em> as well as enterprise level <em>Sun storage devices</em>.</p>
<p>NO OTHER COMPANY HAS THE EXPERIENCE TO RECOVER YOUR DATA!</p>
<p>The Sun StorEdge 9900 series includes the Sun StorEdge 9970, and 9980 systems. These devices require specialized equipment and software for data recovery. DRZ has recovered 50TB SAN devices from SUN running their Solaris operating systems..</p>
<p>Mission critical data stored on multi-arrays require data recovery engineers with the experience ONLY DRZ can provide.</p>
<p><strong>Data Recovery Zone</strong> has successfully recovered data from up to 12 Fibre Channel ports in dual RAID controller configurations where one or more drives have failed.</p>
<p>The most common problems are hardware failures that lead to configuration corruption. At this time <strong>Data Recovery Zone</strong> can still recover data even after an initialization.</p>
<p>In several instances data corruption is due to SATA 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 personally.</p>
<p><strong>Call 727-251-2058 before initializing or rebuilding anything on a Sun StorEdge</strong></p>
<p>Sun StorEdge 6920 System Release Notes 11<br />
System Usage Limitations<br />
TABLE 7 lists maximum values for elements of the Sun StorEdge 6920 system.<br />
Network Connection Limitations<br />
The Sun StorEdge 6920 system firewall that connects to the site (customer) local area<br />
network (LAN) supports a half-duplex 10-Mbps network connection. Configure the<br />
port settings on your network switch or hub to an “auto-negotiate” setting. If for<br />
some reason you cannot use an auto-negotiate setting, set the network switch or hub<br />
to half duplex 10 Mbps.<br />
TABLE 7 Sun StorEdge 6920 System Limitations<br />
System Attribute Maximum<br />
Volumes per system 1024 volumes<br />
Virtual disks per tray 2 virtual disks<br />
Volumes per virtual disk 32 striped volumes<br />
Snapshots per volume 8 snapshots<br />
Initiators* that can communicate with<br />
the system<br />
* The term initiator means the “initiator instance” as seen by the Sun StorEdge 6920 system. If a data<br />
host-side HBA port sees ‘N’ ports, the system sees ‘N’ initiators. The 256-initiator limit translates to a maximum<br />
of 128 dual-path data hosts, where each data host HBA port can see one port of the system.<br />
256 initiators<br />
Data Host HBA ports that can<br />
communicate with one system port<br />
128 data host HBA ports<br />
Volumes that can be mapped to a<br />
single data host HBA port worldwide<br />
name (WWN)<br />
256 volumes<br />
Storage domains 14 storage domains (1 system defined; 13<br />
available for user definition)<br />
Storage pools 64 storage pools<br />
Storage profiles 14 system-defined storage profiles; no limit for<br />
user defined profiles<br />
Fibre Channel Port Limitations<br />
The Sun StorEdge 6920 system is configured with either two or four storage resource<br />
card (SRC) sets; each SRC set consists of one SRC and one storage I/O card. Each<br />
SRC set has four processors and eight Fibre Channel (FC) ports. One processor<br />
serves adjacent FC ports (for example, ports 1 and 2 share a processor, ports 3 and 4<br />
share a processor, and so forth). The FC ports are shared between SAN/data host<br />
and storage array connections. These arrays are connected to the DSP and physically<br />
installed in the Sun StorEdge 6920 system.<br />
As described in the Sun StorEdge 6920 System Getting Started Guide and the online<br />
help, you should evenly distribute FC ports between SAN/data host and storage<br />
array connections. For example, in a system with two SRC sets and a total of 16 FC<br />
ports, you would allocate 8 ports for SAN/data host connections and 8 ports for<br />
storage connections. In a system with four SRC sets and a total of 32 FC ports, you<br />
would allocate 16 ports for SAN/data host connections and 16 ports for storage<br />
connections.<br />
If you cannot evenly distribute the total number of FC ports between SAN/data host<br />
and storage array connections, you must adhere to the following port allocation<br />
rules:<br />
¦ Adjacent FC ports that share a processor must be used exclusively for SAN/data<br />
host connections or exclusively for storage array connections. For example, if port<br />
1 is used for a SAN/data host connection, port 2 can be used only for a SAN/data<br />
host connection.<br />
¦ If only one of the FC ports that share a processor is used for a storage array<br />
connection and the other port is unused, the unused port can be used only for a<br />
future storage connection. Similarly, if only one of the FC ports sharing a<br />
processor is used for a SAN/data host connection and the other port is unused,<br />
the unused port can be used only for a future SAN/data host connection.<br />
These rules apply to the following system configurations:<br />
¦ 16 FC ports and more than 4 arrays<br />
¦ 16 FC ports and more than 8 SAN/data host connections<br />
¦ 32 FC ports and more than 8 arrays<br />
¦ 32 FC ports and more than 16 SAN/data host connections</p>
<p><!-- InstanceEndEditable --></p>
]]></content:encoded>
			<wfw:commentRss>http://www.datarecoveryzone.com/sun_data_recovery.htm/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
