Fail-over friends keep Exchange chugging
Five disaster-proofers take different tacks to mail server protection
Cemaphore MailShadow is an effective product that allows you to take a granular approach to protecting e-mail accounts. High-priority users can be replicated while others are protected only by backups, resulting in lower replication costs. Although some admins may take issue with the absence of automated fail-over, the product is easy to set up and administer and offers a reasonable value.
Quest Availability Manager for Exchange
Quest offers QAM (Quest Availability Manager) alone or as part of the Quest Availability Suite. The suite also includes a management application that proactively monitors Exchange, looking for data errors or configuration errors that might cause problems. I tested the management product, Quest Spotlight on Exchange, earlier this year.
QAM -- Version 2.0 in this review -- works in a fashion similar to MailShadow, allowing the administrator to designate specific mailboxes to be protected and moving users to a reserve server if any of the protected Exchange servers becomes unavailable. As does MailShadow, QAM replicates transactions rather than duplicating the message store, so it is not vulnerable to replicating database problems, and one backup server can protect multiple primary Exchange servers.
As opposed to MailShadow, QAM does use an agent on the server, but it offers additional benefits, including automatic fail-over from the primary to the secondary mailbox store. Another advantage is lower pricing per mailbox than MailShadow.
Installation of QAM involves the agent and an extension to the Microsoft Exchange System Management application to allow it to manage the QAM functions as well. In addition, you must give the Administrator account the proper permissions and set up a service account. Finally, you will need a second mailbox store, which may either be on the same Exchange server as the primary or on a second Exchange server. QAM allows you to set up secondary stores on two Exchange servers so that each fails over to the other, or to set up
Click for larger view.
If QAM detects a failure on the primary Exchange server, either in the availability of the store or in Exchange services, it will initiate fail-over to the secondary store. Users will have to restart Outlook to switch to the secondary store, and QAM provides an alert notifying them of this. It takes about five minutes for the fail-over process to take place, during which users cannot access their accounts, although incoming messages are still received by the backup Exchange server.
When the administrator shifts mailboxes back to the primary Exchange server, all changes made to the secondary server are replicated back to the primary.