Just don't mix.
Congratulations to me! We went live on our new server. And it went so smoothly: put up a "closed for maintenance" page, transfer the data, update the DNS and Done! Six and a half hours (I was up all night, restoring a 2GB MySQL backup file takes a looooong time) and we are ready to rock.
I really was amazed at how painless the process was. The two glitches we had were: 1 - a SQL query that had to updated due to the upgrade to MySQL 5, and 2 - and ASP page buried in a ColdFusion website that used an ODBC datasource I forgot to create (I didn't even know it was needed.) Thats it!
Just when I was going to file for the Guinness World Record for Most Painless Webserver Transfer, disaster struck. Disaster in the form of my co-worker, who felt the irresistible urge to delete the DNS record. You see, instead of changing DNS servers, I update the IP address of the current record, so the update was complete in about an hour or so. He went and removed that DNS record, and added one pointing to the LogicWorks (our new host) DNS servers, which were not configured for our domain name.
Within 5 minutes, the site was completely inaccessible. I'm getting yelled at from all sides, nobody's happy, least of all me. We recreated the DNS record within minutes of it having been deleted, but it seems that its much more effective at deleting records than it is at adding.
About 3 hours later, the crisis was over. The new DNS record (the same as the old one) propagated out, and all was good and happy again. Moral of the story: don't screw around with the DNS records!
Oh, and be proud of me. I took responsibility for the mishap rather than pass the blame to my co-worker (who is really a bit junior to me, I stand up for my people!)
Item of the Day: Freestanding Bath Tub: Cube BC0803 by Wet