I just observed this on SQL Server 2008R2. I don't have a pair of newer servers to test whether this also happens on later versions, so if someone could check it on 2012 or 2014 so that would be appreciated.
Steps to reproduce:
On ServerB:
- create a database called 'example_db'
On ServerA:
- create a database called 'example_db'
- set up log shipping from this database to server B, with a secondary database name of 'logship_target_example_db'
So, we now have:
ServerA.example_db -> log ships to ServerB.logship_target_example_db
ServerB.example_db -> is a local database on ServerB, completely independent of ServerA.example_db
Run a few iterations of the log shipping jobs, then in SSMS right-click ServerB.example_db and go to Properties.
"Last Database Log Backup" shows as the time the log shipping job last ran, even though ServerB.example_db has nothing to do with the log shipping configuration and has never had its log backed up.
Right-clicking ServerB.logship_target_example_db shows "Last Database Log Backup: None".
(If the above steps don't reproduce the issue, it may be necessary to first set up log shipping with ServerB.example_db as the target name, then delete that log shipping configuration, then delete ServerB.example_db, then follow the above instructions.)
Edit:
I have confirmed through experimentation that only the backup history is ending up with the wrong database: log shipping restores do go to ServerB.logship_target_example_db; that is, SQL server is not trying to replay ServerA.example_db's logs onto ServerB.example_db -- so this bug might be harmless, but I don't know what the implications are of having the wrong backup history associated with a database.