<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi All.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I wanted to follow-up on the “portability” thread for a comment made in the process about data center moves…. I started a new thread since its really a different discussion.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have a /24 that we own and is currently advertised via BGP on our data center’s internet as well as on a dedicated circuit from another provider. I am planning for a move in the future – like a year from now. Last time I moved data centers 10 years ago I put up a firewall and switch at the new location and then moved all the servers 1 by 1 or few by few. Its was close by so it wasn’t a big deal. But virtualization has certainly changed the options available, and I expect to move about 30 minutes away from my current location. Also a lot has changed in terms of my customer’s expectations of uptime.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have been casually thinking about the move and wondering how I might be able to do something a bit more “slick” to move it with minimal downtime. I don’t purport to be a BGP expert so pardon me if I say something stupid but…. I was thinking that since I will put my own circuits into the new place (one with the “other provider” I have today), I could probably just use BGP to move things. The thought was to replicate at least the most critical/public facing servers to the new location and then just stop/start the BGP advertising to change to the new location. It seems to me that this should be nice and easy at least with the 1 “other provider” I have today, and avoid the need to re-IP anything. I mean, the convergence should be like normal and quick. Correct?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If so, it seems I can have almost zero downtime on the more static things like web sites. Then I can move the SANs, main virtual hosts and such a bit more “leisurely”. Obviously things like mail servers and such will be more of an issue because they are constantly changing (but are less visible to the outside world if they go down for an hour), but DNS servers, many web servers, etc should be ok I would think.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I welcome any thoughts on this. Want to make sure I am not overlooking something basic.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks,<o:p></o:p></p><p class=MsoNormal>Rick<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>