Atomicorp

In the process of migrating from one server to another I have added another complexity. I am moving to a new co-location. Due to time constraints I will have to start with moving the old server to the new colo before migrating to new servers. Now I'm wondering a little about how you usually do this maneuver.

I was thinking something like this.

0. Lower TTL in SOA-records.
1. Shutdown server7 (the server about to be relocated).
2. Re-locate (easy to write, hard work to pull off).
3. Start up server7.
4. Change IP-adress on server7 (for example http://blog.hostonnet.com/how-to-change ... tos-server)
5. Change IP-adresses in Plesk on server7 (http://kb.parallels.com/en/943)
6. Update secondary DNS with new primary DNS IP of server7 (script for Cloudns running locally on my Mac)
7. Update reverse DNS entries for server7

Anything I'm missing?

The location is within the same city so it wouldn't take more than a 1-2 hours to get it up and running physically.

Thats pretty much what I would do too. Maybe get your TTL changes in 24 hours before you start so you know that you're controlling everyones caching

Thanks Scott!