Solved

Don't understand how Shadow Redundancy in Exchange 2010 work

Posted on 2010-09-11
7
1,088 Views
Last Modified: 2012-05-10
I've reading Shadow Redundancy article from Microsoft site:
http://technet.microsoft.com/en-us/library/dd351027(EXCHG.140).aspx

Question 1: In the document, it gives an example of "Multiple Hop Scenario", the step 3 says:

3.The Chicago hub queries the New York hub for discard status and receives the discard notification for the message. At this time, it can remove the shadow message from its database. Whether the message was delivered from London to Dublin doesn't have an impact on when the Chicago server deletes the shadow message.

Why "whether the message was delivered from London to Dublin doesn't have an impact on when the Chicago server deletes the shadow message"???

It seems to comflict with the Microsoft definition of "Shadow Redundancy" saying "With shadow redundancy, the deletion of a message from the transport database is delayed until the transport server verifies that all of the next hops for that message have completed delivery"

it clearly says that the deletion of a message until verifying that ALL of the next hops for that message have completed delivery!

Anyone can help to explain that?

Thanks in advance,
Jerry
0
Comment
Question by:JerryJay
  • 3
  • 2
  • 2
7 Comments
 
LVL 32

Accepted Solution

by:
endital1097 earned 300 total points
ID: 33653967
because at that point the new york ht has passed the message to the next hop so the message is no longer in its queue, therefore to the chicago server the message has been "delivered"
0
 
LVL 32

Assisted Solution

by:endital1097
endital1097 earned 300 total points
ID: 33654028
the best way to think of it is that exchange will always attempt to deliver the message to the final destination
so with shadow redundancy it is still taking the best possible route, but after the message is handed off to the next hop, to the source hub transport server that's its destination. at that point the purpose of shadow redundancy is to ensure that hop processed the messag
when the message no longer exists at that hop shadow redunancy considers the message delivered

shadow redundancy is not guaranteed delivery from source to destination, just from hop to hop
0
 
LVL 49

Assisted Solution

by:Akhater
Akhater earned 200 total points
ID: 33654683
Back to exchange 2007 we had an issue that a failing HUB will lead all the emails in its queue to be lost.
 

With Exchange 2010 Microsoft tries to make hardware "disposable" meaning that any failing hardware can be replaced without any impact or data loss.

For the HUB servers they have implemented Shadow Redundancy which means that each hop will only delete the email after it gets the confirmation that the next hop was able to relay it.

assuming the email sent from A to B needs to pass by Server1 -> Server2 -> Server3

Server1 will delete the email only when it gets the confirmation from Server2 that it was able to deliver it to server 3.

that's the 3 hop concept
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 

Author Comment

by:JerryJay
ID: 33657215
thanks to all above comments, now I understand "shadow redundancy is not guaranteed delivery from source to destination, just from hop to hop" as endital1097 explained

But...

Akhater says: "With Exchange 2010 Microsoft tries to make hardware "disposable" meaning that any failing hardware can be replaced without any impact or data loss"

The document talked about an example of an Hub trying to deliver a msg to an Edge, after delivery, it query the Edge for confirmation of delivery, but failed to talk to the Edge, it then resent the msg from Shadow queue to another Edge for delivery. sounds great!!! but what about in a senario that the very first Hub server picks up whole bunch of messages from a Mailbox server, but before it tries to deliver them, it fails. will that cause any data lost? it answer is YES, how can Microsoft make hardware "disposable".

My understanding is the shadow Redundancy is for data protection between hub to hub/edge communication, not for mailbox to hub communication. If a hub fails, there will be data lost if it didn't deliver msgs which it picked up from mailbox servers. this can be very common, i think, when a hub fails
0
 
LVL 32

Assisted Solution

by:endital1097
endital1097 earned 300 total points
ID: 33657231
take a look at the following:
http://technet.microsoft.com/en-us/library/dd351091.aspx

but to answer your question (taken from link)

Message submissions from MAPI or Windows Mobile clients aren't redundant. After the message is successfully stored on the Mailbox server, Exchange high availability features can take effect and help prevent data loss. This scenario provides a complete picture of message flow, from beginning to end.
0
 
LVL 49

Assisted Solution

by:Akhater
Akhater earned 200 total points
ID: 33657345
The document talked about an example of an Hub trying to deliver a msg to an Edge, after delivery, it query the Edge for confirmation of delivery, but failed to talk to the Edge, it then resent the msg from Shadow queue to another Edge for delivery. sounds great!!! but what about in a senario that the very first Hub server picks up whole bunch of messages from a Mailbox server, but before it tries to deliver them, it fails. will that cause any data lost? it answer is YES, how can Microsoft make hardware "disposable".


no the answer is no since, in this case, they are still on the mailbox server. Mailobx -> hub messages are also redundant with shadow redundancy.

for the Mailbox server, however, you will need DAG for redundancy
0
 

Author Comment

by:JerryJay
ID: 33659302
many thanks to Akhater and endital1097. good answers! appreicate all your help here.
0

Featured Post

Do email signature updates give you a headache?

Constantly trying to correctly format email signatures? Spending all of your time at every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now