X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7AEA4.D1C9E5DD@onstor-exch02.onstor.net>; Thu, 14 Jun 2007 08:55:32 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7AEA4.D1C9E5DD"
Content-class: urn:content-classes:message
Subject: RE: Perforce maintenance and upgrade tomorrow Thursday 6/15
Date: Thu, 14 Jun 2007 08:53:17 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D290@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Perforce maintenance and upgrade tomorrow Thursday 6/15
Thread-Index: AceuHYQmjajhxLlZRHqErF27TicSwAAhv1rf
X-Priority: 1
Priority: Urgent
Importance: high
References: <BB375AF679D4A34E9CA8DFA650E2B04E02F3D28C@onstor-exch02.onstor.net>
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"dl-Engineering" <dl-engineering@onstor.com>

This is a multi-part message in MIME format.

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

We're on schedule for migrating Perforce today, and in about an hour =
I'll be halting the old services and bringing up the new server. I'll =
send a last minute warning before I do. Thanks much to John Rogers for =
materializing a nice machine to use.

-Ken


-----Original Message-----
From: Ken Renshaw
Sent: Wed 6/13/2007 5:58 PM
To: dl-Engineering
Subject: Perforce maintenance and upgrade tomorrow Thursday 6/15
=20
Sorry to have to do this, but the Perforce server database is in a bad =
way since yesterday and I need to rollback and rebuild it before we get =
any further. My plan is to rollback to the last checkpoint before the =
crash, manually add the changelists done subsequent to the crash, while =
at the same time upgrading the hardware and Perforce software to the =
latest version. This will not only fix a number of bugs but make the =
migration go more quickly and give us a more performant server in the =
end.=20

John R. is prepping a new system for me and will be online by tomorrow =
morning. As soon as the system is ready I will shut down the old server, =
bring up the new, and then replay the checkpoint into it and we should =
be good to go. I expect the outage to be from mid-morning sometime until =
mid-afternoon, I have no way to gauge the time it takes to replay a =
checkpoint, but it should be pretty quick with the new hardware and =
software.

I will send out an email in the morning when we're getting ready to cut =
over, if there are any questions please let me know.

The cougar team has been impacted the most, and I'm working with them to =
get their environment restored.

Thanks, sorry for the inconvenience.

-Ken

P.S. I suggest you hold your pending checkins if not absolutely needed =
until this fire drill is over tomorrow afternoon.=20



------_=_NextPart_001_01C7AEA4.D1C9E5DD
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>RE: Perforce maintenance and upgrade tomorrow Thursday =
6/15</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>We're on schedule for migrating Perforce today, and in =
about an hour I'll be halting the old services and bringing up the new =
server. I'll send a last minute warning before I do. Thanks much to John =
Rogers for materializing a nice machine to use.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Wed 6/13/2007 5:58 PM<BR>
To: dl-Engineering<BR>
Subject: Perforce maintenance and upgrade tomorrow Thursday 6/15<BR>
<BR>
Sorry to have to do this, but the Perforce server database is in a bad =
way since yesterday and I need to rollback and rebuild it before we get =
any further. My plan is to rollback to the last checkpoint before the =
crash, manually add the changelists done subsequent to the crash, while =
at the same time upgrading the hardware and Perforce software to the =
latest version. This will not only fix a number of bugs but make the =
migration go more quickly and give us a more performant server in the =
end.<BR>
<BR>
John R. is prepping a new system for me and will be online by tomorrow =
morning. As soon as the system is ready I will shut down the old server, =
bring up the new, and then replay the checkpoint into it and we should =
be good to go. I expect the outage to be from mid-morning sometime until =
mid-afternoon, I have no way to gauge the time it takes to replay a =
checkpoint, but it should be pretty quick with the new hardware and =
software.<BR>
<BR>
I will send out an email in the morning when we're getting ready to cut =
over, if there are any questions please let me know.<BR>
<BR>
The cougar team has been impacted the most, and I'm working with them to =
get their environment restored.<BR>
<BR>
Thanks, sorry for the inconvenience.<BR>
<BR>
-Ken<BR>
<BR>
P.S. I suggest you hold your pending checkins if not absolutely needed =
until this fire drill is over tomorrow afternoon.<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7AEA4.D1C9E5DD--
