Answered by:
SCOM 2007 / ADMP : Collecting Replication Performance Data: how many DCs?

Question
-
Hello,
The ADMP documentation says " . Replication monitoring performance collection is not enabled by default because the performance reduction can be significant if replication data is collected automatically for every domain controller"
If I wanted to monitor replication on 300+ DCs, what would be the limiting factors? DB size? scom server perf?
What are my options, apart Ultrasound? (mix environment 2003/2003R2/2008)
Thanks
Martin
Tuesday, May 17, 2011 3:29 PM
Answers
-
It is first important to think what you want to have and what added value it will have for you. Especially in large environments you want to be carefull with adding many counters if you dont need them. You might not be interested to know how long a replication took from every one of the servers to every other server. More important is t see that replication is happening. I think when adding only a few counters the performance hit on the scom side of things will not be too big. So adding another monitoring tool to the mix will not make it better (perhaps worse actually).
Bob Cornelissen - BICTT (My BICTT Blog)- Marked as answer by Vivian Xing Wednesday, May 25, 2011 9:16 AM
Wednesday, May 18, 2011 6:12 AM -
I also would like to share the following information:
SCOM 2007 – AD MP – Reasons why Replication Latency Performance won’t show up:
Active Directory Management Pack - Replication Monitoring Account Permissions:
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by Vivian Xing Wednesday, May 25, 2011 9:16 AM
Wednesday, May 18, 2011 6:24 AM
All replies
-
you are monitoring the replication by default. You just aren't collecting perf data for reporting.
So what do you want to know?
Rob Korving
http://jama00.wordpress.com/Tuesday, May 17, 2011 4:08 PM -
It is first important to think what you want to have and what added value it will have for you. Especially in large environments you want to be carefull with adding many counters if you dont need them. You might not be interested to know how long a replication took from every one of the servers to every other server. More important is t see that replication is happening. I think when adding only a few counters the performance hit on the scom side of things will not be too big. So adding another monitoring tool to the mix will not make it better (perhaps worse actually).
Bob Cornelissen - BICTT (My BICTT Blog)- Marked as answer by Vivian Xing Wednesday, May 25, 2011 9:16 AM
Wednesday, May 18, 2011 6:12 AM -
I also would like to share the following information:
SCOM 2007 – AD MP – Reasons why Replication Latency Performance won’t show up:
Active Directory Management Pack - Replication Monitoring Account Permissions:
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by Vivian Xing Wednesday, May 25, 2011 9:16 AM
Wednesday, May 18, 2011 6:24 AM