We are requesting the application-aware SQL Server transaction log backup schedule is made more sophisticated in line with the SQL Server Job scheduler or Windows task scheduler.
Instead of, say, 'every 15 minutes of every day' as present, it would be beneficial to us to have something like 'every 15 minutes of each weekday starting at 06:00 and finishing at 21:00'.
We have configured Veeam to undertake application-aware SQL Server transaction log backups every 15 minutes. We get occasional errors: "12/07/2017 21:15:37 :: SQL Server transaction log backup took longer than desired log backup interval" This was touched upon in the closed case #02198593 and the recommendation from Veeam was for us to increase the logging interval to 30 minutes rather than 15. The business managers are extremely reluctant to do this as it would expose us to greater risk of data loss if we could only roll forwards to potentially 30 minutes prior to an incident. They want to explore alternative solutions. Looking at the timing of the errors, they generally occur when the Veeam server is busy with other backup jobs on other servers and hence 'working hard'
A solution is sought whereby the transaction log backups could be scheduled in such a way that they didn't conflict with other out of hours Veeam jobs and it would probably overcome the need for us to increase the interval of the log backups.
See Case #02221008