|
DBADave
Constraint Violating Yak Guru
USA
366 Posts |
Posted - 04/16/2004 : 09:57:12
|
I'm trying to determine why occassionaly we receive errors during daily restores indicating earlier log backups exist. Can someone help me understand First_LSN, Last_LSN and Database_Backup_LSN in msdb..backupset? I realize they are pointers to the starting and ending addresses of data contained for a particular backup, but I'm having trouble tracing this information in msdb..backupset.
backup_start_date first_lsn last_lsn database_backup_lsn -------------------- --------------------------- --------------------------- --------------------------- Apr 15 2004 4:05PM 3193000001516800001 3193000001643400001 3184000002632600006 Apr 15 2004 7:01PM 3193000001516800001 3193000001684500001 3184000002632600006 Apr 15 2004 11:17PM 3193000001643400001 3215000001783700001 3193000001682900006 Apr 16 2004 6:05AM 3215000001783700001 3215000001991300001 3193000001682900006
I expected to see the First LSN of a T-Log dump to be identical to the last LSN of the previous T-Log dump or DB Backup. In the example above, all entries pertain to T-Log dumps except 7:01PM, which is a database backup.
The 4:05PM T-Log backup has the same First_LSN as the 7:01PM DB Backup. Why? The 11:17PM T-Log backup has the same First_LSN as the 4:05PM T-Log backup's Last_LSN. I expected it to match the Last_LSN of the 7:01PM DB Backup. Doesn't the DB backup essentially reset the pointers so any T-Log backup that follows should reference it's Last_LSN? What is database_backup_lsn?
Thanks, Dave |
Edited by - DBADave on 04/16/2004 09:58:11
|
|