• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 184
  • Last Modified:

Exchange 2013 Virtualization


I am going to be be running Exchange 2013 on VMware and am looking to run my setup passed others who have done the same to make sure I'm not missing anything in doing it. This will be hosted on local storage with other VM's in one big RAID10 array.

Thick Provisioned VMDK for OS
Thick Provisioned VMDK for Database
Thick Provisioned VMDK for Logs

As well as reserve all the guest memory for the VM so it is always available. Format the Database and Logs VMDK disks with 64k allocation size.

I just am not sure if each disk should be on a seperate controller in VMware, or share the controller. Some use the paravirtual controller, and some use the LSI Logic default controller. This isn't for a large amount of users, around 100-125.
1 Solution
Nick RhodeIT DirectorCommented:
For mine I had technically 2 separate connections (2 Datastore LUNS) connected to the host.  I had 1 vmdk for the OS and a 2nd vmdk for the database and logs.  It is not actually necessary and more preventative if anything to separate the database and logs onto a different drive, this way if the logs build up to fill the vmdk it wont crash the server and the server is still accessible to resolve the issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now