• Mike Hinds (5/16/2013)


    2) Schedule the log backups at a slightly odd start time (i.e. 12:01:35) so they can not run (and will not be running) when either the Full or the Differential is running.

    3) Additionally, or as an alternative, to have the log backup job disable the log backup before the Full or Differential begins, and re-enable it when the Full or Differential is complete.

    The former won't achieve its intended result when you have a full backup that takes more than an hour and to be honest, there's no good reason to stagger backups like that. You can't run a full and a diff together, but log backups will run concurrently with full backups (since SQL 2005), which is great when you have a small data loss allowance and a long running full backup.

    I've had a scenario where the data loss allowance was 15 minutes and the full backup took 7 hours every week. Suspend the log backups while the full's running and I've got a scenario where I can have a disaster occur and lose 20x the data that's allowed for.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass