Drupal updates and server migration

It seems I get more experience with Linux server migrations and Drupal site migrations that I should. Recently I started a phased approach to winding down and closing my company's Rackspace account. Rackspace provides a solid service, but they just weren't meeting my needs. What it came down to is that on the low-mid end, there are much cheaper options. Also, I wasn't fond of the bandwidth bills I was getting. Hosts like Liquid Web, for example, offer 3 TB of transfer as part of the package. Since the sites I host tend to be heavy on images, audio files, and very large documents, it gets pricey.

So I ended up opening up a VPS account with Linode. I get plenty of bandwidth that so far seems fast enough. The included bandwidth will make it easier on my cash flow when it comes to podcasts and other large numerous downloads.

That means I've been spending hours putting together migration documentation. Always have a solid plan, and test it, before migrating production sites. And on top of that, have a rollback plan. There's nothing worse than a site migration gone wrong and no plan to roll it back.

So far I've migrated half a dozen sites, including this one, to Linode from Rackspace. That includes:

  • Nameserver changes
  • DNS setup
  • apache virtual host setup
  • putting Drupal into Maintenance Mode
  • copying site files over
  • Exporting/Import MySQL db dumps
  • Configuring users and privileges on new server's MySQL db
  • Testing
  • Monitoring

I'm looking forward to lowering my hosting bills for my VPS and using Linode.

This is the first time I've used Drupals multi-site installation. All the sites I host are so different that they run off their own Drupal install. It's a mix of Drupal 6 and Drupal 7. For a new project I've started, I'll be hosting a handful of static content sites. That's where Drupal's multi-site install feature comes into play. Since I never needed it before I almost forgot about it. But for these small one-off content sites using a shared Drupal install with shared modules and themes will make maintenance for me a lot easier and less stressful. With all the modules a typical Drupal  site uses, there's always something that needs to be updated. Multiply that across all the sites I manage and it adds up.