Exchange Hub / Dumpster
If I understand, Exchange 2010 uses the log shipping between 2 database to keep them synchronized.
The Hub-T server has a role as "Dumpster".
Now, let say the Mailbox server1 has the active copy of the DB and when in the process of synching with MB2 , it has failed and the MB2 became the Active. how does the MB2 get the missing emails from MB1 seeing that the synching was not complete.?
Thanks
The Hub-T server has a role as "Dumpster".
Now, let say the Mailbox server1 has the active copy of the DB and when in the process of synching with MB2 , it has failed and the MB2 became the Active. how does the MB2 get the missing emails from MB1 seeing that the synching was not complete.?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Does your mouse not work? The article gives a FULL explination of how exchange 2010 handles continuos replication. You should be reading the whole article if you wish to "Understand" this in full. I pointed out the section of the article to pay extra attention to, not the ONLY bit to read.
ASKER
thanks... the links don't work...
Link works perfectly, have clicked on it 3 times and opens the correct page at microsoft everytime. What browser are you using?
ASKER
from inside the company , don't work
ASKER
Cannot you just try to explain it here?
You can't visit Microsoft sites from work? Some kinda network that!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found this article:
The function of the Transport Dumpster has changed in Exchange 2010. When using DAGs the transport dumpster now receives feedback from the replication pipeline to determine which messages have been delivered and replicated. As a message goes through Hub Transport Servers on its way to a replicated mailbox database in a DAG, a copy is kept in the transport queue until the replication pipeline has notified the Hub Transport server that the transaction logs representing the message have been successfully replicated to and inspected by all copies of the mailbox database. Once the logs have been replicated to and inspected by all database copies, they are truncated from the transport dumpster. This keeps the transport dumpster queue leaner by maintaining only copies of messages whose transactions logs have not yet been replicated
The function of the Transport Dumpster has changed in Exchange 2010. When using DAGs the transport dumpster now receives feedback from the replication pipeline to determine which messages have been delivered and replicated. As a message goes through Hub Transport Servers on its way to a replicated mailbox database in a DAG, a copy is kept in the transport queue until the replication pipeline has notified the Hub Transport server that the transaction logs representing the message have been successfully replicated to and inspected by all copies of the mailbox database. Once the logs have been replicated to and inspected by all database copies, they are truncated from the transport dumpster. This keeps the transport dumpster queue leaner by maintaining only copies of messages whose transactions logs have not yet been replicated
this is how it works in DAG the rest I wrote is still applicable
ASKER
I din't know that HUB server has a database to keep each mail going in/out.
so when you install hub role does it have a database that gets installed by default? if so what is its name?
so when you install hub role does it have a database that gets installed by default? if so what is its name?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
excellent
ASKER