X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C70537.CC20A000@onstor-exch02.onstor.net>; Fri, 10 Nov 2006 18:19:20 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C70537.CC20A000"
Content-class: urn:content-classes:calendarmessage
Subject: Mirror reversal discussion
Date: Fri, 10 Nov 2006 18:19:20 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E014FF2BC@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Mirror reversal discussion
thread-index: AccFN8pWprCCpqabREGghhD5fgbKDw==
From: "Tim Gardner" <tim.gardner@onstor.com>
Cc: "dl-Design Review" <dl-designreview@onstor.com>

This is a multi-part message in MIME format.

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

When: Monday, November 13, 2006 1:00 PM-2:00 PM (GMT-08:00) Pacific Time =
(US & Canada); Tijuana.
Where: conf-Hawaii

*~*~*~*~*~*~*~*~*~*

While designing and implementing the mirror reversal functionality for =
lambo an issue was uncovered
leading to this proposal to change the EMO functional spec.

Currently, we enforce a restriction that a volume can only be the source =
or target of a single mirror.
A volume can not be a target of one mirror and the source for another.
We would like to retain this restriction as we do not yet have any =
requirement to do otherwise.
Retaining the restriction also limits bad configurations customers could =
get into and limits the
number of test cases that need to be run.

The problem is that the current mirror reversal workflow specifies that =
a second mirror be created
to sync a target volume back to the source. The workflow is pretty =
involved. To retain the single mirror
restriction, the workflow would need to be made even more complicated by =
requiring that the admin
delete the original mirror before creating the mirror to sync the target =
back to the source.
After the resync, the admin would have to delete the mirror and recreate =
the original mirror.

We propose to simplify the workflow and retain the single mirror =
restriction by introducing
a mirror reverse command:=20
mirror reverse MIRROR_NAME

In this meeting we will dicusss the specifics of this new command and =
the new mirror reversal
workflow. I would also like to get closure on the previously proposed =
mirror modify enhancements.



Microsoft Outlook Web Access:
http://ONSTOR-EXCH02/Exchange/andy.sharp/Inbox/Mirror%20reversal%20discus=
sion.EML?cmd=3Dopen


------_=_NextPart_001_01C70537.CC20A000
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.7650.28">
<TITLE>Mirror reversal discussion</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">When: Monday, November 13, 2006 1:00 =
PM-2:00 PM (GMT-08:00) Pacific Time (US &amp; Canada); Tijuana.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Where: conf-Hawaii</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">*~*~*~*~*~*~*~*~*~*</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">While designing and implementing the =
mirror reversal functionality for lambo an issue was uncovered</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">leading to this proposal to change the =
EMO functional spec.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Currently, we enforce a restriction =
that a volume can only be the source or target of a single =
mirror.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">A volume can not be a target of one =
mirror and the source for another.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">We would like to retain this =
restriction as we do not yet have any requirement to do =
otherwise.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Retaining the restriction also limits =
bad configurations customers could get into and limits the</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">number of test cases that need to be =
run.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The problem is that the current mirror =
reversal workflow specifies that a second mirror be created</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">to sync a target volume back to the =
source. The workflow is pretty involved. To retain the single =
mirror</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">restriction, the workflow would need =
to be made even more complicated by requiring that the admin</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">delete the original mirror before =
creating the mirror to sync the target back to the source.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">After the resync, the admin would have =
to delete the mirror and recreate the original mirror.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We propose to simplify the workflow and =
retain the single mirror restriction by introducing</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">a mirror reverse command: </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">mirror reverse MIRROR_NAME</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In this meeting we will dicusss the =
specifics of this new command and the new mirror reversal</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">workflow. I would also like to get =
closure on the previously proposed mirror modify enhancements.</FONT>
</P>
<BR>
<P>Microsoft Outlook Web Access: <A =
HREF=3D"http://ONSTOR-EXCH02/Exchange/andy.sharp/Inbox/Mirror%20reversal%=
20discussion.EML?cmd=3Dopen">http://ONSTOR-EXCH02/Exchange/andy.sharp/Inb=
ox/Mirror%20reversal%20discussion.EML?cmd=3Dopen</A></P>
</BODY>
</HTML>
------_=_NextPart_001_01C70537.CC20A000
Content-class: urn:content-classes:calendarmessage
Content-Type: text/calendar;
	method=REQUEST;
	name="meeting.ics"
Content-Transfer-Encoding: 8bit

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:(GMT-08.00) Pacific Time (US & Canada)/Tijuana
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=4;BYDAY=1SU
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20061111T021917Z
DTSTART;TZID="(GMT-08.00) Pacific Time (US & Canada)/Tijuana":20061113T1300
 00
SUMMARY:Mirror reversal discussion
UID:040000008200E00074C5B7101A82E00800000000107A33BCF404C701000000000000000
 010000000B1E0A323964F4F4D8B1CD5F9FD1D4573
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="dl-Design
  Review":MAILTO:dl-designreview@onstor.com
ORGANIZER;CN="Tim Gardner":MAILTO:tim.gardner@onstor.com
LOCATION:conf-Hawaii
DTEND;TZID="(GMT-08.00) Pacific Time (US & Canada)/Tijuana":20061113T140000
DESCRIPTION:While designing and implementing the mirror reversal functional
 ity for lambo an issue was uncovered\Nleading to this proposal to change t
 he EMO functional spec.\N\NCurrently\, we enforce a restriction that a vol
 ume can only be the source or target of a single mirror.\NA volume can not
  be a target of one mirror and the source for another.\NWe would like to r
 etain this restriction as we do not yet have any requirement to do otherwi
 se.\NRetaining the restriction also limits bad configurations customers co
 uld get into and limits the\Nnumber of test cases that need to be run.\N\N
 The problem is that the current mirror reversal workflow specifies that a 
 second mirror be created\Nto sync a target volume back to the source. The 
 workflow is pretty involved. To retain the single mirror\Nrestriction\, th
 e workflow would need to be made even more complicated by requiring that t
 he admin\Ndelete the original mirror before creating the mirror to sync th
 e target back to the source.\NAfter the resync\, the admin would have to d
 elete the mirror and recreate the original mirror.\N\NWe propose to simpli
 fy the workflow and retain the single mirror restriction by introducing\Na
  mirror reverse command: \Nmirror reverse MIRROR_NAME\N\NIn this meeting w
 e will dicusss the specifics of this new command and the new mirror revers
 al\Nworkflow. I would also like to get closure on the previously proposed 
 mirror modify enhancements.\N\N\N
SEQUENCE:0
PRIORITY:5
CLASS:
CREATED:20061111T021920Z
LAST-MODIFIED:20061111T021922Z
STATUS:CONFIRMED
TRANSP:OPAQUE
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-OWNERAPPTID:-110446634
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE:20061111T021917Z
X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE:20061111T021917Z
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR

------_=_NextPart_001_01C70537.CC20A000--
