cancel
Showing results for 
Search instead for 
Did you mean: 

Transaction logs are not being truncated even though there is a job which should be doing this

KHAdmin1
Level 0

I run a full backup of all our SQL databases (they are not set to simple recovery mode), and then an incremental job which starts just after the full has finished and this is set to "Log - Backup and truncate transaction Log", this job runs weekly and yet the logs filled up the HDD and there was an error reported that they were not being truncated in another backup job.  How do I ensure this works reliably?  It is backup exec 16, I have had a similar issue with 2010 in the past and it seems there is the same problem.

2 REPLIES 2

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Look at te event logs on the SQL server to understand what is happening

pkh
Moderator
Moderator
   VIP    Certified

Truncating the logs will not decrease the disk space occupied by the log files. To decrease the size of the log files, you need to run the "dbcc shrinkfile" command separately.