Commentary

Howard Marks
 

Cemaphore MailShadow -- Exchange Failover With A Twist

E-mail, and more particularly Microsoft Exchange, is a classic example of how user adoption can turn an application mission critical before the IT guys catch on. Most IT departments protect Exchange servers with the same techniques they use to protect other applications. Replicate the data to another disk somewhere and have an idle Exchange server mount the database for failover. Rather than collect data at the file or block level, MailShadow collects Exchange objects at the transaction layer for replication. Working higher on the stack brings MailShadow some significant advantages.
E-mail, and more particularly Microsoft Exchange, is a classic example of how user adoption can turn an application mission critical before the IT guys catch on. Most IT departments protect Exchange servers with the same techniques they use to protect other applications. Replicate the data to another disk somewhere and have an idle Exchange server mount the database for failover. Rather than collect data at the file or block level, MailShadow collects Exchange objects at the transaction layer for replication. Working higher on the stack brings MailShadow some significant advantages.The biggest advantage is not replicating database corruption the way disk replication can, especially as the production server crashes. Replicating transactions also means less data to replicate. Exchange writes every transaction at least twice, once in the transaction log and once in the .EDB file and a disk replicator has to send it each time. Disk replicators use a lot of bandwidth in the middle of the night when Exchange does an online database defragmentation.

Failover is faster than mounting a crash-consistent database since the target Exchange server is always running against it's own database. All MailShadow has to do is a little magic so the client stations will connect to the backup server. Source and target can be running different versions of Exchange. At least one customer has used this feature of MailShadow to migrate to a newer version of Exchange.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links