Exchange 2013 high availability best practices
Posted on 2015-01-23
I am currently running a windows server 2012 R2 with exchange 2013 SP1 CU5.
This is a virtual machine running on VMware.
I want to have high availability for this server in the future.
What are the best practices in the current situation?
Tthe server has DAS, database and transaction logs are still on the default location.
Since I have the possibility to use NAS iSCSI storage, is it advisable to use this instead of DAS? (whole VM on SAN or just the db?)
Or, keep the DAS, JOBD with 1 volume with multiple databases? (and logs on the same volume)
In the current situation I think one extra virtual exchange server and a witness server should be setup for the DAG?
On the vmware side, so I also need to configure things? (cluster Vmware, ...?)
Do you have other hints, tips, advise?