locked
DAG RRS feed

  • Question

  • Hi,

    I am setting up a dag with 2 nw one for MAPI and another for replication.

    How about planning for redunacy if replication fails ( automitcally mapi picks it up.. ) or how can i plan it..

    Thanks

    Muthu


    Thanks Muthu

    Tuesday, January 28, 2014 2:33 PM

Answers

  • Exchange handles this by default:

    http://blog.gothamtg.com/2012/09/26/configuring-dag-networks/

    "If the replication network fails, the DAG will fail back to the MAPI network for replication."

    • Proposed as answer by Amine.G Tuesday, January 28, 2014 2:42 PM
    • Marked as answer by cara chen Tuesday, February 4, 2014 6:10 AM
    Tuesday, January 28, 2014 2:41 PM
  • It will do that for you automatically.

    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx

    • In the event of a failure affecting the Replication network, if the MAPI network is unaffected by the failure, log shipping and seeding operations will revert to use the MAPI network, even if the MAPI network has it’s ReplicationEnabled property set to False. When the failed Replication network is restored to health and ready to resume log shipping and seeding operations, you must manually switch over to the Replication network. To change replication from the MAPI network to a restored Replication network, you can either suspend and resume continuous replication by using the Suspend-MailboxDatabaseCopy and Resume-MailboxDatabaseCopy cmdlets, or restart the Microsoft Exchange Replication service. We recommend using the suspend and resume operations to avoid the brief outage caused by restarting the Microsoft Exchange Replication service.


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    • Proposed as answer by Belinda Ma Wednesday, January 29, 2014 4:49 AM
    • Marked as answer by cara chen Tuesday, February 4, 2014 6:10 AM
    Tuesday, January 28, 2014 2:43 PM

All replies

  • Exchange handles this by default:

    http://blog.gothamtg.com/2012/09/26/configuring-dag-networks/

    "If the replication network fails, the DAG will fail back to the MAPI network for replication."

    • Proposed as answer by Amine.G Tuesday, January 28, 2014 2:42 PM
    • Marked as answer by cara chen Tuesday, February 4, 2014 6:10 AM
    Tuesday, January 28, 2014 2:41 PM
  • It will do that for you automatically.

    http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx

    • In the event of a failure affecting the Replication network, if the MAPI network is unaffected by the failure, log shipping and seeding operations will revert to use the MAPI network, even if the MAPI network has it’s ReplicationEnabled property set to False. When the failed Replication network is restored to health and ready to resume log shipping and seeding operations, you must manually switch over to the Replication network. To change replication from the MAPI network to a restored Replication network, you can either suspend and resume continuous replication by using the Suspend-MailboxDatabaseCopy and Resume-MailboxDatabaseCopy cmdlets, or restart the Microsoft Exchange Replication service. We recommend using the suspend and resume operations to avoid the brief outage caused by restarting the Microsoft Exchange Replication service.


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    • Proposed as answer by Belinda Ma Wednesday, January 29, 2014 4:49 AM
    • Marked as answer by cara chen Tuesday, February 4, 2014 6:10 AM
    Tuesday, January 28, 2014 2:43 PM
  • You generally want the two networks to be in separate broadcast domains. If it is in the same broadcast domain you will cause a lot of overhead in the replication and cause more problems then help. 

    I would suggest you do not put them on the same network. 

    http://www.msexchange.org/articles-tutorials/exchange-server-2010/high-availability-recovery/uncovering-exchange-2010-database-availability-groups-dags-part2.html

    Tuesday, January 28, 2014 2:51 PM