Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Ageing SQL Transaction Logs

Ageing SQL Transaction Logs

Ageing SQL Transaction Logs


I have a large number of tapes still holding small amounts of 'Valid data' on them. These tapes are Primary copies which have an ageing of 28 day days, 4 cycles and these are then Auxiliary copied and stored offsite. The data ageing is having no problems ageing off all data apart from SQL transaction logs. There are tapes which have data on them long after the 28 days, 2 years in some cases! I have been a bit wary of pruning the contents until i got someones advice. I read in the CommVault online book that SQL Transaction Logs are not considered to be part of the CommVault backup/ageing process. So how would i be able to include them in any ageing or do I have to manually prune each month?



RE: Ageing SQL Transaction Logs

Have you run a Data Retention Forecast to check the "Reason for Not Aging"? It may help you narrow down the cause.

Also, it may be worth checking out Update 0683, as it contains fixes for problems that sound similar to the issue you are having:

-DataAging does not age Microsoft SQL Transaction log jobs if Data and Logs are going to different Storage Policies.

-DataAging may retain database log jobs on multiple copies with Log rule instead of only the copy with highest retention.

RE: Ageing SQL Transaction Logs


Thank you for your response. I ran the Data Retention Forecast Report and it comes back with REQ_BY_DATA for the tapes with Log files on them even though the data is two years old and has exceeded the normal ageing of 28 days - 4 cycles. Also the Log and Data Jobs are going to the same storage policy. The data is ageing off fine but the logs remain with a green tick saying it is still valid when it clearly isnt. How could I change the Log rule?


RE: Ageing SQL Transaction Logs

There is a "Prune SQL Logs Only By Days Retention Rule" option within the Media Management Control Panel applet, however, you will probably want to research it thoroughly before turning it on, but I believe it is what you are after.

Also, it may be worth ensuring that the logs files have been auxiliary copied elsewhere before pruning - just in case!

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close