May 24, 2021 at 6:49 pm
We recently deployed a AOG for our critical databases. 3 databases were added to the availability group, and two of those were seeded properly to to the secondary replica. The third however failed. The primary replica shows all three databases as synchronized, and availability databases is all green. On the secondary replica server, only two of the databases appear synchronized, and the availability databases has all three, but one has a yellow "bang" on it. Right clicking on it gives the option to "Join to Availability Group", but it fails. Is there a way to reseed the database without removing the database from the group on the primary replica?
May 25, 2021 at 7:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply