X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7AC4C.B16DD419@onstor-exch02.onstor.net>; Mon, 11 Jun 2007 10:19:39 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7AC4C.B16DD419"
Content-class: urn:content-classes:message
Subject: RE: 3.0 system config copy
Date: Mon, 11 Jun 2007 10:17:44 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E03E56449@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 3.0 system config copy
Thread-Index: Acep5pv9gtJz6XfeTzahbqIvDiJXngCWwpfAAAIrk4YAAC9H8AAAVs/C
References: <BB375AF679D4A34E9CA8DFA650E2B04E041BF207@onstor-exch02.onstor.net>
From: "Paul Hammer" <paul.hammer@onstor.com>
To: "David Crispin" <david.crispin@onstor.com>,
	"Sudheesh Nair" <sudheesh.nair@onstor.com>,
	"Doug Cook" <doug.cook@onstor.com>,
	"Steffen Thuemmel" <steffen.thuemmel@onstor.com>,
	"Tim O'Callaghan" <tim.ocallaghan@onstor.com>,
	"dl-Delorean" <dl-Delorean@onstor.com>

This is a multi-part message in MIME format.

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

QA is checking out the flash burner that Ops uses to generate the =
flashes fromt he gold master, want to make sure it is not creating some =
bad cards.  If the flashes are unformated in the feild it may mean the =
flash burner is not working properly. We shall be able to rule this in =
or out shortly.
=20
-Paul
=20

=20
________________________________

From: David Crispin
Sent: Mon 6/11/2007 10:10 AM
To: Sudheesh Nair; Doug Cook; Steffen Thuemmel; Tim O'Callaghan; =
dl-Delorean
Subject: RE: 3.0 system config copy



Hold on! I've been talking with Eric Barrett. It seems that the system =
should do a one off auto copy of the config on first boot but I've tried =
two CF cards and they both booted into the ICT. Eric is looking into it.

Regards,
Dave.


-----Original Message-----
From: Sudheesh Nair
Sent: 11 June 2007 18:03
To: David Crispin; Doug Cook; Steffen Thuemmel; Tim O'Callaghan; =
dl-Delorean
Subject: Re: 3.0 system config copy

What's going on here guys? Do we have 2 different methods now?


Regards,
Sudheesh
sudheesh.nair@onstor.com
408-802-2856
--------------------------
Sent from my BlackBerry Wireless Handheld

-----Original Message-----
From: David Crispin
To: Doug Cook; Steffen Thuemmel; Tim O'Callaghan; Sudheesh Nair; dl-se
Sent: Mon Jun 11 09:09:30 2007
Subject: RE: 3.0 system config copy

Guys,



I just did an upgrade today on a spare 2220 before I do it live tomorrow =
and this is what I found. Just doing a system reboot -s doesn't =
automatically copy the system config and upgrade you to 3.0.



I only saw this as I was running the system reboot -s command from the =
serial console. It comes up just like a new install with the ICT and you =
have new options to copy the system config. This needs to be put in the =
Release Notes in the Compact Flash Card Upgrade Procedure section.



Here is the text from the session:-



User pressed ENTER



gathering system info, please wait...



                 ONStor NAS Gateway Initial Configuration Tool







     1. Configure Administrative Settings





     2. Configure Network Settings





     3. Display Current Settings





     4. Commit Changes





     5. Help





     6. Copy Configuration Files From Secondary Flash





     7. Exit





    Enter Selection: 6



Value Entered is 6





                 Copy Configuration Files from Secondary Flash







     1. Copy Configuration and proceed with bringup





     2. No - return to main menu





    Enter Selection: 1



Value Entered is 1



Copying configuration...........................done.

starting network

add net default: gateway 192.168.0.1

starting system logger

starting rpc daemons: portmap ypserv ypbind.

sendto: Network is down

savecore: no core dump

building ps databases: kvm dev.

clearing /tmp

starting pre-securelevel daemons: tickadj.

setting kernel security level: kern.securelevel: 0 -> 1

remounting root read-only...done.

starting network daemons: inetd sshd.

starting local daemons: ntpdate ntpd.

starting agile daemons: mgmtbus0 pm.

created /tmp/ramdisk

starting mount_mfs: done

standard daemons: cron.

checking domain name [SANfiler]... passed

Mon Jun 11 16:53:09 BST 2007



login: admin

Password:

Last login: Mon Jun 11 16:47:22 on console

OpenBSD 2.8 (BOBCAT) #0: Mon Jun  4 14:42:17 PDT 2007





Welcome to the ONStor NAS Gateway.



Initialization in progress...

\

Timeout... Try logging in later - It now makes you wait until it is =
fully up!





login: admin

Password:

Last login: Mon Jun 11 16:53:30 on console

OpenBSD 2.8 (BOBCAT) #0: Mon Jun  4 14:42:17 PDT 2007





Welcome to the ONStor NAS Gateway.



bobcat> sys ver

3.0.0.0

bobcat>









David Crispin

Technical Services Manager



ONStor, Inc.

office: +44(0)118 963 5866

mobile: +44(0)7940 547 895





david.crispin@onstor.com

http://www.onstor.com <http://www.onstor.com/>=20

    =20

-----Original Message-----
From: Doug Cook
Sent: 08 June 2007 17:04
To: Doug Cook; Steffen Thuemmel; Tim O'Callaghan; Sudheesh Nair; dl-se
Subject: Re: 3.0 system config copy



Just a clarification.  After inserting the 3.0 flash, do a "system =
reboot

-s".



DC



> From: Doug Cook <doug.cook@onstor.com>

> Date: Fri, 08 Jun 2007 11:16:00 -0400

> To: Steffen Thuemmel <steffen.thuemmel@onstor.com>, Tim O'Callaghan

> <tim.ocallaghan@onstor.com>, Sudheesh Nair <sudheesh.nair@onstor.com>, =
dl-se

> <dl-se@onstor.com>

> Subject: Re: 3.0 system config copy

>

> Hey Everyone,

>

> I believe that there is a fundamental misunderstanding of the feature =
in 3.0

> that copies information from the pre-3.0 flash.  Let me explain it the =
way I

> understand it and hope this clears the confusion.

>

> In pre-3.0 versions of EverON the compact flashes are partitioned =
drives

> each with six partitions upon which a filesystem is created and the =
ONStor

> binaries are stored.  In Ever-ON 3.0 the compact flashes are =
partitioned

> with only 4 partitions.

>

> In pre-3.0 version of EverON, commands such as "system config copy", =
"system

> copy all -I", and "system upgrade -s" are all dependent on, and look

> specifically for, the compact flashes with 6 partitions.  Hence, the =
only

> way to upgrade a running system from pre-3.0 to 3.0 is to use a new =
compact

> flash from corporate with 3.0 preloaded; a "system upgrade -s" will =
not

> work.  Once you swap the secondary flash with the new 3.0 flash, there =
is no

> way to copy the current cluster configuration to the new flash -- a =
"system

> config copy" will not work since it doesn't understand the new =
partition

> layout.

>

> So, how do you upgrade an existing system without rebuilding the =
cluster

> from scratch?  After swapping out the pre-3.0 secondary flash with the =
3.0

> flash, you are supposed to just reboot the filer.  Upon booting, the =
3.0

> flash has the intelligence built in to grab the configuration files =
from the

> pre-3.0 flash and boot fully into a configured 3.0 system.  Note that =
there

> are no changes to the remaining pre-3.0 flash.  And, until the last =
node in

> the cluster has been upgraded to 3.0, there are no permanent changes =
to the

> cluster database -- you can "revert" back to pre-3.0 just by doing a =
"system

> reboot -s".

>

> Once all of the nodes are upgraded to 3.0 and the cluster database has =
been

> upgraded, you lose the ability to revert to a pre-3.0 state UNLESS you =
are

> willing to reboot every node simultaneously to the pre-3.0 flash.  =
Note that

> any changes you have made (new vsvrs, new shares, etc) since upgrading =
will

> be lost.  Plus, if you have done any "system config copy" commands, =
your

> revert window is closed.

>

> Another major item to note is the introduction of a new command, =
"filesystem

> convert".  This command converts existing StorFS filesystem from =
version 26

> to version 28.  This supports some of the new underlying filesystem =
features

> introduced in 3.0.  Obviously, if you have a version 28 filesystem =
that was

> either newly created or recently upgraded, you cannot use this =
filesystem in

> a pre-3.0 cluster.  Once you create, or upgrade to, a version 28 =
filesystem,

> you cannot "revert to a previous OS version".

>

> Hope this helps.

>

> Doug

>

>

>

>> From: "Steffen Thuemmel" <steffen.thuemmel@onstor.com>

>> Date: Fri, 8 Jun 2007 05:50:16 -0700

>> To: "Tim O'Callaghan" <tim.ocallaghan@onstor.com>, "Sudheesh Nair"

>> <sudheesh.nair@onstor.com>, "dl-se" <dl-se@onstor.com>, "dl-Training"

>> <dl-Training@onstor.com>

>> Subject: RE: 3.0 system config copy

>>

>> I'd like to emphasize what Tim says. The option to keep different =
versions

>> and

>> configurations on the second flash card is welcomed in sales calls. I =
hope

>> there is a switch to turn this automatic copy off.

>>

>> st.

>>

>> Steffen Thuemmel

>>

>> ONStor GmbH

>>

>> telf.      +49 6102 884 84-0

>> mobil.     +49 173 673 3434

>> mail.       steffen.thuemmel@onstor.com

>> =20

>>

>> -----Original Message-----

>> From: Tim O'Callaghan

>> Sent: Donnerstag, 7. Juni 2007 18:00

>> To: Sudheesh Nair; dl-se; dl-Training

>> Subject: Re: 3.0 system config copy

>>

>> Isn't this a little unsound? It will remove our backout option

>>

>> Tim

>> Tim.OCallaghan@onstor.com

>>

>> M:+44 7767435472

>> --------------------------

>> Sent using BlackBerry

>>

>>

>> -----Original Message-----

>> From: Sudheesh Nair

>> To: dl-se; dl-Training

>> Sent: Thu Jun 07 07:31:41 2007

>> Subject: 3.0 system config copy

>>

>> Hi all:

>>

>> In 3.0 system config copy is done automatically after reboots.

>>

>> No need to manuall copy config from pri to second.

>>

>>

>> Regards,

>> Sudheesh

>> sudheesh.nair@onstor.com

>> 408-802-2856

>> --------------------------

>> Sent from my BlackBerry Wireless Handheld

>

>






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

<HTML dir=3Dltr><HEAD><TITLE>RE: 3.0 system config copy</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3059" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText55297 dir=3Dltr>=0A=
<DIV dir=3Dltr>QA is checking out the flash burner that Ops uses to =
generate the flashes fromt he gold master, want to make sure it is not =
creating some bad cards.&nbsp; If the flashes are unformated in the =
feild it may mean the flash burner is not working properly. We shall be =
able to rule this in or out shortly.</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>-Paul</DIV>=0A=
<DIV dir=3Dltr>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><BR>&nbsp;</DIV>=0A=
<DIV dir=3Dltr>=0A=
<HR tabIndex=3D-1>=0A=
</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>From:</B> David =
Crispin<BR><B>Sent:</B> Mon 6/11/2007 10:10 AM<BR><B>To:</B> Sudheesh =
Nair; Doug Cook; Steffen Thuemmel; Tim O'Callaghan; =
dl-Delorean<BR><B>Subject:</B> RE: 3.0 system config =
copy<BR></FONT><BR></DIV></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hold on! I've been talking with Eric Barrett. It seems =
that the system should do a one off auto copy of the config on first =
boot but I've tried two CF cards and they both booted into the ICT. Eric =
is looking into it.<BR><BR>Regards,<BR>Dave.<BR><BR><BR>-----Original =
Message-----<BR>From: Sudheesh Nair<BR>Sent: 11 June 2007 18:03<BR>To: =
David Crispin; Doug Cook; Steffen Thuemmel; Tim O'Callaghan; =
dl-Delorean<BR>Subject: Re: 3.0 system config copy<BR><BR>What's going =
on here guys? Do we have 2 different methods =
now?<BR><BR><BR>Regards,<BR>Sudheesh<BR>sudheesh.nair@onstor.com<BR>408-8=
02-2856<BR>--------------------------<BR>Sent from my BlackBerry =
Wireless Handheld<BR><BR>-----Original Message-----<BR>From: David =
Crispin<BR>To: Doug Cook; Steffen Thuemmel; Tim O'Callaghan; Sudheesh =
Nair; dl-se<BR>Sent: Mon Jun 11 09:09:30 2007<BR>Subject: RE: 3.0 system =
config copy<BR><BR>Guys,<BR><BR><BR><BR>I just did an upgrade today on a =
spare 2220 before I do it live tomorrow and this is what I found. Just =
doing a system reboot -s doesn't automatically copy the system config =
and upgrade you to 3.0.<BR><BR><BR><BR>I only saw this as I was running =
the system reboot -s command from the serial console. It comes up just =
like a new install with the ICT and you have new options to copy the =
system config. This needs to be put in the Release Notes in the Compact =
Flash Card Upgrade Procedure section.<BR><BR><BR><BR>Here is the text =
from the session:-<BR><BR><BR><BR>User pressed =
ENTER<BR><BR><BR><BR>gathering system info, please =
wait...<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ONStor NAS Gateway =
Initial Configuration =
Tool<BR><BR><BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 1. =
Configure Administrative =
Settings<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 2. Configure =
Network Settings<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 3. =
Display Current Settings<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; =
4. Commit Changes<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 5. =
Help<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 6. Copy =
Configuration Files From Secondary =
Flash<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 7. =
Exit<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp; Enter Selection: =
6<BR><BR><BR><BR>Value Entered is =
6<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Copy Configuration =
Files from Secondary =
Flash<BR><BR><BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 1. Copy =
Configuration and proceed with =
bringup<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp; 2. No - return =
to main menu<BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp; Enter Selection: =
1<BR><BR><BR><BR>Value Entered is 1<BR><BR><BR><BR>Copying =
configuration...........................done.<BR><BR>starting =
network<BR><BR>add net default: gateway 192.168.0.1<BR><BR>starting =
system logger<BR><BR>starting rpc daemons: portmap ypserv =
ypbind.<BR><BR>sendto: Network is down<BR><BR>savecore: no core =
dump<BR><BR>building ps databases: kvm dev.<BR><BR>clearing =
/tmp<BR><BR>starting pre-securelevel daemons: tickadj.<BR><BR>setting =
kernel security level: kern.securelevel: 0 -&gt; 1<BR><BR>remounting =
root read-only...done.<BR><BR>starting network daemons: inetd =
sshd.<BR><BR>starting local daemons: ntpdate ntpd.<BR><BR>starting agile =
daemons: mgmtbus0 pm.<BR><BR>created /tmp/ramdisk<BR><BR>starting =
mount_mfs: done<BR><BR>standard daemons: cron.<BR><BR>checking domain =
name [SANfiler]... passed<BR><BR>Mon Jun 11 16:53:09 BST =
2007<BR><BR><BR><BR>login: admin<BR><BR>Password:<BR><BR>Last login: Mon =
Jun 11 16:47:22 on console<BR><BR>OpenBSD 2.8 (BOBCAT) #0: Mon Jun&nbsp; =
4 14:42:17 PDT 2007<BR><BR><BR><BR><BR><BR>Welcome to the ONStor NAS =
Gateway.<BR><BR><BR><BR>Initialization in =
progress...<BR><BR>\<BR><BR>Timeout... Try logging in later &#8211; It =
now makes you wait until it is fully up!<BR><BR><BR><BR><BR><BR>login: =
admin<BR><BR>Password:<BR><BR>Last login: Mon Jun 11 16:53:30 on =
console<BR><BR>OpenBSD 2.8 (BOBCAT) #0: Mon Jun&nbsp; 4 14:42:17 PDT =
2007<BR><BR><BR><BR><BR><BR>Welcome to the ONStor NAS =
Gateway.<BR><BR><BR><BR>bobcat&gt; sys =
ver<BR><BR>3.0.0.0<BR><BR>bobcat&gt;<BR><BR><BR><BR><BR><BR><BR><BR><BR><=
BR>David Crispin<BR><BR>Technical Services =
Manager<BR><BR><BR><BR>ONStor, Inc.<BR><BR>office: +44(0)118 963 =
5866<BR><BR>mobile: +44(0)7940 547 =
895<BR><BR><BR><BR><BR><BR>david.crispin@onstor.com<BR><BR><A =
href=3D"http://www.onstor.com/">http://www.onstor.com</A><BR><BR>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;<BR><BR>-----Original Message-----<BR>From: Doug =
Cook<BR>Sent: 08 June 2007 17:04<BR>To: Doug Cook; Steffen Thuemmel; Tim =
O'Callaghan; Sudheesh Nair; dl-se<BR>Subject: Re: 3.0 system config =
copy<BR><BR><BR><BR>Just a clarification.&nbsp; After inserting the 3.0 =
flash, do a "system =
reboot<BR><BR>-s".<BR><BR><BR><BR>DC<BR><BR><BR><BR>&gt; From: Doug Cook =
&lt;doug.cook@onstor.com&gt;<BR><BR>&gt; Date: Fri, 08 Jun 2007 11:16:00 =
-0400<BR><BR>&gt; To: Steffen Thuemmel =
&lt;steffen.thuemmel@onstor.com&gt;, Tim O'Callaghan<BR><BR>&gt; =
&lt;tim.ocallaghan@onstor.com&gt;, Sudheesh Nair =
&lt;sudheesh.nair@onstor.com&gt;, dl-se<BR><BR>&gt; =
&lt;dl-se@onstor.com&gt;<BR><BR>&gt; Subject: Re: 3.0 system config =
copy<BR><BR>&gt;<BR><BR>&gt; Hey Everyone,<BR><BR>&gt;<BR><BR>&gt; I =
believe that there is a fundamental misunderstanding of the feature in =
3.0<BR><BR>&gt; that copies information from the pre-3.0 flash.&nbsp; =
Let me explain it the way I<BR><BR>&gt; understand it and hope this =
clears the confusion.<BR><BR>&gt;<BR><BR>&gt; In pre-3.0 versions of =
EverON the compact flashes are partitioned drives<BR><BR>&gt; each with =
six partitions upon which a filesystem is created and the =
ONStor<BR><BR>&gt; binaries are stored.&nbsp; In Ever-ON 3.0 the compact =
flashes are partitioned<BR><BR>&gt; with only 4 =
partitions.<BR><BR>&gt;<BR><BR>&gt; In pre-3.0 version of EverON, =
commands such as "system config copy", "system<BR><BR>&gt; copy all -I", =
and "system upgrade -s" are all dependent on, and look<BR><BR>&gt; =
specifically for, the compact flashes with 6 partitions.&nbsp; Hence, =
the only<BR><BR>&gt; way to upgrade a running system from pre-3.0 to 3.0 =
is to use a new compact<BR><BR>&gt; flash from corporate with 3.0 =
preloaded; a "system upgrade -s" will not<BR><BR>&gt; work.&nbsp; Once =
you swap the secondary flash with the new 3.0 flash, there is =
no<BR><BR>&gt; way to copy the current cluster configuration to the new =
flash -- a "system<BR><BR>&gt; config copy" will not work since it =
doesn't understand the new partition<BR><BR>&gt; =
layout.<BR><BR>&gt;<BR><BR>&gt; So, how do you upgrade an existing =
system without rebuilding the cluster<BR><BR>&gt; from scratch?&nbsp; =
After swapping out the pre-3.0 secondary flash with the 3.0<BR><BR>&gt; =
flash, you are supposed to just reboot the filer.&nbsp; Upon booting, =
the 3.0<BR><BR>&gt; flash has the intelligence built in to grab the =
configuration files from the<BR><BR>&gt; pre-3.0 flash and boot fully =
into a configured 3.0 system.&nbsp; Note that there<BR><BR>&gt; are no =
changes to the remaining pre-3.0 flash.&nbsp; And, until the last node =
in<BR><BR>&gt; the cluster has been upgraded to 3.0, there are no =
permanent changes to the<BR><BR>&gt; cluster database -- you can =
"revert" back to pre-3.0 just by doing a "system<BR><BR>&gt; reboot =
-s".<BR><BR>&gt;<BR><BR>&gt; Once all of the nodes are upgraded to 3.0 =
and the cluster database has been<BR><BR>&gt; upgraded, you lose the =
ability to revert to a pre-3.0 state UNLESS you are<BR><BR>&gt; willing =
to reboot every node simultaneously to the pre-3.0 flash.&nbsp; Note =
that<BR><BR>&gt; any changes you have made (new vsvrs, new shares, etc) =
since upgrading will<BR><BR>&gt; be lost.&nbsp; Plus, if you have done =
any "system config copy" commands, your<BR><BR>&gt; revert window is =
closed.<BR><BR>&gt;<BR><BR>&gt; Another major item to note is the =
introduction of a new command, "filesystem<BR><BR>&gt; convert".&nbsp; =
This command converts existing StorFS filesystem from version =
26<BR><BR>&gt; to version 28.&nbsp; This supports some of the new =
underlying filesystem features<BR><BR>&gt; introduced in 3.0.&nbsp; =
Obviously, if you have a version 28 filesystem that was<BR><BR>&gt; =
either newly created or recently upgraded, you cannot use this =
filesystem in<BR><BR>&gt; a pre-3.0 cluster.&nbsp; Once you create, or =
upgrade to, a version 28 filesystem,<BR><BR>&gt; you cannot "revert to a =
previous OS version".<BR><BR>&gt;<BR><BR>&gt; Hope this =
helps.<BR><BR>&gt;<BR><BR>&gt; =
Doug<BR><BR>&gt;<BR><BR>&gt;<BR><BR>&gt;<BR><BR>&gt;&gt; From: "Steffen =
Thuemmel" &lt;steffen.thuemmel@onstor.com&gt;<BR><BR>&gt;&gt; Date: Fri, =
8 Jun 2007 05:50:16 -0700<BR><BR>&gt;&gt; To: "Tim O'Callaghan" =
&lt;tim.ocallaghan@onstor.com&gt;, "Sudheesh Nair"<BR><BR>&gt;&gt; =
&lt;sudheesh.nair@onstor.com&gt;, "dl-se" &lt;dl-se@onstor.com&gt;, =
"dl-Training"<BR><BR>&gt;&gt; =
&lt;dl-Training@onstor.com&gt;<BR><BR>&gt;&gt; Subject: RE: 3.0 system =
config copy<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; I'd like to emphasize what =
Tim says. The option to keep different versions<BR><BR>&gt;&gt; =
and<BR><BR>&gt;&gt; configurations on the second flash card is welcomed =
in sales calls. I hope<BR><BR>&gt;&gt; there is a switch to turn this =
automatic copy off.<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; =
st.<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; Steffen =
Thuemmel<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; ONStor =
GmbH<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; telf.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+49 6102 884 84-0<BR><BR>&gt;&gt; mobil.&nbsp;&nbsp;&nbsp;&nbsp; +49 173 =
673 3434<BR><BR>&gt;&gt; mail.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
steffen.thuemmel@onstor.com<BR><BR>&gt;&gt;&nbsp;&nbsp;<BR><BR>&gt;&gt;<B=
R><BR>&gt;&gt; -----Original Message-----<BR><BR>&gt;&gt; From: Tim =
O'Callaghan<BR><BR>&gt;&gt; Sent: Donnerstag, 7. Juni 2007 =
18:00<BR><BR>&gt;&gt; To: Sudheesh Nair; dl-se; =
dl-Training<BR><BR>&gt;&gt; Subject: Re: 3.0 system config =
copy<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; Isn't this a little unsound? It =
will remove our backout option<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; =
Tim<BR><BR>&gt;&gt; =
Tim.OCallaghan@onstor.com<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; M:+44 =
7767435472<BR><BR>&gt;&gt; --------------------------<BR><BR>&gt;&gt; =
Sent using BlackBerry<BR><BR>&gt;&gt;<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; =
-----Original Message-----<BR><BR>&gt;&gt; From: Sudheesh =
Nair<BR><BR>&gt;&gt; To: dl-se; dl-Training<BR><BR>&gt;&gt; Sent: Thu =
Jun 07 07:31:41 2007<BR><BR>&gt;&gt; Subject: 3.0 system config =
copy<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; Hi =
all:<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; In 3.0 system config copy is done =
automatically after reboots.<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; No need to =
manuall copy config from pri to =
second.<BR><BR>&gt;&gt;<BR><BR>&gt;&gt;<BR><BR>&gt;&gt; =
Regards,<BR><BR>&gt;&gt; Sudheesh<BR><BR>&gt;&gt; =
sudheesh.nair@onstor.com<BR><BR>&gt;&gt; 408-802-2856<BR><BR>&gt;&gt; =
--------------------------<BR><BR>&gt;&gt; Sent from my BlackBerry =
Wireless =
Handheld<BR><BR>&gt;<BR><BR>&gt;<BR><BR><BR><BR></FONT></P></DIV></BODY><=
/HTML>
------_=_NextPart_001_01C7AC4C.B16DD419--
