Microsoft Exchange dumped for Linux-based clone

Linux-based PostPath Server addresses cost, message store issues at hospital

Pennsylvania hospital Moses Taylor Hospital replaces Microsoft Exchange 5.5 e-mail system with Linux-based PostPath Server to save money, support more users and messages.

Taking a page from the doctors at Moses Taylor Hospital, IT staff at the Scranton, Pa., facility last year diagnosed their messaging system and came up with an effective treatment that's turned out to be a life saver.

The patient in this case was an aging Microsoft Exchange 5.5 environment that couldn't support increased message loads and was going to cost a bundle to upgrade.

After conducting an evaluation of alternatives, the hospital decided not to upgrade to a newer version of Exchange. Instead, it went with a  Linux-based Exchange clone that it felt could meet the needs of its 700 users without forcing them and IT to learn a whole new system. (Compare Messaging products.)

As it turns out, it wasn't feature sets that swayed the decision. It was the price, according to Frank Fallo, manager of network systems and workflow development at Moses Taylor.

"[With Exchange,] I saw extremely high cost, especially the [client access licenses]," Fallo says. "The Microsoft billing structure was considerably more expensive and that is just talking about the software side. If you want to include hardware, we also needed a more robust server."

Fallo got the more powerful hardware anyway, but it is running PostPath Server, a Linux-based clone of Exchange, on top of the Linux Centos operating system.

"We have estimated that PostPath saved us 50% over the cost of Exchange," Fallo says, and that doesn't count what Microsoft would have charged for maintenance and support (Fallo declined to get into the project's specific dollar figures).

The hospital also went from three staffers managing e-mail to one.

Another benefit is that PostPath is a "very good representation of the Exchange server," Fallo says.

So good, in fact, everything on the network that talks to the server thinks it is Exchange, including Active Directory, making integration of Microsoft and third-party tools, and other add-ons much less of a headache, Fallo says.

The integration also includes the Outlook clients that run on desktops at Moses Taylor, a 173-bed hospital that was opened in 1892 by New York City merchant/banker/industrialist Moses Taylor to care for the railroad workers and coal miners of the region.

Fallo says the integration with Outlook has eased any training issues for the hospital and numbed the inevitable end-user complaints.

The one client difference, however, that has worked in Fallo's favor is the AJAX-powered Zimbra Web mail client that PostPath uses. The hospital likes it better than the Outlook Web Access client of Exchange 5.5 (Microsoft has since improved its Outlook Web Access client).

"You can basically do anything with the Web mail client that you can do in the [Outlook] desktop client," Fallo says.

While the PostPath benefits are a reality now, Fallo had to validate them with a proof-of-concept before he got the green light to migrate. "There was concern we were moving away from the Microsoft platform," Fallo says. The hospital is basically a Microsoft and Dell shop.

Fallo downloaded the free 12-user trial from PostPath and ran it side-by-side with Exchange for more than six months. When it was clear that PostPath was viable, Fallo began the migration using tools from third-party vendors, PostPath and even Microsoft.

"We did the same clean-up and tidy-up for the migration that we would have done with any migration," Fallo says.

He says the PostPath management tools are on par with Exchange's, but that users should realize there are still some command-line features.

"You don't have to be a Linux guru, but need to know your way around as an administrator," Fallo says. Later this year, PostPath will introduce PostPath Administrator, which is a GUI-based tool.

Solving message store issues

Fallo says PostPath also has solved message store issues that led to some painful management in Exchange.

Exchange's Jet Database Engine puts a limit of 16GB on the data store, at which point the message service shuts down. The limit forces administrators to put restrictions on in-box size.

Moses Taylor's message store in Exchange was at 15.7GB. With PostPath and its simplistic file structure, the hospital has been able to eliminate restrictions on mailbox sizes using a Dell storage server.

"We may go back [to limits], but right now we are pleased we don't have to do that," Fallo says.

In addition, the hospital has been able to give e-mail to 105 employees that never had the service because of Exchange's storage limitations.

Message recovery also is easier.

"If we had to restore a single mailbox in Exchange, we could not do it. We had to restore the entire message store. That is the way we were configured. PostPath is a simple file structure. We can recover a single message for a single person," Fallo says.

It has now been six months since Fallo made the switch over.

"I think we made a wise decision," he says.

Learn more about this topic

Trio of e-mail vendors upgrade Exchange alternatives

Insider Tip: 12 easy ways to tune your Wi-Fi network
Join the discussion
Be the first to comment on this article. Our Commenting Policies