Log shipping monitor primary not seeing recent backups, warnings triggered in error I am receiving the Log shipping Primary Server Alert warning in error

In msdb.dbo.log_shipping_monitor_primary the last backup time is 1215 however on that machine there are .trn files that have been created since

In msdb.dbo.log_shipping_monitor_secondary the destination is updating as I'd expect it to

So the .trn files are being created correctly, transferred correctly, and saved correctly, however SSMS appears to be unaware of this hence the warnings that are being triggered in error

Any ideas on why this might be happening? I set up TLS around 3 months ago and apart from a few little problems it's worked fine, this has only occurred today

edit: Rather than the full output as there are a lot of databases being backed up, I've added below the relevant mismatch, please excuse my formatting I'm not sure exactly how to neaten this up

msdb.dbo.log_shipping_monitor_primary

primary_server  primary_database    backup_threshold threshold_alert    threshold_alert_enabled last_backup_file                        last_backup_date        last_backup_date_utc    history_retention_period
DREAM           ACCDRE              60               14420              1                       e:\tlshipping\ACCDRE_20170209121501.trn 2017-02-09 12:15:02.010 2017-02-09 12:15:02.003 5760


msdb.dbo.log_shipping_monitor_secondary

secondary_server secondary_database primary_server  primary_database    restore_threshold   threshold_alert threshold_alert_enabled last_copied_file                                last_copied_date        last_copied_date_utc    last_restored_file                              last_restored_date      last_restored_date_utc  last_restored_latency   history_retention_period
WHSQLDR          ACCDRE             DREAM           ACCDRE              45                  14420           1                       E:\DreamLogShipping\ACCDRE_20170209163001.trn   2017-02-09 16:32:02.397 2017-02-09 16:32:02.397 E:\DreamLogShipping\ACCDRE_20170209163001.trn   2017-02-09 16:34:11.477 2017-02-09 16:34:11.477 4                       5760
You are correct the last backup time is showing 2017-02-09 12:15:02.010 while last copied and restored are much greater 2017-02-09 16:32:02.397 and 2017-02-09 16:34:11.477. So I believe somehow the catalog is not getting updated. There can be two reasons:


This can be a bug make sure  SQL Server 2008 R2 is patched to SP3
There was old logshipping which was configured and was not removed correctly and completely.


I believe the solution here would be to drop and recreate log shipping.