what version of tssa are you using ?
We are using the BL version_8.9.03.162.
can you clarify what is being removed - is it the job run of a snapshot job that is older than 360 days, or the job object itself ?
and is this actually causing a problem that you can demonstrate ?
Yes - it is removing the job run of the snapshot job older than 360 days and not the Job object.
The issues is , we have snapshot job created for a server type and run the job to capture the status also update it to an Audit job. We did notice that Audit job fails sometime - on investigation we found that audit job is missing the snapshot thats being added, when we look for the snapshot job we can find them but, the run result is was getting removed as part of the BL cleanup script as its has 360 of retention in it.
So, we had to run the snapshot job again and add them to the Audit Jobs.
Hope this helps.
Found this mentioned in documentation: Marking data for deletion - Documentation for BMC Server Automation 8.9 - BMC Documentation
"You can set the number of days to retain the results of job runs before they are marked for deletion. BMC typically recommends a value of 30 days for this retention time. If the number of days is not set, the default value is 0, and job runs are not deleted."
So, options are to change RESULTS_RETENTION_TIME=0:
1. you can override it by changing the job property for snapshot job you want excluded from cleanup.
2. you can set it at Property Dictionary level for all Snapshot Job type.
But, remember once you have done this, you will need to delete old snapshot results manually.
I believe you are running into a know defect found in 8.9.02: DRBLG-119006 which is resolved in 8.9.04.001. i'd suggest opening a support case so they can confirm if this is the case or you have encountered a different problem.
Thanks Prabin , i have tried this approach.