The suggestions below are general advice intended to help alleviate and prevent issues. Every environment is different, and while these settings and suggestions may work in one environment, they may have little or no impact in others. Generally speaking stability issues which occur are often environmental, and will require investigation of all components involved, both physical and software.
The suggestions below include configuration changes to VMware as well as Microsoft Exchange. Veeam is not responsible for any issues incurred after making the suggested changes. You are advised to contact and review all setting changes with the respective product support organization.
cluster /propAdjust Microsoft settings for failover sensitivity (in bold, run from command line)
cluster /prop SameSubnetDelay=2000:DWORD ::(Default: 1000 in Server 2008 R2) cluster /prop CrossSubnetDelay=4000:DWORD ::(Default: 1000 in Server 2008 R2) cluster /prop CrossSubnetThreshold=10:DWORD ::(Default: 5 in Server 2008 R2) cluster /prop SameSubnetThreshold=10:DWORD ::(Default: 5 in Server 2008 R2)
Note: With Server 2012 or newer cluster.exe may not be available, as such you will need to install and use the PowerShell cmdlets. The cmdlets may need to be enabled using the following command:
Install-WindowsFeature -name RSAT-Clustering-CmdInterface
View cluster settings:
Get-cluster | fl *subnet* - provides current settings for timeout
Adjusting cluster settings:
(get-cluster).SameSubnetThreshold = 20 #(Default 10 in Windows 2012R2+) (get-cluster).SameSubnetDelay = 2000 #(Default 1000 in Windows 2012R2+) (get-cluster).CrossSubnetThreshold = 40 #(Default 20 in Windows 2012R2+) (get-cluster).CrossSubnetDelay = 4000 #(Default 1000 in Windows 2012R2+)