Jobs “roll off” the log files once jobs that run after fill a log. You can change the size of the log files, which allows them to hold more information, as well as increase the number of log files being retained. You can do this either from the Process Manager on the client:
https://documentation.commvault.com/11.24/expert/5554_setting_logging_parameters_in_process_manager_01.html
or from Additional Settings:
https://documentation.commvault.com/additionalsetting/?q=Log%20Files
One thing to note...this can cause issues with disk space if you tune these settings up too high and do not have the space to support it.
Hi @Orazan
I think what you shared might not be the case. In your provided link it creates another file… <the file is rolled over to an additional file: <filename>_1.log.>
If it rolls over and creates new file - it should still be available to view job logs? Problem is that when the job is aged (greyed out) and you click view job logs - it says no job logs available. So I presume it is something related to aging instead of rolling over?
@benjaminas , the setting you found should do the trick; just note it is only going forward. It won’t un-age the job history that is already purged.
The latter (view logs) are likely fore that exact reason. As logs roll over, those entries are no longer available.
As @Orazan mentioned, you can increase the size and iterations of each log file, but the space consumption will rise quite a bit as a result.