RE: [cobalt-users] Strategy Question

["Devin Smith" <devinsmith@xxxxxxxxxxxxxxx>]

I think my approach would be a little different, as long as you can get
the raq from one location to the other overnight and hooked up.  This is
what I would do:

1) Buy another RaQ4 and just ghost the original, move the mail queues
after DNS is updated. :-)

Or 

0) Email/Contact your customers, and let them know that their sites and
email will be unavailable from 5:00PM on day 1 until approximately
9:00am on day 2.  
1) A few days before, set the TTL on the DNS to something short, maybe
30 minutes.
2) The day of the move, update the DNS to the new IP addresses.  
3) Ship your RaQ to the new location overnight 8:30AM delivery, and plug
it into the new location.
4) Set your TTL back to whatever it was before for good netizen karma.

While your server WILL indeed be down, I suspect it will be a LOT less
work and a lot less interruption (and possibly corruption) of your
customer's data.  Moving between dis-similar machines for the sake of
being down overnight is not woth the hassles it could end up causing
you.  With wonderful shipping from FedEx or UPS, I'm sure you can drop
the server off at 5:00 in Tulsa, and have it appear magically in Tampa
early next morning.  With your customers notified (and since you're
doing it off a DSL and a single RaQ, I'm guessing you don't have an
unweildly number of customers to contact), they should be more than
understanding.