[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Advice on how to relocate a server?



----- Original Message -----
From: "Ben Liddicott" <ben.liddicott@xxxxxxxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Tuesday, December 04, 2001 9:03 AM
Subject: [cobalt-users] Advice on how to relocate a server?


> We will be relocating two Cobalt RaQs to another datacenter very soon, and
I'd be really interested in anyone's advice on how best
> to do it.
>
> Thus far my plan is:
>  *  Announce planned downtime, about four hours from 0:00 sunday to 4:00
sunday of the chosen week.
>  *  Install additional RaQ in new datacenter, configure it as DNS primary
for all sites where we control DNS. Inform others of our
> intended move time and new IP addresses.
>  *  Cut DNS TTLs on our sites to about an hour, a couple of days in
advance (perhaps in stages)
>  *  Rip out the servers from the old datacentre. (point of no return).
>  *  Stick the servers in the new datacentre, configure new IP etc. via
LCD.
>  *  Run script to change IP of all virtual sites to new IP via SSH. Test
sites.
>  *  Increase TTLs again.
>
> Any reason why that won't work? Have I missed anything?
>
> The other obvious method involves installing a server in the new
datacentre, then migrating the sites over to it one by one. That
> involves more labour while avoiding some of the downtime, but are there
any other advantages or disadvantages?
>
> Cheers,
> Ben Liddicott
>
>
Myself, when I change servers be it in a new datacenter or just to a new
server.  I create all the sites on a new machine
make copies of all the sites either with cmu or my own script,  copy them
over and install.  Then change dns to reflect the new addresses
once they are migrated.  then after a week take down the origional server.
Then repeat with the next one.

Granted this is a little more work and does require an additional server,
but I find it is the safest.  Also during the move I disable the ftp server
so no one can upload to the site,  it will prevent accidental data loss by
customers.

I moved 400 sites from Virginia to my center here in Chicago that way.  it
went off without a hitch..  Of course after I got them moved
the company I was hosting thru gave me a great deal so I kept 2 servers
there anyway.

But I find it is better to have an overlap since places like aol do not seem
to update dns as frequent.

Bill
http://www.biz-webhost.com