Exchange 2010 - DAGs and other questions
Posted on 2011-03-10
I'm running in a test env now. I've successfully been able to migrate an exchange 2003 server over to exchange 2010.
My Exchange 2003 solution (in lab and in production) is running on a single server. I have several hundred users but the vast majority of them infrequently check their mail and when they do, we have them set up as POP users (too complicated to explain why). We have had no performance issues with this current Ex2003 setup.
In the new Ex2010 solution, there will be just a few (maybe 50-100 users) who will need to connect to the server via MAPI (Outlook Anywhere), and maybe 50 of these users have smart phones that will need to connect to Exchange as well. The rest will all be POP or connecting via OWA.
I have a list of questions that might very well overlap, but I'm trying to get some big picture vision here.
I'm thinking that what I will do is have two physical servers. One will run all Exchange Roles as well as be the primary DC. The second server will be my backup DC as well as my backup Exchange server to hook up to for DAGs. Is this a reasonable solution?
If I understand DAG's correctly, I need to have Exchange running on a second server in order for the DAG's to work correctly, yes?
Am I correct in assuming that a POP user connecting to an Exchange server will use less server resources then say a full-fledged Outlook MAPI connection?
The reason I want to keep the number of physical servers down is because we are renting these servers from Rackspace, we don't run these servers in house. So each additional server is a pretty big expense for us.
I want to create this solution with the fewest number of servers possible. I know two servers might not be optimal - but I need to know if this will work, and how far from optimal it is.
Thanks for your suggestions and thoughts.