Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

AlwaysOn AG-sys.dm_hadr_database_replica_states last set lsn and last received lsn is different

$
0
0

Hi 

We have always on production 2016.SP2 Enterprise version.

I have notice  through dynamic view sys.dm_hadr_database_replica_states last set lsn and last received lsn is different( only on database Id  5). But looks like all healthy. I am not sure why this appearing. . Is there any way to force(commit/checkpoint on primary site) and allow to send logs  to secondary site then the LSN number to be matched in both sides? any expert idea. Thank you very much 

select database_id,replica_id,synchronization_state_desc,last_sent_lsn,last_sent_time,last_received_lsn,last_received_time,end_of_log_lsn,last_commit_lsn from sys.dm_hadr_database_replica_states

Checked in 10.05am today:  Last pictures shows that last harden time ,last redone time  in secondary as 2020-06-19 10:01:00.937. But primary site remain 05.02am this morning 


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>