Hi everyone
This is just to let you know if you are having troubles with backing up Exchange 2013 DAG.
My backups were running great until the exchange team applied CU11, then all jobs failed.
Microsoft changed a basic function within exchange which caused all DAG backups to fail.
I found the solution for CU11 only to be shoot in the foot by that solution in Excange CU14.
Cause: "Exchange 2013 CU11 and 2016 CU1 introduces a new functionality called mailbox anchoring: Instead of connecting locally, Exchange Management Shell session will now be proxied to the server where the user’s mailbox is located. If the user does not have a mailbox, an arbritration mailbox is used instead and the session will be proxied to the server where that arbitration mailbox is located. This new behavior may cause backup to fail, since part of the process involves querying Exchange topology using PowerShell."
Solution:
Repeat the following procedure on all Exchange mailbox servers:
Launch Registry Editor (regedit).
Browse to HKEY_LOCAL_MACHINE > SOFTWARE > NetBackup > BEDS > Engine > Exchange.
On the right hand pane, create a new DWORD (32-bit) value. For the name, type: PowerShellOptions, and hit Enter.
Double click PowerShellOptions and enter 1 as the value data. Hit Enter again to save.
Setting PowerShellOptions to 1 forces monad (the NetBackup process responsible for running PowerShell queries) to connect to local Exchange Management Shell session, thereby bypassing the need to interact with mailbox anchoring.
Exchange 2013 Cumulative Update 12 reverses the Mailbox Anchoring changes which were introduced in Exchange 2013 CU11. The CU11 solution above was not removed and backups were successfull.
Exchange CU13, backups are still ok.
Exchange CU14, backups fail. You have to remove the registry settings from the CU11 solution on all Exchange nodes before backups function are successfull again.
Microsoft sure keeps me busy :)
