MS SQL Transaction Logs not expiring even though Retain Until time has passed

@tgladson  thanks for the question!

This is answered here:

Short version is that transaction logs don’t prune like other jobs, but the long version is pretty long (and detailed in that thread)!

Thanks @Mike Struening I’m not convinced yet that this is our problem. I’m doing some research to see if that is what we are seeing across multiple storage policies. I’ll reply with my findings. 

@tgladson run the Data Retention Forecast and Compliance report against the media or Copies where you see these jobs./  You’ll get a clearer picture of what is keeping them around.

Thanks @Ledoesp! This is very helpful! I am going to research that option.

I turned off the “Honor SQL Chaining for Full jobs on Selective copy” parameter. I will monitor to see if it did the trick. 

Just adding this for reference for other folks reading/searching the thread.
https://documentation.commvault.com/11.26/expert/11019_media_management_configuration_data_aging.html

 

Thanks, @Scott Reynolds! One more question: When this parameter is changed from 1 to 0, will Data Aging clean up all of the old log backups that have exceeded the original basic retention?

@tgladson 
Yes that is correct old backups will be valid for aging.