Solved

SIDBPrune.log and SIDBPhysicalDeletes.log activity

  • 21 April 2022
  • 1 reply
  • 317 views

Userlevel 2
Badge +9

Hi, 

I can see activity on those files on one of my Media Agent servers without a correspondent job on the Commcell console. 

 

 

 

Can someone explain to me how to “read” the lines above?

icon

Best answer by Sean Crifasi 21 April 2022, 19:25

View original

If you have a question or comment, please create a topic

1 reply

Userlevel 4
Badge +9

Hi @Eduardo Braga 

The sidbprune and sidbphysicaldeletes logs are not expected to correspond to specific jobs in the Commcell Console. What you are seeing is expected behavior and not cause for concern.

Below is a high level explanation of the data aging and pruning process.

- When a deduplicated job meets retention it is first marked as prunable in the database and can also be viewed in a Data Retention Forecast and Compliance Report.
- When a Data Aging job runs it logically deletes the jobs that are marked as ‘prunable’
- This deleted job is then added to a different table in the database for data that is to be deleted
- We then send batches of records at intervals through the deduplication database.
- This will check and determine which chunks of data no longer contain references for other jobs and if so will physically prune the corresponding chunk of data
- This physical pruning process is something that occurs in the backend without a corresponding jobid

Kind Regards,
Sean