Hello
I am not sure if someone else brought this up earlier, but I am surprised to see that this feature is still not available with Litespeed.
Backup escalation currently happens for Differential backups (where the maintenance plan is smart enough to know that the db is a newly created one and needs a full backup to be performed first before attempting a differential), but does not happen for T-Log backups. This is causing the T-Log backup jobs to fail each time a new database gets created because the new database lacks a current database backup. The job continues to fail until the full backup job kicks off.
Here is an example, we have Fast Compression Maintenance Plan (full/diff backups) scheduled every night at 8 PM, and T-Log backups scheduled every 15 minutes. If a new db gets created at 10 AM in the morning, the T-Log backup job starts to fail because there is not current full backup for the db. It will continue to fail every 15 minutes until the Full/Diff job kicks off later that night at 8 PM. This is really annoying where we have to go kick off a Full/Diff job manually to make sure there is a full backup generated for the newly created database. If we do not do that, the newly created database will not have a full backup until later that night. We are having a window where the db is missing backups. It would be nice to see an option to perform a full backup when the LS Maintenance plan see that there is no current full backup.
