I'm having trouble finding the proper steps for what I would think would be a pretty routine task:
My SQL availability group secondary is no longer synching, and I need to get it working again without breaking my application.
(It has been broken for a while, so presumably this would be via a fresh backup of the primary restored to the secondary. This is SQL 2017, if that matters. All the other pre-reqs are already in place, since we've had this working before.)
All the references I can find either assume I'm starting completely from scratch (I already have an availability group listener with live applications using it) or are for unrelated tasks like restoring over the primary.
Other pages I've found say you have to remove then re-add the database to the availability group to get things re-initialized. I can do that if it's the only way, but that's definitely not preferred, since my applications are currently using the listener name.
What are the proper steps to get my secondary working properly again?