2016 – Search Topology – too many databases and one corrupt

Our organization was having an issue with our Search Service App on our SharePoint 2016 On-Prem environment. Once we got it working properly, we noticed that there were 3 sets of topology component databases than our expected two. Then, one of our CrawlDBs became suspect. Any recommendations on how to move forward? It would make sense to me to transfer the current topology component databases to the orphan ones and then remove the corrupt, but I don’t know if this is best practice. Much appreciated.