Backup MX With Exchange 2007
Hi I need some guidelines to make a Backup MX with Exchange 2007. I have a Exchange 2007 in location "A", and when, let's says, it is down, or the internet link is down, I want Exchange 2007 Server in location "B" to receive (most important) email for it, and when Exchange Server in location "A" is back, to forward the emails to it. I know the requirements at DNS level about MX priorities. But What about Exchange 2007 in location "B" Configuration? Can anyone help me? I really appreciate your help, Thanks
December 7th, 2008 4:30pm

Hi, f the servers are part of the same exchange organization you don't need to make any configuration on server B. Leif
Free Windows Admin Tool Kit Click here and download it now
December 7th, 2008 10:00pm

More specifically Exchange 2007 Hub Transport servers are resilient by default. I recommend you read up on this built-in resiliency via the following links: http://technet.microsoft.com/en-us/library/bb124721.aspx http://technet.microsoft.com/en-us/library/bb267003.aspx 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.html
December 7th, 2008 11:25pm

Thanks both for the answer, If I have an Edge Server does changes something? Edit: More info: Intented topology design: Internet ---> Edge Server---> Hub Transport Server The document you sent to me says: "Edge Transport server to Hub Transport serverThe Edge Transport server automatically load balances inbound Simple Mail Transfer Protocol (SMTP) traffic to all Hub Transport servers in the ActiveDirectorysite to which the Edge Transport server is subscribed." Do you know what will happen if the hub transport serveris down? Will the messages be held at Edge and released later when hub becomes available? THANKS
Free Windows Admin Tool Kit Click here and download it now
December 9th, 2008 4:43pm

Hi Andres, The Edge Transport server that needs to route the message to an internal Hub Transport server will pick the next one in the list, as Hub Transport servers are resilient by default. If only one Hub Transport server exist in the AD site, the messages will queue up on the Edge Transport server and when the Hub Transport server is available again, messages will be delivered.
December 9th, 2008 7:45pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics