I recently migrated a database from a SQL 2008 R2 RTM instance to a separate SQL 2008 R2 SP2 instance by backing up the database and restoring it on the new instance. I noticed that my differential and log backup jobs are successfully backing up this database even though a full backup has not been done on it.
The database properties show that a log backup has been done recently but shows "None" for last database backup. When I try to restore the database from 2012 SSMS, I get a message that a restore plan cannot be created because of a break in the LSN chain. In 2008 R2 SSMS, it does not show the error but it also does not display any backup sets as it normally would for a database that is properly backed up.
My question is, why am I not getting the error that would normally occur if you try to run a differential or log backup when a full backup doesn't exist? Has anyone else seen this?
I use Ola Hallengren's maintenance scripts for backups so I would normally expect the differential or log backup to fail in this situation and then the maintenance script would do a full backup instead. This is not occurring though since the
differential and log backups are successful.