Always On synchronous commit Partially_Healthy

Question

Always On synchronous commit Partially_Healthy

Marcia Q

SSCrazy

Points: 2648
More actions
July 24, 2018 at 9:01 am

#358851

I'm new to always on, so any help would be appreciated.
One of our AlwaysOn availability groups contains one database, and its health status is partially_healthy. The database on the primary says synchronized while the secondary says synchronizing. All of the other availability groups on our cluster have a healthy status.
I have checked both the aoag setup on primary and the secondary, and they are both set to synchronous commit. There isn't any activity on this database, so it should be synchronized by now. This is our testing server, so I haven't looked anything for a while, so I don't know how long this has been out of sync.
I'm not sure how to get this back to a healthy state. Any suggestions?

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

SQL learner22 Default port Points: 1487 More actions · Answer 1

primary synchronized while the secondary says synchronizing may be the right status for something that keep moving any new logs cross to the secondary. b<a| b is always less than a for normal condition.

Marcia Q SSCrazy Points: 2648 More actions · Answer 2

I need to patch the server, so I need all availability groups in a healthy status. All of the other AOAG's on the primary and secondary are in a healthy status. I don't think partially_healthy is normal in this case.

Beatrix Kiddo SSC-Dedicated Points: 32407 More actions · Answer 3

Is it still showing as partially healthy? I'm finding it hard to know what to suggest without being able to poke around and look at everything. Can you post an obfuscated screenshot of the AG properties maybe? (Once I saw this happen when the synchronisation state was for some reason set to synchronous on one replica but asynchronous on the other).

Marcia Q SSCrazy Points: 2648 More actions · Answer 4

Yes, it's still showing partially_healthy. I had already read where someone's primary and secondary had different synchronization modes, and I checked that. They are both the same.
We've made this a lower priority, so I probably won't start looking at this for a few more days. If I find anything further, I will post it. If I don't find a solution, I will probably restore the database since it's our testing server.