Exchange 2016 Shadow Redundancy

I'm thinking of disabling shadow redundancy on Exchange 2016. I'm curious has one here permanently disabled it and were there any problems as a result. I understand its HA for message delivery but its gets really annoying with messages in the message queue. They are not there for days or anything, but annoying seeing them. Curious about anyone who has disabled it, good or bad.

Also i will be migrating alot of mailboxes from Exchange 2010 to Exchange 2016, and I have enabled circular logging but wondering if shadow redundancy should be disabled for this move. I would like to leave shadow disabled though. Let me know your opinions.
LVL 14
timgreen7077Exchange EngineerAsked:
Who is Participating?
 
RoninConnect With a Mentor Commented:
In a sense what you trying to do, for me sounds like: "I don't need brake pedal, I never go fast."
You have read the documentation, probably both for Exchange 2010 as well as for Exchange 2016, you know all the reasons Microsoft created this and recommends leaving it alone. They probably had enough cases with critical email gone that pushed them to created such redundancy, for me it's only natural and appropriate to have additional safety mechanism for message delivery until it hits the destination. They also created safety net, which you probably should also read about.

Note, to the best of my knowledge no other email server on the planet have those safeguards.

As for coexistence between 2010 and 2016 there's a specific approach how correctly to make it work.

To me, I honestly don't see a reason why make things complex more than it supposed to be.

Good luck.
0
 
RoninCommented:
You should not be changing this behavior and disabling shadow redundancy. It is there for a reason. Shadow redundancy is not utilized during mailbox moves as well it shouldn't be disabled.
0
 
timgreen7077Exchange EngineerAuthor Commented:
Thanks for the info about it not being used during a migration. the reason I want to disable it is because it always seems that the queues have are full of shadow redundancy queues. when i say full I don't mean excessive but it just seems to never completely clear. is there a good reason not to disable it. MS provided the option to disable so it should be fine. what are your thoughts other than this is default actions.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
RoninCommented:
What you described is a normal and expected behavior, this is not something that you need to touch and alter. If there's emails in the queue is because emails flow through your environment, that's by design.
0
 
timgreen7077Exchange EngineerAuthor Commented:
Agreed but is there really a good reason to make a shadow copy of every email that comes and then based on each hop in the environment?
0
 
timgreen7077Exchange EngineerAuthor Commented:
we also have exchange 2010 and about 98% of our mail goes through exchange 2010 and the queues are always at 0 and shadow redundancy is also enabled on our 2010 environment. there are only about 8 users on exchange 2016 and they all have host files since we haven't changed internal DNS to all 2016 to proxy to 2010. you would think most mail goes through 2016 since there is always something in the shadow redundancy queue. it just seems really really strange.
0
 
timgreen7077Exchange EngineerAuthor Commented:
Thanks for taking the time responding buddy.
0
 
RoninCommented:
All the best, I would gladly assist you with any other questions if needed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.