VMWare Archtect Bootcamp is held from 22-24 July in Carlton. Just take this chance to recall the tips & tricks for E2K10 on ESXC4.1 even it has been up & running since Apr 2013
- PAU size for Mailbox servers – When formatting the volumes to host Exchange databases, it is recommended the use of a NTFS allocation unit size of 64KB & NOT do quick formatting. The recommendation of 64KB is based on the performance improvements seen with large sequential read operations, such as streaming backup and some eseutil tasks
- Disk defragmentation is supported, but not required nor recommended for Mailbox servers
- Hyperthreading should be disabled by default for production Exchange servers and only enabled if absolutely necessary as a temporary measure to increase CPU capacity until additional hardware can be obtained.
- The total number of vCPUs should be equal to or less than the total number of cores on the ESXi host machine.
- Do not over-commit memory on ESXi hosts running Exchange workloads and set the memory reservation to the configured size of the VM
- Do not disable the balloon driver. This is default.
- Exchange is not NUMA aware so keep VM size less than NUMA node size
- Use multiple vSCSI adaptors and distribute the mailbox/log load across them. [Jonson] need to follow up this
- For DAG cross-WAN, set the clusterheartbeat to 2000ms, up from 1000ms default .
- Turn off DRS or vMotion for DAG – to modify the VM’s settings to prevent it.
VMFS or RDM for mailbox DB ?
It is advised to go for VMFS unless you depend on some SAN technology for E2K10, or plan to revert from VM to PM.
For Netbackup API, Is it possible only snapshot to protect DAG OS instead of all VM if the DB is converted to VMFS?