btanguay wrote:Hi jromalino,
Did you get any update on your MS ticket or veeam support case. i've just upgrade to v9 yesterday and got the error two time in a row.
Any update on that issue from Veeam? I've got some 2010 and 2013 mailbox server and this only happen in the 2013 active server mailbox.
Everything tested from a Microsoft standpoint worked as expected. They have since closed the case. I really don't think it's a Microsoft problem as I am not having any Exchange issues and this problem didn't start until I upgraded to V9. Never had the problem with V8.
No luck with Veeam support. They escalated the case to tier 2 support but still don't have a resolution. I get the impression they don't know what it is. I've been through at least 4 or 5 remote support sessions only to watch them poke around looking at logs. The last thing they had me do was run a chkdsk /f on all the volumes and sfc /scannow. Everything came up clean and caused me a lot of extra Exchange maintenance due to the need to remove the server from the DAG before running the commands. Needless to say, I am very frustrated with the situation. I have even tried extending the DAG heartbeat as indicated but it did not make a difference.