With that log backup frequency, you have a data loss of up to 10 minutes, depending on the type of failure of the primary.
If the primary fails entirely and you cannot get to the transaction log of the database, then the best you can do is to restore the last log backup that you have on the secondary and bring it online.
If you can get to the transaction log of the primary database, then you can take a tail-log backup, restore that on the secondary after all other log backups and that will bring it online with 0 data loss.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass