Feature request: Let transaction log backups honour schedule exceptions

[FrancWest]

In the job setting you can set a time frame the backup should not run. However, when you enable transaction log backups for a job that includes an SQL server, this exception window is not honoured by the transaction log backup job. It runs 24/7 on the interval you specify.

Since we perform automated databases maintenance on Saturday, we want to pause the transaction log backup during this maintenance window. For now this is only possible using a script and windows task scheduler, but that's not ideal, because you won't know if an error occurs when enabling the job again. Leaving the database server unprotected until we manually fix it.

It would be nice, if the transaction log backup honours the schedule setting you set on the job settings and stops doing transaction log backups during that time yo specify no backup should be taken.

[PetrM]

Hi Franc,

I think it's a bit risky because the regular backups prevent the transaction log from filling. Anyway, the request is noted!

Thanks!

[FrancWest]

Hi, yes, but that’s not what I mean. We schedule a backup 4 times a day starting at 0:00 with an interval of 6 hours (so 0:00, 06:00, 12:00, 18:00) and have set an exclusion in the schedule tab for Saturday night between 01:00 and 05:00. I would expect that transaction logs wouldn’t run during that time, but they do. What else is the use of setting an exclusion on the schedule button next to the ‘periodically ever’ option then, if nothing is done with it?

[FrancWest]

Or is it a bug that when you enable transaction log backups on a job it doesn’t take into account the schedule setting and runs 24/7 even when you specify the backup shouldn’t run at specific times when you choose to run the job every x hours?

[PetrM]

Hi Franc,

No, it's not a bug, this is the behavior by design. Anyway, the request is clear.

Thanks!