Andreas Jordan

Currently I can not reproduce this. I just had a look at the code: BackupDatabaseLSN is not used.

Does it return the correct script if you don't use -RestoreTime?

If you look at $ListBackupFile - the file is missing already there - correct?

Sorry for all the messages - I think I found the problem...

@saxet77 - Can you please verify that you get the correct result from `Get-DbaDbBackupHistory` if you add `-IncludeCopyOnly`, so using `$ListBackupFile = Get-DbaDbBackupHistory -SqlInstance Server1 -Database Database1 -last -IncludeCopyOnly`? @Stuart-Moore...

About your situation: The full backup finished after the log backup started, but before the log backup finished. That's why the missing log backup has a different DatabaseBackupLSN than the...

Yes, we have to fix Get-DbaDbBackupHistory. Your case (first log backup started before full finishes but finishes after full) is a rare case and thus has not seen in tests...

Can you add `-StopAfterGetBackupInformation -GetBackupInformation backupInformation` to the command? Then the variable `$backupInformation` is filled with the backups that would be restored. I would like to know if the "missing...

So here the $FilteredBackupHistory (that is what is in your $backupinformation) is still including the "missing log backup": https://github.com/sqlcollaborative/dbatools/blob/879021234ae8730f4550d75f1ee43397b6b673a7/functions/Restore-DbaDatabase.ps1#L705 `Test-DbaBackupInformation` is then building an internal `$DbHistory` which is passed to...

Can you please run the command that fails (edit: that writes the warning about the brocken chain) with `-Verbose` - maybe that output helps us.