When we add a new database (restore from a staging instance) to our live instance we have a job which sets it to Full recovery (in case the tech forgot that) and then a maintenance plan that runs a Full backup each night. We also have a maintenance plan that runs a transaction log backup every 30 minutes. How do I stop the latter failing whilst we are waiting for the first Full backup to complete? I’m thinking I maybe cannot achieve this with maintenance plans but need a bespoke agent job?
1 Answer
Check out Ola Hallengren's maintenance scripts. They have a @ChangeBackupType
parameter that lets you automatically escalate to fulls if necessary.
msdb.dbo.backupset
. Now write a small TSQL to check if there is row for the database in the backupset table if it has do not do log backup. Yes it would not be possible from MP.