I have a powershell script that is restoring from production into a test availability group database. It
My issue is that there's a fork point being created when I take the log backup which gives me an error when restoring on the secondary. It makes no sense because the log backup doesn't start until after the full has been taken.
Here is the error:
The log in this backup set terminates at LSN 67867000000017200001, which is too early to apply to the database. A more recent log backup that includes LSN 67869000007776500001 can be restored.
Here is the output from the backupset:
and here is the info about the last restore:
My eyes are crossing looking at this, and it's probably something simple. Ideas?