Sorry..last email on this I promise...is the setting you're talking about putting to "200" for the SCOM threshold or something we set on the retry queue?
From: Binner, Lori A [mailto:lbin...@jjkeller.com] Sent: Wednesday, October 24, 2012 9:02 AM To: MS-Exchange Admin Issues Subject: RE: Frequent SCOM error alert - problem or no? Thanks for all your explanations/details!!! I feel much better... time to move onward & begin moving more users over to the new servers! From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, October 24, 2012 8:50 AM To: MS-Exchange Admin Issues Subject: RE: Frequent SCOM error alert - problem or no? It is perfectly OK for emails to be sitting in the redundancy queues. And it may be more than one. :) Shadow redundancy is designed to ensure that there is no possibility of an email ever being lost. So, not only does it wait for delivery, it waits for log flushes, and then it waits for the next connection to the same SMTP server in order to empty the queue (at a 5000 foot view). From: Binner, Lori A [mailto:lbin...@jjkeller.com] Sent: Wednesday, October 24, 2012 9:41 AM To: MS-Exchange Admin Issues Subject: RE: Frequent SCOM error alert - problem or no? Thanks...yes I understand there are times where it could be a problem and that's what I'm trying to figure out. Because this is a brand new server I want to make sure things are functioning correctly before we move our users to it... As Jim said in his reply to me on this there will, of course be retrys at times for emails that have typos or something wrong with them so they sit in these queues longer. This makes sense, but wondering why there's always just "1" email always sitting in these retry queues of this new CAS/HUB/MBX server and also the fact I've noticed that sometimes the email is for myself and it's addressed properly and actually just sent from someone internally here...even though I see it sitting in the queue to me, I know I received the email 10 min ago already in my inbox. So, why do these sit in the queues so long and are these emails what's setting the SCOM alert (or possibly another email with an incorrect email address that I just am not able to see in the queues). I know...I should & I'm going to read up on these shadow redundancy type queues that are new to me (don't have them on my first brought up hub servers where this is the only role running on the box and I never see any emails sitting in the queues). If you guys tell me seeing these emails sitting in the queues regularly is normal, I'll be more at peace with it. :) From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, October 24, 2012 8:21 AM To: MS-Exchange Admin Issues Subject: RE: Frequent SCOM error alert - problem or no? I can't say that it wouldn't ever be a problem for any customer of any size. It wouldn't be prudent. :) For the situations I have investigated, with busy mail servers, the value of 30 is too small. If the alerts will just be "noise" to you - that is, that you will ignore them. In that case then you need to adjust the value. I think that 200 is a good value. From: Binner, Lori A [mailto:lbin...@jjkeller.com] Sent: Wednesday, October 24, 2012 9:03 AM To: MS-Exchange Admin Issues Subject: RE: Frequent SCOM error alert - problem or no? So, you're confirming, it sounds like this is not a problem, is normal?...and that there isn't some kind of delay in the message...we should increase the value so we don't get these alerts? That's what you seem to be saying...I just can't find much out there when I try to research this. The shadow redundancy queues are new to us since are original hub server was on it's own server. Thanks, Lori From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, October 23, 2012 5:34 PM To: MS-Exchange Admin Issues Subject: RE: Frequent SCOM error alert - problem or no? Increase the value in the rule. I've bumped it to 200 at several of my clients. From: Binner, Lori A [mailto:lbin...@jjkeller.com] Sent: Tuesday, October 23, 2012 3:24 PM To: MS-Exchange Admin Issues Subject: Frequent SCOM error alert - problem or no? Hello- We have recently set up 2 new Exchange 2010 sp1 r7 servers with the CAS/HUB/MBX roles on them. We are beginning to move mailboxes to them from our original Exchange 2010 sp1 r7 servers. Our original servers have only 1 Role per server (so the HUB is on it's own server on the original servers and nothing as far as a "Shadow Redunancy Queue" listed in the Queue Viewer). I'm not accustomed to the new "Shadow Redundancy" queues I now see on the new server's Queue Viewer. I'm noticing that there's always an email sitting in these redundancy queues but I believe the end user/recipient is getting the emails just fine delivered to them, but am curious why these emails seem to linger there for quite some time even after the user's already received it. It looks like when I "google" on this, it may be normal "For any message delivered to a mailbox database that's part of a DAG, the shadow copy for that message is retained in the transport dumpster until that message is replicated to all DAG members." Okay, but why then do we keep getting these SCOM errors (see below)? Alert: Retry Remote Delivery Queue Length - sustained for 30 minutes - Red(>1) - Hub Transport. Priority: 2 Severity: 2 Source: Queues - EXCHGSVR01 (Hub Transport) - Path: EXCHANGESVR01.xxxxx.local;EXCHANGESVR01 (Hub Transport) - Last modified by: System Last modified time: 10/22/2012 6:09:32 PM Alert description: TimeSampled: 2012-10-22T18:06:28.0000000-05:00 ObjectName: MSExchangeTransport Queues CounterName: Retry Remote Delivery Queue Length InstanceName: _total Value: 30 SampleValue: 3 Knowledge: http://go.microsoft.com/fwlink/?LinkID=67336&id=026E0E71-A5B3-4781-8FBA-E29D7FC4225D Computer: EXCHANGESVR01.xxxxxx.local Impacted Entities (3): Hub Transport Service - This electronic communication may contain confidential information. If you believe you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist This electronic communication may contain confidential information. If you believe you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist This electronic communication may contain confidential information. If you believe you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist This electronic communication may contain confidential information. If you believe you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist This electronic communication may contain confidential information. If you believe you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
