Comments on: Using Test-ReplicationHealth to Troubleshoot Database Availability Groups https://practical365.com/exchange-2013-test-replicationhealth/ Practical Office 365 News, Tips, and Tutorials Tue, 15 Mar 2022 06:32:32 +0000 hourly 1 https://wordpress.org/?v=6.3.2 By: Angga https://practical365.com/exchange-2013-test-replicationhealth/#comment-237994 Tue, 15 Mar 2022 06:32:32 +0000 https://www.practical365.com/?p=6682#comment-237994 In reply to Paul Cunningham.

How about the “Database Availability Group Member Health” column like:
Cluster Service
Replay Service
Active Manager
Tasks RPC Listener
TCP Listener
Server Locator Service
DAG Members Up
Cluster Network Quorum Group
File Share Quorum
Database Redundancy
Database Availability
DB Copy Suspended
DB Copy Filed
DB Initializing
DB Disconnected
DB Log Copy Keeping Up
DB Log Replay Keeping Up
the result is n/a, even though when I check manually passed

]]>
By: Salim https://practical365.com/exchange-2013-test-replicationhealth/#comment-154599 Wed, 04 Oct 2017 13:10:28 +0000 https://www.practical365.com/?p=6682#comment-154599 HI Paul,

I hope you’ll find time to response for my request.
I’ve a reccurent error under exchange 2013 : “OUTLOOK.PROTOCOL UNHEALTHY”.
I made many research with no success to find an issue with.

I hope you’ll have ones

Brgds

]]>
By: Nien https://practical365.com/exchange-2013-test-replicationhealth/#comment-119710 Mon, 24 Jul 2017 01:57:39 +0000 https://www.practical365.com/?p=6682#comment-119710 Hi Paul, Thank you for the time you take to write these articles. Not only are they clear, but also help with getting a better understanding of the PowerShell cmdlets.
Nien.

]]>
By: Paul Cunningham https://practical365.com/exchange-2013-test-replicationhealth/#comment-23849 Fri, 21 Oct 2016 11:11:03 +0000 https://www.practical365.com/?p=6682#comment-23849 In reply to Simon Craner.

Sending any PowerShell output as an email is pretty simple really.

https://www.practical365.com/powershell-how-to-send-email/

Or use my Test-ExchangeServerHealth.ps1 script.

]]>
By: Simon Craner https://practical365.com/exchange-2013-test-replicationhealth/#comment-23848 Fri, 21 Oct 2016 10:26:04 +0000 https://www.practical365.com/?p=6682#comment-23848 Hi Paul,

thanks once again for excellent work. Just like the test-exchangehealth script, I would like to have this output to an email that my team could get say twice a day, i.e. at the typical working start time of the day and before we go home for the day.
Any assistance to help generate it will be greatly appreciated.

]]>
By: Paul Cunningham https://practical365.com/exchange-2013-test-replicationhealth/#comment-23847 Wed, 27 Jul 2016 23:06:23 +0000 https://www.practical365.com/?p=6682#comment-23847 In reply to Miko Tupaz.

I don’t. Try a wireshark trace?

]]>
By: Miko Tupaz https://practical365.com/exchange-2013-test-replicationhealth/#comment-23846 Wed, 27 Jul 2016 00:59:41 +0000 https://www.practical365.com/?p=6682#comment-23846 Hi Paul,
Would you happen to have the firewall ports required for this to work? We have an exchange site behind a firewall and not getting any results when I run this test.

]]>
By: Turning to a PAL when troubleshooting Exchange… | https://practical365.com/exchange-2013-test-replicationhealth/#comment-23845 Tue, 21 Jul 2015 11:01:33 +0000 https://www.practical365.com/?p=6682#comment-23845 […] <a href="https://technet.microsoft.com/en-us/library/bb691314(v=exchg.150).aspx">Test-ReplicationHealth</a> is a useful cmdlet to know (MVP Paul Cunningham has a post about it too). […]

]]>
By: Get your brand featured on snapback shouts https://practical365.com/exchange-2013-test-replicationhealth/#comment-23844 Sat, 10 May 2014 20:21:40 +0000 https://www.practical365.com/?p=6682#comment-23844 Get your brand featured on snapback shouts

Testing Exchange 2013 DAG Members with Test-ReplicationHealth

]]>
By: Paul Cunningham https://practical365.com/exchange-2013-test-replicationhealth/#comment-23843 Wed, 12 Feb 2014 23:44:36 +0000 https://www.practical365.com/?p=6682#comment-23843 In reply to Ryan.

I suppose that would make sense that running from a down level server might throw some odd results for higher SP level servers. Though I’ve never run into that issue myself, because I generally run monitoring scripts from the highest version/SP level in the org.

]]>