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

Question

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&nbsp;another backup job. &nbsp;How do I ensure this works reliably? &nbsp;It is backup exec 16, I have had a similar issue with 2010 in the past and it seems there is the same problem.

pkh · Answer

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.&nbsp;

colin_weaver · Answer

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

Forum Discussion

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

Related Content

mssql with transactions logs be truncated

Exchange DAG 2010 Transactional Logs Truncation

Transaction Log Truncate in passive node of DAG

NBU VSS not truncating Exchange 2010 SP1 Transaction Logs

SQL transaction log is not truncate