One of the first things you will configure in vCenter Server is
Start the vSphere client and connect to the vCenter Server.
Once connected right click the vCenter server hostname in the inventory,
Click "New Datacenter".
Give the Datacenter a name that describes its location.
Right click the datacenter and click "New Cluster".
Firstly give the cluster a sensible name. This could describe the processor type, the rack that the cluster of servers will be in, its use etc.
Select "Turn on VMware HA"
Select "Turn on VMware DRS"
VMware DRS will be discussed in more detail in another article.
To setup a fully automated DRS cluster choose "Fully automated" and a desired migration threshold.
VMware DRS Power Management will be discussed in more detail in another article.
Choose "Off" and Click Next.
VMware HA will be discussed in more detail in another article.
Select "Enable Host Monitoring".
Choose to prevent or allow VMs from being powered on if it violates availability constraints in a failure.
Choose an admission control policy if preventing VMs from being powered in when resources are constrained.
Choose default a restart priority (Medium in most if not all cases).
Choose a host isolation response (Shut down being the most graceful but slowest).
Choose to enable VM monitoring via VMware Tools.
Select the sensitivity for monitoring.
Chose "Disable EVC".
For the swapfile policy choose "Store the swapfile in the same directory as the virtual machine" (This will speed up VMotion).
Review the Cluster configuration.
The HA DRS cluster is created.
Right click the cluster and select "Add Host...".
Enter the hostname of the ESX/ESXi Server host.
Enter a username for the host (root).
Enter a password for the host.
Review the host details and a list of virtual machines currently running on the host (if any).
Choose where to put any existing virtual machines on the host. Either:
In the root resource pool.
A new resource pool named after the host.
Review the actions and click Finish.
The ESX/ESXi host is added to the HA DRS Cluster including any existing virtual machines.
Share this blog post on social media:Tweet
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.