Full /Log Backups Don't seem to know what the other is doing

rick.sheeleyrick.sheeley Posts: 32
edited May 27, 2008 10:39PM in SQL Backup Previous Versions
In balancing the maintenance schedule of Full and Log backups for our SQL Servers, we have found that our Full backup will occasionally fail in the Truncate log step of the Full backup, due to the LOG backup running at or near the same time. Are we to assume, or should we always assume that the two backups do not communicate and should be scheduled independently of each other? I think we are assuming that the Redgate backups, like the prodcution SQL Backups, are "aware" of each other, and will not step on each other.

Cheers!
Eric (Rick) Sheeley, Sr. SQL/Oracle DBA
Sacramento, CA Cell: 602.540.6750
"Those are my principles, and if you don't like them... well, I have others." - Groucho Marx
· Share on Twitter

Comments

  • peteypetey Posts: 2,358 New member
    have found that our Full backup will occasionally fail in the Truncate log step of the Full backup
    Could you please clarify what you mean by the 'Truncate log step'? A full backup by itself does nothing to the transaction logs.

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
Sign In or Register to comment.