Consider the following scenario:
- You use the AlwaysOn availability groups feature in Microsoft SQL Server 2012, 2014, or 2016.
- You back up a transaction log of a database while there are transaction log activities.
- The transaction log activities stop after the backup completed.
- You remove the database from the AlwaysOn availability group.
To work around this issue, create a transaction log backup on the primary replica, restore the log backup on the secondary replica with no recovery, and then rejoin the secondary replica to the AlwaysOn availability group.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.