LiteSpeed allows backup jobs to be executed within the same minute allowing it to reuse the same backup filename. The backup filename does not contain seconds in timestamp and causes conflicts in the msdb tables LSN values especially for transaction log backups.
An attempt to restore the transaction log backup file will cause the following error:
RESTORE LOG is terminating abnormally.
The log in this backup set begins at LSN xxxxxxxxxxxxxxxx, which is too late to apply to the database. An earlier log backup that includes LSN yyyyyyyyyyyyyyyy can be restored.
The problem was multiple LiteSpeed files are created within the same minute with 'Overwrite' selected, the file is overwritten with the same name.Since the backup process was run multiple times, there are several rows in the msdb, with different first_lsn, last_lsn and checkpoint_lsn but only one backup file. If a restore were initiated on the full plus the only translog file, the LSN numbers are out of sync and the restore will fail.
Product defect.
WORKAROUND
Do not run the backup jobs within the same minute.
STATUS
Waiting fix for a future release of LiteSpeed for SQL Server.
