Forum Discussion

mlutterloah's avatar
14 years ago
Solved

SQL Transaction Log Backups Failing

Every day at 5pm, my SQL transaction log backups are failing with the warning below. However starting at 7 am - 4pm, the same transaction log backups are running with no warnings. I will get this warining on all following trans backups until the transaction log backup with truncate later on in the night. Why would the job stop working at the same time every day?

 

Database is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.
 

  • The backup method selected in the backup job is "Back up transaction log - no truncate" which means that the logs will be backed up however it will not be marked for truncation. 

    And the warning "Database is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode." 

    will come for SQl backups if "Transaction logs" are not backed up with truncate option. This is to remind the user that they need to perform Transaction Logs backup with truncate option in order to maintain the log size. 

    You can refer to following technote for further details:

    http://www.symantec.com/docs/TECH126063 

  • The message you posted above is not an error but a warning message. Can you please check the job log and paste the error from the failed job log? Else you can attach the failed job log in your reply.

  • Looking at the job log it says that it Completed with exceptions. However, for this job I only have 3 databases set to backup the transaction log with no truncate and all three are showing that warning.

  • Please expand Job Operation Backup section in the job log and let us know what is the backup method selected for this job.

  • The backup method selected in the backup job is "Back up transaction log - no truncate" which means that the logs will be backed up however it will not be marked for truncation. 

    And the warning "Database is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode." 

    will come for SQl backups if "Transaction logs" are not backed up with truncate option. This is to remind the user that they need to perform Transaction Logs backup with truncate option in order to maintain the log size. 

    You can refer to following technote for further details:

    http://www.symantec.com/docs/TECH126063 

  • I understand that but why would all other previous transaction log backups for that day run without warning?

  • In the tech paper  http://www.symantec.com/docs/TECH126063   whi   

    which is mentioned above you will find the following about 1/4 of the way down.

     

    This exception is generated after 11 Full backups of SQL Databases, the 12th backup will display this error message.
     

    This one must be the 12th backup.