I am facing below issues while working with High Availability Group

* While executing PowerShell script as described in below link, getting error

    https://msdn.microsoft.com/en-us/library/hh213078.aspx

System.Data.SqlClient.SqlError: The log in this backup set begins at LSN Which is too recent to apply to the database.

* So i skipped log restoration on seondary server and only restored database, it worked but

          * Now database in Availability Group showing warning sign

           * In Primary server, database is showing Synchronized state and but in Secondary server it is not showing any state, Warning sign may be because of that, but i don't have any idea

It would be great if i can get some clue to get resolution for this issue.

Hello Manish,

The error you got was due to mismatch/lack of a transaction log. The state that you have the database on your secodnary at this point cannot be added to the availability group, so the best thing you can do is to initialize the database from scratch (on the secondary) - you can use again the Powershell from your link (the one that is createing FULL and TLOG backup) or you can use Management studio for the same. Just be carefull that you do not have any other transaction log backups running while you are initializing (probably you have automated backup solution that is creating TLOG backups).