DNS Round Robin is great in theory. But not so great in reality. I recommend a LB or ARR. I’m really enjoying ARR and WAP.
From: [email protected] [mailto:[email protected]] On Behalf Of Adam Farage Sent: Tuesday, September 9, 2014 10:56 AM To: [email protected] Subject: Re: [Exchange] Cas and Mailbox on the same server. Not catching what you are asking, but you can load balance both the CAS and Mailbox role with a multiple server. You just can't use Windows NLB, which I would never recommend anyways since it is evil. There is no longer a CAS Array or a requirement for persistence in Exchange 2013, so you could (in theory) do DNS round robin. Sent from my iPhone On Sep 9, 2014, at 10:49 AM, "Paul Cookman" <[email protected]<mailto:[email protected]>> wrote: If you had a DAG then could the passive member multi role CAS still load balance the connections in an array to the active DAG member? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Adam Farage Sent: 09 September 2014 15:30 To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] Cas and Mailbox on the same server. http://blogs.technet.com/b/exchange/archive/2014/04/21/the-preferred-architecture.aspx I say do it, as long as it's properly sized. It makes for an easier model to scale, and helps in troubleshooting also (logs and everything are in one location). Sent from my iPhone On Sep 9, 2014, at 10:27 AM, "Paul Cookman" <[email protected]<mailto:[email protected]>> wrote: I was talking to a friend who had been advised from Microsoft to put CAS and Mailbox role on the same 2013 server that is in a DAG with about 1000 mailboxes, interesting to hear if anyone else has gone this way or your thoughts? Regards, Paul. ______________________________________________________________________ This email has been scanned by Selection Services Ltd using the Symantec Email Security.cloud service. ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by Selection Services Ltd using the Symantec Email Security.cloud service. ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by Selection Services Ltd using the Symantec Email Security.cloud service. ______________________________________________________________________
