X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C717E6.59B62AB8@onstor-exch02.onstor.net>; Mon, 4 Dec 2006 12:54:11 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C717E6.59B62AB8"
Content-class: urn:content-classes:message
Subject: Lambo: Before you sync your tree...
Date: Mon, 4 Dec 2006 12:54:11 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0138C371@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Lambo: Before you sync your tree...
thread-index: AccX5lnFAGBR6Z3gSCiI3ouQ3MGrNA==
From: "Chris Vandever" <chris.vandever@onstor.com>
To: "dl-lambo" <dl-lambo@onstor.com>,
	"dl-Clio" <dl-Clio@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C717E6.59B62AB8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Back up your clusDb before you sync your tree!!

With my latest check-in for lambo (#22046) to support using a vsvr
hostname in creating a remote mirror, there are clusDb changes that will
make it incompatible with previous lambo and clio builds.  So, once you
do a complete build and run it you will be unable to go back unless you
have a backup copy of your clusDb or feel like doing a "system config
reset".

If you have clio or R1.3.3 on one flash and lambo on the other and want
to upgrade the secondary flash, e.g., to a newer submittal of the same
release, remember that the process of upgrading the secondary flash will
copy the clusDb from the primary to the secondary, which will make it
unusable.  Make a backup copy of the clusDb from the secondary flash
before starting the system upgrade.  After the upgrade is done, and
before you reboot, restore the backup copy on the secondary flash.  You
should then be able to reboot to the secondary with a valid clusDb.

See me if you have any questions.

ChrisV



------_=_NextPart_001_01C717E6.59B62AB8
Content-Type: text/html;
	charset="us-ascii"
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.28">
<TITLE>Lambo: Before you sync your tree...</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><B><FONT COLOR=3D"#FF0000" SIZE=3D2 =
FACE=3D"Arial">Back up your clusDb before you sync your =
tree!!</FONT></B></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">With =
my latest check-in for lambo (#2</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">2046</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">)</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> to support using a vsvr</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">hostname</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> in creating a remote =
mirror,</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> there are clusDb changes =
that will make it incompatible with previous lambo and clio =
builds.&nbsp; So, once you do a complete build and run it you will be =
unable to go back unless you have a backup copy of your clusDb or feel =
like doing a &#8220;system config reset&#8221;.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If =
you have clio or R1.3.3 on one flash and lambo on the other and want to =
upgrade the secondary flash, e.g., to a newer submittal of the same =
release, remember that the process of upgrading the secondary flash will =
copy the clusDb from the primary to the secondary, which will make it =
unusable.&nbsp;</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B> <FONT SIZE=3D2 FACE=3D"Arial">Make a backup copy of =
the clusDb from the secondary flash before starting the system =
upgrade.</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; After the upgrade is =
done, and before you reboot, restore the backup copy on the secondary =
flash.&nbsp; You should then be able to reboot to the secondary with a =
valid clusDb.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">See =
me if you have any questions.</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">ChrisV</FONT></SPAN></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C717E6.59B62AB8--
