Saturday, January 27, 2007

Exchange replacement

First thing first, why in the hell are you running KDE on a server, and more important, why are you running an X server on one at all?

A huge number of people that got stuck with Exchange servers want to get rid of them. That's why these articles keep coming up.

What you meant was that you need the address book and directory services. Scheduling tends to be done by secretaries, and forms/IMAP folder sharing is generally not needed. Now if you say you *want* scheduling, etc, then fine, there are a number of quality products from which you can choose. If you define "what you need" to be the exact feature set of Exchange, then it isn't surprising that you think you need it. You can implement everything that Exchange/Outlook does with other software, cheaper, with more reliability, and on less hardware.

1. As for AD management software... let's see. You bought Windows Server because it's easy to use and admin, Exchange because it's easy to admin, and are using AD because it's easy to admin. So to do it right, you have to buy third party software? Sounds more like somebody screwed up their research and choose a bad solution based on broken assumptions. You have to do basically the same thing on any platform, so that's not a good reason to choose one over another. The UNIX solutions are much more reliable than Exchange, too, and less expensive. They also provide all the same functionality. Unless you go out of your way to ignore the solutions that work, anyway.

2. That's because Windows' does not provide functionality such as LVM. An application can also lock a file and prevent any app with any access level from even reading it. Exchange also keeps quite a lot open and locked when it doesn't need to. If the app was written well, it wouldn't be a problem. However, your backup explaination is an excellent example of why Windows is a huge pain in the ass.

3. BS, that is a perfectly valid comparison; backing up email is backing up email. If the application is written properly, the database will be fine. Exchange isn't written well, so it has problems. That software doesn't even provide a way to do a backup without either getting third party software or shutting Exchange down. Also, your VSS stuff is essentially the *exact same thing* as LVM snapshots. Why would your way work when LVM wouldn't? If the database is inconsistent, then it's inconsistent either way.

So what you're saying is that Windows/Exchange is better because it requires more jumping through hoops, buying more random software, and more dealing with random BS like bad data formats and bad storage techniques?

No comments: