X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7BDBE.3F04BDED@onstor-exch02.onstor.net>; Tue, 3 Jul 2007 14:05:20 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BDBE.3F04BDED"
Content-class: urn:content-classes:message
Subject: 
Date: Tue, 3 Jul 2007 14:05:20 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E028FB4BD@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Index: Ace9vj8CTe8dsSzoR9GaB1NJzYEdHA==
From: "Mike Lee" <mike.lee@onstor.com>
To: "Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BDBE.3F04BDED
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Guys:

Sorry to miss out, but here is the text from the customer "gripe", for =
which support has requested update...
I'll do better for the next movie.

-Mike


Make Private	Checked	Created By: From the Assist Site (7/3/2007 10:49 =
AM)
Dave Johnson commented:

What is it that Engineering will produce a fix for?

Has the problem been identified? As we purchased this second system =
solely for use as a DMIP target for WAN replication to replace our =
outdated tape backup, need to get 1) the source of the problem =
identified, and 2) either the problem source removed, or assurance that =
a fix for the problem has been crafted by Engineering.

For us to acheive a baseline mirror requires approximately $5k =
investment in shipping and labor costs, plus 4-6 days of my personal =
time, as I must travel to our DR site 400mi away, get the DR storage =
system to our primary site in San Francisco, perform the baseline local =
mirror via FC, return the unit to our DR site, recreate the mirror via =
DMIP, and pray that it works again.

Unless the source of the problem is unequivocally identified, I can only =
expect this same corruption to occur in the near future.

I hope this description of our environment and usage explains why I =
cannot simply continue without an absolute identification of the =
problem, and a resolution to it in some way, whether removal of the =
problem source, or a fix for it from Engineering.

What would be the next step in determining the actual cause of the =
problem? I am at the disposal of you and your engineering team and will =
help in any way I can.

-=3Ddave
Make Private	Checked	Created By: Call Center TSE (7/3/2007 9:09 AM)
Hi Mr. Johnson,
From a practical point of view for yourself, for the moment the =
situation is that you will have to do a baseline mirror, preferably =
deleting the target prior to recreating the mirror.

Engineering will continue to work on the problem to produce a fix in a =
later release. What release that will be and when it wil be available I =
do not know.
We will advise you when we know.

Thanks .. Alan.

------_=_NextPart_001_01C7BDBE.3F04BDED
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE></TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Guys:<BR>
<BR>
Sorry to miss out, but here is the text from the customer =
&quot;gripe&quot;, for which support has requested update...<BR>
I'll do better for the next movie.<BR>
<BR>
-Mike<BR>
<BR>
<BR>
Make Private&nbsp;&nbsp;&nbsp; Checked Created By: From the Assist Site =
(7/3/2007 10:49 AM)<BR>
Dave Johnson commented:<BR>
<BR>
What is it that Engineering will produce a fix for?<BR>
<BR>
Has the problem been identified? As we purchased this second system =
solely for use as a DMIP target for WAN replication to replace our =
outdated tape backup, need to get 1) the source of the problem =
identified, and 2) either the problem source removed, or assurance that =
a fix for the problem has been crafted by Engineering.<BR>
<BR>
For us to acheive a baseline mirror requires approximately $5k =
investment in shipping and labor costs, plus 4-6 days of my personal =
time, as I must travel to our DR site 400mi away, get the DR storage =
system to our primary site in San Francisco, perform the baseline local =
mirror via FC, return the unit to our DR site, recreate the mirror via =
DMIP, and pray that it works again.<BR>
<BR>
Unless the source of the problem is unequivocally identified, I can only =
expect this same corruption to occur in the near future.<BR>
<BR>
I hope this description of our environment and usage explains why I =
cannot simply continue without an absolute identification of the =
problem, and a resolution to it in some way, whether removal of the =
problem source, or a fix for it from Engineering.<BR>
<BR>
What would be the next step in determining the actual cause of the =
problem? I am at the disposal of you and your engineering team and will =
help in any way I can.<BR>
<BR>
-=3Ddave<BR>
Make Private&nbsp;&nbsp;&nbsp; Checked Created By: Call Center TSE =
(7/3/2007 9:09 AM)<BR>
Hi Mr. Johnson,<BR>
From a practical point of view for yourself, for the moment the =
situation is that you will have to do a baseline mirror, preferably =
deleting the target prior to recreating the mirror.<BR>
<BR>
Engineering will continue to work on the problem to produce a fix in a =
later release. What release that will be and when it wil be available I =
do not know.<BR>
We will advise you when we know.<BR>
<BR>
Thanks .. Alan.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7BDBE.3F04BDED--
