The Planet Blog

Hi there. It’s me again. I’m still in the trenches, trying to find a decent Reuben sandwich in the tunnels.

Daylight saving time ended last month in Texas, and as I changed my clocks, I dutifully replaced the battery in my smoke alarm, just like the public service announcements advised. As I balanced on a chair on top of my coffee table, I pondered: Why is the smoke alarm running on a battery and not, say, plugged into the wall?

Well, in a fire, power can get interrupted, so it’s best to have the smoke alarm running on an independent source of power that you can test and replace when necessary. In a way, this applies to your server, too.

Since my previous post, I’ve counted up a total of 18 incidents where a customer did not get notification of an update to a ticket or a critical message regarding a change to our services. Every one of those missed communications could be traced to an e-mail address residing on the affected server. Each one of those customers suffered downtime because they either didn’t receive an alert in a reasonable amount of time or they didn’t respond to a technician who was ready and waiting to assist them.

And those incidents were just the ones that I fielded … there’s no telling how many folks out there have their “server smoke detectors” hard-wired into the wall.

It’s critical that you keep your contact information up-to-date in Orbit and that you provide us with an external e-mail address. Same thing goes with the monitoring system: Use a contact address that will work if the server goes down.

The best solution I’ve found is to use a third-party provider like Gmail, Hotmail or Yahoo Mail, and forward those contacts/alerts to your primary mailbox (which can be on your server). By setting your contact address to a third-party provider first, you can ensure that you will always be able to access any important notifications. If you use a mail program like Outlook or Thunderbird, you can have the program check your third-party mailbox in parallel with your primary mailbox, eliminating the need to set up an auto-forward rule.

My advice: Do both.

Yes, I know that means you’ll get two messages for every one delivered to that emergency line, but in the end, isn’t it better to be over-notified of a potential emergency than to not hear about it at all?

-Laurence