I have tried the Veeam KB http://www.veeam.com/kb1744 no luck still 1 out of 8 for that site failed over.
Tweaked DAG Settings as recommended (this helped by keeping 1 or 2 databases others failed over)
- cluster /prop SameSubnetDelay=2000:DWORD (Default: 1000)
- cluster /prop CrossSubnetDelay=4000:DWORD (Default: 1000)
- cluster /prop CrossSubnetThreshold=10:DWORD (Default: 5)
- cluster /prop SameSubnetThreshold=10:DWORD (Default: 5)
From PowerShell as Admin:
. 'C:\Program Files\Microsoft\Exchange Server\V15\Scripts\RedistributeActiveDatabases.ps1' 'YOUR-DAG-NAME-HERE' -BalanceDbsByActivationPreference -Confirm:$false
Or Script it in Task Scheduler
Program/script: powershell
Add arguments: -command "& 'C:\Program Files\Microsoft\Exchange Server\V15\Scripts\RedistributeActiveDatabases.ps1' 'YOUR-DAG-NAME-HERE' -BalanceDbsByActivationPreference -Confirm:$false"
NOTE: Run this a few hours after the backup, because when the DAG will fail the Content Index State will go to FailedAndSuspended then followed by Seeding state. After it has returned to Healthy then the script will run without errors. So run this before business hours start or middle of the night after the Index state state has returned to healthy. You can write another PS to query the state once all DAGs are healthy then balance them out.
Hope this will help someone if it does +1 or send a comment.
Cheers,
Jakub