As a result Disk Library is out space of now and the Customer has disabled schedules to not run any backup.
As a troubleshooting step we tried to delete some jobs assigned to sealed DDB.
AS you can see, there are over 20,000 jobs assigned to this DDB.
We deleted over 12,000 jobs.
Hovewer, Commvault is still showing the same number of jobs and no data has been pruned from DL.
Is any way to force Commvault to free some disk space removing data assigned to sealed DDB?
Rgds,
Kamil
Best answer by Kamil W
Hi Guys,
Please find the below information that I got after the remote session with the support.
Investigation: -----------------
Since the DDB reconstructions got failed, the previous DDB was Sealed. After which the jobs are not pruned from the Sealed DDB and space reclaim didn't happen.
Verified that no jobs are listed from the Sealed DDB.
Noticed that there are no pending prunable records on the Sealed DDB as below
Noticed there are 2 jobs not pruned from archjobOnStoreInfo table
JobID- 1010466 and 1012254
Ran ‘qoperation agedata -delbystoreid -sid 11’ followed by data aging once and confirmed that the jobs are pruned successfully.
Suggested to wait for some time to reclaim the space on the library.
“ Some scenarios will prevent micro pruning of the data in a DDB and will not reclaim any free space until all jobs are pruned. “ - this is exactly what I expected when the Customer called me.
Anyway, I will get back to the Customer with your answer and I’ll let you know how it goes ASAP.
The data size on the sealed DDB may not necessarily progressively change as it prunes. Additionally the DDB tabs do not dynamically update and you may not see a change until you close and reopen the Commcell Console or refresh with F5 on the DDB Engine level.
As Mike suggested, please check SIDBPhysicalDeletes and possibly SIDBPrune log as well for the Media Agent in question for the DDB partition. for a total size on disk of over 100tb this could take several hours or more to completely prune all data on the sealed store depending on the performance of the Media Agent.
Please find the below information that I got after the remote session with the support.
Investigation: -----------------
Since the DDB reconstructions got failed, the previous DDB was Sealed. After which the jobs are not pruned from the Sealed DDB and space reclaim didn't happen.
Verified that no jobs are listed from the Sealed DDB.
Noticed that there are no pending prunable records on the Sealed DDB as below
Noticed there are 2 jobs not pruned from archjobOnStoreInfo table
JobID- 1010466 and 1012254
Ran ‘qoperation agedata -delbystoreid -sid 11’ followed by data aging once and confirmed that the jobs are pruned successfully.
Suggested to wait for some time to reclaim the space on the library.
Are you receiving this error? We should spawn a separate thread to track your issue better. Can you confirm and provide some additional details? Where are you seeing this and when?
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.