The server change

On Friday night we started the migration to a new host server for The Batavian. We thought it would be a one-night job.

Our new IT support guy -- Nick, of Batavia -- put the site in "read only mode" and began transferring the database to the new server.

But we've published so much content over the past two and a half years years that the transfer ended up stretching well into Saturday.

Around 7 a.m., today, everything seemed set to flip the switch on the domain name and start pointing traffic to the new location.

Then we had some technical bug.

Things have seemed to settle down, but it will take a couple of days to get everything back to normal. Primarily, search isn't working yet and in posts pictures may not be appearing yet.

If you're seeing this post, you are seeing the new server. Everything should be fine.

There's no effective way to communicate this to people not seeing this post, but I'll put it out there anyway. If you're not seeing the new site, try restarting your computer. If that doesn't work, your Internet Service Provider just hasn't caught up with the change yet.  That can take some service providers as much as 48 hours to catch up.

Why the move: We anticipate a performance improvement. I feel like I'm already seeing it, though the server is still working pretty hard indexing the database and such. 

The simplest way to explain why we anticipate an improvement: When you have a site on a server that shares the server with other Web sites (a common type of commercial hosting environment), there is software that acts like a traffic cop and says, "OK, it's your turn to get this site, now it's your turn to go here, and now it's your turn to get this one."

This should happen very fast but, after we hired Nick to take over IT duties, he discovered that the type of software our previous host used had been shown to perform about four times slower than other options, so we decided in order to improve performance, we should change hosts.

Like I said, I feel like I'm already seeing better initial load times, so here's to hoping all of the frustration of the past 24 hours or so have been worth the change for all of us.