Wednesday, 22 June 2011

Virtualization of Exchange 2010 in a small environment

As I'm following the Microsoft course 10135A Configuring, Managing and Troubleshooting Microsoft Exchanges Server 2010, I found this herunder post concerning the installation of Exchange 2010 for Small Environment.
For any questions, please refere to the original post URL given above.
Question :
We are running an Exchange 2003 server with less than 100 mailboxes.  We would like to purchase a new server that will run Hyper-V and virtualize Exchange 2010.  So, I wanted to get some recommendations on the hardware we should order and configuration of the virtual guest machines.

I'm thinking of getting a server with two quad-core processors, 24GB of RAM and 12 drives carved out into RAID 1 configurations.

1. Should I install the host server with 2008 R2 core to reduce security footprint (let security updates requiring a reboot)?
2. Should the guest Exchange 2010 VM include multiple roles: CAS, Hub, Transport, MBX on a single VM since we are a small deployment or should I still break out the MBX into a separate VM running core or Enterprise?
3. I'm thinking of configuring the guest Exchange 2010 VM with VHDs dedicated to separare RAID1 arrays for the OS, DB and logs. Since the host server will have two quad core processors, I would dedicate 4 virtual processors and 16GB or RAM.  Does this sound OK?
4. Since we are running 2003 domain controllers, I was thinking of upgrading to 2008 AD by adding a 2008 domain controller as a VM on this same server.  Would that work as I am short additional server hardware?

Thanks for your input.

--------------------------
Reply :
The Host machine Hardware Cofiguration look good enough for 100 mailboxes.

1. Should I install the host server with 2008 R2 core to reduce security footprint (let security updates requiring a reboot)?
    Yes. You can. Ref to http://technet.microsoft.com/en-us/library/aa996719.aspx -> Root Machine Storage Requirements


2. Should the guest Exchange 2010 VM include multiple roles: CAS, Hub, Transport, MBX on a single VM since we are a small deployment or should I still break out the MBX into a separate VM running core or Enterprise?
   One of the reason for installing MX,CAS,HUB in seperate servers is for server load balancing between the roles. But As you are gonna install MX,CAS,HUB in Same Host machine, Its not Required to install them as Seperate VM.
  So You may go for Single Server with MX,CAS,HUB Roles.

3. I'm thinking of configuring the guest Exchange 2010 VM with VHDs dedicated to separare RAID1 arrays for the OS, DB and logs. Since the host server will have two quad core processors, I would dedicate 4 virtual processors and 16GB or RAM.  Does this sound OK?
  Dedicated array disk for OS , DB & Log is good deployment plan. It sounds ok.

4. Since we are running 2003 domain controllers, I was thinking of upgrading to 2008 AD by adding a 2008 domain controller as a VM on this same server.  Would that work as I am short additional server hardware?
 Its not recommended to install Exchange 2010 and Domain controller in same machine. But you may try to bring a seperate Vm for W2K8 Domain controller.

 Please read the following articles before you deploy.

 Ref to:
 Exchange 2010 Prerequisites, System Requirements & Recommendation
 http://msexchangehelp.wordpress.com/2010/02/08/exchange-2010-prerequisites-system-requirements-recommendation/

 Exchange 2010 System Requirements - Hardware Virtualization
 http://technet.microsoft.com/en-us/library/aa996719.aspx Navigate to Hardware Virtualization


 Mailbox Server Storage Design
 http://technet.microsoft.com/en-us/library/dd346703.aspx


 All the Best :)

Sathish Kumar Elango | MCSE 2003 & MCSA Messaging | http://msexchangehelp.wordpress.com

--
That's all folks

No comments:

Post a Comment