This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi team,
Got alert message from SCOM, telling:
Alert: Exchange Health Set
Source: MYSERVER - HubTransport
Path: MYSERVER; MYSERVER
Last modified by: System
Last modified time: 12/22/2020 5:08:57 PM Alert description: The total number of messages rejected due to shadow failure over the last 60 minutes exceeds 200
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'MYSERVER' -HealthSet 'HubTransport'
When I run this command in Exchange Management shell, I get:
[PS] C:\WINDOWS\system32>Get-ServerHealth -Identity 'MYSERVER' -HealthSet 'HubTransport' | select name, alertvalue
Name AlertValue
---- ----------
**Messages.failed.to.be.made.redundant.Monitor Unhealthy**
Guys, instructions here:
https://learn.microsoft.com/en-us/exchange/management/health/troubleshooting-hubtransport-health-set?redirectedfrom=MSDN
says, that I have to rerun Probe. But there is no Probe for this Monitor.
(none (notification or check) - HubTransport - Messages.failed.to.be.made.redundant.Monitor)
Please assist, how to fix this Critical alert.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 69%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAD%3C/text%3E%3C/svg%3E)
I get the same error, we do have multiple exchange in the environment and not sure why this is unhealthy. Can anyone help me with its probe to invoke ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
This alert may have something to do with shadow redundancy,which only works in an environment with multiple Exchange servers.
Do you have other Exchange servers in your environment?
If you just have one server and currently no user is having problems with mail flow, you can safely ignore the alert or you can disable the shadow redundancy feature on the server via the following command:
Set-Transportconfig -ShadowRedundancyEnabled $false
Here is a similar thread for your reference: Messages Rejected Due to Shadow Failure
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi,
Do suggestions above help? If you have any questions or needed further help on this issue, please feel free to post back.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi KaelYao,
Thanks for your support.
We have 1 standalone exchange 2016 server and 'ShadowRedundancyEnabled' = True.
Does it mean it can stay as is or preferable to Disable it?
Why I ask - we found from our end users, that on that day, when SCOM reported alarms, our end users were sending mass Christmas Wishes to our clients - more than 10K emails, actually, via Mail Merge function in Word. (sending mass emails in batch, where one batch = 200 outgoing emails). Every email was ~ 0,6MB big and we think, this was a root cause.
When mass mail sending was ended, SCOM did not report anymore problems.
Hi,
Does it mean it can stay as is or preferable to Disable it?
You can safely disable it as actually this feature doesn't work in a single exchange server environment.
While leaving it enabled may also be fine,but sometimes you may get some warnings or alerts like in this post.
When mass mail sending was ended, SCOM did not report anymore problems.
Shadow redundancy creates message copies to prevent potential message loss during the mail flow.
It may reject messages and put messages in the queue waiting to be sent if it can't create shadows copies for these messages.
In your case,since a large amount of messages were sent through the server, shadow redundancy wasn't able to create copies in time.
Thus it generates this warning.