Hi VMware Experts,
I have to provision a new VM for running CallXpress service on a virtualised environment.
This is the first time I am trying to install CallXpress server on a VM.
I have found out we can run the server on a windows server 2012 R2 environment.
These are the basic requirements
1)The new VM should have at least two data drives C:\ and D:\.
2)It should have min 4GB of memory.
3)It should have NIC.
2)It should have the ability for vMotion, HA, Flash read cache and dynamic resource allocation.
We already have a server 2012 R2 template which have 60GB C:\ partition with 4GB memory which I can use to deploy the c:\ drive,but how do I create a D:\ partition?
What is the advantages and disadvantages of creating the C:\ and D:\ partition in the same LUN of SAN?
What I was planning for this project is to deploy the VM from the existing template and then just before finishing the creation, customize it by adding another one more vDisk and use a different LUN for the D:\ drive vmdk file than using the same LUN used for creating the system files,so that in the future if I need to expand the d:\ drive I can expand in a fly without affecting the c:\ drive datastore.I am not sure that is the best practice for Compellent FC SAN.
Also How do I achieve the high Availability and vMotion side of things to work once I have created the VM?
I have read that adding the VM to a Host Cluster will achieve the HA,FT and vMotion, but not sure that will achieve all I want by just adding into the host cluster,what else I have to do to achieve that on a FC SAN environment?
any help/suggestions would be appreciated,
thanks in advance
You don't usually assign LUNS directly to windows drives.
What you do instead is create VMware datastores, and the LUNS map to the datastores.
Each VM (which basically they are hosted on a folder kept on a datastore), is stored in the datastores, and can be moved (migrated) between different datastores.
You can add as many drives as you want to your VM, and they will be stored as different files inside the VM folder.
Said this, if you really want to map LUNs directly to a windows host, you can use what is called RDM drives or Raw Device Mappings. But if you want to use VMware HA capabilities, it's best no to use them.
You can expand a virtual drive whenever you want, it's the OS the one that has the problem to expand, some support it on the fly, and others need a power cycle.
And you can have HA, as long as you have a VMware ESXi cluster, once you move the VM to the cluster, then you can change it's HA priorities to handle different scenarios.
FT or Fault Tolerance is not as simple as HA, so if you need this you will need to look at it more carefully. But for most cases HA is good enough.