In Alwayson, last commit LSN vs last hardened LSN

Chirag Sachdeva 281 Reputation points

In 3 node Alwayson,

no of records are same at primary and both secondarys the sides but last commit LSN and Last hardened LSN values does not match in dashboard, though other columns end of log lsn, last sent lsn and last redone lsn are all matching. Kindly help on this.



SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
11,587 questions
0 comments No comments
{count} votes

Accepted answer
  1. AmeliaGu-MSFT 13,936 Reputation points Microsoft Vendor

    Hi ChiragSachdeva-6150,

    The values of the last_hardened_lsn column is not actual log sequence numbers (LSNs). last_hardened_lsn is flush LSNs and indicates the start of the next block past the blocks that are already on disk. So any LSN < the value of last_hardened_lsn is on disk. LSN that are >= to this value are not flushed. Please refer to this doc which might be helpful.
    And your Alwayson group looks healthy. Please don’t worry.

    Best Regards,

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

0 additional answers

Sort by: Most helpful