Rip and Replace: So long Exchange features--we hardly knew ye!

TechRepublic has an article out the features of Exchange that Microsoft has ripped out of Microsoft Exchange 2007. Althought not comprehensive, it lists the following as most significant:

• Exchange 5.5 integration: No longer available. Users will have to migrate to Exchange 2000 or 2003 before they can install 2007 (which is 64-bit only, of course) in their infrastructure. - You can still run a Domino 4.6.7a server in a mixed 5, 6, and 7 infrastructure
  
• Network-attached storage: Exchange 2007 does not support network-attached storage, only iSCSI.
• Active Directory Computers and Users-based management: The author seems to think this will make it more difficult to manage users. ROI?
• NNTP: Gone. NNTP has been removed from Exchange 2007. - Same in Lotus Domino. RIP, NNTP.
• Active/Active clustering: Only active/passive clustering is supported in Exchange 2007. - Active clustering has always (since Release 4.5?) - and still is - supported in IBM Lotus Domino.
  

The article then sums it up:

This isn’t a complete list of what Microsoft has gutted from Exchange 2007. While some of these features won’t be missed, some will take some getting used to and will require workarounds.

I'm sure Active/Active clustering (that has a single point of failure) will definitely not be missed since it never worked in the first place? ;)

Info Corporate: The mail server is down. Now what?

In the latest print edition of Info Exame, an article entitled "The mail server is down. Now what?" stands out. It reads (translated from portuguese):

IT'S NEARLY IMPOSSIBLE to work without e-mail in large companies, but mail server outages have been occurring more often than CIOs would like. A study by IBM Global Services shows that at any moment during a 12-month period, the probability of an unplanned system outage to occur is of 75%. And when it does, the solution takes good while to recover the server. In 82% of the cases the mean time to recovery is longer than four hours. The main cause of the sudden disruption in service is server failure (35%), followed by a connection loss or a corrupted database.

I'm not aware of the scope of the research done, if this was a world-wide study or not. But obviously 4 hour MTTR is way too long. And corrupted mail databases does not cause a mail server outage. Well, not that often ;-). Unless, of course, you're using Microsoft Exchange, where one db handles the mail for all of your recipients.

This reminds me of what happened at Brasil Telecom a couple of years go. After a sucession of MS Exchange server outages, the CIO just said "enough is enough" and migrated all of their distributed Exchange environment to clustered Lotus Domino servers running on pSeries. Full redundancy, and no more mail databases bringing a service down.

Link: Info Corporate - O servidor de e-mail caiu. E agora?)