And apparently it was not a good option. I think you need to drop the AG entirely. This may a situation that AGs in SQL 2012 was not designed for. (Recall that SQL 2012 was the first version to sport AGs at all.)
Log_reuse_wait_desc = AVAILABILITY_REPLICA but there is no secondary replica
SQL version = 2012 (yeah it's older than the hills but I still have to support it)
I have an AG (availability group) with only one replica - the primary (obviously). There is no secondary replica to be sending log data to, however 4 out of 19 database replicas are showing AVAILABILITY_REPLICA in the log_reuse_wait_desc column of sys.databases. How is that possible?
Why is there only one replica in the AG you ask? The secondary was a DR server in the DR data center which is in the process of being physically relocated to another region. Prior to the DR server being shut down, I removed the replica from the AG to prevent log files from growing out of control on the primary replica. The secondary will be down for over a week and there's not enough space on the primary to retain logs for that long. Apart from removing the AG entirely it was the only option.