Planning Exchange 2007 DR strategy for server roles
Hi Experts,
We are just planning our Exchange 2007 system, and had some queries regarding DR that I thoght I would throw out...
We will have the roles on seperate servers, and be using SCC for the Mailbox servers.
I was wondering what the recommended methods of DR were for each of the server roles?
Also, I have heard that the Hub has something called a Transport Dumpster, what does this do? If we lose the Hub, how do we restore messages that it was processing - is it related to that?
Thanks in advance.
Answers
- HI,
I will suggest to implement NLB for Hub transport and client access servers. For edge transport server you can create multiple equal MX records for each. I will mention below articles for those options.
For Mailbox servers you can you SCR, SCC or CCR. CCR can be combined with SCR.
Transport Dumpster is a new feature of Exchange Server 2007 Hub Transport servers through which the transport can defer the deletion of certain emails in their queues.High Availability
===========
http://technet.microsoft.com/en-us/library/bb124721.aspxHigh Availability Deployments
====================
http://technet.microsoft.com/en-us/library/bb201729.aspxStandby Continuous Replication in Exchange Server 2007 Service Pack 1 =====================================================
http://msexchangeteam.com/archive/2007/06/28/445538.aspxStandby Continuous Replication
====================http://technet.microsoft.com/en-us/library/bb676502.aspx
Load Balancing Exchange 2007 Client Access Servers using Windows Network Load-Balancing Technology – Part 1: Overview of Windows NLB Clusters
==============================================================================
http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/load-balancing-exchange-2007-client-access-servers-windows-network-technology-part1.html
CAS Load-Balancing Best Practices
======================
http://blogs.msdn.com/brad_hughes/archive/2007/09/10/cas-load-balancing-certificates-autodiscover-and-webservices.aspx
Load Balancing Exchange 2007 SP1 Hub Transport Servers using Windows Network Load Balancing
==============================================================
http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/load-balancing-exchange-2007-sp1-hub-transport-servers-windows-network-load-balancing-technology-part1.htmlExchange Server 2007 Hub Transport (HT) and Client Access Service (CAS) on the Same NLB Cluster
===============================================================
http://msmvps.com/blogs/clusterhelp/archive/2007/10/05/exchange-server-2007-hub-transport-and-client-access-service-on-the-same-nlb-cluster.aspx
How the Transport Dumpster works with a CCR cluster
=======================================
How to Configure the Transport Dumpster Settings
http://msexchangeteam.com/archive/2007/01/17/432237.aspx
=================================
http://technet.microsoft.com/en-us/library/bb676352.aspx
Regards
Chinthaka- Marked As Answer byJames-LuoMSFT, ModeratorThursday, June 18, 2009 2:14 AM
- Edited byChinthaka Shameera Friday, June 12, 2009 3:04 AM
For DR of server roles (MBX, CAS, HUB, UM and Edge), please see What Needs to Be Protected in an Exchange Environment, which will tell how to backup the configuration files for each server role and restore them
In order to know what are Transport Dumpster and its function, please see the “Transport Dumpster” section in Transport Server Storage Design
Resources:
- Marked As Answer byJames-LuoMSFT, ModeratorThursday, June 18, 2009 2:15 AM
All Replies
- HI,
I will suggest to implement NLB for Hub transport and client access servers. For edge transport server you can create multiple equal MX records for each. I will mention below articles for those options.
For Mailbox servers you can you SCR, SCC or CCR. CCR can be combined with SCR.
Transport Dumpster is a new feature of Exchange Server 2007 Hub Transport servers through which the transport can defer the deletion of certain emails in their queues.High Availability
===========
http://technet.microsoft.com/en-us/library/bb124721.aspxHigh Availability Deployments
====================
http://technet.microsoft.com/en-us/library/bb201729.aspxStandby Continuous Replication in Exchange Server 2007 Service Pack 1 =====================================================
http://msexchangeteam.com/archive/2007/06/28/445538.aspxStandby Continuous Replication
====================http://technet.microsoft.com/en-us/library/bb676502.aspx
Load Balancing Exchange 2007 Client Access Servers using Windows Network Load-Balancing Technology – Part 1: Overview of Windows NLB Clusters
==============================================================================
http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/load-balancing-exchange-2007-client-access-servers-windows-network-technology-part1.html
CAS Load-Balancing Best Practices
======================
http://blogs.msdn.com/brad_hughes/archive/2007/09/10/cas-load-balancing-certificates-autodiscover-and-webservices.aspx
Load Balancing Exchange 2007 SP1 Hub Transport Servers using Windows Network Load Balancing
==============================================================
http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/load-balancing-exchange-2007-sp1-hub-transport-servers-windows-network-load-balancing-technology-part1.htmlExchange Server 2007 Hub Transport (HT) and Client Access Service (CAS) on the Same NLB Cluster
===============================================================
http://msmvps.com/blogs/clusterhelp/archive/2007/10/05/exchange-server-2007-hub-transport-and-client-access-service-on-the-same-nlb-cluster.aspx
How the Transport Dumpster works with a CCR cluster
=======================================
How to Configure the Transport Dumpster Settings
http://msexchangeteam.com/archive/2007/01/17/432237.aspx
=================================
http://technet.microsoft.com/en-us/library/bb676352.aspx
Regards
Chinthaka- Marked As Answer byJames-LuoMSFT, ModeratorThursday, June 18, 2009 2:14 AM
- Edited byChinthaka Shameera Friday, June 12, 2009 3:04 AM
- Hi joe
Transport Dumpster is basically a feature that is used in CCR basically"Transport Dumpster is a new feature of Exchange Server 2007 Hub Transport servers through which the transport can defer the deletion of certain emails in their queues. The condition for an email to be retained in the transport dumpster is that at least one of the recipient's mailboxes must resides on a CCR mailbox server. This retained email can later be re-delivered if necessary. The amount of mail retained in the queues is a Organization wide setting on the Transport Settings container".
It is very helpfull when failoer cluster excercise is going on ,during this procedure the transport dumpster contact with all hub transport server in your infrastructure and execute the remaing email queues to succesfully delivered to mailbox server.
The recommended method with SCC with SCR is that you placed one mailbox server + one dedicated server for (Hub + CAS ) and one additional domain controller .the databse is replicated by the help of third party replication tools such as builtin in different SAN softwares.
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/32c90fad-05bb-4b77-bc06-fca6e951f285
Thanks
Syed Arsalan
syed.arsalan
...during this procedure the transport dumpster contact with all hub transport server in your infrastructure and execute the remaing email queues to succesfully delivered to mailbox server.
That's not strictly true. All Hub Transport servers in the same Active Directory site are contacted, not across the infrastructure which may of course contain multiple Active Directory sites.
Neil Hobson, Exchange MVPFor DR of server roles (MBX, CAS, HUB, UM and Edge), please see What Needs to Be Protected in an Exchange Environment, which will tell how to backup the configuration files for each server role and restore them
In order to know what are Transport Dumpster and its function, please see the “Transport Dumpster” section in Transport Server Storage Design
Resources:
- Marked As Answer byJames-LuoMSFT, ModeratorThursday, June 18, 2009 2:15 AM
Ex2007 sp1 HUB transport have its on mechanism to load balance, so bydefault we NLB is not required for HUB severs.
But there are some exceptional cases"""""""The resilient behavior that by default is built into the Hub Transport server works just fine for many organizations, but there are situations where you as an Exchange messaging administrator or consultant, for example, have a line of business (LOB) application, Microsoft Office SharePoint Server 2007 (MOSS 2007) portal, or perhaps a System Center Operations Manager 2007 (SCOM 2007) service management solution which, in order to submit messages to an Exchange organization must use a SMTP relay as these applications cannot log on to a mailbox using MAPI and then send the messages as that mailbox.
So what are your options in these types of scenarios? Well, with the Exchange Server 2007 RTM version, it was not supported to load-balance Hub Transport servers using Windows Network Load Balancing (WNLB) technology. This meant that if you had an application which needed to use your Exchange 2007 messaging environment to relay messages, you either had to specify two SMTP servers in the application (often not possible), use DNS round robin (not as intelligent as NLB) or MX records (not viable if the application only allows you to specify a smart host).
As mentioned load balancing Hub Transport servers in Exchange 2007 RTM was not a supported scenario, but now that Exchange Server 2007 Service Pack 1 (SP1) has been released guess what? Yes you’re right, it’s supported to load balance Hub Transport servers using a hardware load balancer or standard WNLB technology.
Although it’s now supported to configure Hub Transport servers in an NLB, please note that it isn’t supported to load balance connections between Hub Transport servers on your internal corporate production network using this method. You should only use NLB to load balance inbound SMTP connections from applications (such as LOB application, MOSS, and SCOM 2007 etc.) and other non-Exchange sources as well as client connections (in order to send messages, POP & IMAP clients uses the default client receive connector on a Hub Transport server).In this article series, I’ll show you step by step how you configure Hub Transport servers in a NLB using WNLB. We’ll also verify things works as expected as well as take a look at how fault tolerance and load balancing works for outbound message flow (messages leaving the Exchange organization).""""""""
