Hello All, We have the following topology: ====================== 2 CAS/HUB Role Servers with WNLB 2 Mailbox Role Servers in a DAG We need to add another Exchange 2010 that host CAS/HUB/Mailbox roles as part of DR plan. Anything I need to watch out for? Is that even recommended or am I going to run into issues? Thanks, Yassar

There is nothing wrong with what you are proposing. Of course there can be problems with how you implement things you didn't disclose.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Adding to Ed, you mentioned you are planning to implement that server for DR purpose; I would assume you are implementing that on different location than from the current servers located.Cheers

To clarify our plan, the new Exchange Server which will host CAS/HUB/Mailbox will be in our environment as a production server in the same data center. However, an image of this server will be hosted in another data center and any changes that happens to that production server will be replicated to the hosted hosted in the remote data center.

However, an image of this server will be hosted in another data center and any changes that happens to that production server will be replicated to the hosted hosted in the remote data center. Can you expand on how that is going to happen please, as I can forsee issues with this.Cheers, Rhoderick Microsoft Premier Field Engineer, Exchange Blog: http://blogs.technet.com/rmilne  Twitter:     LinkedIn: Note: My posts are provided AS IS without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

The Server that will host CAS/HUB/Mailbox roles, which will be part of our production environment, will have a replication agent (ex. veeam replication), which will replicate all the changes to the other server that resides in the DR Data Center. The agent will continuously replicate any changes on that server.

Take a look at this please http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/a53d0353-73d4-47af-9975-d498c0a60b21 Cheers, Rhoderick Microsoft Premier Field Engineer, Exchange Blog: http://blogs.technet.com/rmilne  Twitter:     LinkedIn: Note: My posts are provided AS IS without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Take a look at this please http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/a53d0353-73d4-47af-9975-d498c0a60b21 Cheers, Rhoderick Microsoft Premier Field Engineer, Exchange Blog: http://blogs.technet.com/rmilne  Twitter:     LinkedIn: Note: My posts are provided AS IS without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hi , I recommend youd better separate the CAS role and Mailbox role if it is possible. If the Exchange 2010 server add to DAG, it will not use CAS Array with WNLB. If you plan to deploy multi-role Exchange 2010 servers with both DAG protected mailbox databases and load balanced/highly available CAS server service, you cannot use WNLB due to Windows Failover Cluster (WFC) and WNLB hardware sharing conflicts. Windows Network Load Balancing isn't supported on Windows failover cluster servers. After a Client Access server array is defined within an Active Directory site, all Client Access servers within that Active Directory site are automatically part of the Client Access server array. So if you have already configured CAS Array, I recommend youd better separate the CAS role and Mailbox role if it is possible. Load Balancing Exchange 2010 Client Access Servers using an Hardware Load Balancer Solution (Part 1) http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/load-balancing-exchange-2010-client-access-servers-using-hardware-load-balancer-solution-part1.html Understanding Database Availability Groups: http://technet.microsoft.com/en-us/library/dd979799.aspx#ClientExp Understanding RPC Client Access: The Client Access Server Array: http://technet.microsoft.com/en-us/library/ee332317.aspx Wendy Liu TechNet Community Support

Hi , I recommend youd better separate the CAS role and Mailbox role if it is possible. if you plan to deploy multi-role Exchange 2010 servers with both DAG protected mailbox databases and load balanced/highly available CAS server service, you cannot use WNLB due to Windows Failover Cluster (WFC) and WNLB hardware sharing conflicts. Windows Network Load Balancing isn't supported on Windows failover cluster servers. After a Client Access server array is defined within an Active Directory site, all Client Access servers within that Active Directory site are automatically part of the Client Access server array. So if you have already configured CAS Array, I recommend youd better separate the CAS role and Mailbox role if it is possible. Load Balancing Exchange 2010 Client Access Servers using an Hardware Load Balancer Solution (Part 1) http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/load-balancing-exchange-2010-client-access-servers-using-hardware-load-balancer-solution-part1.html Understanding Database Availability Groups: http://technet.microsoft.com/en-us/library/dd979799.aspx#ClientExp Understanding RPC Client Access: The Client Access Server Array: http://technet.microsoft.com/en-us/library/ee332317.aspx Wendy Liu TechNet Community Support