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?
Sql-server – Transaction Log Backup Maintenance Plan and Newly Restored Databases
backupmaintenance-planssql serversql server 2014transaction-log
Related Question
- Sql-server – Maintenance Plan Job running at additional unscheduled times
- Sql-server – Automatic database restore fails as cannot find file
- Sql-server – Transaction log backups cleaning
- Sql-server – backup maintenance plan fails with error 0x80131534
- Sql-server – Text file report is not generating of Availability Databases other Databases during auto backup through maintenance plans in MS SQL Server 2012
- Sql-server – Are there differences between which AlwaysOn AG server (Primary or Secondary Replica) I store the backups and retention maintenance plans on
Best Answer
Check out Ola Hallengren's maintenance scripts. They have a
@ChangeBackupTypeparameter that lets you automatically escalate to fulls if necessary.